8.5p1
hi,
we are trying to upgrade IIQ 8.4p3 to IIQ 8.5p1 version.
but after upgradation completed, when I am trying to open the ‘Request Access’, in the Manage User Access page I can see the ‘Review and Submit’ and ‘Remove Access’ button labels are missing.
I searched the iiqMessages.properties, those values are available in the identityiq.jar file.
So not sure, what is the issue? Can anyone help?
Thanks
Mautusi
Hi @mautusi_dey,
Since the message keys are already present in identityiq.jar, the issue is likely not related to iiqMessages.properties.
A very similar issue was reported after upgrading to IdentityIQ 8.5, where labels such as Review & Submit and Remove Access were missing even though the text was present in the DOM. The root cause was a customized SailPointBundle.js that was no longer compatible with the upgraded version. Replacing it with the OOTB SailPointBundle.js resolved the problem.
Reference:
I would recommend checking the following:
If the issue persists even with the OOTB bundle, please let us know whether there are any custom plugins, themes, or UI overrides deployed, as they could also affect label rendering after an upgrade.
can you try something like a customized SailPointBundle.js that was no longer compatible with the upgraded version caused labels like “Review & Submit” and “Remove Access” to be missing even though the text was present in the DOM. Replacing it with the OOTB SailPointBundle.js resolved the problem.
can you check any plugin which is controlling it.
Hello Mautusi,
@ssowmya567 covered this well. This is the customized SailPointBundle.js from 8.4p3 not being compatible with 8.5p1. The message keys exist in the jar, but the outdated JS bundle prevents the UI from rendering them.
Replace it with the OOTB 8.5p1 version, redeploy, and hard-refresh the browser. That should bring the labels back.
If it does not, check for any custom CSS or UI plugin overrides that could be hiding those elements post-upgrade.
@mautusi_dey You can also trace the browser console logs to see if there are any issues related to any of the web components. including SailpointBundle.js .
Can you please also confirm if you have any custom iiqMessages.properties, xhtml, any js script,? If so, it’s worth comparing them with OOTB 8.5p1 artefacts and make necessary changes on top of it.
hi Sangeetham,
There is no customization in SailPointBundle.js from us. We have customization only in
| quicklinks.js and ext-all.js. |
I compared as well still with the OOTB version. |
|---|
Let me try that. Will put the update soon.
hi Harish,
I tried to put the OOTB version for that js as well, though there was no customization from us for that particular js. But still same.
Thanks for the update.
Since you’ve already verified that iiqMessages.properties contains the required entries and SailPointBundle.js matches the OOTB 8.5p1 version, it sounds like we’ve ruled out the most common causes.
A couple of things I’d check next:
When you inspect the page in the browser, do the “Review and Submit” and “Remove Access” labels exist in the HTML but are simply not visible, or are they missing entirely?
Do you see any JavaScript errors in the browser console when the Manage User Access page loads?
Does this happen for every user, including a System Administrator account, or only for specific users?
The answers to those questions should help determine whether this is a UI rendering issue or something happening during page generation.
If everything looks normal and the issue still persists, it may be worth opening a SailPoint Support case, as this could be a product-specific issue in 8.5p1 rather than something related to your customizations.
@mautusi_dey Have you checked this?
Since the OOTB SailPointBundle.js did not resolve it, I would suggest testing a clean 8.5p1 web deployment without custom JavaScript, CSS, XHTML, theme, or plugin changes.
After taking a backup, stop the application server, delete the existing deployed IdentityIQ files, and deploy a fresh 8.5p1 WAR. Use the 8.5p1 iiq.properties file and carry forward only the required environment-specific values, then restore iiq.dat and iiq.cfg. Clear the application server and browser caches before testing.
SailPoint advises not to expand a non-patch upgrade over the previous deployment because files removed from the new version can remain and cause unexpected failures (8.5 Installation Guide).
If the labels return with the clean deployment, reapply the quicklinks.js and ext-all.js customizations one at a time using the 8.5p1 files as the baseline. If the issue remains, inspect the affected button in browser dev tools. If the text exists in the DOM, check the computed CSS..
@mautusi_dey Could you please also share the screenshot of what are you seeing now after the upgrade?
Please click on console, and see if there are any errors logged.
@mautusi_dey If your environment has a custom iiqCustom.properties file that was carried over from 8.4 P3, it may contain stale or incomplete message keys that are now overriding the new keys introduced or renamed in 8.5 P1. Even an empty or partial override for a key will suppress the default value from the JAR.
Also, try this once in Incognito mode to see if it is working or not.
We don’t have any custom iiqCustom.properties file but we have one custom ‘iiqMessages_en.properties’.
Thanks
Mautusi Dey
Could you please share the contents of this file?
