Approvals

The Approval with e-Signature plugin (com.glide.e_signature_approvals) allows users to approve requests by re-entering their login credentials.

Approve or reject an approval record by re-entering your login credentials. See the history of an approval from its activity stream or its audit history.

The differences in the way that companies handle their approvals, as well as the differences between approvals for the various applications (such as Service Catalog Requests and Change Management), calls for supporting flexibility in setting up approvals within applications.

Many organizations rely on an approval process to ensure that requests are reasonable and fit an organization's budget.

The approval status of a change request is determined by looking at the current status of all the approvers.

When you are looking at an approval request, the form has a context-appropriate summary of the item to be approved.

A gating approval acts as a gate through which a request must pass before it can start.

The system can automatically generate an approval request to individuals or groups when specific criteria are met. The automatic generation of approval requests is driven using the System Policy feature.

It is possible to manually add approvers to a request.

Workflow Studio flows are a powerful and flexible method of generating approvals. Use workflow flows to create group approvals and user approvals.

With multiple approvers, all approvers must authorize the request before the status will change to "Approved".

Once a request has passed its gating approvals, any relevant execution plans are initiated.

Individuals who are designated approvers automatically receive approval notifications, including approval status updates.

In the diagram below of a hypothetical approval process, the gating approval is color coded blue and an in-process approval is orange.

In addition to adding approvals via approval rules, you can also add approvals based on what kind of item is being ordered.

Approval summarizers are stored in the Macro [sys_ui_macro] table.

Embed an interactive approval request for service catalog requests in the email notification sent to a user. The user can accept or reject the approval request from the email client.

Scripts, assignment rules, business rules, workflows, escalations, and engines all take effect in relation to a database operation, such as insert or update. In many cases, the order of these events is important.

Classic approvals are records that store the authorization tasks that must be done to approve or reject a request. Approval records are typically created by a Workflow Studio flow or classic workflow. An approval defines both the approval tasks and the users or groups are assigned to approve or reject them.

The approval summarizer formatter creates the summary at the bottom of an approval form.

Use this procedure to de-activate e-signatures.

Installing approval with e-signature installs certain properties.

Approval rules can automatically set the approval state to something other than Not yet requested. As a result, an approval rule can create a set of approvers. You can also start the approval process by setting the approval state to Requested.

An SSO approval with e-signature requires configuration on the SAML IdP and the ServiceNow instance.

You can modify existing approval summaries to include additional information.

After you add a new table that has approvals to an instance, you can add a custom activity formatter by creating a new UI macro and then add it to the appropriate form.

Process guides work similarly to approval rules in that their execution is controlled via a condition.

By default, activating the Approval with E-signature plugin enables e-signature for all tables for which an approval exists.

You can set up a gating approval via an approval rule.

To manage the approvals for each of the Task tables in the system, set up an approval engine.

Enable users to authorize e-signature approvals using local database credentials.