Set up a gating approval via an approval rule You canset up a gating approval via an approval rule. Before you beginRole required: admin Procedure From the left navigation pane, select System Policy > Approval Rules. Click New. Table 1. Approval rules Field Description Name Name of this rule. Table Task table to which this rule applies. For most service catalog approvals, select Request.Note: The list shows only tables and database views that are in the same scope as the approval rule. Active Indicator of whether the rule is active (defaults to true). Run Rule Before Indicator of whether the rule runs before or after the request record is saved. For most approvals, select this check box. User User who must approve this request (can be empty). Group Group that must approve this request (can be empty). Set State Value of the approval field on the task in after this rule runs. In most cases, select Requested. Condition Condition under which the rule applies. Script An optional server script to programmatically specify who the approver should be. For example, for the one-line script current.requested_for.manager, ServiceNow checks the requested_for reference field on the current record. It then locates the manager field on the referenced record and assigns that person as the approver. For other examples, see the Script field on approval rules provided by ServiceNow. Notes and limitations: You can have as many rules as you want on a given table. If more than one rule applies, you'll get more than one approver. You can't get duplicate approvers, for example, if two rules both want Fred Luddy to approve a particular request, the system will only create one approval entry for him. By default all requests start out in a Not yet requested approval state. Approval notifications will not go out until the request's approval state is set to Requested. You can do that manually, or you can do it in script, but the easiest way to do it is to use the Set State field to automatically set the request to Requested.