Navigation:  Admin Panel > Processes > Process Steps > Sub-process step >

Sub process settings

Previous pageReturn to chapter overviewNext page

In this section, a process can be selected to be part of the main process. When that is done, all fields of all steps in the sub-process appear and each field can be automatically filled with values from a main process step or be left blank.

There are three parts to this section.

Sub process settings

This is where the process is selected to be used in the main process. To view the selected process details an edit button is available next to the drop-down.

SubprocessDetails1

SubprocessDetails2

 

Available sub process form fields

Here all fields from the steps appear. Each field in each step in the sub-process can be automatically filled with values from the main process. For example in the above example, the first step in the sub-process is an approval step. If the approval in the sub-process is the same as the approval from the main process (for example both require the line manager's approval but it doesn't make sense to have the manager approve the request twice) then the sub-process approval step can be automatically filled and submitted from the main process. The decision field will match the decision of the approver from the main process approval step, and the comments will match the comments from the same approval step in the main process.

Or the third field is "Group name" which is a free text field. Again, the value of this field can be defined from the main process or can be left blank and the actor of step "Pick actor" will fill in the required information.

Available sub process form fields

In the second set of fields all other information can be defined from the main process. For example, in the above example, the first such information is Email (Email approvers) / this field appears in Step "test" and also as a condition in the decision step "test DP". If the actor of step "test" needs to be defined from the main process, this can be done by matching that field to an actor definable from the main process. Otherwise, if left blank, the actor will be defined from the sub-process.

The other field in this section from our example is Name(addorremove). The Context explains that this field appear several times in the Step Information (otherwise known as Translation) of the step "Approval from Tim". This can also be defined from the main process or if left blank, the original definition will be used.

End of sub-process

When the sub-process is completed, the main process continues. All steps of the sub-process are also shown as part of the main process. To the end user it is not obvious that several processes have been used to handle a ticket.