...
| Info |
|---|
| icon | false |
|---|
| title | Best practice |
|---|
|
| Multiexcerpt |
|---|
| MultiExcerptName | Don't use tasks if you don't have any human activity in your workflow |
|---|
| Don't Do not use tasks if you don't have any human activity in your workflow. Tasks and Pulse notifications are great for humans but unnecessary for operations that only involve the system itself. |
|
...
A task is an object that you create using the
| Javadoc |
|---|
| 0 | info.magnolia.task.TasksManager |
|---|
| className | info.magnolia.task.TasksManager |
|---|
| renderType | asynchronous |
|---|
|
. You can send the task to a list of users or to a list of groups. The recipient can assign the task to himself. Other recipients can see who owns the task and its status when they go to the Pulse.
...
Start by giving the
| Javadoc |
|---|
| 0 | info.magnolia.task.Task |
|---|
| className | info.magnolia.task.Task |
|---|
| renderType | asynchronous |
|---|
|
a name. The name is unique for the type of task you are creating and acts as a reference to the task definition in the registry.
...
Changes to task status can be tracked by registering a
| Javadoc |
|---|
| 0 | info.magnolia.task.event.TaskEventHandler |
|---|
| className | info.magnolia.task.event.TaskEventHandler |
|---|
| renderType | asynchronous |
|---|
|
to the system event bus.
...
The simplest
| Javadoc |
|---|
| 0 | info.magnolia.task.definition.TaskDefinition |
|---|
| className | info.magnolia.task.definition.TaskDefinition |
|---|
| renderType | asynchronous |
|---|
|
needs the following properties:
...
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 |
|---|
| 0 | info.magnolia.ui.admincentral.shellapp.pulse.task.DefaultTaskDetailPresenter |
|---|
| className | info.magnolia. |
|---|
|
See T above for | ui.admincentral.shellapp.pulse.task.DefaultTaskDetailPresenter | | renderType | asynchronous |
|---|
|
. See Task view for its functionality.
Most likely the task data you want to display in the Pulse can be rendered with the DefaultTaskDetailPresenter. But in case the default presenter is not sufficient you can implement your own presenter and have it render whatever view is needed.
To implement a custom presenter, extend or use
| Javadoc |
|---|
| 0 | info.magnolia.ui.admincentral.shellapp.pulse.task.definition.TaskUiDefinition |
|---|
| className | info.magnolia.ui.admincentral.shellapp.pulse.task.definition.TaskUiDefinition |
|---|
| renderType | asynchronous |
|---|
|
instead of
| Javadoc |
|---|
| 0 | info.magnolia.task.definition.TaskDefinition |
|---|
| className | info.magnolia.task.definition.TaskDefinition |
|---|
| renderType | asynchronous |
|---|
|
and add a
presenterClass property with a custom implementation of the
| Javadoc |
|---|
| 0 | info.magnolia.ui.admincentral.shellapp.pulse.task.TaskDetailPresenter |
|---|
| className | info.magnolia.ui.admincentral.shellapp.pulse.task.TaskDetailPresenter |
|---|
| renderType | asynchronous |
|---|
|
interface to the configuration.
...