Form

Form

Form Overview

Forms are one of the main components of a business process, and can be seen on the “Business Process Home” page.

The “Business Process Home” page for the “Finished Good” process with the “Forms” section circled.

The “Form” is the interface that is presented to end users where they can provide details requested during the business process. Any data you enter in the form is automatically saved when you click any of the action buttons. The data is saved to the entity (described in data chapter), and can be manipulated in the Logic (described in the logic chapter).

Form Structure

The form designer gives control over the types of questions end users are asked because the business users can build and design the form in the no-code platform. The questions, design and structure can all be configured by the business user to meet their needs.

Groups and SubGroups

The “Form” is a top level view that holds groups and subgroups. Both of these are holders for properties.

Groups are most often used to divide the form into categories or roles. For example, creating a group for the Marketing team that only holds the related properties. This provides a clear and easy format for end users to know what information is needed by them.

A sample group named “Initiate” with properties: “Proposed Description of Material”, “Primary Business Unit”, “Target Completion Date”.

A sample group named “Marketing” with two subgroups: “Product Hierarchy” and “UOM Conversion”.

Properties

These groups and subgroups will contain property form fields, where the information needed in relation to the request can be entered. Properties can be added while designing the form.  

If a property belongs to a JDE table, it will be preconfigured with the UDC or data dictionary settings.

Properties for a “Custom Attributes” table and for the JDE table “Item Master” (F4101) as seen on the “Form Designer” page

Form Designer Page

All forms are configured on the “Form Designer” page which can be opened from the “Business Process Home” page.

The “Business Process Home” page with the “Designer” button circled

This “Form Designer” page has a drag and drop UI style that allows the business user to configure the forms to request the information needed for that process.

The right side of the form designer displays the form groups, and provides a “+” and “delete” button to create or delete form groups.

Under the group title is a secondary “+” button which will allow subgroups to be created. Subgroups cannot be created if there are fields added to the group. Therefore it is best practice that if subgroups are used, all form fields should be contained within subgroups.

The right side of the “Designer” page displays two groups: “Finance” and “Product Development”, which currently has three existing subgroups. There is a “+” button at the top of the form to create new groups, as well as a “+” button below the “Product Development” header to create additional subgroups.

The “Designer” page. The “MaterialType” attribute is dragged from the properties menu onto the form in the “MDM Pre Edit” group.

The properties are then dragged from the left side properties menu to the appropriate form group.

Each property can be edited to further assist the end user through the workflow. Once the attribute is on the form, selecting the edit icon will open an “edit window” titled “Manage Form Group Properties”,  to customize the attribute.

Once forms are configured on the “Form Designer” page, they can be implemented in a process by adding them to the business process workflow. This will be further explained in Chapter 4: Connecting the Workflow and Forms.

Creating a New Form

Starting on the “Business Process Home” page, a “+” button in the “Forms” header will open a “Add Business Process Form” widget to create a new form.

The “Business Process Home” page for the “Finished Good” process, with the new form “+” button circled

“Add Business Process Form” widget

The “Add Business Process Form” widget provides the “Process Id” which is an automatically generated id number used to reference the form internally. The widget then prompts the business user to enter a “Form Name” and a brief “Form Description”.

Form Field Event

An additional feature exists to create a form field event, which attaches logic to a field in the form that will be executed when the field is filled out.  

The “Initiate a Finished Good Request” contains three form fields. The “Event” button next to the field allows the business user to create an event for that field. The event button will turn green to indicate when an event has been created.

Selecting the “Event” button will open a “Manage Form Events” window, which will list all existing events, and will allow the business user to add an event.

The “Manage Form Events” window prompts the user to select an “Event Type” which defines what triggers the event. For example, a “change” event will occur any time a change has been made to the field the event is for.

A “change” event has been created and is now displayed in the list with a gear icon next to it which allows the user to configure the event logic.

Selecting the gear icon will forward the user to a “Logic Canvas” where the event logic can be created. Creating logic is further explained later in Chapter 6: Writing Logic.