IBM Sterling Ideas

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:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

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.

  • Guest
  • Jun 3 2020
  • Not under consideration
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.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.