FIFO Error Elements
FifoError Element
The FifoError Type indicates the type of FIFO task that is being executed. At present, Async WorkFlow is the only type supported.
The table below lists the other FifoError elements:
| Type | Description |
|---|---|
| TaskId | A unique ID given to each FIFO task executed by the FIFO framework. |
| TaskQueueId | The queue where the FIFO task was executed. |
| TaskQueueKey | The key that was returned through the FIFO routing key business process execution. |
| ErrorMessage | This element contains the information that assists in determining the cause of the failure. |
WorkFlow Error Element
The table below lists the WorkFlow Error elements:
| Type | Description |
|---|---|
| WorkFlowId | This element contains the workflow id that was executed. |
| WorkFlowContextId | This element contains the workflow context id for the first step of the business process. This information is used to retrieve the workflow and extract additional data in advanced scenarios. |
| WorkFlowInitiator | This element contains the name of the workflow initiator. In most cases, name of the adapter that started the process will be the workflow initiator name. |
| PrimaryDocumentId | This element contains the ID for the primary document of the business process. |
FifoInitializationBPReport
This element contains metadata that describes the execution of the routing key initialization business process.
This is an optional node. It will be included both in process data of the executed business process and in the error queue XML. It is automatically included in the XML data if an error occurs during task initialization. To force the inclusion of this data, both in the error report and process data of the executed business process, ForceFifoInitializationDump to "true" in the routing key business process
The table below lists the initialization BP report elements:
| Type | Description |
|---|---|
| AdvancedStatus | This element contains the advanced status for the final step of this business process. |
| BasicStatus | This element contains the basic status for the final step of this business process. |
| PrimaryDocumentId | This element contains the primary document id at the last step of this business process. |
| ServiceName | This element contains the service name for the last step of this business process. |
| wfdName | This element contains the workflow definition name for this business process. |
| wfdVersion | This element contains the workflow definition version for this business process. |
| WorkFlowContextId | This element contains the workflow context id for this business process. |
| WorkFlowID | This element contains the workflow id for this business process. |
| StatusReport | This element contains the status report, if any, at the last step of this business process. |
| ProcessData | This element contains the process data at the last step of the business process. |
FifoErrorNode Element
When the routing key business process is executed, the business process author can optionally write additional metadata to the FifoErrorNode element in the process data. This element and all the child nodes will be included in the FifoError document as part of this element.
The routing key business process has access to all process data information passed onto it through the adapter. See the example below for additional information about generating an error node.
<process name=”AssignQueueKey">
<sequence>
<assign to=”FifoRoutingKey”
from=”DocToDOM(PrimaryDocument)/Order/@OrderId” />
<assign to=”FifoErrorNode/MSMQ/@QueueName” from=”string(MSMQ/@QueueName)”
append=”true”/>
</sequence>
</process>The additional information from the adapter can be included in the element to preserve the context of the error information in an easily identifiable manner.