Datatables, Fields & Data

Flows

Flows are now part of your Buzzy app definition and should be defined alongside your datamodel.

Flows describe functional behavior such as navigation paths, branching logic, and lifecycle stages. This context helps Buzzy generate screens and blueprint structure that better match your intended app behavior.

For flow-first requirement design, see:

Datatables - Working with Data in Buzzy

Working with data in Buzzy is done through Datatables: an intuitive and powerful solution that makes designing great apps straightforward. Datatables are used to store data, build forms, collect data, and add interactivity with sophisticated relationship modeling.

Datatables are one core part of your app definition. You can now also define Flows as part of the same app context, so functionality described in flow diagrams works in combination with your brief, datamodel, blueprint, and theme.

This helps you define requirements more completely: flows make user journeys and process states explicit, while datatables define the data structure needed to support them. In practice, this usually leads to better generated fields, relationships, and screen behavior.

New to Buzzy's datamodel? Start with our Buzzy Datamodel Overview for a comprehensive guide to understanding relationships, fields, and how to work with data programmatically.

Please note - Datatables were previously called "Microapps" - some code snippets may still refer to a microapp (e.g. the API end-point microappdata). If in doubt, email support.

circle-info

Note This section documentation may include references to deprecated field types

Table of contents


Last updated