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
Improved retry handling for FA transfers based on status information
The request is needed since the retry for files in Accepted status is no more needed given that SWIFT retries for 4 hours, if after 4 hours a file is not sent, it means that a huge technical problem is likely affecting the receiver, in this case w...
As discussed with Gabi von Carlowitz, I opened this RFE. It is regarding the length checking functionality which is missing in the MER application to avoid that customer entered too long message and thinking that the message is valid.
Message Entry and Repair facility in FTM for SWIFT (formerly WBIFN):when entering a non-SWIFT-character into the field 20, the error message refers to the expected field length, and it also limits the range of valid characters to SWIFT characters:...
1. Allow to mark failed Q&A transmission as handled outside the system (refer to MR0821142527 in WBI-FN requirements database)
Customer needs a way to distinct read and unread records from those failed Q&A transmissions, since these data ...
In A&O, customer suggests to have enriched functions of Logical Terminals from the requirement below.
Multiple choice of LTs for the case when the wanted action from end-user is identical.
2. Group/Filter LTs by OUs.
Client is looking for custom screen, custom fields, and search options in the FTM4SWIFT MER screen.
Currently, In MERVA environment client using custom MERVA screen and custom fields to journal (Message Tracking) all incoming/outgoing FIN SWIFT messages as well re-routing activities within MERVA branches/users.
For All the Message Types, the fo...
The printed message layout is unclear by using MER local-printing solution.
System: WBIFN MERActor: End-user Customer uses MER Local-printing function to print out their business messages. The printed messages are treated as very important evidence for their further off-line processing and hard copy. However, in some case...
Do not place IBM confidential, company confidential, or personal information into any field.