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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Created by Guest
Created on Apr 25, 2024

Support for FNCM Operator in separate namespace(s) to it's operands on OpenShift

On OpenShift deploying FNCM as on CNCF with no Cluster roles is not a supported configuration.  FNCM when deployed on OpenShift requires Cluster Level roles (for Cluster level artefacts such as Routes).  On a shared Cluster (multiple customers or multiple solutions) the Cluster operations team/providers commonly have policy restrictions or prohibitions on any Cluster level roles and customer access to any ServiceAccounts with such privileges.  The concern is both with the actual privileges (information leakages, impact on other namespaces) and secondly privilege escalation or takeover of roles.  LBG are deploying into an internal shared (internal) customer and solution OCP Cluster.  The Policy is that no Cluster level roles are permitted to be managed by customer/solution teams and preferably are not used at all by solutions.


A partial solution is for the Cluster Operations team to manage the operator: as it is co-located with the operand (FileNet) this means that they are in effect managing FileNet.  This is the worst case solution for our customer - one of the big 4 Banks in the UK.  They would lose autonomy and control over their FileNet solution.

 If the FNCM operator could be in a separate namespace to it's operand(s) (one to one or one to many) - FNCM in the "Dev FNCM Operator" namespace managing the 'Dev FileNet with CR' namespace we would argue for the Cluster Management team owning the FNCM Operator namespace and the FileNet team managing the CR in the FNCM namespace.  We would need to negotiate for management of FNCM in lower (Dev or similar) Clusters to allow the FilNet team to understand and direct changes but we believe this would be viable. A one to one mapping would permit versioning across the Cluster and route-to-live ripple testing of versions and changes through standard environments mapped to namespaces. 

The better solution may be support for FNCM without cluster level roles on OCP - that is the subject of a second 'idea' submitted by Olivier Guyotot for this customer.



Idea priority Urgent