What's new ·
Phased tables: simple requirement rules and defined pathways
Mandatory fields charged according to the phase, path mapping between phases, and display conditions in the table schema.
By Lucas Marchon, Founder at BrainChat
Phased processes used to have two requirement rules that sometimes conflicted. Now there is just one, and the field's position in the form determines when it is required.
A single requirement rule
- The asterisk marks the mandatory field.
- The phase where the field appears in the phased form determines when it becomes required. "Signed contract" is only required in the contract phase, not at registration.
Path mapping
Define which phases a record can move to from each phase. Tried to skip a step? The system warns you and shows the button to move along the correct path.
Display conditions in the schema
"Show this field only when…" is located in the table schema and applies everywhere the field appears, such as the form, the record card, and Studio.
Separate registration and process
Customer registration in one table and the sales process in another, linked by a connection. The customer exists only once, even with multiple processes.
Related
- Record card with field rules and layered navigation: the first field rules.
- Revamped record card, with phase arrows and conversation in the center: the phase bar that shows the path.