Skip to Main Content

This is an IBM Automation portal for Integration 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 (

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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Under review
Workspace App Connect
Created by Guest
Created on May 10, 2024

Ability to reload OpenAPI definitions for API's in design

API are intended for reusabilty. Ideally they are grouped by functional relationships, which help assure improved management of the API flow. As a result of these groupings, there will be times will be times when additional methods and changes would need to be added to a group of flows contained in a single API flow Designer Flow.

The problem that arises is that once the API has been cataloged, updates to the methods can not be made by reimporting the OpenAPI without deleting it or creating another. This can have large impacts if the API is used in multiple flows. If a change needs to be made it is possible that every flow that uses the catalogged API will have to be changed.

Need the ability to update API definitions without having to reconnect all flows to a new API definition.

Idea priority High
  • Admin
    Ben Thompson
    May 10, 2024

    This request poses an interesting conceptual question about the desired lifecycle of the Open API definition and the lifecycle of the flow logic which is then executed. In ACE Toolkit message flows, we separate the API definition yaml from the flow definition (.msgflow) and also have one subflow (separate .subflow) file per operation. This gives users options for controlling the lifecycle of those file assets independently should they so desire. When also considering the wider ramifications within a managed software service (assuming that this requirement is raised within the context of ACEaaS on AWS?), there are further considerations for the internal architecture (such as where Open API definitions need to be pushed to under the covers when updated - potentially into both a gateway component and a flow execution component). Moving status of this request to Under Review for the PM team for ACEaaS on AWS to consider.