Skip to Main Content
Digital Business Automation Ideas

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

Start by posting 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 notifications 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 that cannot be implemented in a reasonable time.

Please use the following category to raise ideas for these offerings for all environments (traditional on premises, containers, on cloud):

  • Cloud Pak for Automation - incl Business Automation Studio, Business Automation Insights

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

  • Content and Capture Services - incl Filenet, Automation Document Processing, Daeja, Navigator, Content Collector, Enterprise Records, Business Automation Content Analyzer, Datacap, Automation Mobile Capture, Content Manager OnDemand, IBM Content Manager

  • Automation Decision Services (ADS) - incl ADS, Operational Decision Manager

  • Robotic Process Automation

  • Robotic Process Automation with Automation Anywhere

  • IBM Blueworks Live

If you encounter any issues accessing the Ideas portals, please send email describing the issue to ideasibm@us.ibm.com for resolution. For more information about IBM's Ideas program visit ibm.com/ideas.

Status Not under consideration
Created by Guest
Created on Apr 21, 2022

cmod do not allow oam storage set assignment for application group that is expire type segment

when an application group is assigned to a storage set that was initially cache only and then a storage node for oam is added and marked for load data....... arsmaint is expiring the cmod indexes, but not the oam directory rows or oam objects.


this issue came to light because OAM's OSMC cycle was running for hours for this specific OAM storage group. Even though CMOD is controlling expiration, OSMC runs a query to grab all rows may needing attention (including expiration from its perspective). Then it determines that the expire exit is not needed.


If not supported, then the definition via the admin client and arsxml should not allow it.

Idea priority Medium
  • Guest
    Apr 27, 2022

    i understand your comments and I know all about ECM Lab Services.... I was part of it for 7+ years. And I already wrote code to clean this up. My request was to have the admin client prevent this combination. If you know it will be a problem, why do you allow it to occur. If it is not a supported combination, dont allow it.

  • Admin
    NEIL Parrott
    Apr 26, 2022

    Expiration type of SEGMENT has never expired data (via arsmaint) from any storage manager, including OAM. It was specifically designed this way 30 years ago to avoid doing individual object deletes and instead allows the storage manager to expire the data. It was also known that such an approach allows for the metadata and physical data to not be in sync, but that was the acceptable use case for this expiration type. If you require metadata and physical data to be in sync, expiration type of LOAD must be specified, which is also the default expiration type when creating application groups. If you do have application groups with an expiration type of SEGMENT, then IBM ECM Services does provide a way in which to move an application group with expiration type of SEGMENT to LOAD.

  • Guest
    Apr 26, 2022

    you are not 100% correct. when arsmaint runs it deletes the application data and then makes a call to OAM to delete the data. It has worked that way for years. OAM has the auto delete feature disabled so cmod controls all expiration. The difference is that it works differently for expire type segment. If you dont support this approach for segment expire type, then fine. all I am asking is to disable that combination if not supported. The current set up allows a disconnect between the life of data and indexes and the document objects themselves.

  • Admin
    NEIL Parrott
    Apr 26, 2022

    Not a defect. Content Manager OnDemand and the archive storage manager delete the documents that expired index data points to independently of each other. Content Manager OnDemand uses the application group's expiration policy to determine when indexes and documents expire and should be removed from the system. The archive storage manager marks documents for removal based on the criteria specified in the archive copy group. However, you should specify the same criteria to Content Manager OnDemand and the archive storage manager. The Life of Data and Indexes, which is used by Content Manager OnDemand, and the Retention Period, which is used by the archive storage manager, should specify the same value.

    Content Manager OnDemand does not explicitly delete data stored with segment or document expiration from the Storage Manager (e.g. OAM), however, the data might still expire in the storage manager (e.g. OAM) based on its expiration settings.


  • Guest
    Apr 26, 2022

    and you do delete the physical data from cache


  • Guest
    Apr 26, 2022

    if not supported then the code should prevent it from being used...... this is a bug

  • Admin
    NEIL Parrott
    Apr 26, 2022

    For Expiration type segment, CMOD only expires the meta-data not the physical data.

    Use expiration type 'Load' if you want both to be expired.