Form-Type Screens: Best Practices

Follow best practices, and avoid worst practices, when designing Form-type Screens.


Follow basic form design best practices so your Form-type Screens are easy to navigate and read. Many of these best practices may apply to Display-type Screens.

Use Multicolumn / Table controls to organize the layout and width of other controls.

For each example, the Bad Practice tab displays by default. Click the adjacent Good Practice tab to view the best practice to follow. Design practices that are similar are grouped into the following sections:

Display User Information

Avoid using placeholders for Line Input controls. When users start typing in the controls, the placeholders disappear.

Organize Line Input Controls

When a user navigates through a multi-column Screen, making the user follow a Z-pattern is more difficult for the user's eyes. Users might not even know where to start.

If your form is large, do not use all Line Input controls in one section.

Label Text in Line Input Controls

Avoid text redundancy as shown in the example below.

Select List Controls as Drop-Down Menus

If there are fewer than four options, as a general guideline do not put them in a Select List control as drop-down options. This design requires the user to click twice to commit an action: once to display the Select List control options, another select an option.

Rich Text Controls as Headers

By providing no user guidance for information to enter into the form, users become confused.

Unmasked Line Input controls allow users to introduce errors when entering commonly-used information.

Record List Controls in Scripts

Entering the following Script code for a Record List control without Row IDs does not work as expected such as allowing to edit, delete, or add records.

"form_record_list_1": [
      "first_name": "testfirst",
      "last_name": "testlast"

Last updated

© Copyright 2000-2024 ProcessMaker Inc. All rights reserved.