If you perform an action from the policy builder as "direct", such as set src attribute value/set dest attribute value, you can't check if the action was successfully processed as the status event returned that contains the information is not available in the policy.
We should be able to access the status of any action through "error" variables such as error.do-send-email, something like that should be available for every action where the mode can be set to "direct".
by: Aleksandar M. | over a year ago | Other
Comments
I'd like to see the status returned through the input transform as per "regular" transactions.
You can actually grab the status of direct operations by executing them yourself at the end of each policy instead of letting the engine do that. Alex McHugh has explained this in detail in https://www.netiq.com/communities/cool-solutions/delving-into-and-beyond-the-current-op-part-3/ including sample code and called is "verified direct write".
It would be great if the status event from direct operations was available as local variable, but since direct operations are executed only *after* all custom policies, where would you check on the results? Maybe an new token do-execute-direct-ops-now (basically calling code similar to Alex' stuff metioned above) could help...
It could be confusing to have direct operations status returned through the remainder of the thread as per regular transactions as Jim G suggests.
I am all for a built-in token as Lothar suggested, but there is not a one-size-fits all solution here. Even with a built-in token, there a good reasons to retain the mechanisms I have mentioned in my cool solutions article.