Skip to Main Content
Digital Business Automation Ideas

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:

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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

  • Automation Decision Services (ADS) - incl ADS, Operational Decision Manager

  • Robotic Process Automation

  • 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 ideasibm@us.ibm.com for resolution. For more information about IBM's Ideas program visit ibm.com/ideas.

Status Future consideration
Created by Guest
Created on Apr 20, 2022

enhance the ODM DC merge

As mentioned in the doc: https://www.ibm.com/docs/en/odm/8.11.0?topic=branches-merging ODM DC always has this limitation that certain changes cannot be merged and must be published separately from RD, as they are not versioned. But from user's point of view, they expect every change can be brought into the target during merge.
Idea priority Medium
  • Guest
    Apr 22, 2022

    Michael Obadia
    The main problem is that the project info is not versionnable and hence not mergeable.
    What I did for the copy release is to replace every project info data of the target branch (categories, dynamic xom, dependencies, build mode, extractors etc) with the same data from the source branch.
    In this case, I guess we could compare the project infos content to see if they are different. There will be some UI work too in order to display/inform about those differences.
    Note that there is a project info per branch so in case of a branch with many dependencies, there might be many differences to report.

    Philippe Guerin
    So to be able to display the changes in project infos and to merge them eventually (by copying the content), that would imply to handle them in a specific way, not using the synchronization. This would be quite an extension of the merge view, which relies exclusively on the synchronization as of today. Maybe we could extend the simulation process to handle that specific case. We need to investigate further to determine the complexity of this.

  • Admin
    Antony Viaud
    Apr 21, 2022

    Hello, I'm checking with the dev team if there could be at least a warning indicating that some elements between the 2 branches to merge are different, although the merge tool cannot do so (as described in the doc in https://www.ibm.com/docs/en/odm/8.11.0?topic=branches-merging )