Home → Bug Reports →

escalation hours

• Edit

harlenweb

Sep 25, 2012 @ 05:19 PM

I can put "240" escalation hours (10 days) into the workflow XML, but when I next edit using the workflow builder, it reverts to "4" hours.

1. 1 Posted by Ryan Griffith on Sep 25, 2012 @ 06:02 PM

   

   Hi Sara,

   It sounds like you are running into this known issue in which the workflow builder is not saving the escalation period properly.

   Feel free to use the the link I have provided to track the progress of this issue to see if it has been resolved in a future release of Cascade.

   In the meantime, I was playing around a bit with this locally. If you enter 864000 seconds (seconds in 10 days), it does seem to convert over to 240 hours. Give that a try and let me know if that works for you.

   Please let me know if you have any questions.

   Thanks

   • Edit

2. 2 Posted by harlenweb on Sep 25, 2012 @ 06:10 PM

   

   Ryan,

   Why is this a "minor" bug? I wasn't able to set the escalation properly and still use the workflow builder (if I use the workflow builder, I have to reset the escalation values each time).

   --
   Sara Haradhvala
   Manager, Harlen Web Consulting LLC
   [email blocked]

   • Edit

3. 3 Posted by harlenweb on Sep 25, 2012 @ 06:17 PM

   

   Ryan,

   I had tried that and it's OK the first time through - the problem is that if you go into the workflow builder again and save, the number comes out wrong.

   Sara

   --
   Sara Haradhvala
   Manager, Harlen Web Consulting LLC
   [email blocked]

   • Edit

4. 4 Posted by Ryan Griffith on Sep 25, 2012 @ 06:32 PM

   

   Correct, because of this known issue, the builder will load 240 hours correctly; however, upon submission it will give you the incorrect conversion again. So you would have to essentially enter 864000 seconds each time.

   • Edit

5. Ryan Griffith closed this discussion on Oct 18, 2012 @ 03:51 PM.