Better Error Checks for New Entities after Upgrade

Idea ID 2704813

Better Error Checks for New Entities after Upgrade

We recently upgraded from Octane 12.60 CP9 to CP10. One new feature of CP10 is calendars. See here for What's New details:  https://admhelp.microfocus.com/octane/en/CP10/Online/Content/WhatsNew/wn-cp10.htm

We had several users get the message "Oops. Something went wrong." with the following details on initial login after upgrade:

"ERROR | {"loggerName":"show-error","details":["unhandled-exception-message","[$interpolate:interr] Can't interpolate: {{entityLabels.calendar.pluralCapitalized}}\nError: Unknown entity type 'calendar'"

 

Logging out and logging back in fixed the issue.

 

Octane stores the user's last location (module/tab) when logging out, so the user is taken back to the same spot when logging back in.

The underlying issue here is that the CP9 version of that information did not contain the "calendar" entity. When the users logged in for the first time with CP10, Octane tried to append the "calendar" information to the CP9 information and couldn't. When the users logged out and back in, the stored information was converted to CP10 format with the "calendar" entity included, and all was fine.

 

My suggestion here is to include better checks after upgrade to ensure new entities are handled properly, especially for users that have previous session information stored.

 

Thanks!

 

Tags (3)
3 Comments
Jesper Outstanding Contributor.
Outstanding Contributor.

This is a general problem with most errors - they hang in history of browser....

Examples:

Problems with Elastic search servers after OS patching on 2 out of 3 servers caused users to get elastic search error when logging on. When error was fixed some users use link directly to certain workspace and empty browser history/restart PC is the only way to get access when error is fixed

br jesper

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
Status changed to: New Idea

Thank you for updating us - R&D are currently checking this issue. we will contact you in case we will need more information to resolve the issue.

 

Thanks,

Sigal 

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
Status changed to: Delivered

This issue was investigated by R&D and fixed for CP11

thank you for your feedback,

Regards,

Sigal

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.