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 Future consideration
Created by Guest
Created on Apr 9, 2019

MER - attribute to allow/not allow to create FIN Output messages in create queues

We need an attribute for MER queue settings (CT DnqERQueue) to allow or not allow the creation or editing of incoming messages (i.e. FIN Output) in unformatted view. Like i.e. attributes AllowDrafts, CHANGELOCALADDR.

Background: Unformatted view in a Create queue allows to submit an FIN output message as valid message, which leads to massive errors in the processing flow afterwards as you cannot send a incoming message to SWIFT (see ref. PMR).

Therefore creation/editing of incoming messages should only be allowed "on request", if a proper processing work flow is implemented for messages submitted from such a queue (i.e. to create incoming messages to be sent to an application for test purposes).

Having this setting connected to a queue the privilege to create incoming messages can be assigned to dedicated persons with access to such a queue only.

Default setting should be to not allow this.