Published at: 2026-09-17
deploy-an-inbound-change-set
Deploying an inbound change set applies configuration changes to the target environment.
[!WARNING] Deployment creates or updates metadata in the target environment. Complete validation and business confirmation before going live.
Before you begin
- The inbound change set has passed validation.
- You have permission to deploy change sets.
- The release window has been confirmed.
- A post-deployment validation checklist is ready.
- A rollback or recovery plan is confirmed.
Step 1: Open the inbound change set
- In the admin backend, go to Environment Management > Inbound Change Sets.
- In the list, click the target change set name.
Step 2: Re-check the deployment content
- On the detail page, view the change set basic information.
- Open the Components tab and re-check the component list.
- Open the History tab and confirm that the latest validation passed.
Step 3: Run the deployment
- On the change set detail page, click Deploy.
- In the confirmation dialog, read the risk prompt.
- Click OK.
Deployment deploys all components in the inbound change set to the current environment. After deployment, the system updates the inbound change set status and adds a deployment history record.
Step 4: View the deployment result
- In the History tab, view the latest deployment record.
- Click the deployment record to view details.
- If deployment fails, view the failure reason.
Expected results and validation
After a successful deployment, the target environment adds or updates the corresponding metadata. Run post-release validation immediately.
[!NOTE] The original manual states that when deployment fails, all content of this deployment rolls back.
After a change set deploys successfully, the system creates or updates metadata in the target environment. This operation cannot be rolled back with one click.
Common issues and troubleshooting
| Issue | Suggested action |
|---|---|
| Deployment fails | View the error details in the history |
| Some features do not take effect | Check permissions, layout, and flow dependencies |
| Rollback needed | Disable the configuration, restore manually, or use a new change set to fix |