Glossary

Workspace

Where one team's environments, configuration, change sets, and work items live. Most teams need only one. Members, roles, and settings like approvals are set per workspace.

Environment

A connected Aprimo instance: a sandbox, a QA instance, your production instance. Each environment carries the instance's address and the credentials Mochi uses to reach it. You add each one once, and Mochi shows you what configuration lives there, reading it and, when a change is delivered, writing it. See Environments.

Production

An environment you mark as a delivery target a pipeline ends at. A workspace can have several. Several at the end of one pipeline deliver in parallel. See Environments.

Configuration

The tracked record of how your Aprimo configuration is set up: fields, content types, classifications, and the rest. It's built up one change set at a time. See Configuration.

Change set

A bundle of configuration changes, grouped so you can look them over and move them together. Each one has a number, like #115, and that number is how an environment says what it holds. See Change sets.

Work item

A piece of work you're tracking, like a request or a requirement, sitting on a board. Link change sets to it and you can see what work reached which environment. See Work items.

Check

A rule that says what must be true about your configuration, or about the records it produces, which Mochi proves by reading a live environment and comparing. A check can run when you choose, after a change set becomes part of your configuration, or at a pipeline stage. Running one changes nothing in the environment. See Checks.

Approval

An optional checkpoint where named approvers say yes before a change moves ahead. You can require any one of them, everyone, or a set number. Approvals are off until you turn them on. See Approvals.

Pipeline

An ordered path that carries a change from one environment toward a production environment, with an optional checkpoint along the way. See Pipelines.

Delivery

Carrying a change set along a pipeline. You start one with New run on the pipeline. Runs lists one row per delivery, with its attempts inside. See Run a pipeline.

Attempt

One try at a delivery. Trying again adds another attempt to the same delivery rather than starting a fresh one, and the earlier attempt is called off (its history says it was tried again as a new run). See When a delivery doesn't finish.

Run

One attempt at a delivery, or one run of your checks. A run records what happened to each item and has its own page. Checks runs are listed under the environment they ran in, not among deliveries. See Pipelines.

Replaced

A stopped delivery the environment has since moved past: a newer version landed there after it stopped. Trying it again or sending it anyway would take the environment backwards, so it has no actions left and stays in Runs as history.

Refused

An item Aprimo turned down on its own terms: a user group only an operator may create, one of Aprimo's own setting definitions, and the like. The run lists them under Aprimo refused, the delivery stays Failed until they're marked as managed by Aprimo, and the next attempt then leaves them out. See When a delivery doesn't finish.

Gate

A pause built into a pipeline. When a run reaches a gate it waits for an approval before going on, so nothing reaches an environment until the right person has said yes. See Approvals.

Settle a delivery

Deciding what happens to a delivery that stopped at a safety check: try again (another attempt), update anyway, or call it off. A stopped delivery doesn't hold its environment; a newer update can overtake it, and it is then called off with Replaced by a newer run on its history. See When a delivery doesn't finish.

Roll back

Putting the configuration Mochi manages in one environment back to an earlier change set. The changes stay part of your configuration, so they can reach that environment again later. See Undoing changes.

Undo

A change set that takes an earlier one back out of your configuration. It removes from your environments whatever the original added, and puts back whatever it changed. It goes through review and delivery like any other change set. See Undoing changes.

Broken reference

A tracked item that points at a piece of configuration Mochi isn't tracking yet. Mochi flags these and helps you bring the missing items in. See Broken references.

Managed by Aprimo

A mark a person puts on items that an Aprimo feature looks after itself. Marked items stay out of Not tracked, Changed, and deliveries, and if any were tracked, a Stop tracking change set is proposed. A run offers the mark for the items Aprimo refused. Marking changes nothing in Aprimo. See Configuration.

AI access

The workspace setting that lets people connect an AI assistant to Mochi. Turning it on lets an assistant look at things; letting it put change sets together and edit work items is a separate setting, and changing a connected Aprimo instance is set per instance. A change set an assistant puts together always waits for a person to approve it. See Give an AI agent access.