Idea ID: 1684651

Add configuration options for "Open in UCMDB Browser" button

Status : Declined
over 2 years ago

Hi all,

it would be great to have following configuration options for the "Open in UCMDB Browser":

  • most important: enable the button to only those CIs having a global id set (or any other configurable attribute)
  • choose for which entity type the button can be enabled/disabled (e.g. it is currently not available for Infra & Peripherals)
  • provide the possibility to configure a specific widget/view/topology which should be opened directly in the UCMDB Browser for the selected CI

Thanks and regards



  • Thank you for your idea. At this time, your idea hasn’t received enough community support and doesn’t align with our priorities so we are closing this idea. But we may review this again in the future. Thank you for your support and continue posting & voting on ideas to help make our products better.

  • hi Tonya,

    I need to extend the idea with another point:

    it must be possible to define the language which is used to display the ucmdb browser information --> right now, if you configure the ucmdb browser URL in the SACM dashboard like the following: https://[ucmdb_browser_server]/ucmdb-browser

    and when you then click on View in UCMDB Browser button, SMAX extends the URL like this: https://[ucmdb_browser_server]/ucmdb-browser/ucmdb_browser.jsp?server=Default%20Client&locale=en#tab=search;search=[ci_global_id];refocus-selection=[ci_global_id]

    By the hardcoded parameter locale=en UCMDB Browser can be opened in English only, however other languages must be supported as well.

    regarding your question about the "why it shouldn't be available": well, if a user clicks on View in UCMDB Browser button and the CI does not exist in UCMDB Browser, the UCMDB Browser still opens, but with 0 results. this is pretty confusing and annoying for end users. the button should only be shown/enabled in SMAX if a corresponding CI exists in UCMDB Browsers, otherwise it just makes no sense to click it.



  • 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 reviewed by the product team.

     can you please describe further the "why" behind this? Why it shouldn't be available.