Disabling Workflows with Overrides

re: Disabling Workflows with Overrides

Travis Wright MSFT — Tue, 04 Oct 2011 15:47:48 GMT

@Kirill -

It could work a little bit better if you trigger your workflow not on the status property change but on the property value change instead. For example you had this requirement:

"in Activity1 if custom field is selected, then next Activity2 is not needed"

If you trigger your workflow when Activity.CustomField property changes then it will trigger the workflow and make activity 2 not needed. Of course if the custom field property change happens at the same time as the status change you will still have this problem. You could try to train your users to change the property value and submit before submitting the status.

Another option is to only ADD activities to the process based on the user's selections and not try to remove. This might be a little trickier but would be more predictable.

re: Disabling Workflows with Overrides

Kirill — Wed, 28 Sep 2011 06:30:10 GMT

Yes. The workflow "SetSkipped" triggers when Activity1 changes status to Completed. But in practice, when Activity1 is completed, then Activity2 has time to changes status to In progress (by built-in workflow i think ActivityStatusChangedRule ) and after that changes status to Skipped (by SetSkipped). I can see it at history tab in activity2. That behavior triggers notification email to implementer about Activity2 (which action not needed). That is my problem. If i can take priority of workflows, that my workflow Setskipped runs first.

re: Disabling Workflows with Overrides

Travis Wright MSFT — Wed, 28 Sep 2011 02:05:00 GMT

It sounds like you are currently triggering your SetSkipped workflow when the status of Activity 1 changes. Is that right?

re: Disabling Workflows with Overrides

Kirill — Tue, 27 Sep 2011 17:31:53 GMT

Travis, I am trying to do something like this. I have created change request template with several activities (some of them custom classes, some manual activity, some review activities). I need some activities from this sequence to be skipped (not be in progress state), if some criteria meets. For example, in Activity1 if custom field is selected, then next Activity2 is not needed, and Activity3 should be in progress state. So i have achieved this. I created additional state for activity (named "Skipped"), and created workflow "SetSkipped", with triggers when Activity1 is completed. That workflow (smlets powershell script) checks if field is selected, and if so sets Activity2 to "Skipped" state, And Activity3 to "In progress". Everything works fine, but there is some problem. I have also created notification workflows, when Activities enter "In Progress". That workflows send email to implementer of this activity. So when i test my scenario, Activity2 enters in "Skipped" state, but implementer of Activity2 anyway recieves email. I think it happens because my workflow "SetSkipped" runs AFTER built-in workflow (i think ActivityStatusChangedRule). So i need my workflow "SetSkipped" runs first. I try to change polling interval of "SetSkipped" to 1second, but no happy :(

I hope you will tell me some advices how to achieve my senario. Thank you.

re: Disabling Workflows with Overrides

Travis Wright MSFT — Tue, 27 Sep 2011 16:47:40 GMT

@Kirill - what is the scenario you are trying to achieve?

re: Disabling Workflows with Overrides

Kirill — Tue, 27 Sep 2011 08:46:34 GMT

Hi !

Can i override Rule priority like this?

</RulePropertyOverride>

I am getting error while importing the management pack, saying that property Priority is incorrect...