Hi Team,
After upgrading our environment to 8.5 version , we are observing a change in behavior on the Finalize & Submit page during access requests.
However, after the 8.5 upgrade:
@akashk Could you please share screenshot showing the page highlighting what options you are talking about?
Hi @akashk ,
Make sure the following option is enabled in Gear → Global Settings → IdentityIQ Configuration → Roles.
If not enabled, please enable to it to see start and end dates when requesting the entitlements and roles in manage access.
After the upgrade the previous settings might have been over ridded with default settings in 8.5
Please once go through this.
Dear @akashk ,
can you please tell me what you are referring as “bulk change”.
And more Start date/End date, please follow the below steps:
Click gear menu > Global Settings > IdentityIQ Configuration
On the Roles tab:
In the Role Start/End Dates section, check the option to Enable Sunrise/Sunset Dates on Role Assignment
Enter number of days to send the notification for Sunset expiration (if this is the use case)
Save your changes.
Hi @Sammy271200 and @neel193
is there any way that we can only disable the Bulk change button and comment button
@harsha33 I don’t think there is any OOTB configuration to hide the bulk change+comment and keep individual line item dates and comments.
You need to create a plugin to hide this. Let us know if you need any help with it.
Note: This post is discussing about missing options, while your’s a different one. Better to start a new post to avoid confusion and to have the conversation focused to the original issue.
No, there is no OOTB way, You can write a small plugin and invoked it at accessrequest.jsf page, and hide the Bulk change and comment button.
HI @neel193
i need help in creating the plugin.
Hi @harsha33 Please follow this document: Plugin Development - Compass there is a sample plugin provided which you can use for learning. Basically you need to inject a UI snippet that reads the element of bulk change and comment and hide it.
Go over it and let us know if you have any further queries.
Hi all,
Upon investigation, the root cause was identified as a customized SailPointBundle.js file, which was not properly aligned with the upgraded version.
The issue has now been resolved by replacing the custom SailPointBundle.js with the OOTB (out-of-the-box) version. After this change, the missing options are now functioning as expected.
