Contents Now Platform Capabilities Previous Topic Next Topic Approve with a process guide Subscribe Log in to subscribe to topics and get notified when content changes. ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Share Approve with a process guide Process guides work similarly to approval rules in that their execution is controlled via a condition. About this task The default version of approval tasks allows you to specify that the approval in question be approved by: One or more specific people One or more groups of people You can optionally use Process Guides instead of approval tasks. Process guides are more flexible in that they allow for: "Any of" or "All of" approvals Sequenced approvals You can link a process guide to an execution task. Procedure From the left navigation pane, select System Policy > Process Guides. Create a new guide. Set the table to Catalog task. Fill in a condition under which this guide should attach. Example #1: Apply to all "Capacity Review" tasks. Example #2: Apply to all "Capacity Review" tasks where the requester is in Atlanta. Process guide tips and tricks: All catalog tasks are generated when a request is first submitted, but tasks which are not active yet have a state of "pending." So if you do not want to send out approval requests until a task has started, add "state=open" as part of your condition. There is a "Default" process guide in the system for catalog tasks with a sequence number of 10,000. It behaves the same way the old, pre-process guide code did regarding approvals. Approvals are based on the execution of task-related lists. On this page Send Feedback Previous Topic Next Topic
Approve with a process guide Process guides work similarly to approval rules in that their execution is controlled via a condition. About this task The default version of approval tasks allows you to specify that the approval in question be approved by: One or more specific people One or more groups of people You can optionally use Process Guides instead of approval tasks. Process guides are more flexible in that they allow for: "Any of" or "All of" approvals Sequenced approvals You can link a process guide to an execution task. Procedure From the left navigation pane, select System Policy > Process Guides. Create a new guide. Set the table to Catalog task. Fill in a condition under which this guide should attach. Example #1: Apply to all "Capacity Review" tasks. Example #2: Apply to all "Capacity Review" tasks where the requester is in Atlanta. Process guide tips and tricks: All catalog tasks are generated when a request is first submitted, but tasks which are not active yet have a state of "pending." So if you do not want to send out approval requests until a task has started, add "state=open" as part of your condition. There is a "Default" process guide in the system for catalog tasks with a sequence number of 10,000. It behaves the same way the old, pre-process guide code did regarding approvals. Approvals are based on the execution of task-related lists.
Approve with a process guide Process guides work similarly to approval rules in that their execution is controlled via a condition. About this task The default version of approval tasks allows you to specify that the approval in question be approved by: One or more specific people One or more groups of people You can optionally use Process Guides instead of approval tasks. Process guides are more flexible in that they allow for: "Any of" or "All of" approvals Sequenced approvals You can link a process guide to an execution task. Procedure From the left navigation pane, select System Policy > Process Guides. Create a new guide. Set the table to Catalog task. Fill in a condition under which this guide should attach. Example #1: Apply to all "Capacity Review" tasks. Example #2: Apply to all "Capacity Review" tasks where the requester is in Atlanta. Process guide tips and tricks: All catalog tasks are generated when a request is first submitted, but tasks which are not active yet have a state of "pending." So if you do not want to send out approval requests until a task has started, add "state=open" as part of your condition. There is a "Default" process guide in the system for catalog tasks with a sequence number of 10,000. It behaves the same way the old, pre-process guide code did regarding approvals. Approvals are based on the execution of task-related lists.
