Using TN conversation ID as PRT custom ID

What’s the trick to using the TN conversation ID as the custom process ID so that the conversation ID shows up in Monitor?



If the conv ID is same for the next set of document coming into TN, then modeler wouldn’t initiate the start of a new instance of a Business Process but would use the process which was initiated by the document arrived prior to the current other words, it would join the running process.
It is not mandatory to use the TN conv ID as the process ID, but you can use a custom ID also.
just my 2 cents.