Inside the platform: capabilities, architecture and security.

Model and flow separated. The model defines the master data (the golden record); each model can have several registration flows, each with its own steps.

Field types: text (line or area), multi-value text, multilingual text, number, yes/no, list and multi-list, reference and multi-reference to other models, table (rows within the record), date, date and time, link, file (single or multiple) and phone.

Field attributes: name, help description, width in the grid, default value, placeholder, integration variable, mask, required, visible, editable and lock after filling.

Reusable sections. A field section is assembled across several models and flows, which keeps the same semantics throughout the company; describe the process and the Architect's ADAM creates the domain, model, sections, fields, flow and steps, which you review.

Attribute and fill-in rules. They show, hide, make required or editable, or apply a mask according to conditions; or calculate a field value with expressions (arithmetic, concatenation, conditional, lookup in another model, uppercase/lowercase).

Event and model rules. When a step changes state, they send an email, trigger connector automation, invite a third party to fill in a step or open a linked record; plus quality assertions with error or warning severity, where an error prevents the record from being published.

Rich conditions and masks. Nested AND/OR, regular expressions, comparison with the current user or department; masks for public registry identifiers and postal codes, plus custom masks, with key fields that prevent duplicates at the source and show the collision live on the registration screen.

Test before it takes effect. Every rule is tried against real records and sample entries, on screen or through ADAM; test environments let you design and test rules outside production and promote them with review.

Named, ordered steps, with no technical limit, and conditions to skip steps.

Approval steps, with the option to prevent whoever edited the previous step from approving (segregation of duties) and return for adjustment; permissions by department, flow and step: view, edit, approve, advance and publish, with section-level visibility in the models.

Row-level filters: for example, only records from your own department or created by the user.

Deadline per step in business hours, with a working-hours and holidays calendar, time remaining on screen and a work queue sorted by urgency.

Email invitation with a secure link that opens a specific step for someone outside the organization; it can be sent automatically by rule.

The guest fills in with the same validations and rules as the internal flow.

It is recorded who requested, who opened and who completed, and when.

See supplier qualification → · See customer onboarding →

Individual registration, bulk upload and bulk update by spreadsheet, all through the same flow rules. The spreadsheet template can come pre-filled with current data.

Deactivation and reactivation controlled per record.

Complete, versioned history of every record.

All three entry methods go through the same rules and the same configured approval flow.