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
Solution packaging and deployement using both BA Studio and ACCE configuration
The goal is to automate as much as possible the CP4A/BA Studio solution deployment.
For the moment, when you design a solution within BA Studio, for the document management part, you can only configure the document types, associated properties and some basic parameters. As soon as we need to configure more finely the content management part (security, behavior, etc), we need to use the ACCE.
There’s some direct impact of this limitation on the detailed configuration capability within BA Studio for the Content Management part on the solution rollout/lifecycle:
- Once we need to use ACCE for some advance management configuration, it’s no more possible to deploy a BA Studio solution using only the standard solution deployment process. It requires to complete the deployment with FileNet Deployment Manager (FDM) tool to deploy ACCE specific configurations.
As the goal is to automate the solution deployment across many CP4A environments without human interaction, FDM is a problem because there’s a command line to execute the work but the selection of the items to be deployed from one environment to another one is still a manual operation.
Our request is to enhance BA Studio/solution deployment to be able to package the solution with all configuration (including the configuration from the ACCE) and therefore rollout the solution to many CP4A deployment without adding FDM operations.
Do not place IBM confidential, company confidential, or personal information into any field.