IBM RegTech Ideas Portal



Our team welcomes any feedback and suggestions you have for improving our offerings. This forum allows us to connect your product improvement ideas with IBM product and engineering teams.


For product documentation, see Knowledge Center.
Create and View Support Cases and Use the Discussion Forum here


Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases


The shorter URL for this site is:

IBMers, please visit the WFSS Internal Ideas portal


note: The IBM ICM IDEAS Portal is no longer available at this location. If you have reached this page, please look for a new link in the Varicent Administrator. Direct links are found under the "?" in the upper right corner.
A period of transition is likely to impact this service, while ICM becomes Varicent. Please contact Varicent support if you have additional challenges or concerns.

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.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Aug 7 2019
  • Reviewing
Component Administration & Configuration
Priority Medium - Important
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    10 Jan 04:44pm

    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.