---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Classic approvals

# Classic approvals {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Classic approvals are a legacy process to require authorization on tasks before the work is done. In earlier releases, you could create approval records to define approval tasks and associate users or groups to approve or reject them.
Administrators can define classic approval logic by navigating to AllSystem PolicyRulesApprovals.  
Wichtig:  
Classic approval rules have been replaced by the Workflow Studio [Ask for Approval action](https://www.servicenow.com/docs/access?context=ask-approval-flow-designer&version=australia&pubname=australia-build-workflows&ft:locale=en-US). Use Workflow Studio to create workflow-driven approval logic that is easier to maintain and provides better reporting information.

Administrators can see all approval requests by navigating to AllSelf-ServiceMy Approvals and removing the list filter.

An approval record consists of these fields:
{#r_Approvals__table_dkw_tvt_lt__entry__2}

| Field | Input value |
|-|-|
| Approver | A reference to the user who is responsible for approving the related record. |
| State | Choices are: * Not Yet Requested (This state indicates that you are not yet asking your approvers to approve this request. Until you set the status to Requested they will receive no email notifications about the request.) * Requested * Approved * Rejected {#r_Approvals__ul_ggy_wvt_lt} |
| Approving | A document_id reference field to the record being approved, on any table. |
| Comments | A journal field for storing comments regarding the approval. |
| Approval Summarizer | A [Create a formatter and add it to a form](https://www.servicenow.com/docs/access?context=t_CreateAFormatter&version=australia&pubname=australia-platform-administration&ft:locale=en-US) that displays key fields relevant to the approval from the referenced document. This summarizer will not display if there is no record referenced. |
[Tabelle : 1. Approval record components]

{#r_Approvals__table_dkw_tvt_lt}
* **[Approval engines](https://servicenow-prod.fluidtopics.net/cIFK3QplNSo2UGhu9Au4WQ)**   
  The 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.
* **[Approval rules](https://servicenow-prod.fluidtopics.net/Mh3HTTY8g76vRHSNcRmohw)**   
  Many organizations rely on an approval process to ensure that requests are reasonable and fit an organization's budget.
* **[Approval summarizer formatter](https://servicenow-prod.fluidtopics.net/p1SqmeH6ai6945ZNWdLL4w)**   
  The approval summarizer formatter creates the summary at the bottom of an approval form.
* **[Approval with e-signature](https://servicenow-prod.fluidtopics.net/1sK0wdGlZS5yCSBA7Vu7GQ)**   
  Approve 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.
* **[Approval status](https://servicenow-prod.fluidtopics.net/W675uUr4Rh1WuFiylxAvxg)**   
  The approval status of a change request is determined by looking at the current status of all the approvers.
* **[Generate an approval using approval rules](https://servicenow-prod.fluidtopics.net/sO2WWw2kE1z4KEeXQxkvGQ)**   
  The 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.
* **[Generate approvals using the approvers related list](https://servicenow-prod.fluidtopics.net/0o6gfPt~g3Di4SgQJ11WqA)**   
  It is possible to manually add approvers to a request.
* **[Generate approvals using Workflow flows](https://servicenow-prod.fluidtopics.net/ZuyuaYlrKTENzXVDfVf7uA)**   
  Workflow Studio flows are a powerful and flexible method of generating approvals. Use workflow flows to create group approvals and user approvals.
* **[Multiple approvers](https://servicenow-prod.fluidtopics.net/G1yCyH42JjOtEQcYyqmHBg)**   
  With multiple approvers, all approvers must authorize the request before the status will change to "Approved".
* **[Receive notifications](https://servicenow-prod.fluidtopics.net/eDuW6XSR7d~ZugwzAFFYDw)**   
  Individuals who are designated approvers automatically receive approval notifications, including approval status updates.
* **[Dynamic approval forms](https://servicenow-prod.fluidtopics.net/59i99Wkl_fnYjsLPezGmIg)**   
  When you are looking at an approval request, the form has a context-appropriate summary of the item to be approved.
* **[Scripts and engines execution order](https://servicenow-prod.fluidtopics.net/d7sUNQon~UELNP8f8FtQZw)**   
  Scripts, 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.