SubmitTransactionResponse
objectThe unique identifier for the submitted transaction. Echoed back from the request.
>= 1 characters
Human-readable confirmation that the submit request was accepted.
>= 1 characters
Subscriber
objectNamedItem identifiers of the form fields whose value change fires this subscriber.
Optional conditions that must hold for the subscriber to execute. Omitted when not used.
Actions executed when any of the triggers fire. Each action declares an HTTP call plus one or more response handlers.
Example:{"type":"http","verb":"get","url":"/market-connect/order-entry/v1/transaction/1064727","token":"OEToken","payload":{"type":"none"},"responseHandlers":[{"type":"blueprint-modification","action":"replace-whole","value":{"type":"response-query","kind":"json-path","value":"$.data"}}]}
Show Child Parameters
SubscriberAction
objectThe action transport. Currently always “http”.
HTTP verb to use (e.g., “get”, “post”).
Relative URL of the OE endpoint to call when the trigger fires. Three shapes are emitted: ‘/market-connect/order-entry/v1/dataset’ (dataset refresh); ‘/market-connect/order-entry/v1/transaction/{transactionId}/{stepName}’ (multi-step blueprint refresh); ‘/market-connect/order-entry/v1/transaction/{transactionId}’ (single/enhanced blueprint refresh).
Bearer-token alias forwarded by the UI on the call. Always “OEToken” today.
Request payload envelope. Use type “none” when no body is required.
Example:{"type":"basic","payload":{"transactionId":"1125715","stepName":"MCDPS","fieldId":"531783"}}
Show Child Parameters
One or more handlers that apply the upstream response back to the form.
Example:{"type":"blueprint-modification","action":"replace-whole","value":{"type":"response-query","kind":"json-path","value":"$.data"}}
Show Child Parameters
SubscriberActionPayload
objectPayload kind. “basic” includes a key/value map in the “payload” field; “none” omits the body.
Inner payload key/value map. Omitted from the JSON envelope when type is “none”.
SubscriberResponseHandler
objectHandler kind. “context-modification” updates a context namespace; “blueprint-modification” applies the response to the rendered blueprint.
Action to perform within the chosen handler kind. Examples: “update-namespace”, “replace-whole”.
Namespace to update for context-modification handlers. Omitted for handler types that do not use a namespace.
How to extract the value to apply from the upstream response.
Example:{"type":"response-query","kind":"json-path","value":"$.data"}