Recursive Faulty view upon clicking on 'Additional Information' under CR link in the Activity/Approval tabs in RSA Governance & Lifecycle
Article Number
Applies To
This is a known issue in the following versions:
- RSA Identity Governance & Lifecycle 7.5.0 P08
- SecurID Governance & Lifecycle 7.5.2 P04
Issue
As per the below screenshot, recursive view with the same information from the initial popup of "change request link" is displayed again after expanding "Additional Information"
and the below error message in aveksaServer.log,
08/10/2023 08:44:44.519 ERROR (default task-4) [com.aveksa.gui.pages.changeRequest.detail.ChangeRequestDetailHelper] Exception occurred while rendering the Addional information.[Ljava.lang.StackTraceElement;@268223a2 08/10/2023 08:44:44.520 DEBUG (default task-4) [com.aveksa.server.utils.Step] Starting execution step: null.. , Time Elapsed=-5 secs STARTING method=ExecuteStep subTask=start
Resolution
- SecurID Governance & Lifecycle 7.5.2 P08
- RSA Governance & Lifecycle 8.0.0 P01
Related Articles
RSA Governance & Lifecycle Recipes: CR Approvals & Activities Trending 24Number of Views Add access unsuccessful due to PS CR behavior in RSA Identity Governance & Lifecycle 63Number of Views Clicking on the 'View the Approval Request' URL from an approval email fails with 'Request could not be handled' in RSA Id… 71Number of Views Form variables not displaying under "Additional Information" on request in RSA Identity Governance & Lifecycle 43Number of Views Form used in manual fulfillment node does not reflect the changes done in the CR created in RSA Identity Governance & Life… 18Number of Views
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records RSA Release Notes for RSA Authentication Manager 8.8 AFX Server remains in a 'Not running' State, afx status shows 'timed out waiting for AFX applications to start' and mule_e… RSA Authentication Manager 8.7 SP1 Patch 1 Hotfix 1 RESTful Web Service Connector capability test fails with unauthorized (401) error when using Basic authentication in RSA G…
Don't see what you're looking for?