Skip to Main Content
IBM Data and AI Ideas Portal for Customers


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 updates on 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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps (http://ibm.biz/Data-and-AI-Roadmaps) - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at https://hybridcloudunit-internal.ideas.aha.io/


Status Future consideration
Workspace IBM Safer Payments
Components Technical
Created by Guest
Created on Sep 2, 2021

Safer Payments purge outdated entries limit

Problem Description:

Purge outdated entries of indexes inside IBM IRIS Safer Payments does not support the concept of span control to limit the scope of removal of all index entries that are older than a defined maximum lifetime period.

Supporting Details/Description:

The IBM Safer Payments uses a fully automated system for cleaning outdated entries within the limit of maximum lifetime. The lack of limiting the scope of entries to clean does not allow for IBM Safer Payments user control closing the Start End of Day (EoD) job before high traffic time, as the procedure does not stop until it completes purging whole data. For example: The amount of records marked for purging by the system is 50 million, the Start End of Day (EoD) job does not stop until it deletes all unnecessary data, and IBM Safer Payments enters the high traffic period with job running.

Recommended solution:

Customizing the number of entries to be purged will solve the crucial issue. With proper analysis and configuration, closing the task Start End of Day (EoD) job before peak load period is guaranteed and index will not intensely increase in size without creating unwanted load on CPU.

Needed By Month
  • Guest
    Mar 6, 2022

    Wouldn't it be better to define some defined "high traffic" timeframe which has no purging and no eod at all? - The period when there is no high traffic is analyzed and eod starts at this time, but the period is not enough to finish purging. You can not define high traffic timeframe when it work real-time, in that case IBM Safer Payments will catch potentially fraud transactions in defined timeframe!

    Limiting the number of purged records might be a solution but it wouldn't actually guarantee to finish the eod job before peak load -for example if there are other disk operations that slow down the purging of index entries.- When EOD starts, that specific instance is isolated and other operation are stopped. Of course, it is not guaranteed that job will not be finished, but is there any better solution?

  • Guest
    Feb 17, 2022

    Wouldn't it be better to define some defined "high traffic" timeframe which has no purging and no eod at all?
    Limiting the number of purged records might be a solution but it wouldn't actually guarantee to finish the eod job before peak load - for example if there are other disk operations that slow down the purging of index entries.