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
Currently we need to manually select and delete expired risk list entries. We would like to see an option to enable this for a lisk and have the daily maintenance job wipe the expired entries from the list.
The client has a requirement to see exactly case related transactions under the case when we use a calendar profile. For example; (1month calendar - txns amount > 1000 and sent to Turkey).. We can put a query with the same conditions and I can ...
Consolidated alarm in Index Based Evaluation cases should show the timestamp of the aggregated hits and also the IBE name that triggered the hit
Right now it only shows the index value and the score and investigator has no way of knowing when the hits were aggregated. So if in a case there are multiple hits consolidated the investigator has no way of knowing which hit was aggregated at wha...
2-point review of cases Looking for a solution (enhancement) where after an analyst dispositions a case but the case meets pre-defined criteria i.e., New Account Open, High Dollar Value, High Dollar Deposits etc. would then be reviewed by a 2nd an...
User Preference settings for Case Management set up
Have one control setting for user preferences on how they want Investigation cases to look. It seems I have to set my column and field preferences for each queue. SP should have one control setting for cases.
Working queue- change functionality offers too much capability
As an External Admin User with working queue-change privileges, I can do more than just add the user to the queue. I can change Insertion Conditions when these are preset by Network and should not be changed.
The change feature should break ou...
During Safer Payments implementation some issues were raised regarding the form SP relates the transaction messages with mandators. In the mandator structure there needs to have Issuers and Acquirers. Most of transactions belong to two mandators, ...
To allow merchants interaction with SaferPayments SIBS FPS is planning to give the access to them. We were informed that merchants will not be able to change but will be able to see rules at higher mandators lever. This is not desirable. As a proc...
New data type: geolocation, built using the longitude, latitude and a margin of error, allowing a more seamless use of distance calculations on profiling attributes (e.g. in a counter calculate the number of chip transactions in a radius of 10 km ...
Define overwritable input attributes which values can be changed in the monitoring tab, to influence rules per mandator (e.g. define a numeric attribute from 0 to 1, that a mandator could customize and influence a rule; or use it as a threshold to...
Do not place IBM confidential, company confidential, or personal information into any field.