Child pages
  • Showing action progress messages in forms
Skip to end of metadata
Go to start of metadata

Ready for implementation


Magnolia informs the user, if an action triggered in a form (e.g. a multi-step form) or triggered as the result of data collected in a form has started, on its progress and as soon as it has ended.

Concept, general character and basic properties

You can find all of the above on the main page defining action progress messages. All the ideas sketched there apply for notifications showing such messages in forms as well. In fact, it is imperative that all notifications for these type of messages look and act the same across all interfaces they are being used in.

Concept for action progress messages in forms

This concept extends the basic concept for action progress messages in Magnolia 5.

There are two situations, in which action progress notifications may get shown:

  • an action is triggered after all data has been collected in a single or a multi-step form
  • an action is triggered inside a form to retrieve data used in the form again

If an action is triggered after user input has been collected, the action progress notification generated by the action is not shown by the form or dialog. Instead, the form is first dismissed and the interface the flow returns to takes over again. It is this interface which is responsible for showing all action progress notifications.

If an action is executed while user input is still being collected - so in between two steps of a multi-step form or in order to retrieve data used by a simpler form -, the action progress messages are shown in a notification bar at the top of the form as is the case when validation messages are shown. The bar moves all form elements down enlarging the form while doing so, if required. Note that you may alternatively use intermediate "screens" or pages showing only a notification, if appropriate. This might be a better solution in cases where still showing and disabling existing controls turns out to be difficult or would lead to a confusing interface.

If an action fails or has to warn the user, it must use the error or warning validation notifications designed for forms. Any visible action progress notification must be dismissed before the validation message shows.


  • No labels