Magnolia 5.6 reached end of life on June 25, 2020. This branch is no longer supported, see End-of-life policy.
The Pulse is Magnolia's message hub. Users communicate with each other and the system using the Pulse. Messages in the Pulse provide users with relevant runtime information about the system.
The Pulse has two tabs:
The select-all checkbox in the Pulse is enabled by default and configurable:
Magnolia 5.6.2+: If the actual number of messages/tasks stored in the system is causing performance issues, admins can configure a threshold for the maximum number of selected items or completely disable the select-all checkbox. The configuration is possible under /modules/ui-admincentral/config/pulse/selectAll
.
true 150Node Value
enabled | optional default is true Disables the select-all function if set to |
threshold | optional default is 1000 Defines the maximum number of items to be selected. If the total number of items is greater than the configured threshold, an error message will be displayed to the user after clicking the select-all checkbox. |
Messages are displayed to the user in apps using banners. Unlike alerts and notifications, messages are persisted in the repository and can be read later in the Pulse. The system stores a separate copy of the message for each user in the messages
workspace.
There are three types of messages:
In the Messages tab:
Here's are the banners the user sees in the app they are working in.
Tasks make collaboration better. They have a clear status and an assignee. Users can go to the Pulse to see who owns a task and perform actions on it. Magnolia uses human tasks in the publishing workflow. When an editor publishes a page, the system creates an approval task and sends it to the publishers group. Under the hood we use the jBPM workflow engine's user task feature. See also Custom tasks and User tasks in Magnolia workflow documentation.
Unlike messages, tasks are not persisted for each user. Tasks are a single persisted entry shared by different users and groups, so all can see the same task and its state.
Tasks have five states:
Please note that a task may also be Archived . Such a task is not shown in the ALL TASKS tab of the Pulse at all (5.5.4+) or shown with the "–" (dash) marker in the Status column (pre-5.5.4). An Archived
task is still stored in the repository and may be re-opened if necessary.
This is how workflow tasks work in the
Travel demo
. See Default roles, groups and users for more about permissions assigned to each user.