@uipath/maestro-builder-sdk 6.40.0 → 6.40.1

package/dist/bpmn/typed-node.d.ts

@@ -104,7 +104,29 @@ export interface RegistryTypeSpec {
     eventDefinition: string | null;
     /** True when authoring needs a tenant read (a connection, a process, a queue). */
     requiresDiscovery: boolean;
+    /**
+     * The registry's `IsDynamic`: a type whose fields the canvas discovers at design time.
+     * The CLI's merged-body required-field check (`validateMergedBodyFields`) skips exactly
+     * these, so for a dynamic type `check`'s EMPTY_REQUIRED_FIELD is the only gate on a
+     * missing required input (measured on uip 1.205: `A2A.AgentExecution` validates with
+     * one absent); every other merged-body type has its fields read inside the payload.
+     */
+    isDynamic?: boolean;
     bindingPattern: string;
+    /**
+     * The registry's `Placements`: where the canvas offers the type, by placement name
+     * (`Activity`, `StartEvent`, `IntermediateEvent`, `EndEvent`, …), with the BPMN
+     * element and, for an event, its definition. Kept as data; it is NOT an
+     * authorability signal — `{}` is what the case manager's internal nodes carry, but
+     * also `BPMN.ScriptTask`, `Intsvc.TimerTrigger`, `Maestro.AcquireLock` and
+     * `Maestro.NotificationService` (measured on uip 1.205), all of them authored. The
+     * internal set is `CASE_RUNTIME_INTERNAL_TYPES` (typed-node.ts). Absent on a spec that
+     * predates the field.
+     */
+    placements?: Record<string, {
+        element: string | null;
+        eventDefinition: string | null;
+    }>;
 }
 /** Every extension type in the snapshot, sorted. */
 export declare function registryTypeNames(): string[];
@@ -127,6 +149,17 @@ export declare function registryTypeNames(): string[];
  * typo, or no `uip` to ask.
  */
 export declare function registryType(type: string, inline?: RegistryTypeSpec): RegistryTypeSpec;
+/**
+ * The types the case-management runtime writes for itself when it materializes a
+ * case plan into an executable process: scheduler state (`decisions`, the current
+ * execution state, lock and cycle bookkeeping) that only the platform produces. The
+ * canvas offers none of them, and `check` warns on an authored one
+ * (TYPE_RUNTIME_INTERNAL). The ledger (`bpmn-coverage.json`) records each as
+ * `out-of-scope` under `docs/BPMN_BUSINESS_RULES_PLAN.md`; a test pins the two lists
+ * to each other. Not derivable from the spec: `placements: {}` is shared with
+ * authored types (see {@link RegistryTypeSpec.placements}).
+ */
+export declare const CASE_RUNTIME_INTERNAL_TYPES: ReadonlySet<string>;
 /** True when the snapshot itself carries the type — no tenant needed to emit it. */
 export declare function isSnapshotType(type: string): boolean;
 /**
@@ -458,36 +491,4 @@ export declare function missingRequiredInputs(type: string, inputs?: Record<stri
  * agree with the CLI instead of guessing on either side of it.
  */
 context?: Record<string, unknown>, inline?: RegistryTypeSpec): string[];
-/**
- * Whether this type's required payload fields are UNSATISFIABLE on the wire.
- *
- * A platform defect, recorded here because the SDK cannot emit its way around it.
- * `RequiredFieldsRule` builds its required-name set from `InputFields` and then
- * fires when a name is absent from the serialized rows **by name**. Under
- * `mergedBody` and `splitInputsItemData` every payload field collapses into ONE row
- * — named `body` or `ItemData` — so a required input field is never present by
- * name and the rule fires however the node is filled in:
- *
- *     [error] [call] EMPTY_REQUIRED_FIELD: The field 'agentUrl' in node 'call' is
- *                    required but has no value.
- *
- * Note the registry's own `XmlTemplate` for `A2A.AgentExecution` emits exactly the
- * body-only shape that fails, which is the clearest statement that the two halves
- * of the platform disagree rather than that the SDK is writing the wrong thing.
- *
- * Whether a workaround exists is per-type and not derivable from the spec, so it is
- * not encoded here. Measured: `A2A.AgentExecution` accepts redundant sibling rows
- * alongside the merged body (`Valid`); `Maestro.SendMessageEvent` refuses them
- * outright — `does not support input payload "Reference"` as a row, `does not
- * support context input "Reference"` in context, and `ItemData`'s `target="body"`
- * is enforced — so for that type NO artifact satisfies both gates.
- *
- * Selects exactly `A2A.AgentExecution` and `Maestro.SendMessageEvent` today. The
- * three other types with required payload fields are `separateInputs`, whose rows
- * DO carry their own names, and are unaffected.
- *
- * @param type - The extension type.
- * @returns The required payload field names that cannot be expressed, or `[]`.
- */
-export declare function unsatisfiableRequiredInputs(type: string, inline?: RegistryTypeSpec): string[];
 export {};

