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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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 Automation - including Business Automation Studio, Business Automation Insights
Business Automation Workflow (BAW) - including BAW, Business Process Manager, Workstream Services, Business Performance Center, Advanced Case Management
Content and Capture Services - including 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) - including ADS, Operational Decision Manager
Robotic Process Automation
Robotic Process Automation with Automation Anywhere
IBM Blueworks Live
Specific links you will want to bookmark for future use
Add a guardrail feature in CP4BA to avoid Elastic Mapping Explosion or alert them upon reaching a certain threshold
Elastic Search has a known issue called "Mapping Explosion" (More about it here: https://www.elastic.co/blog/3-ways-to-prevent-mapping-explosion-in-elasticsearch), the issue is CP4BA by default is configured to use 1000 fields in Elastic and when customers have multiple Rule Apps in ODM and generate rich messages/events they can easily exhaust the 1000 unique fields threshold and run into a Mapping explosion situation which results in corrupted Kafka instance.
The recovery from this is painful and frustrating especially it will disrupt the business of the customer and there is no warning posted by the product.
The idea is to add some guardrails in CP4BA to prevent/detect/or even warn the customers about potential Mapping Explosion before it occurs so that they take corrective actions accordingly.
Do not place IBM confidential, company confidential, or personal information into any field.