{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":46562,"path":"servicenow-platform/approvals/t_SetupAnApprovalEngine.md","title":"Set up an approval engine","bundle":null,"doc_type":null,"release":"australia","body":"\n# Set up an approval engine\n\nTo manage the approvals for each of the Task tables in the system, set up an approval engine.\n\n**Important:** Classic approval rules have been replaced by the Workflow Studio [Ask for Approval action](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/ask-approval-flow-designer.md). Use Workflow Studio to create workflow-driven approval logic that is easier to maintain and provides better reporting information.\n\n## Before you begin\n\nRole required: none\n\n## Procedure\n\n1.  Navigate to **All** > **System Properties** > **Approval Engines**.\n\n    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.\n\n    \\[Omitted image \"ApprovalEnginePage.png\"\\] Alt text: Approval engine page\n\n2.  Select the [approval engine option](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/approvals/c_ApprovalEngines.md) for each Task table from the choice list.\n\n3.  Click **Save**.\n\n    These preferences are saved as system properties that are named **glide.approval\\_engine.<table\\_name>**.\n\n\n**Parent Topic:**[Approval engines](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/approvals/c_ApprovalEngines.md)\n\n"}}