There are numerous features of Process Street that make the platform as useful as it is for managing recurring workflows and processes.
Beyond the ability to create process checklists, features such as form fields, rich media, conditional logic, real-time tracking, and the ability to set up automation with 1000+ other applications, provide a huge amount of value.
In this post, we’re going to take a closer look at one feature in particular: form fields.
An essential component of our software, form fields allow users to safely store important data that can then be automatically passed to and from other tools in your tech stack.
The goal of the post is to show you how you can name your form fields so that they are as effective as possible when used by other team members, as well as suppliers and customers who may be interacting with your checklists.
First, I’ll run through a brief overview of form fields, the various different types, and what value they provide. Then we’ll take a quick look at some typical use cases that will give you a better idea of when they are used, before going through a set of naming best practices with examples.
Let’s get started.