How to reset the process escalation date?

  • 13 January 2016
  • 3 replies
  • 4 views
E
Badge +4


 

Symptoms


Is this possible to change a process escalation date after the process has started? The date is set via a data field. However changing the data field doesn't seem to have an effect on the escalation. So the process escalated on the original date. Is there a way around this?
 

Diagnoses


In order for changes to take place the process has to be redeployed and a new instance has to be started.
 

Resolution

Changes cannot be applied after the process has started. Please note that escalations get scheduled when the instance hits that step. So, an Activity-level Escalation gets scheduled when that Activity Instance starts. Similarly, an Event-level Escalation gets scheduled with the Event Instance starts. This means that without re-instantiating the instance, there is no way to change the escalation schedule.




 

3 replies

R

Hi,

Once the activity or event level escalation starts, it's set though you have a dynamic rule to act based on a data field. We had a similar situation on one of our massive k2 workflows. Once the activity instance starts, the escalation rule starts ticking and any change to data field has no effect on the trigger to escalate. 

 

The way to get around is by jumping to another activity using k2 'Go to activity' feature which makes the current activity to expire and any rule inside the activity will no longer be active. In our case, when there is a change occur on data field we had another modify flow to handle. We had to initiate a go-to activity to jump to modify flow and make the escalation rule to expire. You can have an empty activity above this step and push to that activity whenever such change occurs in order to flush out the old rule and rewire the new rules.

 

I hope this helps someone as we had to live with this issue for more than 6 months and finally this resolved our problem.

 

Thanks for taking the time to read. All the best.

 

With regards,

Raj

R

Hi,
Once the activity or event level escalation starts, it's set though you have a dynamic rule to act based on a data field. We had a similar situation on one of our massive k2 workflows. Once the activity instance starts, the escalation rule starts ticking and any change to data field has no effect on the trigger to escalate.

The way to get around is by jumping to another activity using k2 'Go to activity' feature which makes the current activity to expire and any rule inside the activity will no longer be active. In our case, when there is a change occur on data field we had another modify flow to handle. We had to initiate a go-to activity to jump to modify flow and make the escalation rule to expire. You can have an empty activity above this step and push to that activity whenever such change occurs in order to flush out the old rule and rewire the new rules.

I hope this helps someone as we had to live with this issue for more than 6 months and finally this resolved our problem.

Thanks for taking the time to read. All the best.

With regards,

Raj

R
Hi, Once the activity or event level escalation starts, it's set though you have a dynamic rule to act based on a data field. We had a similar situation on one of our massive k2 workflows. Once the activity instance starts, the escalation rule starts ticking and any change to data field has no effect on the trigger to escalate. The way to get around is by jumping to another activity using k2 'Go to activity' feature which makes the current activity to expire and any rule inside the activity will no longer be active. In our case, when there is a change occur on data field we had another modify flow to handle. We had to initiate a go-to activity to jump to modify flow and make the escalation rule to expire. You can have an empty activity above this step and push to that activity whenever such change occurs in order to flush out the old rule and rewire the new rules. I hope this helps someone as we had to live with this issue for more than 6 months and finally this resolved our problem. Thanks for taking the time to read. All the best. With regards, Raj

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings