Hi Ashish,
Thanks for your reaction.
- Some years ago UIM was one of the best and flexible monitor softwares (specially for service providers) available.
- totally customized environments
- only the reports/views/options the different customers are paying for
- once logged on in UIM no other logon was needed
- VERY flexible listviews and prd views
Now in 1 version most of these positive points are (totally) removed without anything that replaces this flexibility.
The removal of Liferay will be a very difficult one to digest.
- Version 20.3 needs to be in production before end of year, so what can a service provider say to his paying clients?
No custom environment,
No listview,
No prd view,
No reference to created web reports,
No custom report menu that list/execute all available cabi/jasper reports,
No customized consoles with pre-defined filters/columns,
very difficult to show a user only the reports/dashboards that he needs (in previous versions we added a custom menu structure)
- In previous versions we added access to the custom dashboard in our customized portal, like most clients do, NO additional logon was needed
- The alarm console is not really usable in this format:
- UIM alarms have 3 different date/time fields. Alarm console manages to include only 1 of them; initial creation date!!
Normally we sort a console on arrival date so that we see the new arrivals/updates. Sorted on creation date we are potentially missing important updates.
- some fields are fixed position (owner). Several clients are not using this field that can not be removed.
- date field (again) in a fixed date format (in the original IM console we could customize the date fields into every possible format).
- column width is not saved
- we cannot place the console as starting point in OC
- For several portlets that are removed there is even
NO replacement to migrate to the "new" suggested possibility. (like listview and prd reports)
(a lot of clients have Liferay sites for their clients build with 100's of different listview and prd reports!!!)
My remarks had as only goal to start a discussion to have some feedback to know which points would be interesting to open an idea for.
* For my remark that the enriched origin is not shown I have a ticket open. Because once we enrich/change the origin via the qos_processor we would expect that the origin field in OC (very visible via Inventory) would be the modified origin (in a lot of cases the client name). This is not the case, it stays the original origin.
* For the date format there is at least 1 idea open, but I can only vote 1 time for an idea. But with a new GUI like OC, I would AT LEAST expect that such tiny tings would be included from the design. Each time I see AM or PM my brain doesn't understand what he is seeing.