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.
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...
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.
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...
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...
OAMS Administration Utility dnfcaoma -Expand message section criteria for action delete and delete force.
Modify the Financial Transaction Manager utility dnfcaoma to provide targeted selection criteria for removal of a large volume of unwanted messages that are interrupting message delivery. Selection criteria should include 1) sending bic 11 positio...
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...
FTM for Swift Services RMA import display number of records to be processed in trial mode
The import RM (relationship management) command used to import RM records from a distribution file into the RM data store already has the parameter -trial.It could be useful that when an import has issued with the -trial parameter, it display also...
Implement a config property that allow to control the printing of deleted messages on FTM for SS
When a message is deleted from print queue, a printout is send on the printer. This behavior is as expected, but it would be better to implement a config property that allow to control the printing of deleted messages.
Do not place IBM confidential, company confidential, or personal information into any field.