
Callable object design requires specialist knowledge of the services and applications that are exposed. It is covered in detail in Exposing Applications as Callable Objects .
For a particular process or action, you can create only one due date notification. The date of this notification is displayed in the GP worklist in the portal. The number of all other notifications set before the due date is not limited.
The item's design time opens.
Adding Notifications
You use this type of notification whenever you want to inform a user that a task has been assigned to him or her. The task appears as a worklist item in the portal.
You use this type of notification whenever you want to inform a user that a task has been removed from his or her worklist and assigned to a different user.
To assign a callable object to the due date or to the notification, use Choose, select the callable object and choose Select.
When you create On Assign or On Deassign notifications, an additional parameter structure (NOTIFICATION PARAMETERS) is automatically created in the action context, which you can use in the consolidation phase. It holds important information about the activity and its processor, such as:
The new due date or notification appears in the notification's list.
To determine whether a notification is a due date, check if the Due Date indicator is enabled.
Editing Notifications
To be able to do that, enable the Allow changes at instantiation indicator.
This step is available only for processes.
Parameter mapping is preserved, unless the parameters of the new object version are different. In this case, you need to define mappings again.
Deleting Notifications
The process or action must be executed prior to the due date that you have configured.
If it does not reach status Completed before that date, the selected callable object for notification is executed.