Page tree
Skip to end of metadata
Go to start of metadata

Simple dialog

Use a simple dialog whenever only few data points need to be collected. Its main characteristic is simplicity. It only provides limited ways to organize and group fields.

Characteristics:

  • No tabs
  • Displays only a single form

Complex dialog

The complex dialog allows to collect larger amounts of data than its simple counterpart. The main characteristics of this dialog are that it is capable of handling complex, hierarchical data sets and that it may summarize key settings of some or all of its sub forms.

Characteristics:

  • Multiple tabs (optional), one tab per topic
  • One form per tab.
  • Show all tab displays content from all the other tabs in one go.

 

Light dialog

Light dialogs ask for quick input but do not severely interrupt the user. Use them as an integral part of the task the user is currently working on.

Modality levellight

Characteristics:

  • Collects quick input.
  • Use to:
    • Present a message and confirm
    • Confirm or cancel, for example to proceed with a delete action
    • Rename an item
  • Only makes sense in the context the user currently works in.
  • Only valid in the single session in which they are created.
  • Only displayed to the current user.
  • Displayed modally but does not black out the background.
  • Transient and therefore not recorded in Pulse.

Choose dialog

The target app can also provide a chooseDialog. This is an alternative to the usual workbench view and may be better suited for selecting an item. When a chooseDialog is configured, it is used instead of the workbench view provided by the browser subapp. For example, the Assets app provides a choose dialog for selecting images. The choose dialog looks like a workbench but it also provides a custom action for uploading images from the desktop. The definition is in /modules/dam-app/apps/assets/chooseDialog.