Hello everyone!
Situation: We've been prompted to find a way to somehow capture and
process possible exceptions made by certain non-critical actions in the
context of a rule, without distinguishing the driver's or driver's
policy nature. For example, performing an "add role" action within a
rule's logic and being able to audit a "Connection refused" error in the
form of sending a notice email or generating a customer-frienly report.
Log analysis is not really an option here due to the driver's heavy

We couldn't think of an inline, high-level way to implement this luck of
try/catch block for the action in question...

Do you by any chance know how can this be adressed?



rodyan's Profile: https://forums.netiq.com/member.php?userid=7717
View this thread: https://forums.netiq.com/showthread.php?t=52445