Creating a task solution extension
Tasks are created using a solution extension on any business object.
Prerequisites
• Register a solution extension in > .
• Add the solution extension to the business object for which you want to create the notification definition in Field Definer. For example, business object Orders.
• An example solution extension: nl.planon.hades.userextension.examples.TaskBOCreater
. For more information, refer to Creating a task solution extension.
. For more information, refer to Creating a task solution extension.
The solution extension is triggered during the status change when a business object creates a Task.
 | A sample solution extension (source code) is supplied in the install set (..\manual installation resources\planon software development kit\UserExtension\examples). |
For example, create a task on the Orders business object, to notify the user about all the orders that change to 'Administratively completed' status.
To create this task, add the following solution extension along with the parameter mentioned below in Field Definer > Orders > Details > Extensions.
To create this task, add the following solution extension along with the parameter mentioned below in Field Definer > Orders > Details > Extensions.
For more information on the concept of an event-based notification definition, refer to Event-based notification definition.
Solution extension:
nl.planon.hades.userextension.examples.TaskBOCreater
Parameter: UsrAdministravelyCompleted.
The Parameter field contains the system name of the business object status.
| | Note that the solution extension must be first registered in > . The solution extension must then be added to the business object on which the task must be scheduled. |
| | For information on registering and using solution extensions, refer to Field Definer. |
Information displayed when a task is created:
• A task has a reference to the action it must execute along with the reference to the notification definition.
For a description of these fields, refer to Task fields.
Each task undergoes the following five statuses:
• To do - default status.
• In progress – task is picked up.
• Notified – if the notification definition for the task returns a business object instance.
• Executed - if the notification definition for the task does not return a business object instance and no user is notified.
• Executed with errors - task was executed, but an exception occurred in the application that stopped the notification to be sent.