This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
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
Specific links you will want to bookmark for future use
Safer Payments server stops responding when sending requests with HTTP header "Transfer-encoding: chunked" Use case Sample: curl -k \ -X POST https://safer-payments.uat.feci.geci:37911/ \ -H "X-SP-Protocol-Version: 1" \ -H "Accept: application/jso...
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.
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 ...
New AML Type/AML Timestamp field (Duplicate of SP Fraud Type/Timestamp)
A field similar to SP Fraud type/SP Fraud Timestamp is needed for AML marking purposes We have had cases where we would need to mark a transaction as both fraud and an AML type This would have the same function as SP fraud type/timestamp field as ...
Queries Data selection - In “Choose attributes as columns for the query result table”, there should be a column to inform the Case ID. (associate the case ID with the transaction)Possibility do “join” cases with transactions
Monitoring Test Rules - It should be possible testing rules (lists from monitoring) against history (period of time definable by the user), before enable them. (Sandbox). It could be a query with the same attributes (index + filter criteria)
Do not place IBM confidential, company confidential, or personal information into any field.