TransactionResponse
objectThe unique identifier for the created transaction
>= 1 characters
The case identifier returned by the product service
Answers keyed by blueprint question id or composite collection field id. Named properties below are representative examples (same keys as the default example); any other field id is valid and uses the same value shape (see additionalProperties → QuestionDataRows → QuestionData). Each array entry is one row; use index for repeatable collection instances.
Example:{"259726":[{"id":"259726","type":"dropdown","questionText":"Account designation","questionSubText":"Account designation","displayValue":"Owner","value":"Owner","index":0}],"486958":[{"id":"486958","type":"date","questionText":"Date of birth","questionSubText":"","displayValue":"1989-10-13","value":"1989-10-13","index":0}],"488043":[{"id":"488043","type":"radio","questionText":"Gender","questionSubText":"","displayValue":"Male","value":"Male","index":0}],"489353_FirstName_Main":[{"id":"489353_FirstName_Main","type":"text","questionText":"First Name","questionSubText":"","displayValue":"John","value":"John","index":0}],"489353_LastName_Main":[{"id":"489353_LastName_Main","type":"text","questionText":"Last Name","questionSubText":"","displayValue":"Doe","value":"Doe","index":0}]}
Show Child Parameters
Show Child Parameters
Reactive subscriber definitions consumed by the UI. Each subscriber declares trigger fields, an HTTP action to run on change, and a response handler. Two flavors are emitted: dataset-dependency (context-modification) and blueprint-modification (replace-whole).
Example:{"triggers":["FirstName"],"actions":[{"type":"http","verb":"get","url":"/market-connect/order-entry/v1/transaction/1125715/MCDPS","token":"OEToken","payload":{"type":"none"},"responseHandlers":[{"type":"blueprint-modification","action":"replace-whole","value":{"type":"response-query","kind":"json-path","value":"$.data"}}]}]}
Show Child Parameters
Collection of errors if the operation failed
Example:{"code":"VALIDATION_ERROR","description":"Input validation failed","details":"One or more input fields are invalid","timestamp":"2024-01-15T10:30:00.000Z"}
Show Child Parameters
One validation message in API shape. Optional properties are omitted in JSON when null (e.g. fieldId is missing or 0).
Example:{"fieldId":"BeneficiaryAddress","answerNodeId":"Transaction.PrimaryOwner.PersonName.Prefix","message":"First name is required","sectionName":"EntityOwners"}
Show Child Parameters
UpdateTransactionRequest
objectTransaction update request. The data property matches TransactionResponse.data (field id → QuestionDataRows → QuestionData, with index for collection rows). Each field value must be a JSON array of rows. Every QuestionData object must include a value property (JSON null is permitted for an empty optional answer).
Answers keyed by blueprint question id or composite collection field id. Named properties below are representative examples (same keys as the default example); any other field id is valid and uses the same value shape (see additionalProperties → QuestionDataRows → QuestionData). Each array entry is one row; use index for repeatable collection instances.
Example:{"259726":[{"id":"259726","type":"dropdown","questionText":"Account designation","questionSubText":"Account designation","displayValue":"Owner","value":"Owner","index":0}],"486958":[{"id":"486958","type":"date","questionText":"Date of birth","questionSubText":"","displayValue":"1989-10-13","value":"1989-10-13","index":0}],"488043":[{"id":"488043","type":"radio","questionText":"Gender","questionSubText":"","displayValue":"Male","value":"Male","index":0}],"489353_FirstName_Main":[{"id":"489353_FirstName_Main","type":"text","questionText":"First Name","questionSubText":"","displayValue":"John","value":"John","index":0}],"489353_LastName_Main":[{"id":"489353_LastName_Main","type":"text","questionText":"Last Name","questionSubText":"","displayValue":"Doe","value":"Doe","index":0}]}
Show Child Parameters
ValidationCondition
objectSingle validation condition inside a FieldValidationRule. The shape varies by type: matchesRegexCondition uses regex; numberComparisonCondition uses value + operator; characterCountInBetween uses value: { minLength, maxLength }.
The kind of validation this condition performs.
Allowed values:matchesRegexConditionnumberComparisonConditioncharacterCountInBetween
Example:matchesRegexCondition
The answer node identifier this condition evaluates.
Example:Transaction.Beneficiaries[0].EmailAddresses["Home"].Address
Regex pattern. Only used when type is matchesRegexCondition.
Example:^\w+([-+.']\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*$
Comparison operator. Only used when type is numberComparisonCondition.
Allowed values:lessThanlessThanOrEqualgreaterThangreaterThanOrEqualequalnotEqual
Example:lessThan
Any OfCondition-specific value. Number for numberComparisonCondition; object { minLength, maxLength } for characterCountInBetween. Absent for matchesRegexCondition.
Example:9999999999
ValidationConditionGroup
objectThe boolean operator used to combine multiple conditions (e.g., “and”). Omitted when there is only one condition.
Single validation condition inside a FieldValidationRule. The shape varies by type: matchesRegexCondition uses regex; numberComparisonCondition uses value + operator; characterCountInBetween uses value: { minLength, maxLength }.
Show Child Parameters
ValidationErrors
objectOne validation message in API shape. Optional properties are omitted in JSON when null (e.g. fieldId is missing or 0).
ControlID as a string (numeric ids appear quoted). Omitted when fieldId is 0.
Answer node path from annuity NamedItem; matches FieldBlueprint.AnswerNodeId.
The validation error message
The section/step name where the error occurred