---
title: "Approval Templates Table"
canonical: "https://help.agiloft.com/space/SDA2603/521281233/Approval+Templates+Table"
format: markdown
---
The Approval Templates table holds records that define the steps in [Approval Workflows](https://agiloft-public.atlassian.net/wiki/spaces/SDA2603/pages/521278808). Each template is one step. In the out-of-the-box system, Approval Templates are used in Contract, Sourcing Event, and Supplier Profile approvals. Approval Templates define the following attributes of the step:

- Which type of approval process the step is for: Contract, Sourcing Event, or Supplier Profile
- Whether it's a required step or needed only under certain conditions
- The order the step appears in the approval workflow
- If it's for contracts, the type of approval required: standard approval, review, or notification only
- The assigned approvers

Each Approval Template can only be used by a single Approval Workflow record.

# Use Case

Approval Template records are usually created from the Approval Templates related table in an Approval Workflow record. It's a best practice to create Approval Templates from Approval Workflows so the template is automatically linked to the workflow. If you create an Approval Template directly from the Approval Templates table, you must manually select the Workflow Title to link the template to. By default, members of the admin, Admin Import, and Business Admin groups can create and modify Approval Templates. 

![Approval Workflow record showing All Approval Templates](media://c86cbaff-0048-4a14-b85d-02556a537b2a)

Each Approval Template record contains information about the Approval Workflow that uses it as well as the details described in the sections below.

![New Approval Template record created from an Approval Workflow record](media://26201124-dc1d-48c2-8f42-82d2fcc5497f)

### Defining the Template Type

The Related To field defines the type of approval the step relates to. In the out-of-the-box system, the choices are Contracts, Sourcing Events, or Supplier Profile. Choosing the related type changes the layout of the form to show fields that are relevant for that type. 

![Choices for the Related To field in an Approval Template](media://53d5df06-b315-4e93-bdf4-7ccf6cdb74cb)

### Defining the Approval Type for Contracts

If the template is related to Contracts, the Approval Type field is available. This field allows you to select the type of approval that is needed for the step: Approval, Notification, or Review.

![Approval Type choices on an Approval Template record](media://06784f90-d329-4482-ae0c-ea2f6b7ea448)

When set to Approval, the approver can either approve, require changes, or reject the contract. When set to Notification, the assigned user is notified via email about the approval, but no action is required on their part. The Review option allows the assigned approver to require changes to the contract, but they can't reject the contract.

### Requiring or Conditionalizing a Template

All Approval Template records include the Approval Usage field, which defines when to include the step in the workflow, always or only when certain conditions are met. Setting the field to Required means the step is always included in the workflow. Setting the field to Conditional presents the Condition field where you can define the conditions under which the step should be included in the workflow.

Condition is a formula field that gets evaluated before an Approval record is generated. For example, you can define a condition that includes the approval step only if the contract value exceeds a certain amount or the contract is auto-renewing. If the condition is not met, an Approval record is not generated for the parent record and the step isn't included in the workflow.

Typically, the Condition field contains search criteria based on field values in the parent records. The field can contain any number of formulas using operators such as OR, AND, and CONTAINS. For information about defining formulas, see [Formulas](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43715029). For example, the following settings conditionalize the template so this step is only included in the workflow if the Contract Amount is more than $10,000.

![Formula in the Condition field](media://65de301d-50df-4a52-aa36-ae0d14fed676)

> 📝 In the example, note that the formula uses `latest_contract_id` rather than `contract_id` to link to contracts. This is necessary because multiple contracts may share approval templates, and template conditions aren't evaluated until you trigger approval creation from a specific contract. When you click Create Approvals in a Contract record, the system sets Latest Contract ID to the ID for that contract and then evaluates the condition in the template. If the condition is met, an Approval record is generated. At that point, the Approval is linked to the specific contract using Contract ID instead of Latest Contract ID. 
> 📝 
> 📝 The same logic applies to Sourcing Event and Supplier Profile templates. When defining conditions, use the appropriate ID field with "latest_" prepended to the name.

### Assigning a Step Number

The sequence of Approval Templates in a workflow is determined by the Step Number field. Approvals are arranged in ascending order based on the Step Number value. To set up concurrent Approvals, assign the same Step Number to each Approval Template that should occur simultaneously. All Approvals with the same Step Number must be complete before the next Approval step is triggered.

### > Macro (anchor)

Assigning the Approver

Approval Templates dictate who the approval's assigned to. They can be assigned to a team from the parent record, a person from the parent record, or a specific team and person.

The Assign Approval Based On field defines whether to base the assignment on users already linked to the parent record or other specific users. The choices available for this field depend on the type of parent record this template relates to. You can choose Assigned Team / Person to assign the approval to a specific person or team, or you can choose Person from [Parent] or Team from [Parent].

- To assign the approval to a specific person or team not necessarily from the parent record, select Assigned Team / Person, and then select a team from the Approval Team field. If you want to assign the approval to a person on that team, select the person from the Approver field.
- To assign the approval to a team from the parent record, select Team from [Parent] and then select the team from the Assign To field.

> ℹ️ The selections for Assign To are based on records in the [Replacement Variables Table](https://wiki.agiloft.com/display/SD/Replacement+Variables+Table).

- To assign the approval to a person from the parent record, select Person from [Parent]. In the Assign To field, select the role that represents the person.

# Views

The out-of-the-box Approval Templates table includes the [standard views](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43718574). The Default View shows the Edit icon, ID, Step Number, Approval Type, Approval Title, and Workflow Title fields.

![Default View for the Approval Templates table](media://44167df8-d1ce-48a3-86d5-addbad230585)

# Saved Searches

The out-of-the-box Approval Templates table includes the following saved searches:

- **Demo Records**: Finds records where the Demo Data field is set to Yes.
- **Status is Active, sorted by Step Number**: Finds all records where the Status is Active and sorts them in ascending order by Step Number.

# Fields

In addition to the [standard fields](https://agiloft-public.atlassian.net/wiki/spaces/SDA2603/pages/521273545/Table+Concepts#standard_fields), the out-of-the-box Approval Templates table includes the following fields.

| **Field Label** | **Data Type** | **Description** |
| --- | --- | --- |
| Add one to step | Action button | Increases the Step Number value by 1. |
| All Templates for this Workflow | Embedded Search Result | Displays all other Approval Template records with the same Workflow ID. |
| Approval Team Leader  
Approval Team | Link to selected fields from other table: Teams | When the Assign Approval Based On field is set to Assigned Team / Person, this field defines the team to assign the template to. |
| Approval Template ID and Contract ID | Compound | Used by the system to determine if an Approval record for this template already exists. If there's a match in the Approvals table, the system updates the existing Approval record instead of creating a new record. |
| Approval Title | Short Text | Required field that names the approval. |
| Approval Type | Choice:<br>- Approval
- Notification
- Review | For Contract approvals, this field determines the options the approver has:<br>- When set to Approval, the approver can Approve, Require Changes, or Permanently Reject.
- When Notification, the approval is informational-only.
- When Review, the approver can mark the review complete or require changes. |
| Approval Usage | Choice:<br>- Required
- Conditional | Controls whether this template is always part of the workflow or whether it should only be included when certain conditions are met.<br>- When set to Required, this template is always included in the workflow. This is the default setting.
- When Conditional, this template is only included in the workflow if the specified Condition evaluates to True. |
| Approver  
Approver ID | Link to selected fields from other table: People | When the Assign Approval Based On field is set to Assigned Team / Person, this field defines the person to assign as the approver. |
| Assign Approval Based On | Choice:<br>- Assigned Team / Person
- Person from Contract
- Team from Contract
- Person from Solicitation
- Team from Solicitation
- Person from Supplier Profile
- Team from Supplier Profile | Defines whether to base the approval assignment on users already linked to the parent record or other specific users. The options available depend on the Related To value. For details, see [Assigning the Approver](https://agiloft-public.atlassian.net/wiki/spaces/SDA2603/pages/521281233/Approval+Templates+Table#ApprovalTemplatesTable-assign_approver) above. |
| Assign To Variable  
Assign To  
Assign To Variable ID | Link to selected fields from other table: Replacement Variables | When the Assign Approval Based On field is set to Person from [Parent] or Team from [Parent], this field defines the role that represents the person to assign. |
| AT ID and Latest Contract ID | Short Text | The Approval Template ID and Latest Contract ID. |
| Auto-Approve? | Choice:<br>- Yes
- No | Visible for Sourcing Event and Supplier Profile templates. When set to Yes, the system notifies the approver and then automatically sets the Approval Status to Approved. Defaults to No. |
| Cloned Workflow ID | Link to selected fields from other table: Approval Workflows | Mapped by rule from the Approval Workflow table when a workflow is cloned. |
| Condition | Variable Formula | The formula to evaluate when Approval Usage is set to Conditional. |
| Condition Description | Text | A description of the Condition to evaluate. |
| Condition Value | Short Text | Holds the result of the Condition evaluation. |
| Decrease Step Number by 1 | Action button | Decreases the Step Number value by 1. |
| Default Message | Text | An optional message to send to the approver when launching the approval process. |
| Flag to Clone Template | Choice:<br>- Yes
- No | Flags whether the template is to be cloned. Automatically set by a rule. |
| Flag to Recheck Approval | Choice:<br>- Yes
- No | This flag is used for Conditional approvals to ensure they are reevaluated if the parent record is changed. Default is No. |
| Generated for Contract IDs | Link to single field from other table: Contracts | For templates related to contracts, this field stores the Contract IDs of the Contracts that have Approvals generated from this template. |
| Increase Step Number by 1 | Action button | Increases the Step Number value by 1. |
| Latest Contract ID | Link to selected fields from other table: Contracts | This field is populated by a rule from the Contracts table when triggering the generation of an Approval record. It's used to link to the Contract when evaluating conditions. If an Approval record is generated from the template, the Approval record uses Contract ID rather than the Latest Contract ID. |
| Latest Solicitation ID | Link to selected fields from other table: Sourcing Events | This field is populated by a rule from the Sourcing Events table when triggering the generation of an Approval record. It's used to link to the Sourcing Event when evaluating conditions. If an Approval record is generated from the template, the Approval record uses Sourcing Event ID rather than the Latest Solicitation ID. |
| Latest Supplier Profile ID | Link to selected fields from other table: Supplier Profiles | This field is populated by a rule from the Supplier Profiles table when triggering the generation of an Approval record. It's used to link to the Supplier Profile when evaluating conditions. If an Approval record is generated from the template, the Approval record uses Supplier Profile ID rather than the Latest Supplier Profile ID. |
| Notify for Auto-Approval | Choice:<br>- Yes
- No | Defines whether the approver is notified when the approval is automatically approved. Defaults to Yes. |
| Related To | Choice:<br>- Contracts
- Sourcing Events
- Supplier Profile | Defines the type of approval process this template can be used for. |
| Source for Conversion | Choice:<br>- Approval Template
- Document Management
- Ad Hoc Approval | Defaults to Approval Template. |
| Status | Choice:<br>- Active
- Inactive | The status of the template.<br>- When Active, the template is available as an option for related Contracts, Sourcing Events, or Supplier Profiles. This is the default value.
- When Inactive, the template is not available for use. |
| Step Number | Floating Point | Required field that defines the order for this template in the workflow. You can enter a decimal value to insert the step between two existing steps without having to renumber the steps. |
| Trigger Approval Creation | Choice:<br>- Yes
- No | This field is set to Yes by a rule when a Contract is submitted for approval. Default is No. |
| Unique Approval Identifier (text) | Short Text | When Approval creation is triggered from a parent record, an action sets this value. It's a combination of template ID, linked record ID, and Related To. The value is mapped to the Approval to use for matching during conversion. It identifies whether an approval for the linked record already exists. |
| Workflow Related to  
Workflow Approval For  
Workflow Title  
Workflow ID | Link to selected fields from other table: Approval Workflows | These fields identify the Approval Workflow the template belongs to. |

# Automation

This section describes the rules that are implemented for the out-of-the-box Approval Templates table. For details about rule configuration options, see [Rules](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43714473) in the Help Guide.

- **Create/Edit: Blank out fields based on Assign Approval Based On (web, API)**: This rule runs when a record is created or edited. The rule performs the following actions:
  - If the workflow is related to Contracts but the Related To field is blank, set Related To to Contracts.
  - If the workflow is related to Sourcing Events but the Related To field is blank, set Related To to Sourcing Events.
  - Blanks out certain fields based on the value in the Assign Approval Based On field. For example, if Assign Approval Based On is set to Assigned Team / Person, the rule blanks out the Assign To field, since the field is replaced with the Approval Team and Approver fields.
- **Edit: All Solicitation Approval Template Edit Actions (web, API)**: This rule runs when a record related to Sourcing Events is edited. The rule handles triggering new approvals when necessary, cloning templates for reuse, and rechecking existing approvals based on conditions. The rule performs the following actions:
  - Finds records where Trigger Approval Creation is set to Yes, which means a new approval process needs to be initiated. It sets the value to No to avoid reprocessing the same records.
  - If Latest Solicitation ID is not blank and Approval Usage is either Required or Conditional and the condition evaluates to True, it generates a Sourcing Event Approval.
  - If Flag to Clone Template is Yes, it generates an Approval Template and resets the flag to No.
  - If Flag to Recheck Approval is Yes and Approval Usage is Conditional:
    - If the condition is True, it regenerates the Sourcing Event Approval and resets the flag to No.
    - If the condition is False, it marks the approval as not needed.
- **Edit: All Supplier Profile Approval Template Edit Actions (web, API)**: This rule runs when a record related to a Supplier Profile is edited. The rule handles triggering new approvals when necessary, cloning templates for reuse, and rechecking existing approvals based on conditions. The rule performs the same actions as the rule above:
  - Finds records where Trigger Approval Creation is set to Yes, which means a new approval process needs to be initiated. It sets the value to No to avoid reprocessing the same records.
  - If Latest Supplier Profile ID is not blank and Approval Usage is either Required or Conditional and the condition evaluates to True, it generates a Supplier Profile Approval.
  - If Flag to Clone Template is Yes, it generates an Approval Template and resets the flag to No.
  - If Flag to Recheck Approval is Yes and Approval Usage is Conditional:
    - If the condition is True, it regenerates the Supplier Profile Approval and resets the flag to No.
    - If the condition is False, it marks the approval as not needed.
- **Edit: All Contract Approval Template Edit Actions (web, API)**: This rule runs when a record related to a Contract is edited. The rule handles triggering new approvals when necessary, cloning templates for reuse, and rechecking existing approvals based on conditions. The rule performs the same actions as the rules for Sourcing Event and Supplier Profile templates above:
  - Finds records where Trigger Approval Creation is set to Yes, which means a new approval process needs to be initiated. It sets the value to No to avoid reprocessing the same records.
  - If Contract ID is not blank and Approval Usage is either Required or Conditional and the condition evaluates to True, it generates a Contract Approval.
  - If Flag to Clone Template is Yes, it generates an Approval Template and resets the flag to No.
  - If Flag to Recheck Approval is Yes and Approval Usage is Conditional:
    - If the condition is True, it regenerates the Contract Approval and resets the flag to No.
    - If the condition is False, it marks the approval as not needed.

# Ownership

Approval Template records are owned by the user who creates them. Specifically, Creator Login is set to the Login of the user who creates the record. For more information on record ownership, see [Record Ownership](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43718158) in the Help Guide.