Multiple Workflow Selection

In case of multiple workflow selection, two processes are selected and these processes are executed consecutively.

All out-of-box workflows that are used in multiple workflow selection scenarios have been modeled into sync-subflows. With these changes, multiple workflow selection behavior has been modeled as follows:

  • The selection of the second process (P2) is initiated by the first process (P1) as a synchronous subflow.
  • Once the second process (P2) completes, it returns control to the invoking process (P1) which sets the event status to Success (or error) and completes its execution.
  • A SubFlowFlag parameter is passed from the first process to the second process, and this parameter ensures that the second process (P2) does not update any event status.

The following workflows (multiple process selection) are applicable for GDSN only (if you have the GDSN plug-in installed).

GDSN Out-of-the-box Workflows Modified for Multiple Process Selection
Feature Workflow/Process 1 Workflow/Process 2
1Sync 
wfout1sync62cic26v1
 
wfin26prodnotifbasicv3
CIM2CIM 
wfoutveloselcin26v2
 
wfin26prodnotifretailerv4
wfin26prodnotifprocessv2
WWRE 
wfoutagentrics50cin26v2
 
wfin26prodnotifretailerv4
wfin26prodnotifprocessv2
wfin26prodnotifv2
wfin26prodnotifbasicv3
wfin26rfcinv2
Note: The table denotes those out-of-box workflows that have been modified for multiple process selection - this is usually in case of 1Sync, CIM2CIM, and WWRE.

For example, for CIM2CIM, the first process wfoutveloselcin26v2 is a workflow to translate the incoming CIM2CIM message to mlXML format. The second process called is either wfin26prodnotifretailerv4 or wfin26prodnotifprocessv2, both of which are workflows to process incoming record messages and save data - except that wfin26prodnotifretailerv4 is a variation targeted towards integration hubs.