Codeunit 7580 "Onboarding Signal"

Base Application · System.Feedback · BC23-30 · source at ea08af5e · facts from BC29

Properties

Event subscriptions

• OnAfterDeleteCompany subscribes to Table “Company” OnAfterDeleteEvent

Procedures

• RegisterNewOnboardingSignal(CompanyName: Text[30]; OnboardingSignalType: Enum "Onboarding Signal Type"): Register a new Onboarding Signal to keep track of.
• CheckAndEmitOnboardingSignals(): Check the status on all registered onboarding signals, and emit corresponding Telemetry when the criteria is met. This is run automatically once a day when login.
• HasCompanyOnboarded(CompanyName: Text): Boolean: Check if a company has onboarded
• GetOnboardingSignals(var OnboardingSignalBuffer: Record "Onboarding Signal Buffer" temporary): Get all Onboarding Signals with Read access

Plus 2 local procedures.

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

• Codeunit 8711 “Telemetry” (2 calls: CheckAndEmitOnboardingSignals → LogMessage, RegisterNewOnboardingSignal → LogMessage)
• Codeunit 457 “Environment Information” (1 call: CheckAndEmitOnboardingSignals → IsSandbox)

Called by

• Codeunit 1351 “Telemetry Subscribers” (1 call: SendDailyTelemetry → CheckAndEmitOnboardingSignals)
• Codeunit 20373 “Register First Party Signals” (1 call: RegisterFirstPartySignals → RegisterNewOnboardingSignal)
• Codeunit 7581 “Company Signal” (1 call: IsOnboarded → HasCompanyOnboarded)
• Codeunit 7582 “Register Company Signal” (1 call: RegisterCompanySignal → RegisterNewOnboardingSignal)

Implemented by

• Codeunit 20370 “Customer Payment Signal”
• Codeunit 20371 “Purchase Invoice Signal”
• Codeunit 20374 “Sales Invoice Signal”
• Codeunit 20375 “Vendor Payment Signal”
• Codeunit 7581 “Company Signal”
• Enum 7580 “Onboarding Signal Type”

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "codeunit", object_name: "Onboarding Signal"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.