Last time, I mentioned that one of the best online form builder tools is Cognito Form. It is an underrated platform. Its flexibility allows for multiple use cases! I discovered that you can use Cognito Form to create a multiple approver workflow. It is actually easy! This tutorial is made for Cognito Form users making a single form go through multiple approvers.
Here, we have a requisition form (ex. An employee wants a certain equipment or supply purchased) which would be passed on to 3 levels of approvals in the workflow.
A team member would fill out the form, which would be passed to Approver Number 1. Then if approved, the same form is passed to Approver No. 2 for input and comments, and finally to Approver No. 3. Each Approver receives an email notification when a form has been assigned to them. For security purposes, specific fields should not be editable by the Approvers, and sepcific fields should only be seen by Approvers in the workflow upon getting the form.
With a flexible tool like Cognito Form, there could be several ways to do this, however, I found one that was the simplest and most efficient to execute. I used Cognito Form’s calculations feature, and the
What is the calculation feature?
If you’ve been using Cognito Form at its fullest, you should be familiar with this feature. But in an nutshell, the calculations feature can be used to compute field values, control visibility of sections and fields, and implement complex data validation. Read more here.
There are dozens of formulas you can use in the calculations field, but the Entry.Version formula isn’t on any support articles on Cognito Form (as of writing this article) so I found it by accident.
Here’s how you can use this formula for multiple approvers.
How does Entry.Version work?
- When a data in the form is first created into the database, the entry’s version is one. This will be
- When the same entry is edited or updated, this becomes a new version of the entry. Hence, this will be
- If the same entry is edited or updated again for the second time, this is now a new version, hence, Entry.Version=3. And so on and so forth.
Create your form as usual. Make sure to include the fields that will be filled in by the Approvers (ex. Approver #1, #2, #3). Remember their parts in the workflow.
How to make fields read-only for Approvers:
1. Click on the field(s) that should not be editable by the Approvers. On the left panel, go to Read-Only.
2. Click on When. On the pop-up window, go to Advanced Editor tab.
3. Inside the text box, type in
4. Click Save.
How to show fields only for Approvers:
1. Click on the fields that will only display by designated Approvers in the workflow. On the left panel, go to Show This Field setting.
2. Click on When. On the pop-up window, go to Advanced Editor. Inside the text box, put in
=Entry.Version=3, depending on the part of the workflow). This means that this field will only be displayed when the form is passed to the appropriate Approver in the workflow.
4. Click Save.
How to enable notification for Approvers:
1. Click on Submission Settings. On the left panel, turn on Notification Emails.
2. On the popup, configure the email addresses, subject and message of the email notification. On the left side, go to Send When Updated. Click When.
3. On the Basic Editor tab, select the last field entered by the previous Approver. On the dropdown, choose is filled out. Then click save. The email notification is triggered when the field is filled out by the previous Approver.
4. Save your form and do not forget to test before using the form.
- Understand and use
Entry.Versionformula in the calculation fields.
- Maximize the Read only…When or Show this field…When features for fields. For notifications, use Send When Updated feature.
- Test, test, and test the form before officially using.
There you have it. If you have any questions on the process, feel free to reach out or comment below.
Leave a Reply