FormWork evaluates form rules on the server. An embedded form and a custom application using the API share the same calculated values, conditional logic and validation. Your interface collects input; the form engine decides what the current answers mean.
Example: a quote that depends on several answers
Imagine an accountancy quote that asks about business structure, turnover and selected services. A useful implementation separates three concerns:
- Inputs: collect the business facts and service selections in typed fields.
- Rules: calculate a quote from those answers, show additional questions only when relevant, and validate required details before submission.
- Result: show the calculated quote, then use the submitted result in the team’s review stage or an automation.
Changing a displayed total in a browser is not a substitute for changing the inputs that the server accepts. Keep the pricing rules in the form and let the server validate the entry.
Our accountancy services quote demonstrates this pattern with a fictional practice. It is an example, not a customer result or an accounting recommendation.
Rules are expressions, not arbitrary backend code
Use calculated values and defaults to derive values, conditional logic to control what shows, and validation to constrain answers. Conditions use the same operators in conditional logic, validation and automations. A default can also look up a value from a data table, such as the price of a chosen product.
When a rule needs more, an automation that runs while someone fills in the form can calculate, look up records or call a web address, and its results show straight away. These instant automations are limited to quick steps so the form stays responsive. Other business systems can be reached through API connectors.
Server-side processing requires a connection to the hosted service. It does not provide offline evaluation, and it doesn’t remove the need to write and test your rules. For a custom interface, handle validation responses and loading states deliberately.
Keep rules and old entries understandable
Rule changes go live when you publish a new version. Entries keep the questions, conditions and validation of the version they were started on, so a new calculation doesn’t silently redefine the form behind an older entry.
Start with the quick start, inspect the REST API, or compare the full product capabilities. For the reasoning behind this design, read why FormWork processes everything server-side.