Action Forms and View Forms

Action Form

The Action form is the version of the business process form that opens when the recipient accepts the task implicit in the form. As a business process arrives at each step in a workflow, Unifier notifies the appropriate users if they are involved in the step. When the users open the notification, the application displays a view-only form of the step task. If the user accepts the task, the form becomes an action form where the user can enter or edit information and attach additional documents.

View Form

The View form is the read-only version of a business process form that appears when the recipient first opens the form. The fields cannot be edited. A View form may also be used when the designer does not want the user to be able to change the data on the form.

Note: Business process forms can only be printed from a View form.

To accommodate both view-only and action forms for a workflow step, you will need to create both forms and then specify which form should be used at the step's entry and which form should be used when the user accepts the task (see Adding Steps to the Workflow).

A quick way to create the action and view-only forms is to copy one form from another and change the fields to "editable," "required," or "read-only" as necessary. You can also add or remove fields as appropriate for the form.

You (the designer) can create a View form so that based on the user persona, the data that is seen in the form can be controlled at runtime.

For a non-workflow business process can have multiple view forms. This is so you can create multiple view forms and for each of the view forms you can decide what data can be put in the form.

Note: Previously, a non-workflow business process had only one form that held all the data. This form was the Action form.

A non-workflow BP design (in uDesigner) will be similar to a workflow BP design, except that a non-workflow BP can only have one Action form and there will be no workflows.

You can create View forms for:

Non-workflow BPs regardless of the Type
Non-workflow BPs existing at both Project and Company Level
Non-workflow BPs of both Single Record and Multiple records
Note: Unifier validations are applicable to all of the above.

If you have any custom data elements in the View form, those custom data elements must be added to the Action form.

Last Published Monday, June 3, 2024