package/dist/bpmn/typed-node.js

@@ -41,6 +41,25 @@ export function registryType(type, inline) {
     }
     return spec;
 }
+/**
+ * The types the case-management runtime writes for itself when it materializes a
+ * case plan into an executable process: scheduler state (`decisions`, the current
+ * execution state, lock and cycle bookkeeping) that only the platform produces. The
+ * canvas offers none of them, and `check` warns on an authored one
+ * (TYPE_RUNTIME_INTERNAL). The ledger (`bpmn-coverage.json`) records each as
+ * `out-of-scope` under `docs/BPMN_BUSINESS_RULES_PLAN.md`; a test pins the two lists
+ * to each other. Not derivable from the spec: `placements: {}` is shared with
+ * authored types (see {@link RegistryTypeSpec.placements}).
+ */
+export const CASE_RUNTIME_INTERNAL_TYPES = new Set([
+    'Maestro.CaseCycleCommit',
+    'Maestro.CaseCyclePrepare',
+    'Maestro.CaseManagerGuardrails',
+    'Maestro.CaseManagerPlaceholder',
+    'Maestro.CaseRulesEvaluator',
+    'Maestro.RetrieveCaseState',
+    'Maestro.UpdateCaseState',
+]);
 /** True when the snapshot itself carries the type — no tenant needed to emit it. */
 export function isSnapshotType(type) {
     return Object.hasOwn(REGISTRY.types, type);
@@ -726,40 +745,3 @@ context = {}, inline) {
         (f.default ?? '') === '')
         .map((f) => f.name);
 }
-/**
- * Whether this type's required payload fields are UNSATISFIABLE on the wire.
- *
- * A platform defect, recorded here because the SDK cannot emit its way around it.
- * `RequiredFieldsRule` builds its required-name set from `InputFields` and then
- * fires when a name is absent from the serialized rows **by name**. Under
- * `mergedBody` and `splitInputsItemData` every payload field collapses into ONE row
- * — named `body` or `ItemData` — so a required input field is never present by
- * name and the rule fires however the node is filled in:
- *
- *     [error] [call] EMPTY_REQUIRED_FIELD: The field 'agentUrl' in node 'call' is
- *                    required but has no value.
- *
- * Note the registry's own `XmlTemplate` for `A2A.AgentExecution` emits exactly the
- * body-only shape that fails, which is the clearest statement that the two halves
- * of the platform disagree rather than that the SDK is writing the wrong thing.
- *
- * Whether a workaround exists is per-type and not derivable from the spec, so it is
- * not encoded here. Measured: `A2A.AgentExecution` accepts redundant sibling rows
- * alongside the merged body (`Valid`); `Maestro.SendMessageEvent` refuses them
- * outright — `does not support input payload "Reference"` as a row, `does not
- * support context input "Reference"` in context, and `ItemData`'s `target="body"`
- * is enforced — so for that type NO artifact satisfies both gates.
- *
- * Selects exactly `A2A.AgentExecution` and `Maestro.SendMessageEvent` today. The
- * three other types with required payload fields are `separateInputs`, whose rows
- * DO carry their own names, and are unaffected.
- *
- * @param type - The extension type.
- * @returns The required payload field names that cannot be expressed, or `[]`.
- */
-export function unsatisfiableRequiredInputs(type, inline) {
-    const spec = registryType(type, inline);
-    if (spec.inputPattern !== 'mergedBody' && spec.inputPattern !== 'splitInputsItemData')
-        return [];
-    return spec.inputs.filter((f) => f.required).map((f) => f.name);
-}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uipath/maestro-builder-sdk",
-  "version": "6.40.0",
+  "version": "6.40.1",
   "description": "Build UiPath Flow, Case, and BPMN artifacts by writing TypeScript.",
   "license": "MIT",
   "homepage": "https://docs.uipath.com/maestro",
@@ -93,5 +93,5 @@
     "@types/node": "^22.7.0",
     "esbuild": "^0.28.1"
   },
-  "gitref": "b3dd153cbf30937f6caf22ae3ad103d6ea678cb1"
+  "gitref": "416f96b5db0e4bbfd59f19f8bd548f138a4a6918"
 }