Your configuration

Your configuration in Mochi is the agreed record of how your Aprimo setup should look: fields, content types, classifications, rules, and more. It isn't a copy of any single instance; it's the picture your team has agreed on, built up one change set at a time.

Browsing by type

Everything you track is grouped by type (content types, fields, field groups, classifications, rules, and the rest) so you can find a single item quickly or scan a whole category. Open any item to see its settings, what it depends on, what depends on it, the checks that name it, and its full history: who changed it, when, and in which change set.

Needs a look

Sometimes a tracked item points at something that isn't tracked yet. Mochi gathers those under Needs a look so they don't hide. These are broken references, and Mochi helps you repair them by bringing the missing items in from an environment you choose.

Renames

Some items can be renamed in Aprimo: classifications, rules, field groups, content types, file types and setting categories. When someone renames one, Mochi treats it as the same item with a new name, not as one item gone and another added. The environment's scan lists it as changed, with both names (“Renamed /Products/Home → /Products/Home and garden”), and capturing it records one change to that item. Its history stays in one place, and anything that pointed at it keeps pointing at it.

Delivering a rename to another environment renames the item there, in place, so whatever is attached to it in that environment stays attached. If that environment never had the item, it is added under the new name. One exception: a classification moved under a different parent isn't a rename, and Mochi says so rather than deleting and re-adding it.

A field's name can't change in Aprimo once it exists, so a field is never renamed. Its labels can change freely, and those are ordinary settings of the field.

Stopping is safe

If you no longer want Mochi to track an item, you can stop tracking it. Stopping is itself a change set. It goes through review like any other, and once it's approved it becomes a new version of your configuration. An environment that was up to date stays up to date: there is nothing to send, so it holds the new version the moment it's approved. An environment that was already behind stays behind until its next update, which carries the stop along with whatever else it was missing. Stopping tracking never deletes anything in Aprimo. The live configuration in your instances stays as it is, and you can start tracking the item again later whenever you like.

From then on Mochi leaves that item out of deliveries too, including the change set that first brought it in. That makes this the way out when an item can't be placed in an environment and is holding a delivery up: stop tracking it, and everything else can move again. Track it again later and it counts from then on, as if you had just picked it.

Managed by Aprimo

Some items are looked after by an Aprimo feature itself. A field filled in by Aprimo's video metadata extraction, or by its AI face detection, is a good example. Mochi can't tell which items those are and doesn't guess; a person who knows marks them. In Configuration, select the items, choose Managed by Aprimo…, and say why if you like. The note is kept with the mark.

That one click does two things, and both are recorded. Mochi records the mark. Then, if any of the items were tracked, it proposes an ordinary Stop tracking change set, which goes through review like any other. From then on those items stay out of Not tracked, out of Changed, and out of deliveries. You'll find them under a Managed by Aprimo tab on Configuration and on each environment. To unmark one, go to that tab; the item goes back to Not tracked. Marking or unmarking changes nothing in Aprimo.