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 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.
Allow saving of user created history entries while ensuring the original message is kept. Properties in DnqErQueueOutput.
Addition of new configuration properties for the DnqErQueueOutput node to allow saving of user created history entries while enforcing that the message is kept the orignal as read in DnqErQueueInput node.
Our users manage messages waiting for ACK in MERVA in this way: when a message is delivered to WBIFN to be sent, itis also recorded in a MERVA queue called WAITING ACK. This queue is visible to final users. When the ack arrives, the message is del...
Do not place IBM confidential, company confidential, or personal information into any field.