Configure Connections

Multiple processes within a process group must be connected to define the relationship between the processes. Connection types define how the processes are related to each other in a visibility scenario.

Prerequisites

You have atleast one process group configured with more than one process. For more information, see Configure Process Groups.

Context

A visibility scenario can consist of heterogeneous processes from different process providers or it can contain events from various objects in SAP S/4HANA. You can connect the processes within the process group by defining the connection types between them and map the attributes between these processes. For more information, see Configure Process Groups and Map Attributes.

The following Connection Types are supported to connect the processes within a process group:

1:1: Defines a 1:1 relationship between the processes of a visibility scenario. For example, consider an employee onboarding process in SAP Success Factors that is triggered for a new hire. This process triggers an extension workflow on SAP BTP for equipment provisioning. A 1:1 connection exists between the processes as each new hire procures an equipment.
N:1: Defines an N:1 relationship between the processes of a visibility scenario. For example, consider a scenario having an order and a delivery process where multiple orders are part of the same delivery. There exists an N:1 connection between the processes as multiple orders can be associated with a single delivery.
1:N: Defines a 1:N relationship between the processes of visibility scenarios in a project. For example, consider a scenario where a process is modeled to initiate multiple approval processes dynamically based on the number of mandatory approvers. In such cases, it is important to keep track of the primary process and monitor the progress of the approval processes that it generates. For more information on enabling 1:N connection, see Configure Group Connections (1:N).

Procedure

In the Process Groups tab, select the required process group from the list and choose  Edit Process Group.

Note

To incude processes that are not related (non-correlated processes) within the visibility scenario, see Configure Non-Correlated Processes.
In the Edit Process Group dialog box, you can change the name for the process group and choose the processes that you want to group together.
If you have more than one process within the process group, you need to connect the processes by defining the connection between the processes.
Choose Next Step.
In the Configure Connections section, choose the Source Process and the Target Process and the type of connection from the Connection Type from the dropdown list.

Choose the Source Context and Target Context attributes from the drop down list.

The supported operators based on the correlation between the processes are listed in the following table:

Operator	Example
=	1:1 connection In an employee onboarding scenario, the onboarded user ID can be used to define the connection. `SFSF.UserID = OnboardingExtensionWF.UserID` N:1 connection In a scenario having an order and a delivery process that has multiple orders as part of the same delivery, the order process includes the details of the delivery. `Order.DeliveryID = Delivery.ID`
IN	N:1 connection The delivery process includes the details of all orders that will be delivered with each delivery. `Order.OrderID IN Delivery.OrderIDs` In this example, the `OrderIDs` is the context attribute that contains an array of IDs. For example, `Order.OrderId = 15, and the Delivery.OrderIds = [15,16,18]`.

Operator

Example

1:1 connection

In an employee onboarding scenario, the onboarded user ID can be used to define the connection.

SFSF.UserID = OnboardingExtensionWF.UserID

N:1 connection

In a scenario having an order and a delivery process that has multiple orders as part of the same delivery, the order process includes the details of the delivery.

Order.DeliveryID = Delivery.ID

N:1 connection

The delivery process includes the details of all orders that will be delivered with each delivery.

Order.OrderID IN Delivery.OrderIDs

In this example, the OrderIDs is the context attribute that contains an array of IDs.

For example, Order.OrderId = 15, and the Delivery.OrderIds = [15,16,18].

Repeat Step 5 to create more connections for the processes with the process group.
Choose Create.
The process group is created and listed under the Process Groups section.
Tip
- You can edit a process group by choosing  Edit Process Group.
- To delete a process group, choose  Delete Process Group.
Choose Save and Deploy the visibility scenario.
Note
Ensure that you follow these guidelines when defining a process group:
- Avoid cyclic dependencies between the connections.
- A process can be a target process in only one connection.
- A process can be part of only one Process Group.
- Each process group creates a scenario instance that represents an end-to-end process based on the processes in the group.
  
  The first process in a group serves as the process participant whose event starts the scenario instance for that group. You derive this initial participant from the defined connections. This participant isn't set as a target participant in any of the connections within the group. You can define only one such process participant in a group.