• State Not Answered
  • Replies 1 reply
  • Subscribers 61 subscribers
  • Views 508 views
  • Users 0 members are here
Options
Related

Workflow filter on Requested Changes cannot distinguished between attribute that was not modified vs attribute that was cleared

Shawn.Ferrier
4 months ago

This is a pretty esoteric issue; it's probably a long shot that anyone else might have encountered it, but just in case...

Per the subject, if you create a Change Workflow that has a filter on the starting conditions looking for cases where an attribute has been cleared, you must add a condition to look for cases where "<attribute name> from Requested Changes is empty":

Such a workflow, however, will be triggered even if the selected attribute is not modified. This does kind of make sense, of course... logically, a non-existent attribute likely should match to the "is empty" operator. That said, I'm still stuck with trying to solve the original problem:

How do you trigger a workflow to know when an attribute has been cleared?

In scripted policy, the $Request object will contain references to cleared attributes, plus you can also look at the ControlCode value. I'm guessing there is probably no workaround to this without having to introduce code?

Thanks so much!

Parents
  • 0 4 months ago

    Hi  

    This would depend to the use case

    1) If the start condition is Modify properties, and you can add only to trigger on SF_Boolean being modified, then you should be good. As if its not in the request properties cache it won't (or shouldn't) fire. If however you have or need multiple (or all) properties being modified to trigger this workflow, the you'll need to look at option two (by itself or in addition to this option)

    2) If you can't do that, then you're probably looking at a script of some variety or another, IE

         A script which checks if SF_Boolean has been modified and returns a true or false (That'll cater for both workflow target (DirObj) and request target (Request) being empty.

Reply
  • 0 4 months ago

    Hi  

    This would depend to the use case

    1) If the start condition is Modify properties, and you can add only to trigger on SF_Boolean being modified, then you should be good. As if its not in the request properties cache it won't (or shouldn't) fire. If however you have or need multiple (or all) properties being modified to trigger this workflow, the you'll need to look at option two (by itself or in addition to this option)

    2) If you can't do that, then you're probably looking at a script of some variety or another, IE

         A script which checks if SF_Boolean has been modified and returns a true or false (That'll cater for both workflow target (DirObj) and request target (Request) being empty.

Children
No Data