|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Relate
|
|
This issue relates to:
|
|
SAK-7670
Creating: Notification of items with release dates should be at release time
|
|
|
|
|
KNL-62
Create Delayable Events
|
|
|
|
|
|
This issue is related to:
|
|
|
SAK-15981 Moving a resource loses the notification status
|
|
|
|
|
KNL-148
Delayed notifications should be sent as the user who initiated the action
|
|
|
|
|
|
|
There are some subtleties in the delayed events behaviour introduced in KNL-62 / SAK-7670, viz.:
1. The UI in Resources is geared around immediate notifications, so there are some subtleties like if you create an item with a future release date and notification, then revise the item with notifications off, then when the content.available event is posted, a notification won't be sent, because the "desired notification" state isn't persisted in the actual content item.
2. When the delayed notification is sent out, it's sent as the system name rather than the user who triggered the notification, because the email notification code is looking at the current session user.
|
|
Description
|
There are some subtleties in the delayed events behaviour introduced in KNL-62 / SAK-7670, viz.:
1. The UI in Resources is geared around immediate notifications, so there are some subtleties like if you create an item with a future release date and notification, then revise the item with notifications off, then when the content.available event is posted, a notification won't be sent, because the "desired notification" state isn't persisted in the actual content item.
2. When the delayed notification is sent out, it's sent as the system name rather than the user who triggered the notification, because the email notification code is looking at the current session user.
|
Show » |
|
Task
/**
* Resends a notification using the bits of data pulled from the original {@link Notification}
* and {@link Event} objects passed into {@link notify(Notification, Event)}. Specifying the
* bits of information to be used allows notifications to be partially serialized and delayed to
* run later. This becomes prominent when sending out emails to unavailable resources.
*
* @param notificationId
* ID of the original notification.
* @param resourceFilter
* The resource filter to be used.
* @param eventPriority
* The priority level of the event.
*/
public void reNotify(String notificationId, String resourceFilter, int eventPriority, Event event)