---
sourceDocument: Australia Build workflows
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/build-workflows

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Approve with a process guide

# Approve with a process guide {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Process guides work similarly to approval rules in that their execution is controlled
via a condition.
Important:  
Classic approval rules have been replaced by the Workflow Studio [Ask for Approval action](https://servicenow-prod.fluidtopics.net/b_wb~rFm82ytUgYBbHM2nA "Request approval for a record. Configure a set of rules to automatically approve, reject, or cancel an approval request without having to write script. Add a due date to automatically approve, reject, or cancel when a decision has not been made by a designated time."). Use Workflow Studio to create workflow-driven approval logic that is easier to maintain and provides better reporting information.

## Before you begin

Role required: none

## About this task

The default version of approval tasks allows you to specify that the approval in question be approved by:

1. One or more specific people
2. One or more groups of people
{#t_ProcessGuideApprovals__ol_obw_k34_rp}  
You can optionally use Process Guides instead of approval tasks. Process guides are more flexible in that they allow for:

1. "Any of" or "All of" approvals
2. Sequenced approvals
{#t_ProcessGuideApprovals__ol_arx_l34_rp}

You can link a process guide to a execution task.

## Procedure

1. From the left navigation pane, select System PolicyProcess Guides.
2. Create a new guide.
3. Set the table to Catalog task.
4. Fill in a condition under which this guide should attach.  
   Example #1: Apply to all "Capacity Review" tasks. ![Capacity]()  
   Example #2: Apply to all "Capacity Review" tasks where there requester is in Atlanta. ![Capacity Atlanta]()  
   Process guide tips and tricks:
   1. All catalog tasks are generated when a request is first submitted, but tasks which aren't active yet have a state of "pending". So if you do not want to send out approval requests until a task has actually started, add "state=open" as part of your condition.
   2. There is a "Default" process guide in the system for catalog tasks with a sequence number of 10,000. It behaves exactly the same way the old, pre-process guide code did in regards to approvals. Approvals are based on the execution of task-related lists.
   {#t_ProcessGuideApprovals__ol_wsg_cj4_rp}

*[\>]: and then