Skip to Main Content
IBM Sterling

This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Jun 3, 2020

Dynamic show/hide UI dialog elements

When trying to make a UI dialog more dynamic, we can currently use labels mapped to XSLT output to generate appropriate text for a partner.

E.g. a screen which can show Test, Prod, or both Test and Prod server details in one dialog. Or Inbound, Outbound, or both IB/OB file details.

Labels can be easily "hidden" by mapping blank text to them. So this approach works for simple text-based dialogs.

When the UI dialog includes other UI elements, such as text input fields and upload/download buttons, this does not work. We now have to create 3 separate versions of the same screen to handle each possible scenario.

Additionally, if the screens gather user input, then we have to add additional logic after them to be able to map values from the appropriate screen.

If there was a "Show/Hide" boolean attribute on UI elements that could be mapped from some XSLT value, we could collapse multiple UI dialogs back down to one UI dialog and reduce the additional logic required to handle them.

What is your industry? Non-Industry Specific
How will this idea be used?

This would be used to create dynamic dialogs that currently require multiple UI dialogs to achieve.

e.g. to allow a single UI dialog to handle showing/gathering "Test", "Prod", "Test and Prod" data. Which currently requires 3 separate dialogs. The separate dialogs increase maintenance time and troubleshooting time when a Sponsor views activity history.