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.


Add a new idea Subscribe
Status Future consideration
Workspace Business Automation Workflow
Created by Guest
Created on Sep 29, 2025

RELATED IDEAS

Support multiple MQ input queues for BAW runtime in CP4BA

Currently CP4BA BAW only supports one single input queue for all automations. We would like to have support for multiple queues.

This makes it possible for each business line and business application to have responsible for its own queues, making the system modular and easier to maintain. Some processes are using queues quite intensively. Not only to start processes (and create tasks)  but to do business operations. 

In the requested implementation when one module fails to process a message, retries and backout queues handling are isolated to that module.  Especially massive failures (lot of  “poisoned” messages) affects only one module (= one application, one business line). In case of one queue per whole CP4BA installation – it affects the whole instance.

It will also provide cleaner insight for monitoring/observability. It is relatively easy to track throughput, failures, and metrics per period of time, situation like queue is full (max depth reached),  backout queue contains messages for longer than x hours , Z days etc. and send notification to proper teams.

Idea priority Urgent
  • Guest
    Mar 18, 2026

    To make this feature viable for production use, more than support for multiple queues is required. The following areas need to be addressed:

    1. Payload Support

    The current implementation assumes the payload is always JSON. While this is sufficient for new systems, legacy applications frequently utilize XML, XBRL, YAML, and other text formats. The solution should be flexible enough to handle these diverse data types.

    2. Message type recognition

    Currently, the system requires message tagging/labeling via custom headers (e.g. automation, mqService, operation). For simple integrations, it would be much more efficient to store this configuration statically in BAW (for example a 1-to-1 mapping  - Queue Name to Service/Operation ). This removes the burden on senders to create specific custom headers.

    3. Headers handling and correlation

    The current solution mandates specific custom headers while ignoring standard ones, such as MQMD and MQRFH2 (specifically JMSMessageID, JMSCorrelationID, and JMSType). JMSType is often used to distinguish between different message types within a single queue. JMSMessageID or  JMSCorrelationID are essential for correlation keys in two-way MQ communication. I think it will be  better to pass the MQ message "as is," including all headers and the unparsed payload string. The BAW developer's task should be to identify the message (based on the queue, headers  or payload) and perform the necessary parsing and transformation into a data object.

    4. Stability and Isolation

    The current solution is quite fragile; if the configuration for an activation specification is incorrect, the entire server (Teamworks app) fails to start. In a development environment, this renders the Process Center inaccessible. It will be nice to have MQ receiver isolated  from the Process Center / Process Server to ensure that a configuration error does not crash the entire environment, while still maintaining transactional integrity.

    Reply

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.