FlinkISO generates Add, Edit, View, Index and reporting pages from a saved form definition. The most important design decision is how each group of information relates to the main record.
Main FormOne primary record, such as an audit schedule, complaint or equipment register entry.
Child FormRepeatable rows stored inside the parent workflow, such as checklist items, actions or calibration readings.
Child Document FormA separate controlled record with its own document and form, linked back to the parent.
Choose the correct form type
| Need | Use |
|---|---|
| A single set of fields for one record | Main Form |
| Several rows that belong only to the parent record | Child Form |
| A related record that needs its own document, form, permissions or history | Child Document Form |
| Shared lookup values such as suppliers, employees or equipment | Master Form or a link to an existing master |
Plan before building
- Write down the purpose and the single record represented by the main form.
- Separate reusable master data from transaction data.
- Identify repeatable groups and decide whether each is a Child Form or Child Document Form.
- List the statuses, approvals, tasks, notifications, reports and PDF output required.
- Group fields into a clear layout and add tabs only where they make a long form easier to use.
What the API generates
The Form Creation API builds the database table and consistent Add, Edit and View pages from the saved JSON definition. It also supports field layouts, tabs, child placement, table permissions, data-entry settings, charts and panels, email triggers, tasks and custom JavaScript where configured.
Empty child rows are ignored. Once a user starts a child row, its required fields are validated. If the row is inside a tab, the affected tab is highlighted when validation fails.
Build in a safe order
Create any required master forms first, then the main document form, followed by Child Forms and Child Document Forms. Configure the generated module only after the form relationships are correct.