{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":46551,"path":"servicenow-platform/approvals/r_Approvals.md","title":"Classic approvals","bundle":null,"doc_type":null,"release":"australia","body":"\n# Classic approvals\n\nClassic approvals are records that store the authorization tasks that must be done to approve or reject a request. Approval records are typically created by a Workflow Studio flow or classic workflow. An approval defines both the approval tasks and the users or groups are assigned to approve or reject them.\n\nAdministrators create approval logic from Workflow Studio flows or classic workflows.\n\n-   Create a Workflow Studio flow that contains an [Ask for Approval action](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/ask-approval-flow-designer.md).\n-   Create a classic workflow that contains either an [Approval - Group workflow activity](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/workflow-activities/r_ApprovalGroup.md) or an [Approval - User workflow activity](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/workflow-activities/r_ApprovalUser.md).\n\nIn either case, the approval record defines this information.\n\n-   The record type that needs approval. For example, a Service Catalog request or a change request.\n-   The people who can approve or deny the approval request. For example, a specific assignment group or a user's manager.\n-   The approval rules that determine how multiple approval decisions interact. For example, an approval that requires all approval users to respond or an approval where any single person can approve or reject an approval request.\n\nUsers can see their approval requests by navigating to **All** &gt; **Self-Service** &gt; **My Approvals**.\n\n## Approval record\n\nAn approval record consists of these fields:\n\n<table id=\"table_dkw_tvt_lt\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nApprover\n\n</td><td>\n\nA reference to the user who is responsible for approving the related record.\n\n</td></tr><tr><td>\n\nState\n\n</td><td>\n\nChoices are: -   Not Yet Requested \\(This state indicates that you aren't yet asking your approval users to approve this request. Until you set the status to **Requested** they will receive no email notifications about the request.\\)\n-   Requested\n-   Approved\n-   Rejected\n\n</td></tr><tr><td>\n\nApproving\n\n</td><td>\n\nA document\\_id reference field to the record being approved, on any table.\n\n</td></tr><tr><td>\n\nComments\n\n</td><td>\n\nA journal field for storing comments regarding the approval.\n\n</td></tr><tr><td>\n\nApproval Summarizer\n\n</td><td>\n\nA [Create a formatter and add it to a form](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/t_CreateAFormatter.md) that displays key fields relevant to the approval from the referenced document. This summarizer will not display if there is no record referenced.\n\n</td></tr></tbody>\n</table>-   **[Approval engines](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/approvals/c_ApprovalEngines.md)**  \nThe differences in the way that companies handle their approvals, as well as the differences between approvals for the various applications \\(such as Service Catalog Requests and Change Management\\), calls for supporting flexibility in setting up approvals within applications.\n-   **[Approval rules](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/approvals/c_ApprovalRules.md)**  \nMany organizations rely on an approval process to ensure that requests are reasonable and fit an organization's budget.\n-   **[Approval summarizer formatter](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/approvals/r_ApprovalSummarizerFormatter.md)**  \nThe approval summarizer formatter creates the summary at the bottom of an approval form.\n-   **[Approval with e-signature](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/approvals/approval-with-e-signature.md)**  \nApprove or reject an approval record by re-entering your login credentials. See the history of an approval from its activity stream or its audit history.\n-   **[Approval status](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/approvals/c_ApprovalStatus.md)**  \nThe approval status of a change request is determined by looking at the current status of all the approvers.\n-   **[Generate an approval using approval rules](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/approvals/c_GenAnApprovalUsingApprRules.md)**  \nThe system can automatically generate an approval request to individuals or groups when specific criteria are met. The automatic generation of approval requests is driven using the System Policy feature.\n-   **[Generate approvals using the approvers related list](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/approvals/c_GenApprovalsUsingApprsRelList.md)**  \nIt is possible to manually add approvers to a request.\n-   **[Generate approvals using Workflow flows](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/approvals/c_GeneApprovalsUsingWorkflows.md)**  \nWorkflow Studio flows are a powerful and flexible method of generating approvals. Use workflow flows to create group approvals and user approvals.\n-   **[Multiple approvers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/approvals/c_MultipleApprovers.md)**  \nWith multiple approvers, all approvers must authorize the request before the status will change to \"Approved\".\n-   **[Receive notifications](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/approvals/c_ReceiveNotifications.md)**  \nIndividuals who are designated approvers automatically receive approval notifications, including approval status updates.\n-   **[Dynamic approval forms](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/approvals/c_DynamicApprovalForms.md)**  \nWhen you are looking at an approval request, the form has a context-appropriate summary of the item to be approved.\n-   **[Scripts and engines execution order](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/approvals/execution-order-scripts-engines.md)**  \nScripts, assignment rules, business rules, workflows, escalations, and engines all take effect in relation to a database operation, such as insert or update. In many cases, the order of these events is important.\n\n**Parent Topic:**[Exploring Service Administration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/c_ServiceAdministration.md)\n\n"}}