Feasibility Response
Feasibility Response is an event sent by Feasibility Provider back to the Orchestrator in response to a Feasibility Request event. It is a reply event to a JMS/REST.
The response for feasibility has
completed and
passed flags. Orchestrator routes the order lifecycle based on the returned value of these flags. The two flags can be used to distinguish between technical and business exceptions. For example, a failure to complete generally indicates a technical exception, so complete is
false
. A validation failure indicates a business exception, where complete is
true
, but passed is
false
.
Completed | This flag indicates whether the feasibility call completed. If this is set to
true , the passed flag becomes relevant.
|
Passed | This flag indicates whether the order has passed feasibility. |
Based on different scenarios, these flags must be set as follows:
Completed | Passed | Description | |
Technical Error | False
|
False True
|
Orchestrator refers the order to the Pre-Qualification Failed Handler if error handling is enabled for feasibility, or the error is withdrawn if error handling is not enabled. |
Business Error | True
|
False
|
Orchestrator refers the order to the Pre-Qualification Failed Handler if error handling is enabled for feasibility, or the error is withdrawn if error handling is not enabled. |
Success | True
|
True
|
The processing continues as normal. |
Event Type | Reply event |
Queue or Topic | Queue |
Destination | tibco.aff.orchestrator.provider.order.feasibility.reply
|
The event has the following property:
Property | Type | Cardinality | Description |
---|---|---|---|
originator | String | Optional | The value of the originator property in the FeasibilityRequest message, received from the Orchestrator, which must be mapped and sent back in the response message. |
The event has the following payload:
The following table lists the details of the elements.
Element | Type | Cardinality | Description |
---|---|---|---|
businessTransactionID | String | Optional | Unique identifier for tracing purposes across function calls. |
correlationID | String | Required | Unique identifier to correlate the request message with a response message. Even though this field is marked as optional in the response schema, it is required for Orchestrator can correlate the response with the correct version of the submitted order. Populate this field the same as correlationID in the request message. |
resultStatus | Type | Required |
Result status type. See Schema References for the specification of this type. |
orderID | String | Required | Order ID for the order that was feasibility checked. |
orderRef | String | Required | Order ref for the order that was feasibility checked. |
completed | Boolean | Required | Flag indicating whether the feasibility call completed. |
passed | Boolean | Required | Flag indicating whether the order has passed feasibility. |
message | Type | 0-M | Message type. See Schema References for the specification of this type. This list of messages is passed to the Pre-Qualification Failed Handler if invoked. |