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 Future consideration
Created by Guest
Created on Nov 18, 2021

Concurrent Access on Decision Table for Editing should not be allowed via Decision Center API

We have a utility exposed that leverages Decision Center APIs to fetch and update data within a decision table and deploy on RES for one of our decision services.


This utility is exposed and used by multiple clients. We've observed that when we receive concurrent or near parallel updates for the decision table, only one of the updates is persisted and deployed


Consider the following scenario:


- A request (Req01) is received by API (at 11:00:00 AM)

We call session.ownsLock() to check whether DT has been locked for edit (at 11:00:10 AM).

At the time DT was not locked so, ownsLock() returned False and we acquired lock on DT via session.lockElement() (at 11:00:20 AM).

- Another request (Req02) is received by API (at 11:00:05 AM)

We call session.ownsLock() to check whether DT has been locked for edit (at 11:00:15 AM).

At the time DT was still not locked so, ownsLock() returned False and we acquired lock on DT via session.lockElement() (at 11:00:22 AM).


We would like for above scenario to be catered such that checking and acquiring lock would be an atomic operation so that only one of the API requests above are allowed to proceed.


Below is a snippet of the implementation we have used:

if(this.session.ownsLock(this.decisionTable)) {

throw new RuntimeException("Decision table is locked by user");

} else {

this.session.lockElement(this.decisionTable, true, false);

}

Idea priority Urgent