Approving a Task with Signature Requirement

Your system might be configured so that you must provide a signature when you approve a task. You only need to provide a signature for tasks that have a Route Base Purpose of Approval. Tasks that have a purpose of Review or Standard do not require signatures, and offer the ability to enter a comment.

Required access roles: All

Before you begin: From any of these locations, select the task and click , , , or to approve a task:
  • Lifecycle Tasks/Signatures or Approvals tab of the Lifecycle category
  • Tasks category
  • Properties for the task
  1. Select Approve.

    If you choose Reject or Abstain, you do not need to provide a signature. You must enter a comment to explain why you rejected the task or abstained from approving it.

    On premises only: Your administrator can configure the app to require a signature when you approve, reject, abstain, or complete a task.

  2. Enter your user name and password.
  3. Read the statement. The statement declares that your approval in this dialog box is equivalent to your handwritten signature. If the task was assigned to an access role, the statement declares that you are approving the task in the capacity of that access role.
  4. Select the check box.
  5. If appropriate, enter a comment.

    On premises only: Your Business Administrator can configure your system so that the Comment field does not display when approving tasks.
    On premises only: By default, the Comments field is mandatory. Your Business Administrator can configure your system so that the Comments field is optional.

  6. Click Done.

The statement shown in this dialog box is added to the history for the task as a permanent record of your signature.