Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Lead:  Liav Nadler

Table of Contents

...

A form is a collection of input fields which allows users to enter data that is then sent for further processingto be stored, and then retrieved and updated as needed.

Forms may appear:

In the main workspace

Inside a Dialog dialog popup

Image RemovedImage Added

Usage & Behavior

Structure

...

  • the input area, which may contain any set of input fields, including Text text fields, Drop drop-down menus, Checkboxes checkboxes, Radio radio buttons etc.

  • the action area, which consists of:

    • A submit buttonsbutton, such as Save, Create, or Update.

    • an additional Cancel button, when shown inside a container.

    • additional actions, if needed.

...

For the usage and behavior of inline inputs, see Inline Inputs.

  • Where possible, field labels will appear above the input field.

  • Where relevant, a red mandatory indicator (*) will be shown next to the label.

  • Where relevant, a help icon will appear next to the label (aligned to the right side of the field, if possible).

...

  • The action area will always be visible.

  • Main action buttons are aligned to the right. If needed, buttons for secondary actions such as clear or delete will be aligned to the left.

    Image RemovedImage Added
  • Where the form takes up the entire workspace, the action area will appear at the top of the page. (See Examples below).

  • In all other cases, the action area will appear below the form.

    • In widgets within the workspace, the action area will be separated by a horizontal line.

      • If the form does not exceed the height of its container, the action area will appear below the last form field.

      • If the form exceeds the height of its container, the action area will stick to the bottom of the container, allowing users to scroll the form above it.

    • Inside other containers, the action area will appear at the bottom of the container.

...

  • Forms can have two states:

    • Idle / Saved. Applies when entering a form or after clicking the Submit button. In this case:, the Submit button is disabled.

    • exiting the form will not save it.

    • Edited. Applies after making changes to the form but before clicking the Submit button. In this case:

      • the Submit button is enabled.

      • attempting to leave the form will trigger a confirmation message. See Validation and errors below.

...

  • Clicking the Submit button:

    • sends the data for further processing. (For error handling see Validations and errors below).

    • In the workspace, if the form was submitted successfully:

      • a success Toast will appear, and

      • if the form was triggered from a parent page, the user will be redirected back to that page.

    • For forms inside containers, refer to the corresponding pattern documentation . For (for example, clicking the Submit submit button in a Dialog dialog popup, will close it).

  • Clicking the Cancel button, if exists, will:

    • trigger a confirmation message, if the form is in the Edited state, and then

    • close the container (unless pinned) without saving the data.

...

  • For input-specific validations see Field Validation.

  • A form cannot be submitted if one or more of its fields are in an error state. Here is a typical flow:

    • When entering a form, the Submit button is disabled. (The Cancel button, if exists, is always enabled).

    • On updating any field, the Submit button is enabled.

    • If there is an input error, the Submit button will be disabled again. Only after all errors have been resolved is it enabled again.

    • After clicking Submit, the button is disabled again.

  • In case the user tries to navigate away from a form after updating one or more fields or while there are errors:

    • a message popup will appear. (See the Common messages repository for wording).

    • the user will choose to either keep editing the form or leave and discard their changes.

...

Unless otherwise specified, see our general compliance information in Fundamentals - Accessibilitytext highlight when using a keyboard + using arrows when in edit mode (left, up or home to set the insertion point at the beginning; right, down or end to set it at the end).

Design

Zeplin link

Screen thumbnail

<<Short Zeplin link. You
Use this
>>

<<Screen with 200 width>>

...