Blueprints

A blueprint defines how one category of case is handled: who it is assigned to, how it routes, and what shows up on its case page. Every case belongs to exactly one blueprint.

---

​

General settings

​

Automatic assignment

Automatic mode reveals “Assign to users with fewer than N cases of the current blueprint assigned to them”. Only officers currently online in the console are considered. When the whole assignee pool is at or over the threshold, new cases queue unassigned and are pulled automatically as soon as an officer resolves a case or comes online.

​

Escalation and transfer

Escalation moves a case to a fixed target blueprint (its queue, its content configuration) in one action. Case transfer instead lets an officer pick any active blueprint of the same application to move a case to. Both are hidden from the case page unless the current blueprint enables them, and both are blocked server-side (400) if attempted while disabled. A blueprint cannot reference itself as its own escalation target or 4-eyes checker.

​

Connected sources

A blueprint’s right rail lists:

• Case creation sources: AML configs, transaction rules, and workflow nodes currently routing new cases into it, with shortcuts to each one.
• Receives escalation from: other blueprints whose escalation target points here.

​

Presets

Install any of the four built-in presets from the Blueprints pill’s presets gallery. Installing copies the preset into your application as a fully editable blueprint, you can then change any setting freely without affecting the catalogue. Installing is idempotent per preset, so re-installing an already-installed preset is a no-op. None of the presets pre-configure assignment, escalation, 4-eyes, or transfer, those routing decisions are always yours to make per blueprint.

​

Case content

The Case content tab controls which tabs and fields appear on the case page, as six togglable sections: A blueprint with no sections enabled still shows the case Overview tab, just without the extra content blocks.

​

Deleting a blueprint

Deleting a blueprint always succeeds and does not touch its cases: existing cases keep their blueprint reference, and its settings (content sections, escalation, transfer, 4-eyes pairing) continue to apply to them. A deleted blueprint no longer appears in blueprint lists and can no longer be chosen as a transfer target. If a maker blueprint is deleted while one of its resolutions is pending 4-eyes approval, a rejected resolution leaves the case on the checker blueprint instead of returning it. To wind a blueprint down cleanly, transfer its active cases to another blueprint before deleting it.