---
schema_version: "1"
id: 5685803187dd6521176d15b9c27dffaf2f9ea3ff14e94779b522c015278b20a6
title: Restrictions for Approval Processes in Change Sets
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/changesets_restrictions_approval_process.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.changesets_restrictions_approval_process.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: fb98ee90bccac1d6ba0e6b1f7687ed171a9ca5fc4ef193784485ae4dc9faec09
description: Understand these restrictions before you include approval processes in change sets.
products:
  - Salesforce Platform
release: "264"
---
# Restrictions for Approval Processes in Change Sets

Understand these restrictions before you include approval processes in change sets.

- If the approval page fields include any custom fields on standard objects, manually add those custom fields to outbound change sets. The View/Add Dependencies option for selecting change set components don't include these fields.
- If the approval process references any post templates that contain custom fields, resave those post templates in the originating organization before adding them to the change set. From Setup, enter Post Templates in the Quick Find box, then select **Post Templates**. For each post template, click **Edit** and then **Save**.
- Change sets don't include the order of active approval processes from the source org. Sometimes you must reorder the approval processes in the destination org after deployment.
- If you change the Unique Name of an approval process that was previously included in a change set and deployed in another organization, and you resend the approval process via a change set, a new approval process is created upon deployment in the other organization. The previously deployed approval process isn’t modified.