Requesting user authentication/signature for a state transition

If there are regulatory requirements for some kind of "electronic/digital signature", or you only want to make sure, that really the logged in user has submitted a state transition (and not somebody else, that had access to an unattended computer where that user was currently logged in), you can associate the Validate the user signature (password) action with (critical) state transitions.


In order to use Validate the user signature (password), you first have to

• Add a new custom Signature field to the Approvals tracker and this field should be mandatory in the target status of the transition
• If regulations are even stricter and require two distinct identification components, for electronic signature, add an additional Signer field.

Please see the configuration examples.


E.g. Additionally secure the Accept transition of the Approvals tracker from the Forking sub-processes from processes (work items) example:

With all these configurations in place, upon execution of an Accept transition for the Approvals tracker, the additional Signature field will be shown and the user has to enter his/her password into this field in order to successfully submit (Save) the transition:




Or, if you have configured Signer and Signature (CB-7.7.0.1 and newer):




P.S.
There is a modified "WorkflowDemo" project template (WorkflowDemo.zip) attached to this wiki page, that allows to setup a Forking sub-processes from processes (work items) example plus the Signature/Authentication features described here.

For CB-7.7.0.1 and newer, there is also (WorkflowDemo3.zip), which shows the Signature/Authentication feature with two distinct identification components (Signer and Signature).