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.
be able to switch to LDAP group if same-named BPM group already exists (without the chaos that deleting the BPM group causes)
The current requirement to delete the BPM security group before the same-named LDAP group can be recognized is too destructive:
• The deleted security group also might have been a nested group for some other BPM security group. There is not a UI that I know of that would tell you the parents
• When you remove the BPM security group, it gets disassociated from all the Teams which might including it in their definition or Team Bindings! There is no list you are provided in advance to tell you which Teams in which Snapshots of which Process Apps (or Toolkits) you would have to recompose. I believe in some cases you may not even have a UI that could get to certain Teams.
One known use-case is if a Process App - which has a Team definition which specifies a "standard group" is deployed or imported to an environment where the "standard group" name does not exist. To satisfy the group-name reference, a BPM security group with that name is created with the description:
"Auto generated during snapshot installment"
This *blocks* the ability for BPM to later recognize an LDAP group with that same group-name.
BPM does not offer an ability to switch over to the LDAP group without first deleting the same-named BPM security group -- which can be destructive (as described in the RFE description).
Do not place IBM confidential, company confidential, or personal information into any field.