A Signature Step (Signature Form) is a variant of a Form Step that allows users to add an e-signature within an app running in the Tulip Player.
An e-signature can be:
An operator cannot proceed to the next step of an app until a qualified user has filled out the e-signature. The signatures cannot be autofilled- they must be signed via the permitted credentials each time they are presented.
An app builder can add one or multiple Signature Steps to an app.
Each E-signature from a Signature Step is recorded in a separate column in the list of Completions.
Name | Description |
Submission Rules | The types of users that can sign the Approval Step.
Options:
|
Approved Submitters (optional) | A list of Tulip users that are approved to sign the app in the Player |
Signature Timestamp | The timestamp is applied based on when the Tulip user signed the Signature Step before the app was completed |
Signer | The full name, user ID and profile image of the user that signed the Signature Step before the app was completed |
Other |
|
ID | Name |
---|---|
QA-T106 | Signature Step : 01 - A signature form can be created |
QA-T107 | Signature Step : 02 - Signature widgets cannot be deleted from a signature form step and additional ones cannot be created |
QA-T108 | Signature Step : 03 - Signature form should allow any user to submit it when configured so |
QA-T109 | Signature Step : 04 - Signature form should allow only the current user to submit it when configured so |
QA-T110 | Signature Step : 05 - Signature forms should only be submittable a single time per process run |
ID | Requirement |
---|---|
PLAT-8893 (815) | Provide an unalterable and enduring link between records and their associated electronic signatures; they cannot be removed, changed, copied, transferred or deleted. |