Using the Signoff Flow
Sign-offs are used to indicate that a Task has been done. For example, a mechanic might complete a Task and the supervisor may need to sign-off later. On Task execution, the user with the appropriate Role Access can sign-off, indicating the completion of the Task.
You can select roles to generate the Signoff for a particular Task. The selected Signoff Roles are displayed with their Roles, Description and Identifier.
![]() |
In the example below, the Battery Functionality Task is being executed by a mechanic. There are two Task Steps namely Battery Check and Battery Details. Each of these Task Steps have two sub-steps.
![]() |
The sub-steps 1.1, 2.1 and 2.2 are marked as required Steps. Let us consider, the mechanic has not answered the required sub-step 1.1 and has marked the Task as done. Now, the Supervisor clicks the Sign the Flow 1 button to approve the executed Task.
![]() |
A warning dialog is displayed.
![]() |
The Sign it button is disabled.
On clicking , the Task cannot be completed dialog is displayed. Sign-off cannot be completed unless the required Steps are answered.
![]() |
Once the required Steps are answered, the Sign it option will be enabled.
![]() |
In the example below, a user with the Role Author has Signed the Task Step Battery Check. The Sign the Flow 1 button is enabled, indicating the Task Step can now be signed off.
![]() |
Similarly, you cannot mark the Task as done without answering the required Steps. Let us consider, the supervisor has not answered the required Steps and clicks the Stop Task button as shown below.
![]() |
The Stopping Task dialog is displayed.
![]() |
On clicking, Complete & Mark Task as done, the Task cannot be completed dialog is displayed.
![]() |
The required sub-steps 2.1 and 2.2 should be answered to complete the Task.
You can pause a Task if the required Steps are unanswered or if the Signoff is incomplete, by clicking the Pause Task button.
![]() |
The Task is Paused.
![]() |