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.
Currently users have to enter memos and then save them and then transition the case to close. It would be helpful to have the memos automatically save when cases are transitioned from one state to another to avoid any lost messages.
It would be beneficial if the latency KPIs had the same condition capabilities as the transaction message rate KPIs. This would allow us to separate different message types in the dashboard and keep track of the latency separately instead of in a ...
Replace JSON script for Case Actions with a more user friendly UI
There are several business reasons that require a manual out going message. The current UI for manual outgoing messages is via case actions; the case actions UI requires the analyst to interact with JSON script
Ability to restrict a case to a particular queue when created from a Network only model/rule. Root Mandator implements a rule for it's own monitoring purpose and does not want the submandators to be able to view the case details.
Job and query execution by predefined time intervals
Create the possibility of executing queries, jobs and other data selection operations by a set of predefined time intervals like "last hour", "last day", "last week", "last month", etc.. It should be possible to apply these predefined time period ...
Provide doublet detection at the message type level, not just at the mandator level
The feature would allow doublets to have different configurations based on the type of message being processed. It would remove complexities of having to develop doublet detections across a wide variety of message types. It would reduce chance of ...
We intend to have a special Fraud Index that is updated when a transaction is set as fraudulent.
Currently, when we set transactions as fraudulent (using a merge) SaferPayments does not re-compute/insert indexes. We intend to have a new index typ...
Do not place IBM confidential, company confidential, or personal information into any field.