Pre-qualification Failed Response Event

Pre-Qualification Failed Response Event is sent by Pre-Qualification Failed Handler as a response to the failed feasibility or plan development step. Orchestrator receives the result and interprets the result accordingly. It is an asynchronous event to a JMS queue.

Event Type Asynchronous event
Queue or Topic Queue
Destination tibco.aff.orchestrator.provider.order.prequal.failed.reply

The event has the following property:

Property Type Cardinality Description
originator String Optional The value of the originator property in the Pre-QualificationFailedRequest message, received from the Orchestrator, which should be mapped and sent back in the response message.

The event has the following payload:

Pre-qualification Failed Response

Pre-qualification Failed Response.

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 to be able to correlate the response with the correct version of the submitted order. Populate this field the same as correlationID in the request message.
orderID String Required Internal unique identifier for the order that failed feasibility or plan development.
orderRef String Required External unique identifier for the order that failed feasibility or plan development.
withdraw Type Required, Choice Flag indicating that the order should be withdrawn.
retryFeasibility Type Required, Choice Flag indicating that the order should retry feasibility without any changes. This response may be made in cases where the request was for either feasibility or plan development failure.
retryOPD Type Required, Choice Flag indicating that the order should retry plan development without any changes. This response may be made in cases where the request was for plan development failure. Technically there is no restriction on doing so in the case of a feasibility failure, but functionally it does not make sense to do so.
orderRequest Type Required, Choice Order request type. See Appendix A for the specification of this type. This is provided in the case of an order resubmit.
message Type 0-M Message type. See Appendix A for the specification of this type. If populated, this list of messages will be returned in any Submit Order Response message occurring after the call to the PreQualification Failed Handler occurred.