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,
Post an idea
Upvote ideas that matter most to you
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.
@sys-time and @sys-date with Fuzzy matching to handle typos
It would be great if @sys-date and @sys-time could support fuzzy matching in order to handle typos, particularly for the descriptive dates such as:
next week (typo: nxt week)
September (typo: Septembr)
It would be great that a slot could accept different prompts for "If not present, then ask", and each prompt could also be conditional.
Imagine this scenario of booking appointment for vet practices: I have a node with a slot configured with a...
hello, we use watson conversation service and are wondering, why it is not possible to have read only API Credentails for this service. is it possible to get a user who can send messages, but who is not able to create/delete/update a workspace?
Add the possibility to jump to common pattern nodes/node groups (e. g. "Please enter your customer number/adress/phone number") from anywhere in the dialog flow and dynamically jump back, based on where you came from.
This could speed up dialog d...
Watson Conversations offers not only the API but also quite a complete interface that can be used by logging in Bluemix.
In many projects, when business and experts train the system, they use the Bluemix interface. It is more or less intuitive an...
Building repetitive nodes on large-scale WCS implementations is very time consuming. If nodes could be effectively copy/pasted (ie replicate an existing node to several hundred other locations in a dialog flow), development time would be massively...
It would be great to have a built-in workspace versioning for managing changes in the workspace.
Today, we have to workaround that using a time-based download of the workspace json and `git push`ing it to be "safe".
Meanwhile this time-based sch...
Ability to export and import multiple or single intents in Conversation
Today we can only export and import the entire Workspace in conversation. The work would be a lot easier if we could export intents in conversation that makes sense in other context to other workspaces that are already running. For example, we c...
AFAIK, the expression language does not allow looping through data.
I a conversation, you often have the situation that multiple entities are recognized. You can easily create a response for one recognized entity. But you may want to loop through...
Do not place IBM confidential, company confidential, or personal information into any field.