Configuration of Send Message Event and Receive Message Event within Process model

Question

Send Message Event: 
 In the Setup tab, for 'Message Destination', select the Receive Message Event that is in the Process Model where you need to send the message. To do this, search for the process model and select your Receive Message Event. 
 In Data tab, ' DestinationProcessID' is the ID of the process instance of the Process Model to which you need to send the message. Click on "New Mapping" and name it. Configure the 'type' based on your need. The 'value' should be your process variable which holds the message(data) to be sent.

Receive Message Event: 
 In the Setup tab , for 'Receive Message', select 'Process to Process'. 
 In Data tab, click on 'Import Custom Properties', search for the Process Model where you have the Send Message Event, and select your Send Message Event. 'Value' will be automatically set. Then store it in the desired process variable. 
 My Use Case: 
 In Process Model A , I call an integration to perform my desired job. When starting that integration, I pass the Process Instance ID because I need this ID to send a message back from Process Model B. After the integration node in Process Model A, there is a Receive Message Event where the process waits. 
 After the job completes, it triggers a Web API to start Process Model B , passing both the job output and the Process Instance ID that was sent earlier. In Process Model B, I use this Process Instance ID as the DestinationProcessID in the Send Message Event. Additionally, I configured Import Custom Properties to pass the job's output data back to Process Model A. 
 Process Model A waits at the Receive Message Event until it receives the message from Process Model B. Once the message is received, Process Model A completes the process. 
 
 This configuration enables process-to-process communication using message events and Process Instance IDs to pass data between process models. This enables efficient coordination between long-running integrations and targeted message delivery.

Shubham Aware · Accepted Answer

Your configuration is correct.
Send Message Event: Uses DestinationProcessID set to Process Model A’s instance Id so the message is delivered to the correct process instance.
Receive Message Event: Is configured to receive from that Send Message Event and uses imported custom properties to map the incoming data into Model A’s process variables.

Tejas Sugandharaju · Answer

Good question! In my use case, I have a long-running integration that takes significant time to complete. 
 Without process messaging, the process would stay active and wait, consuming resources and potentially timing out. 
 With process messaging, the process moves to a wait state and frees up resources. When the external job completes, it triggers a Web API that sends the results back to the exact waiting process instance using the Process Instance ID. 
 This approach is more efficient for handling long-running external operations without blocking the process thread.

Mike Schmitt · Answer

Tejas Sugandharaju said: After the job completes, it triggers a Web API that starts Process Model B. 
 ... in other words, starting a new process. 
 The way you describe here will work, of course, but your original stated request indicated you would rather free up resources utilized by leaving a process running for a long time. The approach Stefan and I have both described would accomplish this. The new process would re-query the needed info from the DB, but this would be a very trivial cost compared to leaving the original process running for a long time.

Configuration of Send Message Event and Receive Message Event within Process model

Top Replies