What Mochi tracks
Mochi Deploy tracks your Aprimo configuration: the settings that shape how everything else works. Here's what that covers.
When you open an environment, Mochi shows you the configuration it can track, grouped by kind. These are the building blocks admins set up in Aprimo:
| Kind | What it covers |
|---|---|
| Content types | The shapes of the things you manage in Aprimo, and the fields they carry. |
| Fields | The individual field definitions that hold your metadata. |
| Field groups | How related fields are gathered together. |
| Classifications | The category trees you organize things into. |
| Rules | The configured logic that shapes how Aprimo behaves. |
| Settings | Instance-level settings that tune how Aprimo works, along with the categories and definitions that describe them. |
| File types | The file formats Aprimo is configured to recognize. |
| User groups | The groups used to organize people and permissions. |
| Languages | The languages your instance is configured for. |
If a tracked item points at something not on this list, or at a piece of configuration Mochi isn't tracking yet, that shows up as a broken reference so you can decide what to do.
What a check can read
A check reads the same things. A configuration check names an item of any kind above by its name, and one of its attributes: whether a field is required, its data type, its label, the fields a content type registers, the options in a list, whether a rule is on. The builder lists the attributes Mochi has seen on each kind, and once a kind is tracked a check saves only with one of those. Where an attribute points at another item, it reads as that item's name. Leave the attribute as the item itself and the condition is about whether the item exists.
A record check finds records with an Aprimo search and reads these on each one:
| On the record | What it reads |
|---|---|
| A field's value | Named by the field's label or its system name. Option lists read as option names and classification lists as paths, so you write what you'd see on the record. |
| Its classifications | The paths the record is filed under, like /Public/Web. |
| Its status, content type and title | As Aprimo reports them. |
| When it was created or last changed | Dates, so “is more than 2026-06-01” means from that day on. |
| Its files | How many it has, and the newest file's extension and size in bytes. |
A condition compares with is, is not, contains, does not contain, begins with, ends with, is less than, is at most, is more than, is at least, is one of, is not one of, is between, is set or is not set. Text comparisons ignore case. On a list, such as a content type's registered fields or a record's classifications, contains means the list has that entry.
A check holds up to 100 conditions, in groups up to four deep, and up to ten tags. A record check's search can be up to 2,000 characters long, and the newest 500 matching records are read.