What to do: |
|
![]() |
To use parallel review processes, it is necessary to assign a minimum
of two different tasks to a single transition step. In order to perform
a state change, all assigned tasks must be carried out. To work through this example, you must have completed the example Create a Lifecycle with Transition Steps. |
![]() |
Select |
![]() |
Search the lifecycle | .
![]() |
On the 120 | In Approval to 220 | Approved. | tab select the transition step
![]() |
To change to edit mode click ![]() |
It is also possible to click the | button to define a parallel review process on the mask.|
![]() |
In the | column tick the checkbox.
![]() |
In the Electronic Check. | column enter
![]() |
To save the entry click ![]() |
![]() |
Insert a new transition step from state 120 | In Approval to 220 | Approved. |
![]() |
Repeat the steps 3 to 5 and enter Mechanical Check in the column. |
![]() |
In the 1000 | Manager Group. | column select
![]() |
To save the entry click ![]() |
The transition step 120 | In Approval to 220
| Approved now comprises two parallel review tasks.![]() |
|
![]() |
For all items that are subject to the lifecycle DOCU-Example, a transition step from state 120 | In Approval to 220 | Approved can only be performed, if all parallel tasks assigned to this transition step are carried out. |
![]() |
If an item fails a test or a test cannot be performed, the item will remain in state 120 | In Approval unless the state is reset manually to 110 | In Work. If a state is reset, all of the performed tasks within a parallel block will be reset automatically, as well. |
When changing the state of an item from 120 | In
Approval to 220 | Approved, the parallel
tasks defined for this transition step will be displayed in a message window.![]() |