Rules and calculations
Write your business rules without code, with the same result on every device.
Turn everyday decisions into calculations, checks and clear conditions. DynamicForm helps designers express those decisions in business terms and shows what each rule expects.
Choose your operations
Start with the kind of information your rule uses. The rule builder includes examples, helping designers connect an operation with a business question.
- Numbers: Round values, calculate percentages, check ranges and find averages. Example: Round the adjustment percentage before calculating the adjustment value.
- Text: Check length, contained words, starting characters and patterns. Example: Require a reference that starts with the branch name.
- Dates: Add months or years, calculate age or service, and use weekdays, month ends or hours between times. Example: Set the review date by adding months to the start date.
- Rows: Find totals, counts, averages, lowest and highest values, and the first or last line. Apply conditional totals and any-line or every-line checks. Example: Total adjustment value equals the sum of line values.
Put rules to work
Use the same rule language for calculated values, checks on save, visibility, read-only fields and workflow conditions. This keeps the decision close to the part of the application it controls.
A calculation can total line values while a save check tests whether required information is present. Visibility rules show relevant fields, while read-only rules control when a value can change. Workflow conditions use business terms to choose a route.
A rule that does not work is never saved. The designer explains what is expected, so you can correct the rule before it becomes part of the configuration. See Workflow Configurator for decisions and default paths.
Keep answers consistent
Line totals update as lines change. Sums, counts, lowest values and highest values give the same result on web, phone and server. The server's value is the value stored.
Date calculations and date checks use the company's own time zone. The server decides the result on save, keeping the saved answer tied to that setting. Working-day rules use company and branch holiday calendars.
For Employee Leave, a working-day rule can use the holidays that apply to the employee's branch. Company administrators maintain those calendars, including branch exceptions. See Company Admin for calendar management.
Use related information
Rules can read values from related records up to two steps away. They can use only records the user may see. For example, a rule can read a customer's minimum shelf life from a related record.
Check live data at save through a strictly limited, read-only check of the application's own data, requiring separate permission.
Update related records after a save or step, only where the user may edit the linked record.
Review rule cost
Every rule receives a cost class at design time: Light, Moderate or Heavy. This makes the expected processing cost visible while the designer is choosing how to express the rule.
Heavy rules need explicit, recorded acceptance. Rule timings are monitored, giving administrators information for reviewing rules after design. See Performance for the cost review.
Explore DynamicForm
AI Core · Screen Designer · Rules and calculations · Configuration document · Compliance · Company Admin · Applications · Security and identity
Updated 16 November 2026