Configuring Outbound Communication

Call a Second iFlow.

1. From the Routing options in the top menu bar, choose Multicast → Parallel Multicast to connect the process step to its predecessor.

   

2. To create your first execution branch, navigate to Persistence → Data Store Operations → Write.

   

3. Position the element following the Multicast. Connect both. You will see an indication of the branch ("Branch 1") through the applied connector.

   

4. Set the name of the Write step as Write SOAP Message into Data Store.

   

5. Switch to Processing. Enter SOAPPurchaseOrder as the name and PurchaseOrder_4500000011as Entry ID. Select Encrypt Stored Message, Overwrite Existing Message, and Include Message Headers.

   

6. Add an End Message event via Events.

   

7. Connect it with the first branch.

   

8. You might notice. that at the top far left of the Integration Process pool box, an error indicator displays. Hovering over this will give you more information about what needs to be done. Highlight the Integration Process pool box to access its configuration menu. Move to the Processing tab and set the Transaction Handling to Not Required.

   Note

   It may happen, that this error displays, when you have performed step 1e of the next task.

   

Persist your Message.

1. To create a second branch, choose Call → External Call → Request Reply.

   

2. Connect this process step with the Multicast and End Message. Set the Name in the configuration view as Run additional iflow.

   

3. Add an additional Receiver via the Participant menu.

   

4. Connect the Receiver and run additional iFlow process steps via the ProcessDirect adapter. You will continue to edit this second branch in the upcoming lesson.

   

5. Choose Save to secure your progress.

   Note

   It may happen, that an error displays. See the explanation at step 1h of the first task.

   Note

   Instead of integrating another iFlow -as this was done here for demonstration purposes- it is also possible to configure the process steps directly in the main iFlow branch.

6. Navigate back to your main iFlow and access the editor.

7. Highlight the ProcessDirect connector to access the configuration view (if not already the case, it is expandable via the bottom right of the screen). Choose the Connection tab. Choose Edit on the top right of the screen.

   

8. You will now enter the path to your Slack notification iFlow. As this iFlow does not exist yet, it does not have a name or path yet. You will choose a name for the iFlow now that will be used later – thus, you are creating the future path of the iFlow once it is actually configured. If you are following the naming conventions of the examples, the correct path will be /PO_scenario/PO_Slack, otherwise /your_package_name/your_iflow_name.

   

9. Choose Save to secure your progress.