tableAL Developmentofficial - Microsoftderived - from the source, no model text

Table 130415 "Semi-Manual Test Wizard"

Base Application · System.TestTools

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-30unchanged

Neighbourhood 2 connected objects and pages

Page 130415 "Semi-Manual Test Wizard" (pages and codeunits on it)Semi-Manual Test WizardCodeunit 4100 "Temp Blob" (calls, 4 links)Temp Blob

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.TestTools · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Semi-Manual Test Wizard
DataClassification CustomerContent

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
1 Codeunit number Integer —
2 Codeunit name Text[250] —
3 Step number Integer —
4 Step heading Text[250] —
5 Manual detailed steps BLOB —
6 Total steps Integer —
7 Skip current step Boolean —

Keys

  • Key1: Codeunit name (clustered)

Procedures

  • Initialize(CodeunitId: Integer; CodeunitName: Text[250])
  • SetManualSteps(Steps: Text)
  • GetManualSteps(): Text

Pages and codeunits on this table

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 4100 “Temp Blob” (4 calls: GetManualSteps → CreateInStream, GetManualSteps → FromRecord, SetManualSteps → CreateOutStream, …)

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: "table", object_name: "Semi-Manual Test Wizard"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources