IBM Data and AI Ideas Portal for Customers


Shape the future of IBM!

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


ADD A NEW IDEA

FILTER BY CATEGORY

FTM for Digital Payments

Showing 77

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...

Ability to call FTM via product exposed rest API for any type of payment.

Ability to call FTM via product exposed rest API for any type of payment.Ex: ACH payments, RTP payments, WiresIdeally single API that accomodates any type of payment rail
over 2 years ago in FTM for Digital Payments / APIs & SDKs 1 Future consideration

UI enhancements to Exposure Limits monitoring screen

To make the Exposure Limit Monitoring screen more user friendly by - 1. tying it with the Partners screen for specific partner2. to allow to sort on the columns (not possible in 3.0.6.5)3. when user navigates to the Exposure Limit Monitoring detai...
over 2 years ago in FTM for Digital Payments / Other 1 Future consideration

Make entitlements easy to align with roles or give better documentation

Rename and make the entitlements and roles in alignment with how they look on the FTM UI to make it easy to understand by selecting an option, the role will get to do 'x' action and view/edit on 'y' screen.The current entitlements are very cryptic...
over 2 years ago in FTM for Digital Payments / Administration & Configuration 0 Future consideration

Detail exact trigger for missing or late files

HNB requests IBM to find a better solution for more exact triggering for Missing or Late files; FTM can't provide the detail we expect and creates too many false positives when used for this. We want to be able to specify the Incoming ACH verses t...
over 2 years ago in FTM for Digital Payments / Alerting & Notification 4 Future consideration

FTM dependency on Websphere Scheduler prevents hot/hot availability across data centers

FTM for Digital Payments is dependent on the underlying Websphere Scheduler to run scheduled framework tasks. It is also a WebSphere best practice is to not run a WebSphere cell across data centers. This leaves customers with an implementation tha...
over 2 years ago in FTM for Digital Payments / High Availability, Zero Downtime 0 Future consideration

supress multiple refresh on Physical inbound Transmission screen

we had a scenario where user's Physical Inbound Transmission screen was not loaded properly and user started clicking f5 which had caused multiple calls to the the DB's and caused DB degradation
about 1 year ago in FTM for Digital Payments / Other 0 Future consideration