Change sets
A change set is a bundle of configuration changes, grouped together so you can look them over and move them as one.
When you change configuration in Aprimo, those edits sit loose in that environment. A change set is how you gather the items you care about (a field, a content type, a set of rules), give them a description, and turn them into something reviewable. Nothing's locked in until the change set is created.
What's in a change set
You build a change set by opening an environment and picking the items you've changed. Each change set carries:
- The items you chose: exactly the items you selected, down to a single one.
- Anything they depend on. If an item you picked points at something that isn't tracked yet, Mochi adds it for you so the change set won't leave a dangling reference. These show up under “Also included,” and you can remove any you don't want.
- A description. The first line becomes the title. Write it for the person who reviews it.
The life of a change set
- Open. You've created it and it's waiting for review. If your workspace asks for approval, it sits here until enough approvers say yes. Usually that means someone other than whoever made it.
- Approved. It becomes part of your configuration: the tracked record of how things should be set up.
- Delivered. Once it's part of your configuration, a pipeline can carry it to your other environments.
A change set can also be denied: it's rejected and never becomes part of your configuration. Nothing in Aprimo changes either way; Mochi writes to an environment only when a run delivers a change there.
Which direction can they go?
Any direction. Most change sets start in a sandbox and move up toward production, but you can also capture a fix that was made directly in production and bring it back down to your sandboxes so they stay in sync. See Move a fix to a sandbox.