BC Observatoryunofficial, made by waldo
codeunitAL Developmentofficial - Microsoftderived - from the source, no model text

Codeunit 1804 "Approval Workflow Setup Mgt."

Base Application · System.Automation

Open in Claude1804.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 3 connected objects and pages

Codeunit 1502 "Workflow Setup" (calls, 20 links)Workflow SetupCodeunit 1520 "Workflow Event Handling" (calls, 9 links)Workflow Event HandlingCodeunit 1521 "Workflow Response Handling" (calls, 6 links)Workflow Response Handling

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

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

Procedures

  • ApplyInitialWizardUserInput(TempApprovalWorkflowWizard: Record "Approval Workflow Wizard" temporary)
  • ApplyCustomerWizardUserInput(TempApprovalWorkflowWizard: Record "Approval Workflow Wizard" temporary)
  • ApplyItemWizardUserInput(TempApprovalWorkflowWizard: Record "Approval Workflow Wizard" temporary)
  • ApplyPaymantJrnlWizardUserInput(TempApprovalWorkflowWizard: Record "Approval Workflow Wizard" temporary)
  • CreateApprovalSetup(TempApprovalWorkflowWizard: Record "Approval Workflow Wizard" temporary)
  • CreateGenJnlLineApprovalWorkflow(var GenJournalLine: Record "Gen. Journal Line"; ApproverId: Code[50]): Code[20]
  • CreateSalesDocumentApprovalWorkflow(DocumentType: Option): Code[20]
  • CreatePurchaseDocumentApprovalWorkflow(DocumentType: Option): Code[20]
  • FindWorkflowStepArgument(var WorkflowStepArgument: Record "Workflow Step Argument"; WorkflowCode: Code[50]; FunctionName: Code[128]): Boolean

Plus 13 local procedures.

Triggers

OnRun

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 1502 “Workflow Setup” (20 calls: ApplyCustomerWizardUserInput → BuildCustomerTypeConditions, ApplyCustomerWizardUserInput → CustomerCreditLimitChangeApprovalWorkflowCode, ApplyCustomerWizardUserInput → CustomerWorkflowCode, …)
  • Codeunit 1520 “Workflow Event Handling” (9 calls: ApplyCustomerWizardUserInput → RunWorkflowOnCancelCustomerApprovalRequestCode, ApplyCustomerWizardUserInput → RunWorkflowOnCustomerChangedCode, ApplyCustomerWizardUserInput → RunWorkflowOnSendCustomerForApprovalCode, …)
  • Codeunit 1521 “Workflow Response Handling” (6 calls: ChangeWorkflowStepArgument → CreateApprovalRequestsCode, CreateCustomerOrItemApprovalWorkflow → CreateApprovalRequestsCode, CreateCustomerOrItemApprovalWorkflow → SendApprovalRequestForApprovalCode, …)

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: "Approval Workflow Setup Mgt."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources