You can group a logical set of task flow windows into a sub process, which can then be used by several top level processes. This simplifies process modelling. Each sub process can contain other sub processes. There are two rules to note regarding sub processes:
A sub process cannot be defined as runnable.
When you use a sub process in another process, you must connect the sub process to the Top Node window.
Enter a unique internal and display name for the new process for the HR Task flow item type.
Suggestion: Use a naming convention for Internal and Display names. For example, a good Internal name might be ASSIGNMENT_DETAILS_SL with a Display name of Assignment Details (Sub Level)
Define the process as NOT runnable.
Specify a user defined result set as a Process Result Type if the sub process requires more than one result value.
Open the Process Diagrammer window and add one Start activity and at least one End activity
Because a process can have more than one result value, many End activities may be required. At least one End activity is required to indicate that the process must connect back to the Top Level node window.
Connect the Start activity to another window.
Note: The Start activity can connect to one window only.
Add other windows to the process, noting the following rules:
A window can only connect to another window where the result type is the same (such as, both Person Context windows).
The transition result value must be the name of the window activity you are connecting to (for example, F4 Enter Assignment).
Each window can only connect once to any other window.
Each window must connect to an End Activity with a <Default> transition result value.
You can connect a window back to its parent using the <Parent> transition result value, rather than the name of the parent window.