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!
- Labels:
-
Usability
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.