WebPlatform Documentation

Linking a sub-process to your process

Things you need to be aware of when joining processes:

• Sub processes will only work properly if the Key Field is an exact match and any other mandatory context objects that are applicable to the sub process must match too
  • must exist in the parent process
  • If imported, the system does not automatically mark the context object as ‘Key Field’ – do it manually
• The process you want to use as a sub process must have a current version
  • otherwise it will not be selectable in the SubProcess ID dropdown box
• Parent/child relationship for Context Objects needs to be taken into consideration
  • If you have a sub-process with a transition on start, the transition context object also needs to be added to the main process.
    • This is very important if you want your process to work (validations are built-in to remind you)
  • Same applies to CO that have dependencies e.g. calculated data, concatenated values
    • All context objects involved in the set up must be imported first
• Another point to remember is Allocation rules – these to not carry over into or from a sub-process, so your first WorkItem needs to include your user context objects and an allocation trigger to ensure that the system knows who to allocate the subsequent WorkItems to.

Best Practice for Configuring Sub-Processes

• Drag the Sub-Process WorkItem into the designer
• Select the sub-process you want to link using the SubProcess ID dropdown box
• Check that the selected process name displays in the SubProcess ID field

• Execution Mode = SYNC (standard process)
• Select Data Fields to import
• The system will show you which context objects are mandatory, just Select & Save
• Connect your sub-process to the process WorkItems

• Rename your Sub-Process WorkItem
  • Best practice is the name of the Sub Process itself
• Save your work

How to import context objects

• Context objects can be easily imported from any process we want to use
  • Guaranteed 100% match for all imported context objects
• All you need to do is select the sub process shape and the respective subprocess from the list
• All context objects will load

• Mandatory context objects in the start form for the selected process will be marked as such
  • Just select the context objects you want to import
  • Dependants need to be selected before calculations/concatenations
• Click Save

• The imported context objects will be visible in the Custom Data Fields grid

Note: Key field will be imported but NOT automatically selected as key. This must be done manually by the designer

Execution Modes

The execution mode for a process is determined by the type of process.

For a standard process the available execution modes are:

• SYNC : The routing is synced meaning when the process gets to the sub process, in the parent process the shape stays active until the sub process completed.
• ASYNC:  When the process gets to the sub process in the parent, the sub process shows it has been completed even though there may be WorkItems still active inside the sub process
  • Thus allowing the parent process to flow without interruption and can complete
  • Active WorkItems in the async sub process will remain active until completed by the user

For Triage Wizards you can use detached mode

• Sub process is launched as a new standalone parent process with no link back to the parent process it started in.

What you need to get right