You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the solution you'd like
The MIG will publish a Workflow Request event to inform the MWM that the results have been received and to continue. The MWM workflow initiation logic will need to be updated, if the message contains a valid workflowInstanceId then match with an existing workflow instance to carry on
New Workflow Request Schema
The text was updated successfully, but these errors were encountered:
@mocsharp@DanielNuttall-AD@neildsouth we need to agree on a schema for the update that differentiates normal export udpate messages from export message message (export)
Hi @JoeBatt1989, MIG will publish a Workflow Request message md.workflow.request with the existing workflowInstanceId instead of publishing an update message. Therefore, when WM sees a Workflow Request message with workflowInstanceId, it can resume that workflow instance. Please let me know if you find any issues with this design.
Describe the solution you'd like
The MIG will publish a Workflow Request event to inform the MWM that the results have been received and to continue. The MWM workflow initiation logic will need to be updated, if the message contains a valid
workflowInstanceId
then match with an existing workflow instance to carry onNew Workflow Request Schema
The text was updated successfully, but these errors were encountered: