Page History
...
Magnolia uses info.magnolia.ui.admincentral.shellapp.pulse.task.action.ResolveTaskAction inside the Tasks app for this step. It allows you to define a decision inside the configuration which is mainly used for approving or rejecting a publication.
...
| heading | 0 |
|---|---|
| multiple | false |
| enableHeadingAttributes | false |
| enableSorting | false |
| class | m5-configuration-tree |
| enableHighlighting | false |
...
| Mgnl f |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl p |
|---|
...
| Mgnl p |
|---|
...
| Mgnl p |
|---|
...
After resolving the task using the ResolveTask action the result map contains only one entry with the configured decision.
...
Every task type needs a unique name. The name is used to read the task definition from the task registry in your module configuration.
...
| heading | 0 |
|---|---|
| multiple | false |
| enableHeadingAttributes | false |
| enableSorting | false |
| class | m5-configuration-tree |
| enableHighlighting | false |
...
...
| Mgnl f |
|---|
...
| Mgnl f |
|---|
...
| Mgnl n |
|---|
...
| Mgnl p |
|---|
...
| Mgnl p |
|---|
...
| Mgnl p |
|---|
...
The simplest
| Javadoc resource link | ||||||
|---|---|---|---|---|---|---|
|
...
Use a message view configuration to define which fields of the task object are displayed to the user. You can use a dot notation such as content.groceries to reference fields from the content or result map. In the same fashion, you can configure your actions, including availability and action bar mappings.
...
| heading | 0 |
|---|---|
| multiple | false |
| enableHeadingAttributes | false |
| enableSorting | false |
| class | m5-configuration-tree |
| enableHighlighting | false |
...
| Mgnl f |
|---|
...
| Mgnl f |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl p |
|---|
...
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
Task presenter
A task presenter is started when a user opens a task to see its details. The presenter builds the form and action bar which are displayed to the user in the browser. Magnolia provides a
| Javadoc resource link | ||||||
|---|---|---|---|---|---|---|
|
...
To implement a custom presenter, extend or use
| Javadoc resource link | ||||||
|---|---|---|---|---|---|---|
|
| Javadoc resource link | ||||||
|---|---|---|---|---|---|---|
|
presenterClass property with a custom implementation of the | Javadoc resource link | ||||||
|---|---|---|---|---|---|---|
|
...
| heading | 0 |
|---|---|
| multiple | false |
| enableHeadingAttributes | false |
| enableSorting | false |
| class | m5-configuration-tree |
| enableHighlighting | false |
...
| Mgnl f |
|---|
...
| Mgnl n |
|---|
...
| Mgnl p |
|---|
...
| Mgnl p |
|---|
...
| Mgnl p |
|---|
...
| Mgnl p |
|---|
...
In your implementation, you can access the task object as well as its definition using injection:
...
The tree below shows the default setting for the archive action (the definition class is info.magnolia.ui.admincentral.shellapp.pulse.task.action.ArchiveTasksActionDefinition) with the superuser role set to access this action:
...
| heading | 0 |
|---|---|
| enableHeadingAttributes | false |
| enableSorting | false |
| class | m5-configuration-tree |
| enableHighlighting | false |
...
Node name
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl p |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl p |
|---|
...
| Mgnl p |
|---|
...
| Mgnl p |
|---|
...
| Mgnl p |
|---|
...
| Mgnl p |
|---|
...
| Mgnl p |
|---|
...
| Mgnl p |
|---|
...
| Mgnl p |
|---|
...
| Mgnl p |
|---|
...
| Mgnl p |
|---|
...
To allow bulk actions for other users, add their role names from the list of default roles as the properties and values of the roles subnode.
...
Overview
Content Tools