Stage data configuration
Besides its type and settings, a stage can carry data configuration — technical settings that tell the stage exactly which data to read and how to shape it. These are aimed at implementers; most flows only need a few of them, and the defaults are usually fine.
Each appears as its own card on the stage's details, and most are simple tables you add rows to.
The configuration cards
- Required data — extra data the stage must have to do its job. Each row gives a mapping key (which data to fetch) and whether multiple records are expected.
- Source fields — which fields are read from the source data for this stage, picked from the available execution fields (with an option to skip lazy loading for performance).
- Search fields — rules for finding the records the stage works on, each with a field name and a search column (and matching options).
- Sort tariff group — for calculation stages, sets the order tariff groups are applied in: each row pairs a sort number with a tariff group.
- Invoice rule application — the rules (by number) to apply at this stage, with a blocks manual approval option (also described in Advanced stages).
Data configurations and lookups
Some stages also have a data configurations section, where you map and look up values — for example translating a source value into the value SHIPM8 needs, via a lookup. This is the most technical part of a stage and is normally set up once during implementation.
Data configuration changes what data a stage sees and how it's matched, which directly affects the invoices produced. Change it on a test flow and confirm with a real execution before relying on it. When in doubt, leave these at their defaults or check with your administrator.