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.
Resuming support for duplet detection and not storing identical sequence values
In Safer Payments 6.3.0.01 it seems that duplet detection and the option for not storing identical sequence values for indexes are still not present. In the index create/edit page the "store entries with identical sequence values" checkbox is not ...
Currently, the computation methods available within SP for profiling attributes is limited. For example, for calendar profiles all that is available is: average amount, frequency, total amount . Standard Deviation is available for this category of...
Automatically filter rules table when the "Open Rules Table" option is selected
Within the Model Components screen, the user has the option to check a particular component and select "Open Rules Table". When that option is selected, the user is redirected to the Rules screen for a view of all rules, regardless of model compon...
Use hexadecimal attributes as reference attribute in counters
Currently, Safer Payments only allows the usage of Numeric and Text attributes as reference attributes in counters. This limits the usage of counters with computation "Most occurrence value" to those two types.
Ability to Aggregate cases within a Single Case Class or an identified list of Case Classes
We only have one Mandator, so Case Aggregation across the entire mandator is not feasible. We have many teams that work different streams and require to aggregate the cases within a case class or an identified list of case classes so that alerts f...
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.
Do not place IBM confidential, company confidential, or personal information into any field.