Support Article

Portal switch error after installing HFix-22614

SA-27876

Summary



After installing HFix-22614, the following use case began producing "Failed to find" rule errors.

Error Messages



com.pega.pegarules.pub.generator.RuleNotFoundException: Failed to find a 'RULE-NAVIGATION' with the name 'MenuName' that applies to '@baseclass'. There were 3 rules with this name in the rulebase, but none matched this request. The 3 rules named 'CCOPORTAL_USERMENU' defined in the rulebase are:
3 related to applies-to class '@baseclass', but were defined on subclasses: {CPM-Portal, Data-Portal}.

at com.pega.pegarules.generation.internal.vtable.ruleres.VirtualTableResolver.throwDetailedRuleNotFoundException(VirtualTableResolver.java:711)
at com.pega.pegarules.generation.internal.vtable.ruleres.VirtualTableResolver.resolveToContainer(VirtualTableResolver.java:390)
at com.pega.pegarules.generation.internal.vtable.ruleres.VirtualTableResolver.resolveRule(VirtualTableResolver.java:154)
at com.pega.pegarules.generation.internal.vtable.VirtualTableImpl.resolveRule(VirtualTableImpl.java:254)
at com.pega.pegarules.generation.internal.PRGenProviderImpl.get(PRGenProviderImpl.java:474)
at com.pega.pegarules.session.internal.mgmt.Executable.doAction(Executable.java:3168)


Steps to Reproduce

  1. Create a menu option available to the End User portal to launch a another application in a new window via the redirectandrun activity.
  2. Launch the End User portal.
  3. Launch the second application from the User portal.
  4. In the second application perform some actions and then logout.
  5. Come back to the End User Portal and re-engage on a navigation control.
  6. Observe error in a pop-up modal window.


Root Cause



An issue in the custom application code or rules.

The logout on the second application expires the shared session which means the original application window will need to re-engage a call to showdesktop which will prompt for re authentication but the Document Object Model(DOM) will not be updated accordingly.

The sequence to get into the state mentioned is not a supported processing path.

Resolution



Here’s the explanation for the reported behavior: 

The logout on the second application expires the shared session which means the original application window will need to re-engage a call to showdesktop which will prompt for re authentication but the Document Object Model(DOM) will not be updated accordingly.

The sequence to get into the state mentioned is not a supported processing path.

​To correct update the application to prevent the dual application in the single session or prevent the logout sequence on the spun off application.


 

 

Published September 12, 2016 - Updated September 22, 2016

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.