Skip to Main Content
IBM Data and AI RegTech Ideas Portal

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:

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

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

Shorter URL for this site is: or

Status Delivered
Created by Guest
Created on Aug 7, 2019

FTM enhancement for audit log message, plus additional restriction number of Transaction UI query results

We have had multiple instances of BCC operators performing queries from the Transactions UI that return a huge number of results, which results in core dumps and out of memory alerts. The existing property that was added in IPD to require at least two filters to be used is only partially successful in preventing this issue. There is also no audit log message that identifies who performed the query and what filters and values were used.

  • Admin
    Craig Rector
    Oct 22, 2020

    Implemented in v3.1 and above

  • Guest
    Jan 10, 2020

    From Top Ten: Federal Reserve (Steve Purser), Item Number: 2018012, Votes: 0, IBM T-Shirt: S

    Top Ten Duplicate of FTMCHECK-I-74


    FTM enhancement for audit log message.


    Add a message in the Audit log that would allow a customer to confirm that an FTM BCC operator was attempting a BCC Transaction UI query. The audit message should include what filters were used and the values for those filters.
    To further decrease the chances of BCC users performing queries that return an extraordinary number of results, include an informational message on the “Transactions” BCC query screen that tells the operator how many rows would be returned before actually retrieving a potentially huge number of rows to format for display on the BCC. We believe would also be feasible and desirable.
    To further tighten the Transaction query processing, we request to have a property that could be configured to have a maximum limit to the number of rows that could be returned. So, if all earlier warnings (“you must use more than one filter”, and “your query will result in 892,118 rows”, etc) have not resulted in the operator using filter criteria to limit the query results, a hard maximum of the customer’s choice (probably set in CORE_PROPERTIES table) could prevent an extraordinarily high number of results being returned and potentially exhausting heap space.


    Comments: Ask Steve about this one.    Emailed FRB (Steve) 10/23/2018.