Guide · Approval workflows Draft for review

Approval workflows your IT team configures instead of codes

Approval workflows look simple until the exceptions arrive: parallel checks, send-backs, deadlines, different approvers by amount or role. Here is what a configurable workflow needs, and how DynamicForm handles each part.

DynamicForm by AG Studio Ventures · Updated 29 Sep 2026

What a real approval workflow needs

• Steps for people, automatic steps that call other systems, and decisions that route by the data.
• Parallel checks that start together and a merge that waits for all of them.
• Send-back to an earlier step with a compulsory remark.
• Owners by role, by named person, by shared queue or chosen in the form.
• Deadlines per step, working days and escalation of overdue cases.
• A full history of who did what and when.

How it is built in DynamicForm

Describe the process in plain words, or paste it from the requirement document. The platform proposes the steps, routes and owners as a list of changes; your IT team reviews and applies it, then adjusts it on the canvas if needed.

Each step opens a screen, and each section of that screen can be editable, read-only or hidden at that step. A menu item can start the workflow in one click.

Changing a workflow that is already live

Add an approval level, change an owner or add a check by describing the change. The platform proposes only the difference, and it applies once saved.

Questions

Can an approval route depend on an amount or a score?

Yes. A decision step routes the case by any value on the form, such as an amount, a product or a score.

Can approvers work on a phone?

Yes. Inbox, screens and approval buttons run in the Android app as well as in the browser.

Related