Connecting the Workflow and Forms

Connecting the Workflow and Forms

Once forms have been created, they can be added to the workflow by configuring the “Form” statuses. Adding the forms to the workflow statuses will enable the process to present the forms to the user at the proper time throughout the business process.

Forms

Selecting the “Form” button opens the  “BP Visibility And Validation” window which contains a radio list with two options: “NoCode” and “MVC”.

 The “MVC” option allows the user to select forms from the low code platform. These can be more complex and have controllers configured, which can contain logic. Although the more complex option, it can reduce the amount of logic statuses needed in the workflow.

In this example, the “MVC” option has been selected. The “MVC View” is configured to a preexisting view of an “MDMWorkbench” and the “MVC Controller” is configured to “ItemRequests”. This will provide the user with a form view to create a new item.

However in the no-code context, the no-code platform provides the basic tools for you to create and select your forms to add them to the workflow. When the “NoCode” radio button is selected the “BP Visibility And Validation” window displays a “Form” dropdown which contains all the existing forms you have added to your “Business Process Home” page.

Once a form is chosen for the status, the form will populate in the “BP Visibility And Validation” window displaying all the form groups and fields.

Clicking the circled “Form” button opens the “BP Visibility And Validation” window where the form can be selected. Once the form has been chosen, in this case the “StartRequest” form, it displays in the window.

The “Validation and Visibility” settings can then be configured using the checkboxes provided in the form.

For each form group:

  • Hidden: When this checkbox is checked, the form group will be hidden from the view.
  • Depending who is viewing the form at various statuses, they may only need to be shown certain groups. For example, if the marketing team is viewing a form, the finance group may be hidden for them.
  • Expanded: When this checkbox is checked, the form will automatically display fully expanded by default meaning the header and all of the fields will be visible. If the box is not checked, the form will be collapsed by default meaning only the header is visible at first.
  • Enabled: When this checkbox is checked, the form will be fully functional and the fields will be able to be filled out. If it is unchecked, the form will be shown, but the fields will be grayed out and not able to be configured.

For each status exit:

  • Required: For each property there will be a “Required” checkbox for each action/exit the status has. When the “Required” box is checked, that form field must have a value in order for the corresponding action button to be clicked.

For example, in the case of the “StartRequest” form, if the “New Item Name” and “Description of the Material” fields are both required in order for the user to select the “Approve” button, but are not needed to “Deny” the request, only the “Required for Approve” boxes will be checked.

In the “BP Visibility And Validation” window the “StartRequest” form is selected and the “Required for Approve” checkboxes have been marked for the form fields “Description of the Material” and “New Item Name”. This means that the form will not submit if the user leaves either field blank and tries to select the “Approve” button.

Once the checkboxes have been selected, the settings can be saved by clicking the “Save” button.