Skip to Main Content
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 Submitted
Workspace Watson Assistant
Created by Guest
Created on Jan 18, 2019

Improve handling with complex values within slots

If you don't want to save the 'Check for'-expression as value for a slot you can use the JSON Editor. Thats important because otherwise we weren't be able to reformat a date or time before saving it. Saving multiple values of a pattern based entity is another example where we need this (see

Unfortunately these edits are not reflected in the simple editor. Even worse: These edits are restored (without any warning or questioning) to it's defaults by just clicking in the 'Save it as' field (see warning at step 4 in You don't even habe to edit that field! Afterwards the assistant does not work as expected anymore.

This behavior of the editor is very annoying and we spend many hours to find out under which circumstances our edits in the JSON Editor were overridden. Restoring these complex value expressions can take even longer because there is no 'undo'-function so far.


  • At least: The editor should not override without any warning the edits that were made in JSON Editor (with every click to the 'Save it as' field)
  • Improve the simple editor UI for slots
    • Split the "save it as" column in two columns "save" and "as" whereas
      • 'save' can be prefilled with the content of the Check-For column but might be edited if needed and
      • 'as' reflects the old 'save it as' column