I didn't know but thought it was a great idea. I created a custom field on my case form called 'respondbydate' and 'respondbytime'. Made them date and time fields respectively. We offer two support plans, one 24 x7 and the other 12 x 5 (excluding holidays). Case rules such as duration (hours) since last modified work fine for 24 x 7 since you would check against actual hours to determine if a case should be escalated. However, 12 x5 (excluding holidays) is much more complicated since you need the duration hours to reflect BUSINESS hours not actual hours and you need to take into consideration weekends and holidays. So thought I was smart. I wrote some client javascript to figure out what time it is in our home office, is it after hours or is there a weekend in between to consider, etc and bam I know how many hours need to pass before escalation needs to occur. I populate the fields and then go to the rules to build a simple logical rule: If 'respondbydate' is greater then currentdate, escalate. Slam: rule doesn't let you do this. You need to actually enter a date!! How ridiculous is that. Dates and times are moving targets. What rule would use a static date? Its a one-time use rule. All that work for not.
Anyone have any ideas on how to salvage this effort. Other than changing the field to a number field to represent hours and writing some 100 rules (to cover possible 4 day weekend/holiday combos) that do:
if respondbyhours=1 and duration from creation=1; if respondbyhours=2 and duration from creation=2; and so on. I'm so-o-o-o close.
Thanks.
-Steve