BC Observatoryunofficial, made by waldo
tableextensionIntegration & APIsofficial - Microsoftderived - from the source, no model text

Table extension 6135 "EDocWorkflowStepArgumentArch"

EDocument · Microsoft.eServices.EDocument

Open in Claude6135.mdSource on GitHub

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 2 connected objects and pages

Table 1531 "Workflow Step Argument Archive" (relates to)Workflow Step Argument ArchiveTable 6103 "E-Document Service" (relates to)E-Document Service

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.

EDocument · Microsoft.eServices.EDocument · BC29-30 · source at ea08af5e · facts from BC29

Extends Workflow Step Argument Archive.

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No. Name Type Explanation Notes
6134 E-Document Service Code[20] — TableRelation Table 6103 “E-Document Service” (E-Document Service); DataClassification CustomerContent

Relations

Ask your agent

Procedure bodies are not stored here (D10). 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: "tableextension", object_name: "EDocWorkflowStepArgumentArch"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources