Does anyone know if this issue is affecting the execution of process models? We ran into the issue yesterday with TN and have applied the fix (on 6.0.1 platform w/ SQL Server), but now our process models won’t execute (wm.ip.cm:processDocument). They were working without issue prior to this. (TN still seems to recognize the document and extracts the sender and receiver):
Error Message:
Error: No matching conversation script.
wm.ip.cm:getConversationScript
Any ideas?
Thanks,
Ben