An engineer needs to trigger a workflow when a Division attribute changes from /7"to Senior...

The scenario describes triggering a workflow when a "Division" attribute changes from a specific value to "Senior IT," but only when the user is a manager. The proposed solution suggests creating a trigger with an event type of "rule" that checks the previous and new values of the "Division" attribute.

However, this approach has a couple of issues:

Trigger Configuration:In SailPoint IdentityIQ, a lifecycle event trigger typically operates on changes in identity attributes, but it’s not standard to define this trigger using a rule that directly inspects the previous and new values. Instead, the lifecycle event would usually be configured in the context of the application or identity to directly listen to specific changes without needing to define the logic in a custom rule.

Condition Validation:The condition of checking if the user is a manager should ideally be integrated within the workflow itself or the lifecycle event configuration, not just as part of a rule in the trigger.

While a rule can be used to define complex conditions, the correct way to implement this in IdentityIQ would involve setting up the lifecycle event trigger specifically for the attribute change and managing any additional conditions (like checking if the user is a manager) within the workflow or using an appropriate script/rule in that context.

Therefore, while partially correct in approach, the described solution is not the best practice or a valid process in IdentityIQ, so the correct answer isB. No.