Description:

The SendMessagesToProcess step belongs to the Engine category in FlowWright. Its XML definition identifies the step as sendmessagestoprocess, with the label "Send messages to specific process instance" and the display name "Send Msgs to process." The step is used to communicate a message to a specific FlowWright process instance.

The step is defined as a Process step with two input connections and two output connections. The step provides two required properties:

• Messages to send – specifies the message content.
• Enter process instance ID – specifies the process instance that should receive the message.

Both properties are defined as string values and are required by the step definition.

The XML definition does not expose additional recipient-selection options such as Current, All, Parents, Children, Siblings, or Top Most. Instead, the receiving process instance is explicitly identified through the Enter process instance ID property.

Typical uses include:

• Sending messages between specific process instances.
• Communicating information from one workflow instance to another.
• Triggering message-based coordination between process instances.
• Passing workflow-related information to a known process instance.
• Coordinating activities between independently running process instances.
• Notifying a specific process instance when an operation has completed.
• Sending status or business-event messages to another workflow instance.

Prerequisite:

Let’s assume the process below is executed with a new process instance ID 2f07d550-f77d-43c2-8a34-c96b5a55b3de. This process instance is shown as Sleeping in the WaitForMessage step.  

Usage:

The SendMessagesToProcess step is typically placed in a workflow when one process instance needs to communicate information to another specific process instance.

During execution:

1. Configure the required Messages to send property.
2. Specify the process instance ID of the receiving process.
3. Execute the step.
4. Continue workflow processing through the True or False path according to the operation result.

Both input properties must be configured because the XML definition marks them as required.

A typical workflow might look like:

Typical workflow suggestions:

• Process-to-process notification - Use the step after an important operation to notify another running process instance that an event has occurred.
• Approval coordination - A workflow handling an approval can send an approval result to another process instance that is waiting for that information.
• Process synchronization - Use the step when independently running process instances need to exchange status information as part of a larger business process.
• Parent/child process coordination - When a workflow knows the process instance ID of another related workflow, the step can be used to communicate information between the two instances.
• Status notification - Send a status such as COMPLETED, REJECTED, or another business-specific message to a specific process instance.
• Event-driven workflow coordination - Use the step after an operation that produces an event requiring another process instance to take action.

Example:

Let’s build and execute the “sendMessagesToProcessDef” example.

• Create a new definition called “sendMessagesToProcessDef” and open the definition in designer mode. 
• Drag the “sendMessagesToProcess” step to the canvas
• Connect the dots between the “Start” and “sendMessagesToProcessDef” steps, as shown above. 
• Click the "sendMessagesToProcess" step to configure its "Required" properties. Provide a name for the step, the text message to send, and the “WaitForMessage” process instance GUID value as shown in the example. Click the Save button. Note: Click the "AI Predict" button for the Copilot to add new process steps that match your process description. 

• The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. This is achieved by configuring the step state and percent fields individually, as shown in the images below. Configure the “Logging” using the following properties.

• Save the process definition, create a new instance, and then execute it. The SendMessageToProcess step sends messages to the other process, and the “WaitForMessage” step determines whether to continue the workflow execution. When rendered, the process instance appears as shown below.

Tips:

• Always configure Messages to send because it is a required property.
• Always provide a valid process instance ID because the receiving process is explicitly identified by this value.
• Use clear, meaningful message content so that the purpose of the communication is easy to understand.
• Verify that the process instance ID identifies the intended receiving process instance.
• Place the step after the workflow operation that produces the information being communicated.
• Use the True path to continue the normal workflow when the operation succeeds.
• Use the False path for appropriate error or exception handling.
• Test the workflow with the intended receiving process instance before deploying it.
• When coordinating multiple process instances, ensure that the target instance is available and that the message content is appropriate for the receiving workflow.
• Do not assume that the step provides the broader recipient-selection behavior documented for other message steps. This step accepts a specific process instance ID as its destination.

Notes:

• Category: Engine.
• Internal name: sendmessagestoprocess.
• Label: Send messages to specific process instance.
• Display name: Send Msgs to process.
• Namespace: FlowWright.Workflow.SendMessagesToProcess.
• DLL: FlowWright.Workflow.dll.
• Step definition type: Process.
• Input connections: 2.
• Output connections: 2.
• Messages to send: Required.
• Enter process instance ID: Required.
• Messages to send: String data type.
• Enter process instance ID: String data type.
• String properties: Supplied by FlowWright.DataTypes.ClsTextBox.
• Execution paths: True and False.
• Result Variable/Global property: Not exposed by the XML definition.
• Connection-string, timeout, transaction, retry, or scheduling properties: Not exposed by the XML definition.
• Detailed message-delivery behavior: Not exposed by the XML definition.

Comparison with SendMessageToSlack:

The SendMessagesToProcess and SendMessageToSlack steps both send textual messages, but they are intended for different communication targets.

The SendMessagesToProcess XML requires both the message and process instance ID.

The SendMessageToSlack definition instead provides Message to send and Channel to send to as its two string properties. Its XML identifies the step as belonging to the Slack category.

The practical distinction is therefore:

• Use SendMessagesToProcess when the recipient is another FlowWright process instance.
• Use SendMessageToSlack when the recipient is a Slack channel.

Definition Sample:

You may provide a sample process definition for the SendMessagesToProcess step and import it by drag-and-drop into the FlowWright Process Definition (XML file) page.

After importing the sample, verify and complete any environment-specific configuration, particularly:

• Messages to send
• Enter process instance ID
• Connections to the surrounding workflow steps
• True and False execution paths
• The target process instance used for testing

After verifying the configuration, save the Process Definition before executing the workflow.

Click here to download the sample file.