Now, assign a custom status to forms upon submission or dispatch. Form statuses give enhanced visibility to submissions and will no longer not be confined to simple labels. Creating custom form statuses will achieve a cleaner and more defined workflow and get jobs done efficiently and clearly.
The Basics of Form Status:
- Creating Custom Form Statuses
- Assigning Statuses to Groups and Forms
- Filtering Submissions By Status
- Creating An Approval System
- Status Triggered Workflow Actions
Creating Custom Form Statuses
An example of a custom status, whether you have completed an inspection or something needs to be urgently repaired, would be marking the finished form as "Completed" or "Repairs Needed."
Form Status should not be confused with Dispatch State. The dispatch state is a static label that will remain constant throughout FastField and displays where a form is currently in its lifecycle: Dispatched, On Device, Started, and Completed.
To add a custom status, navigate to the forms section of the portal, click on the Form Status tab and click New Status to add. From this window, name the status, add color, and assign it to user groups and forms from this window
Assigning Statuses to Groups and Forms
Administrators can assign form statuses exclusively to individual forms and or user groups. Please see this article if you have not created a User Group before. In that case, they can be valuable tools for sharing dashboard visualizations internally and creating enhanced workflow options.
To assign a status to a specific User Group use the drop down menu to chose the group or groups.
Internal forms are differentiated when form statuses are assigned exclusively to groups or individual forms. This way, inspection forms, and human resource forms will have a different selection of form status options based on specific data collection instances within the organization. Use the search bar to add individual forms to a status.
For example, you are a property management organization with multiple departments. You have created groups for your FastField users based on their role within the business giving both the inspectors and human resource professionals their group. Within these two groups, you can assign custom statuses unique to each. For example, the inspectors will use a set of custom statuses such as: In Progress or Requires Repairs. The human resource team will use statuses such as Pending Review or Approved.
Filtering Submissions By Status
Once a custom status is created, users can sort submissions by form status in the submissions section of the FastField portal, creating accessible views and additional clarity.
Creating An Approval System
You can create a system of approval by adding custom statuses to your forms, ensuring users adequately handle data and efficiently complete business processes. For example, your company conducts inspections, and you have created a list of statuses that coincide with your business.
The custom status list could include: Requested, In Progress, Pending Review, Requires Repairs, and Approved. You can then create two user groups, inspectors and property managers. Inspectors will only be able to use the In Progress, Requires Repairs, and Pending Review statuses. Property managers will exclusively be able to use Requested and Approved. Adapting custom status to workflow will minimize input error and create a process that efficiently moves jobs in stages.
To Create, Edit, or Delete any Form Status option in your account will need to have the Admin role.
Status Driven Workflow Actions
With the creation of a list of custom statuses, you may include a status change as a condition to trigger for a workflow action. After setting up the name and configuring the actions, lastly the condition will need to be applied. As you can see in the example I have set the action so that whenever a form status is changed to "Requires Repair" there will be a slack notification sent to my team.