Oracle Identity Governance (OIG) Change Task Getting Triggered For Rejected Disconnected Application (Doc ID 2902576.1)

Last updated on OCTOBER 21, 2022

Applies to:

Symptoms

Change Tasks are getting triggered for Account rejected at Manual Fulfilment task approval level for an Disconnected Application.
This generates a change/modify request for manual fulfilment task approval.

Steps to reproduce the issue:
===================

1. Integrate a disconnected application with OIM.

2. In the Design Console (DC), create a custom field (Example: Custom Field1") on disconnected application form.

3. Configure the Change Task "Change User Street" for any one of the user profile attributes (Example: Street) in user lookup trigger "Lookup.USR_PROCESS_TRIGGERS".

4. Add the change task "Change User Street" in the process definition and map the custom attribute "Custom Field1" with user profile attribute "Street".

5. Open the "ManualProvisioningEnd" process task of disconnected application and Under the "Task To Object Status Mapping", Set the object status from "None" To "Revoked" for response status "X".

Note: object status can be set with other status too like ready, waiting and etc. In the example, set with "Revoked" status.

6. Request for this application and reject it at manual fulfillment task. Disconnected application account status is changed from "Provisioning" to "Revoked" status (This status as per configuration set at step5.

7. Modify user attribute "Street" and see corresponding change task "Change User Street" for the revoked disconnected application account is getting triggered and it is going for manual fulfillment task approval.

Changes

In Design console, open the "ManualProvisioningEnd" process task and set the object status from "None" To "Revoked" for response status "X" under the "Task To Object Status Mapping".

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.