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

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Set up an approval engine

# Set up an approval engine {#ariaid-title1}

Release version: Yokohama  
Updated January 30, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
To manage the approvals for each of the Task tables in the system, set up an approval
engine.

## Before you begin

Role required: none  
Important:  
Classic approval rules have been replaced by the Workflow Studio [Ask for Approval action](https://servicenow-prod.fluidtopics.net/eNjrggHQNOdpv8E3iNKJ4w "Request approval for a record with an approval field. You can configure a rule set for an approval, rejection, or cancellation. If a due date is added to an approval, the approval is automatically approved, rejected, or canceled if the approvers have not responded by the designated time."). Use Workflow Studio to create workflow-driven approval logic that is easier to maintain and provides better reporting information.

## Procedure

1. Navigate to AllSystem PropertiesApproval Engines.  
   The following page appears with the Approval Engine
   option for each Task table in the system. If the Approval Engine option is greyed out and shows Turn engines off, read the Notes in the
   same row. The most common reason an approval engine is turned off is that a
   workflow is managing the approvals on the table. Having the approval engine
   turned off prevents conflicts with the workflow that could cause a range of
   issues. If you want to use an approval engine on the table, set the workflow
   to inactive.
2. Select the [approval engine option](https://servicenow-prod.fluidtopics.net/KD_xl1t00crEs2hP9ciYZg#c_ApprovalEngines__table_ApprovalEngineOptions) for each Task table from the choice list.
3. Click Save.  
   These preferences are saved as system properties that are named glide.approval_engine.\<table_name\>.

*[\>]: and then