I have a validation rule that is trigged by a custom action (and possibly also by a scheduled workflow rule - which the custom action is a test version of).
How do I prevent the validation rule is triggered by the SWR? It already has
Not IsTriggeredBy('Counters')
- and then the normal criteria
Please sign in to leave a comment.
Hi Peter,
I would suggest to set the default work flow user on the Global Settings to a user which is not one of the human admins and than you can user the CurrentUser() as discrete criteria.
Please let me know if it makes sense.
Thanks,
Tamir
Hi Tamir
Thanks for your feedback. Default workflow user is already is a non-human user.
Where should I use CurrentUser()? In the validation rule and some Not statement?
Exactly!
Tamir
Hmm. Iserting
&& CurrentUser()<>'BleauSystem'
has no effect, it seems.
Hi Peter,
What is the SWR and CA purpose? What are the actions that are executing under those rules?
Thanks,
Tamir
Hi Tamir,
The rule is a huge calculation rule that fills a custom field with a currency number which is supposed to give us a much better view of the status of billable but not yet charged work done in our organization (sort of a Revenue EV - but without the scheduling parameters) - especially with focus on fixed price work items since Clarizen sets the value of these at 0 although work has been done on them.
The rule is actually the rule I am also talking about here: https://success.clarizen.com/hc/communities/public/questions/206894617-Clarizen-logic - where I want to filter it so it does not run on archived WIs.
The evaluation criteria for the Validation rule at the WI level (it will look familiar) - which is hit - which I am trying to avoid is:
((Not(IsNull($Parent)) &&
($Parent.Phase='Archived'
||
$Project.Phase='Archived')) )
&& CurrentUser()<>'BleauSystem' <- Your suggestion