Be able to configure Service policies to associate specific No-service periods instead of the all-or-nothing approach that exists today.
Example:
Client with job’s named ABC* need a 24 hour SLA with No-Service periods of Saturday, Sunday and major U.S. holidays
Client with Job’s named XYZ* opted for a higher service level and need a 24 hour SLA with No-Service periods of Sunday and major U.S. holidays. Work is produced on Saturdays.
Client with job’s named 123* are processed and produced by a non-U.S. team and need an SLA of Saturday and Sunday, and a different set of holidays.
I don’t think the above can be accomplished today in RPD with how Service policies and No-service periods are associated.
A very similar association already exists for input device + Expected work objects. I think that same setup makes sense for Service policy + No-service period. This would benefit RPD customers that provide different levels of service for their clients (5 day / 6 day / 7 day) and/or process work for non-U.S. clients as they would be able to define Service policies more precisely and associate the correct policy with the correct type of job.
