Considerations for Chatter Post Templates for Approval Requests from Classic Approval Processes
Keep these limitations and dependencies in mind when working with post templates.
Required Editions
| Available in: both Salesforce Classic and Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions |
Important Try Flow Approval Processes, a modern alternative to Classic Approval Processes. This
new feature provides a more flexible, user-friendly flow-based interface, and it can trigger
on record changes, supporting Apex extensibility and detailed logging for compliance and
audit trails. It supports dynamic routing based on data and business rules, unlike Classic
Approval Processes, which are tied to specific objects and offer limited support for
processes by using conditions. With Flow Approval Processes, you can monitor submitted
records and quickly identify bottlenecks, giving you unprecedented visibility into approval
workflows. And, like Classic Approval Processes, Flow Approval Processes don’t consume
automation credits or orchestration runs.
Limitations
- The associated object must be enabled for approvals and feed tracking.
- If an approval post template is in use by a classic approval process, you can't delete it.
- Chatter posts for approval requests only appear in Salesforce Classic. To respond to approval requests in Lightning Experience, users go to the Approval Requests tab.
Dependencies
- Deleting a custom field removes it from any approval post template that references it. Existing posts aren't affected. Undeleting the custom field restores it to the available fields list, but doesn't restore it to any approval post templates that previously contained it.
- Deleting (or undeleting) a custom object also deletes (or undeletes) its associated approval post templates and any of its approval request posts that are already in Chatter feeds.
- If you rename a custom object, approval post templates associated with it update accordingly.