---
id: "866abc4b-b469-410d-a436-3a82bb604a8b"
name: "Outbound Change Set Flow"
micro_summary: "Use the Lightning Setup wrapper for Outbound Change Sets, but interact with the embedded Aloha iframe. Upload may be blocked until Deployment Connections authorize the sandbox."
status: "resolved"
see_also: []
scope: "Browser UI flow for policy-required Salesforce outbound change sets in Lightning Setup, including list/detail/new/add/upload pages."
warnings: "Upload can be blocked by Deployment Connections authorization; browser automation cannot bypass org-to-org authorization requirements.\nSalesforce renders change-set pages as Classic/Aloha even inside Lightning Setup; browser automation must interact with the embedded iframe content, not only the Lightning shell."
---
## Lightning wrapper URL

Open Outbound Change Sets in the Lightning Setup shell with:

```text
/lightning/setup/OutboundChangeSet/page?address=%2Fchangemgmt%2FlistOutboundChangeSet.apexp
```

Salesforce renders the change-set pages as Classic/Aloha content inside the Lightning wrapper. Use the Lightning Setup Aloha iframe pattern to read/click the inner page.

## Manual outbound flow

1. Open the wrapper URL.
2. Click `New` inside the embedded Aloha iframe.
3. Use compact ticket-code naming, e.g. `SO-931: Prevent Ineligible Patients`.
4. Save the change set.
5. Click `Add` under Change Set Components.
6. Select the component type, e.g. `Validation Rule` (`ValidationFormula`).
7. Use alphabet/rolodex paging if needed, select the target component, and click `Add To Change Set`.
8. Return to detail and verify component rows.
9. Upload only after Deployment Connections authorization exists.

## Observed SO-931 example

In `jtbsandbox`, `SO-931: Prevent Ineligible Patients` was created with component `Prevent_Ineligible_Patient` on parent object `Northstar Order`, type `Validation Rule`. Upload was blocked by lack of outbound authorization to other orgs.