IBM Data and AI Ideas Portal for Customers

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

Post 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 product management 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 notification 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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Workspace Cloud Pak for Data
Created by Guest
Created on Apr 21, 2021

Allow WKC host strings to be changed

The context string for an Information Asset is built from the connection string components. EX: the Hostname on port 1234 using a jdbc connector results in the context string jdbc:ibm:hive://;databaseName=dbName

This context string is seen by users in the information assets view and is too verbose/technical for the user. The context string is also used in extension mapping documents.

There should to be a way to alias the context string (or rename it) to be viewed in information assets and used in extension mapping documents (and where ever the context is required).

EX: jdbc:ibm:hive://;databaseName=dbName changed to NonProd.Location2

Then the context string in information assets would show the more business friendly NonProd.Location2

Needed by Date Apr 21, 2021
  • Guest
    Oct 28, 2021

    If Information Assets is being removed and changed to Catalog then this connection string name shouldn't be needed. But, how does that affect the current lineage external mapping documents import where the Hostname is also used?

  • Admin
    Susanna Tai
    Apr 26, 2021

    Hi Michael, thank you for providing the details of the host string requirement. For the newer screens in WKC, we don't plan to expose the host string except in the connections details screen.

    As for the Information Assets view, since the roadmap is to replace the "legacy" components once we have their replacements, any enhancements to the "legacy" stack will be lower priority on the WKC roadmap.

    For this requirement, I believe the right approach is for any new screens to make visible only the connection name rather than the host name or host ip address as the context string for the data assets. Does that make sense?

    In the meantime, I'll share your requirement with our design team as well.