I want to make comments as mandatory when perform enable/disable/delete operations on IdentityIQ’s built-in Manage Accounts UI

IdentityIQ (IIQ) IIQ Discussion and Questions
1

Which IIQ version are you inquiring about?

I am enquiring about IIQ 8.3 version

2

Hello Sai. In IIQ 8.3, there is no out-of-the-box setting to make comments mandatory for Enable, Disable, or Delete actions in the built-in Manage Accounts UI.

The Manage User Access Require Comments Settings under Global Settings → IdentityIQ Configuration → Miscellaneous applies to role and entitlement requests, not these account operations (documentation).

For your requirement, I would suggest customizing the LCM Provisioning workflow.

  1. Make a copy of your existing LCM Provisioning workflow.
  2. Add an <Approval> step with a <Form> and assign its owner to the requester.
  3. Add a Reason for Account Action field with required="true", and use the Approval step’s return mapping to capture the justification for auditing.
  4. Run this form only for Enable, Disable, or Delete operations, before provisioning. Make sure provisioning continues only after successful form submission. A rejected or canceled form must not allow provisioning to proceed.
  5. Configure the updated workflow for the relevant LCM action and test all three operations.

This collects the justification after the Manage Accounts action is submitted but before provisioning. If you need the mandatory comment directly in the original Manage Accounts dialog, you would need a separate UI or custom QuickLink/Form approach.

3

Hello @vio1336

In IIQ, the built-in Manage Accounts UI does not provide an out-of-the-box configuration to make comments mandatory for enable, disable, and delete operations.

One approach is to customize the relevant UI action or form to validate the comment before submitting the request. However, since this is a built-in UI, the exact implementation depends on how those operations are triggered in your IIQ version.

If the requirement is to enforce this consistently, I would also validate the comment in the underlying workflow or provisioning logic, rather than relying only on client-side validation. This helps prevent the operation from proceeding without a comment through alternate paths.

The main things to check are:

  • Which UI action handles enable, disable, and delete?
  • Is the operation submitted through a workflow or directly through provisioning?
  • Where can the comment be captured and validated before the provisioning request is executed?

I would avoid modifying the out-of-the-box JSP directly if possible, as it can complicate upgrades. A supported customization or workflow-based validation would be preferable.