Stopping the clock on a Process escalation?

  • 18 January 2011
  • 2 replies
  • 16 views

Badge +3

I have a workflow with an Escalate After rule set at the Process level. 


When an administrator elects to stop the process instance using Stop within Workspace and  then restarts the process later on, the escalation appears to be evaluated on the period between the start date/time and the current date/time rather than the actual duration the workflow has been running for.


Is there a way to force K2 to use the latter value - i.e. stop the clock on escalations when the workflow instance is stopped?


Thanks,


David


2 replies

Badge +5

I do not think that this functionality works this way. Escalations are based on Physical ellapsed time, tied into configured working hours rather than process duration.

Badge +3

Thanks for the explanation, Murphy.  That fits with the behaviour I've seen with both Stop and Sleep functions.


Can you think of a way in which I can effectively pause the workflow instance and have that reflected in when the escalations fire?

Reply