You are here:
Considerations for Classic Approval Process History Reports
Understand the limitations and special behaviors when you create or view approval history reports, which provide a detailed history of classic approval processes and steps.
Required Editions
| Available in: both Salesforce Classic and Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions |
Considerations for Approval Processes That Were Completed Before or Pending during the Summer '14 Rollout
When Summer ’14 became available for your organization, the approval history data was automatically populated for completed and pending classic approval processes. However, some approval history field values are never populated or are populated only after the classic approval process instance is next acted upon—such as when a user approves, rejects, or reassigns an approval request—after the Summer ’14 rollout. Additional exceptions apply to approval history data that is available only via SOQL queries of certain objects. See ProcessInstance, ProcessInstanceNode, ProcessInstanceStep, and ProcessInstanceWorkitem in the Object Reference for Salesforce.
| Object | When Fields are Populated |
|---|---|
| Process Instance | For classic approval process instances that were completed before the Summer ’14 rollout, all Process Instance fields are automatically populated, with one exception: Completed Date is never populated for classic approval process instances that were completed before January 1, 2013. For classic approval process instances that were pending during the Summer ’14 rollout, all Process Instance fields are automatically populated, with two exceptions: Completed Date and Last Actor: Full Name are populated only after the classic approval process instance is complete. |
| Process Instance Node | Never populated for classic approval process instances that were completed before the Summer ’14 rollout. For classic approval process instances that were pending during the Summer ’14 rollout, all Process Instance Node fields are populated only after the classic approval process instance is next acted upon after the Summer ’14 rollout. |
Considerations for the Sandbox Environment
If you copy approval history data to a sandbox, some field values are overwritten and don't reflect the actual approval history.
| Object | Field | When an existing process instance or process instance node record is copied to a sandbox... |
|---|---|---|
| Process Instance | Submitted Date | This value is overwritten by the date and time when the process instance record is copied to the sandbox. |
| Submitter: Full Name | This value is overwritten by the name of the user who copied the process instance record to the sandbox. | |
| Process Instance Node | Step Start Date | This value is overwritten by the date and time when the process instance node record is copied to the sandbox. |
