When a user clicks a Transition button, a dialog appears listing all the fields mandated for that transition. The user cannot complete the transition until every mandated field has a value. This is different from a global mandatory field – a Blueprint field mandate is conditional on the specific transition being executed.
You can mandate fields from the primary module and from related modules (such as requiring a line item on a Quote before moving to “Quote Approved”). Fields can be mandated as text, date, lookup, file attachment – any field type supported in the module.
A standard mandatory field (marked required in the Page Layout) must be filled every time a record is saved. A Blueprint Field Mandate is only required at a specific transition point – the field may be optional at all other times. This distinction is important for processes where data is collected progressively as a deal advances through stages.
A Blueprint Field Mandate is a data-capture requirement attached to a specific Blueprint Transition. When a user executes that transition, they must fill all mandated fields before the record can advance to the next state. This ensures critical information is collected at the right stage of a business process.
Yes. Blueprint Field Mandates can include fields from related modules. For example, you can mandate that at least one line item exists in a Quote subform before the ‘Quote Approved’ transition can be completed.
Aaxonix is a certified Zoho implementation partner based in Pune. Architecture-first, no surprises.