We have implemented Next Experience & our end users are trying to use the Notification Preferences experience to apply schedules. There are two places to apply a schedule:
1. at the notification level - the user can select the down arrow to view the channels and then click 'schedule' to apply a schedule. In that place, they can only select from existing schedules that are on the sys_calendar table.
This functionality seems to be working once we created a few calendar entries that meet our organization's needs.
2. from their delivery channel - the user can select 'edit' and then select a schedule to apply. the choices are from the cmn_schedule list, with apparently no reference qualifier. That means they have every schedule entry - be it roster, rotation or individual on-call user. the names are not explanatory of what the schedules are and they do not seem to work anyway.
My question is - has anyone else encountered this and how did you address it? product documentation does direct end users that they can update their preferences for schedule at both the notification and delivery channel level. But the documentation for administration of those schedules is not updated to reflect Next Experience.
The Notification Preferences experience is locked down and i would prefer not to customize.
Hi Chris,
Sorry, no, I did not. My solution was to create three standard schedule entries on sys_calendar (24x7, business hours, off hours/weekends) so that ITIL users could then effectively use next experience notification preferences to create and save a personal filter preference at the notification level.
If I ever get back to this issue - i'd be looking to try to put some kind of reference qualifier on the delivery channels schedule choice list to limit choices to valid options. We faced the same issue with On-Call>My Preferences when we implemented Notify - and i was able to add a reference qualifier to dictionary entry to limit available choices
Karen
This is what we are using.
