Signature Step

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:

• Badge ID
• LDAP Username/Password: If an organization uses LDAP to authenticate users in Tulip, then a user must input their username and password from their LDAP directory.
• SAML Username/Password: If an organization uses SAML to authenticate users in Tulip, then a user must input their username and password from their SAML directory in a popup window.

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.

Fields

<table> <tr> <td><strong>Name</strong> </td> <td><strong>Description</strong> </td> </tr> <tr> <td>Submission Rules </td> <td>The types of users that can sign the Approval Step. Options: <ul> <li><strong>Any User:</strong> Any operator can add a signature.</li> <li><strong>Any operator besides app executor: </strong>Any operator can sign off EXCEPT the one that is currently logged in.</li> <li><strong> Operator executing app:</strong> Only allow the currently logged-in operator to add a signature.</li> <li><strong>Specify a list of allowed users: </strong>Choose from a list of all users and operators in a Tulip account. Multiple users allowed.</li> </ul> </td> </tr> <tr> <td>Approved Submitters (optional) </td> <td>A list of Tulip users that are approved to sign the app in the Player </td> </tr> <tr> <td>Signature Timestamp </td> <td>The timestamp is applied based on when the Tulip user signed the Signature Step before the app was completed </td> </tr> <tr> <td>Signer </td> <td>The full name, user ID and profile image of the user that signed the Signature Step before the app was completed </td> </tr> <tr> <td>Other </td> <td> <ul> <li>A required “Text” input widget can be used by the app developer to enforce signer to manually write reason for signature </li> <li>A “Dropdown” input widget with a list of options can be used to enforce signer to choose reason for signature </li> </ul> </td> </tr> </table>