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 Mar 17, 2021

FTM MER Screen – Additional data entry field for Routing

FTM MER Screen - Having an additional data entry filed (something like editable ‘comments’) in the Formatted Tab. The user can enter the comments filed by viewing the details of the Message. This would help in having the custom actions based on the user inputs after validating the message in the same screen rather switching to ‘Context’ tab. This option should be applicable for All the purpose types of the MER screen.

  • Applicable to all MER queues for Inward Messages i.e. all branches & HO's MER queue defined as Purpose=Application in MER.

  • Not applicable to Queues for Outward messages i.e. with names ending with ***DE, ***AU1, ***AU2, ***ACK, ***COR, ***FILE

  • Not applicable to queues for template, creation, edit, approval, retype, display purposes (i.e. defined with Purpose=Display)

  • users perform routing by specifying the destination Branch or HO department, for example: ROU JSS


The routing program (refer to the logic in MRVRTROU) will determine which MER queue to be routed to depending on the message type.

  • re-routing can be performed more than once in the event it is routed to the wrong branch e.g. HO route to Branch A. Subsequently Branch A can route to Branch B or another HO dept and etc.

  • routing to FILE queue performed using command "ROU FILE"

  • for some HO depts, in addition to routing the message to the destination branch queue, a copy of the message is routed the department's manual routed queue. eg MT103 in TCCMT12 --> ROU JSS command --> message will be routed to the following queues: JSSMT1XX , TCCMTROU, JRNROUTE and the JSSPRS1 printer for printing

  • the UMR-msgID remains the same and must not change when the message is routed to multiple destination queues