Customers upgrading to IGA V15 may encounter several related issues concerning the "Task Run Time Management" feature:
1.Missing Tab (12.x Schema): The "Task Run Time Management" tab is entirely missing in environments where role definitions are still on the 12.x schema. The tab becomes visible after updating the role definitions to V15 via the management console.
2. Functionality Errors:
- In one environment after did the above import, attempting to click the "resubmit task" button initially generated a Java exception with following error:."The IdentityMinder directory does not support this feature.". This specific error is restricted only to the resubmit task.
Migrated from Standalone Jboss 14.5.1 CHF01 with only CA Directory User Store, No Provisioning Store.
V15 Fix Pack 05
No Provisioning Directory also in v15 destination migration.
To show the Task Run Time Management Menu import the v15 role definitions from IM Management Console.
The issue is suspected to be caused by a missing update to the role definition schema during the V15 upgrade process. Engineering review confirmed that the non-provisioning role definitions shipped in V15 do not include the necessary "Resubmit Tasks" task.
The core problem causing the Java exception when attempting to resubmit a task can be resolved by manually modifying the task in the User Console.
Steps to manually correct the task:
1. In the User Console, navigate to Roles and Tasks -> Admin Tasks -> Modify Admin Task.
2. Search for the task named "View submitted task".
3. On the "View submitted task" screen, go to the Tabs section.
4. Edit the "Submitted task" tab.
5. Manually modify the task's settings:
- Change the Resubmit Task Tab action from View to Modify.
- Change the Tab type to Tasks Resubmission (removing the Resubmit Task type).
Permanent Fix and Next Steps
Engineering has committed to attempting to deliver a fix for the upgrade role definition schema in an upcoming fixpack.
In the interim:
- The manual correction above must be applied if the Resubmit Tasks issue is encountered again.
- If the problem reoccurs, the customer must share all relevant logs, including the logs from the deployment, mogrify, and database copy moments, for deeper root cause analysis opening a Support case.
Noticed the issue for Non Provisioning User Store migration type only.