000033793 - The Account Changes table shows an error instead of account details when change request is initiated via Roles in RSA Via Lifecycle and Governance

Document created by RSA Customer Support Employee on Aug 29, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000033793
Applies ToRSA Product Set: RSA Via Lifecycle and Governance(Via L&G_
RSA Version/Condition:  All versions below 6.9.1 P11
 
IssueIf a change request is initiated via Roles, we observe "Account Changes table shows Error - instead of account details"
The aveksaServer logs shows the following errors: 
 
ERROR (http-0.0.0.0-8443-34) [com.aveksa.UI] com.aveksa.gui.components.table.core.TableView.printRows(TableView.java:659) - java.lang.NullPointerException
     at com.aveksa.server.core.account.Account.isDeleted(Account.java:341) at com.aveksa.gui.objects.account.GuiAccount.isDeleted(GuiAccount.java:175)
     at com.aveksa.gui.objects.account.GuiAccount.addIconToName(GuiAccount.java:134)
     at com.aveksa.gui.objects.account.GuiAccount.getNameWithIcons(GuiAccount.java:148)
     at com.aveksa.gui.objects.account.GuiAccount.getPreferredNameDisplay(GuiAccount.java:120)
     at com.aveksa.gui.objects.account.GuiAccount.getPreferredNameDisplay(GuiAccount.java:127)
     at com.aveksa.gui.pages.changeRequest.detail.changes.AccountChangeRequestItemDetailsTable.getRow(AccountChangeRequestItemDetailsTable.java:88)
     at com.aveksa.gui.pages.changeRequest.detail.changes.BaseChangeRequestItemDetailsTable.getRow(BaseChangeRequestItemDetailsTable.java:523)
     at com.aveksa.gui.components.table.core.TableView.printRows(TableView.java:654)
     at com.aveksa.gui.components.table.core.TableView.printPageContent(TableView.java:471)
     at com.aveksa.gui.components.table.core.TableView.printPage(TableView.java:433)

This issue is encountered when a change request is created for a user having two or more accounts in the same application.
User-added image
 
CauseWhen there are two accounts in same application for one user, the change request is not able to determine which account should have the entitlement assigned.
ResolutionThis issue is fixed in 6.9.1 P11 and above. Deploy the patch to resolve the issue.

Attachments

    Outcomes