Once the fulfiller’s internal system has processed the purchase order, it creates the response. In this example, a Purchase Order Acceptance (POA) is created and the pub.estd.rosettaNet:processDocument service is called to convert the document into RNO format. The internal system always includes the original ConversationID in response documents so that the Process Engine can associate the document with the right conversation.

Process Engine searches for a running conversation (or process instance) where a Wait for Internal POA step is waiting for a POA and has a matching ConversationID. When Process Engine finds the correct conversation (or process), it rejoins the POA with the existing conversation. If Process Engine receives a POA, but cannot find the matching conversation, Process Engine ignores the POA.

On the initiator’s side again, the pub.estd.rosettaNet:receive service recognizes the document, creates a BizDocEnvelope, and sends the BizDocEnvelope to Process Engine. Process Engine searches for a running conversation (or process instance) where a Wait for POA step is waiting for a POA with a matching ConversationID. When Process Engine finds the correct conversation (or process), it sends the POA to rejoin the existing conversation. The initiator’s custom service then converts the document response into the internal system’s format.