Request for Consistent NCD Trigger Snapshot Behavior for Delimited Application

Which IIQ version are you inquiring about?

8.4 P2

Share all details about your problem, including any error messages you may have received.

Hi Team,

In our environment, we have integrated the service desk with split provisioning enabled. We have observed an inconsistency in the 2nd Scenario Trigger Snapshot for NCD (Native Change Detection) under the following two scenarios for delimited applications:

Multiple Account Access Requests:
When an access request includes multiple account requests—each mapped to a different business role—the Trigger Snapshot for NCD is correctly triggered for each account’s RITM upon closure.

Single Account with Multiple IT Roles:
However, when an access request contains a single account request where the business role comprises multiple IT roles, the Trigger Snapshot for NCD does not reflect accurate data for the associated RITM.

The trigger behavior in these delimited application scenarios differs from what is seen with multiple account requests.

Expectation:
We would like to achieve consistent RITM behavior in the Trigger Snapshot. Specifically, when an RITM is closed—even for single account requests with multiple IT roles—the NCD trigger should operate the same way it does for multiple account requests.

Could you please advise on how to ensure this consistent triggering behavior for delimited applications? If additional configuration or workflow adjustments are necessary, your guidance would be greatly appreciated.

Thank you for your support.

Please let me know if you would like any screenshots or log files for further context.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.