Classic approvals

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 All > System Policy > Rules > Approvals.

Important:

Classic approval rules have been replaced by the Workflow Studio Ask for Approval action. 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 All > Self-Service > My Approvals and removing the list filter.

An approval record consists of these fields:

Table 1. Approval record components

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
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 that displays key fields relevant to the approval from the referenced document. This summarizer will not display if there is no record referenced.