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 TCH - Considers weekends as holidays by default - Remove this default configs to allow clients to make the decision
Huntington has used the out of the box Product Deadlines provided by IBM for TCH Receive (TCHI – Product Code). This setup indicates that Saturday and Sunday are to be treated as business days. These days are not treated as business days by busine...
Zelle - create (or fix) a timeout value that takes the entire payment flow into consideration
We currently have a problem where the front end has a 20 second time and Zelle has a 15 second timeout but because of the way the product is designed the15 second time applies to multiple components (applying that 15 sec timeout to each component)...
FTM allows user searches via FTM UI to impact transaction performance
This defect was reported in case TS002616911. IBM L3 will not address this defect via the PMR process.
We are looking for a permanent fix to configure a timeout for FTM user searches where FTM/DB would kill the database work after X seconds an...
Responder Name should continue to be a valid field in ZellePaymentRequest as it is today in CXCPaymentRequest
Currently responderName is a field used in CXCPaymentRequest which also populates in CXCParticipantView in the Outgoing Payment Request section. This allows us to use the name the customer saves in their contact list (FTM Recipients). We provide a...
When testing a setup change on the FS37 system at IBM, there was a typo in one of the Collectors. This raised errors in the log (see screen shot of system log), and these errors should have kept the release from activating. However, the BR UI showed the new release as Active (see screen shot of UI).
DescriptionUsing POST CXCPayment, we are sending a value for the isRecurring element. We are sending true for that value, however when we run a GET CXCParticipantView that value is not true (which we take to mean that the value is not stored in th...
Enhancements to define/build filter modal on Inbound transactions screen
The Match case checkbox on the Build Filter on Inbound transaction screen, needs a tooltip (helptext) to let the user what it does. It is not something that a user will pay attention to until they fail in filtering using the criteria. If this is n...
Do not place IBM confidential, company confidential, or personal information into any field.