Keep records in a data store
A data store is a table the application keeps, such as deals waiting for approval, monthly figures or staffing requests. Workflows write to it with a Record step. Views in Workforce read from it.
Define the fields
Each field has a type, so the store only accepts values that make sense:
| Type | For |
|---|---|
| Text | Names, notes and descriptions |
| Money | Amounts, each in a set currency |
| Number | Counts and quantities |
| Choice list | One of a fixed set of values, such as a status |
| Date | Dates |
| JSON | Structured data from another system |
Mark the fields every record needs as required.
See who uses a store
Each store lists the workflows that write to it and the people who read it, so you can see what a change would affect before you make it.
Flowstate’s own records
Some stores come from Flowstate itself, such as employees and effort weeks. Workflows can read them, but can’t change them. To change those records, use Workforce. See Workforce.
If something’s not right
- ”… is required and was left empty.” The workflow tried to save a record without a required field. Check the step before the Record step produces it.
- “The amount for … is not in the field’s currency.” Money fields take one currency. Convert the amount first, or use a field in that currency.