Quickstart: build from scratch

Build your own application from scratch: a table of your own, a rule that reacts the moment a record changes, and a workflow that runs a longer process for you. This is the orientation; the click-by-click guide lives in the builder guides.

Note

This is an orientation to the flow. For exact screens and field names, follow the links to each component and to the full guides.

What you’ll end up with

A table of your own with automation on top: a rule that reacts the moment a record changes, and a workflow that runs a longer process for you.

The path

1. Create a table. Define your fields. If it should behave like a work item, have it inherit from fl_tasks and it gets state, an activity timeline, and SLA support. See Tables and records.
2. Add a business rule. Pick when it fires, the conditions to match, and what it does, such as set a field, spawn tasks, or start a workflow. Stick to the supported operators; an unknown one quietly never matches. See Business rules.
3. Build a workflow. For anything multi-step, build a workflow and dry-run it first. The dry run shows each step’s outcome without touching anything outside the platform, so you can preview safely. See Workflows.

You know it worked when

Changing a record on your table fires the rule under the conditions you set, and the workflow’s dry run shows each step’s outcome.

Now do it

• Read the full step-by-step in the builder guides.
• Understand inheritance in Tables and records.