Awesome. I’m glad that worked!

Changing the order to 50 did the trick. Thanks Mark!!!

Only suggestion I can think of is to try adjusting the ‘Order’ field on your business rule. If you have a very high order it might be triggering after the workflow context is being executed. Try an order of 50 and if that doesn’t work you could try setting this up in a ‘before’ business rule.

The business rule is working for us as for as not initiating the next task in the flow is concerned. The problem I’m facing is that we have a Set Value box right after the cancellation point that is still being triggered. Do you have any suggestions on how to stop this?

My condition to cancel the workflow is state changes to Cancel. I’ve cancelled a change at a point where the following steps are
1) Set value to ZZZ
2) Create Task 123

Task 123 is not being triggered, which is exactly what I want. However, my state is being changed from Cancel to ZZZ, which is not what I want.

Any tips?

Hi Mark, indeed the syntax works fine. The reason that it didn’t work in my case is that we had another client script that makes the a field mandatory, if I just fill that field & save it, the UI action is not really executed completely. If I would trigger the UI action again, then the WF is canceled

thanks for your help!!

Yes, but my UI action only had the single workflow cancel line. I’m guessing that yours isn’t working because you’re calling your update first. Try moving ‘current.update’ after the workflow cancellation. If that still doesn’t work, then try the workflow cancellation on its own and see if you can get that to work.

Hi Mark, did you call this from a UI action? Can you let me see how your UI action script in total is done. It doesn’t work in my case. We have an UI action called Cancel Change defined on change_request table
the scrip in there looks the following

current.state=4;
current.u_change_status=6;
current.update();
new Workflow().cancel(current);
g_form.addInfoMessage(“Workflows for ” + current.getDisplayValue() + ” have been cancelled”);
action.setRedirectURL(current);

both the workflow cancel part & the InfoMessage part doesn’t work

That’s all you have to do. You’ve got the syntax correct. I just tested your code against a change request ticket in a ServiceNow demo instance and it worked correctly.