The BPE retrieves the response business document from its synchronous inbound queue.
The BPE executes the fixed inbound flow. The first step of fixed inbound flow is protocol un-packaging. The BPE iterates through configured handlers, including any user defined handlers, until it finds a handler that can manage the document. It executes un-packaging as needed.
The second step of fixed inbound flow is protocol processing. The BPE iterates through configured handlers, including any user defined handlers, until it finds a handler that can manage the document. It executes protocol processing. The handler checks if the BCG_RESPONSE_URL is null. If the value is null, but the handler has received a response document, then the handler sets GET_SYNC_RESPONSE to 'false' and BCG_SYNC_RESP to null. Otherwise it continues through the rest of the fixed inbound processing steps.
The BPE executes the configured action, which may be WBI-C supplied, a user-modified version of a WBI-C supplied action, or an entirely new action defined by the user. Steps in user-modified or new actions can be user defined. No constants concerning sync status need to be updated during variable workflow processing.
The BPE executes the fixed outbound flow. The first step of fixed outbound flow is protocol packaging. The BPE iterates through configured handlers, including any user defined handlers, until it finds a handler that can manage the document. It executes protocol packaging. No constants concerning sync status need to be updated during fixed outbound workflow processing.
After the successful execution of all workflow steps, the BPE checks the SYNC_RESP attribute on the response document. The response business document is written into the Delivery Manager's synchronous inbound queue.
The Sync Delivery Manager sends the response to the RESPONSE_URL set in the response business document. The Sync Engine retrieves the persisted original connection. The Receiver Framework populates a response object (from a class that implements ReceiverDocumentInterface) with the synchronous response information.
The receiver reads the RESPONSE_STATUS attribute and sends the status code and the sync response back to the initiating partner on the original connection.