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: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io


Status Submitted
Workspace Watson Assistant
Created by Guest
Created on May 3, 2022

Add ability to turn off matching to intents, entities and context in strings

Currently, if Watson Assistant finds a #,@, $ in any string, it will replace the characters with an evaluation of the intent, entity or variable (respecitvely).

This can be very difficult when there are strings passed back from an API that need to be displayed to the UI.

These special characters currently need to be 'escaped' in all cases.

One example is a recent API call that returned "account #1" and since we don't have a #1 intent, it replaced this string with "account false".

Since users are not restricted in what they can type in input fields, this could also cause simlar issues in a variable that is assigned input from a user (for example, if a user typed "Apartment #1" and this variable is passed).

The current solution is for all string fields to have the following processing to avoid this:

$apiField.replaceAll(' #',' /#')

$apiField.replaceAll(' @',' /@')

$apiField.replaceAll(' $',' /$')

This new idea is to allow for the means to dynamically turn on/off this feature in Watson Assistant so that strings do not need to have the #,@,$ escaped.


Needed By Yesterday (Let's go already!)