CMS/UCMDB Include Better Error Handling Information for Model Exceptions

[Whitlock Support]

MF Reference Ticket:  SD02559864

ENVIRONMENT:  Operation Bridge Version 2019.05 on Linux server + UCMDB Standalone Client Version 2019.05 on Windows 10 desktop

BACKGROUND:  The use case conclusion was:  "the value “mam.common.general.object.root” did not change during the upgrade. It looks like this issue is caused by improper configuration from JMX directly and (MF) could not narrow down why this value changed or who changed it from the logs…  R&D suggestion is to change/continue with the setting “ mam.common.general.object.root” by admin UI and avoid setting it by JMX. "

REQUEST:  The Idea/Enhancement request is to add more detailed, targeted, and enhanced error message for issues such as this rather than the generic fatal error pop-up given.

"Fatal error in initialization

A fatal error has occurred during the UCMDB applet initialization.

The application might have entered an unstable state.

It is recommended that you close all browser windows and restart the application."

Inserting picture with too general of error pop-up:

[Bill_Dyck]

Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team