Review and approve
A change set waits for a decision before it becomes part of your configuration.
Open a change set and you can see exactly what's in it: the configuration items chosen, anything included alongside them, and the description its author wrote. Nothing about your setup has changed yet. A change set is just a proposal until someone decides on it.
The list of changes comes first on the screen, and the Approve and Deny buttons sit underneath it. You pass what's changing on your way to the decision, so scroll through the added, changed, and removed items before you get there. Anything under Changed opens up to show the old value beside the new one.
Approve or deny
You have two choices:
- Approve: the change set becomes part of your configuration, the tracked record of how things should be set up.
- Deny: the change set is set aside and doesn't join your configuration. Nothing in Aprimo changes either way.
If an AI agent put the change set together, it's marked Put together by AI at the top, and the review panel says so too. Same decision, same buttons. It's a nudge to read the changes rather than take the description's word for it.
What approving unlocks
Once a change set is part of your configuration, it's ready to deliver to your other environments through a pipeline, carrying the same change from a sandbox up to production, with an optional checkpoint along the way. Mochi delivers it when a run carries it there, whether you start that run or a pipeline runs automatically.