Skip to Main Content
Digital Business Automation Ideas


This is an IBM Automation portal for Digital Business Automation products. 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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Please use the following category to raise ideas for these offerings for all environments (traditional on premises, containers, on cloud):
  • Cloud Pak for Business Automation - including Business Automation Studio and App Designer, Business Automation Insights

  • Business Automation Workflow (BAW) - including BAW, Business Process Manager, Workstream Services, Business Performance Center, Advanced Case Management

  • Content Services - FileNet Content Manager

  • Content Services - Content Manager OnDemand

  • Content Services - Daeja Virtual Viewer

  • Content Services - Navigator

  • Content Services - Content Collector for Email, Sharepoint, Files

  • Content Services - Content Collector for SAP

  • Content Services - Enterprise Records

  • Content Services - Content Manager (CM8)

  • Datacap

  • Automation Document Processing

  • Automation Decision Services (ADS)

  • Operational Decision Manager

  • Robotic Process Automation

  • Robotic Process Automation with Automation Anywhere

  • Blueworks Live

  • Business Automation Manager Open Edition

  • IBM Process Mining


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.


Status Submitted
Created by Guest
Created on Nov 12, 2026

Improve performance of version deletion for document version series with a very large number of versions

Current Functionality: When a version is deleted through the Content Platform Engine (CPE), the server does the following work for each version:

  1. It locks and fetches the version from the DocVersion table, then looks up replica and federation dependencies.

It locks and fetches the whole version series, to decide whether the version is the last one, which version becomes current, and which is the previous major version.

It checks retention and holds.

It checks for deletion-action PREVENT or CASCADE relationships on the Annotation, Task, Subscription, Thumbnail, DocVersion (by owner document) and Relationship tables.

It checks for event handlers on the deletion event and runs them.

It writes the deletion to the DocVersion table and adds rows to the ContentQueue table.

It commits, then deletes the content asynchronously.

Step 2 is repeated in full for every version deleted, so the cost of each delete grows with the size of the version series. For a series with a very large number of versions, bulk deletion takes an extremely long time. The same behavior occurs with these methods:

  • the Java API, one version at a time

ACCE search with bulk actions

Sweep policy (document disposal)

deleting the whole version series in one operation

In reproduction testing on a 1,000-version series, deleting the superseded versions averaged about 0.6 seconds per version, about 569 seconds in total. A single whole-series delete of only 1,000 versions needed a very large transaction timeout. Rewriting the test to use UpdatingBatch and adding database indexes gave little or no improvement. Batching saves only about 5-10 ms of round trip per call, and the traces showed no slow queries to tune. Tuning Db2 (RUNSTATS/REORG, LOCKTIMEOUT) also made no meaningful difference.

Requested Functionality: Make deletion of versions in very large version series efficient enough for bulk cleanup, for example series of 100,000 or more versions.