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 offering manager 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.
For product documentation, see Knowledge Center. Create and View Support Cases and Use the Discussion Forum here
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 th...
For field 23, Either create a drop-down that accepts only TRANSFER and DELIVERY or it allows only TRANSFER and DELIVERY keywords. Current FTM allows users to enter anything within 16 character, when wrong code is entered, no error prompt to stop t...
The Data Entry(Create Purpose) queue information is not reflected in Message History and the user who performed the AU2 function is not displayed in Message History.
The Data Entry(Create Purpose) queue information is not reflected in Message History and the user who performed the AU2 function is not displayed in Message History. In the attached image, a message is created in the TCPDE queue, but queue informa...
Provide an FTM MER configuration to approve or deny a received message that fails RMA . Request to add a requirement to create such an extension to queues of purpose CONFIRM (to allow approve/deny RMA).
To enable received messages that fail RMA to be processed in a MER queue defined as confim, ValidateRM and the actions approve/deny RMA.
MER and RMA screens displaying incorrect datetime in browser
PBB required a short term solution to to display correct datetime in Browser (MER and RMA screens). It would be great if there's a configurable option to control the display of timestamp in browser: * default - the current behavior, displaying loc...
Multiple User sessions to FTM MER, AO and RMA facilities
Multiple User sessions to FTM MER, AO, and RMA facilities As of now, all users are allowed to log in to multiple sessions at multiple workstations at once. This should not be allowed, instead, the previous session should be kicked out whenever the...
FTM-MER should be able to handle this double slash (//) checking
FTM-MER should be able to handle this double slash (//) checking In existing Merva users are required to key in a double slash '//' at the beginning of each account number. In FTM this is not required anymore but since the users are used to keying...
Expected FTM-MER NOT to split bank/location or Prefix/Suffix
Expected FTM-MER NOT to split bank/location or Prefix/Suffix. Field 22 - for MT305 / MT600 Field 22C - for MT300, MT320 For example, current MERVA: Party Ref Party PBBEK0 0175 PBBEPX FTM-MER: Party Prefix PBBE Party Suffix K0 Ref 0175 Party Prefix...
PBB User expecting to have shortcut button to view the next message instead of user have to quit (return to the queue) then only to select the next message in FTM-MER 1) User excepting Next button after opening the message from Message List page 2...
Do not place IBM confidential, company confidential, or personal information into any field.