Forms
Forms offer components that enable users to input information into a workflow, which can subsequently be collected and utilized throughout the workflow. Workflow Studio incorporates form data into a workflow through a compilation and publication process, creating a specific type of activity called a "Form activity." Upon publication, Form activities can be integrated into workflows, where Workflow Studio's drag-and-drop property binding capabilities facilitate the transfer of form data to and from other workflow objects during runtime.
Form Components
Form components in Workflow Studio are divided into two categories: Primitives and RBAC Components. Primitives enable the inclusion of simple objects, such as drop-downs, calendar controls, and fields, on a form. Conversely, RBAC Components allow for the incorporation of properties from objects bound to EmpowerID-protected resources on a form. Each of these RBAC components can be employed to retrieve the properties of protected resources for use within a workflow.
For instance, if you need to capture data specific to a workflow initiator with an EmpowerID identity, you can add an RBAC Component for a Person object to a form. This allows you to integrate only the relevant properties (person attributes) into your form design, according to your data requirements.
Form Types
Workflow Studio offers two types of forms for workflow usage: User Input forms and User Decision forms. The choice of form depends on the desired functionality at a specific point in the workflow.
User Input forms – These forms allow users to input information and submit the data back to the workflow for use in subsequent activities. User Input forms appear to any user running the workflow at the point in the process where the form is placed. They can be used anywhere within a workflow and are often the first form encountered. For example, in a workflow that enables users to request resources or other actionable events, you can add a shape derived from a User Input form, allowing users to enter and submit their request details back to the workflow. The workflow then moves to the next step as dictated by the business requirements.
User Decision forms – These forms appear within a workflow when the process requires further user input or approval to proceed. Typically, User Decision forms derive their data from a User Input form and are used when a response to that data is necessary. Based on the User Decision Form Base Activity developed by EmpowerID, these forms offer routing options, create workflow tasks for approvers, and send email notifications about the request to all relevant parties. When a workflow encounters a User Decision Form activity, it enters an idle state until a response or escalation occurs. Continuing the previous example, after a user submits a resource request via a User Input form, you could add a shape derived from a related User Decision form as the next step, requiring a user decision for the workflow to advance.