Every transaction and document that is exchanged through RosettaNet Module is known as a conversation and is assigned a unique ConversationID . Process Engine uses the ConversationID to monitor the progress of the “conversation” and the relationship of the PIP documents to each other. When a conversation starts, Process Engine chooses the appropriate process model to use and applies it to the conversation. Process Engine can run multiple instances of the same process model at one time. Each instance is a different conversation that Process Engine distinguishes by the unique ConversationID.

When Process Engine receives a document, it determines if the document belongs to an existing conversation by verifying whether the document has the same ConversationID as a running instance of a process model. A document enters your internal system, when the Send to Back-End step in the process model is triggered and Trading Networks submits the document to your internal system (the back-end). When this occurs, Process Engine sends information to the internal system, including the ConversationID.

For the conversation to continue properly, your internal system must keep track of the ConversationID and include it in the business document and all the responses that it returns. This means that, at design time, you must configure your internal system to maintain ConversationIDs when it receives business documents from the RosettaNet Module solution.