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,
Post an idea
Upvote ideas that matter most to you
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
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 email@example.com for resolution. For more information about IBM's Ideas program visit ibm.com/ideas.
Restricting Publisihng Until Approved through Approval Workflow
Within BWL, there are approval workflows in place, but they simply do not restrict anything. For instance, it is a very common business case to require an approval from an assigned user before anyone can Publish a process map.
The approval process can easily be created, but there are no systematic restrictions tied to this workflow.
Why is it useful?
Instead of having an in-flight approval process that doesn't actually enforce/restrict anything, there should be an option to reduce deisred functionality (specifically Publishing process blueprints) until the system registers the correct Approval. This allows the business to be much more confident that unwanted changes aren't occuring within a process.
Do not place IBM confidential, company confidential, or personal information into any field.