Integration


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 (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 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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Add a new idea Subscribe
Status Submitted
Workspace App Connect
Created by Guest
Created on Jul 10, 2025

RELATED IDEAS

Designer: Version controlled artifacts / Git integration

We think Designer should natively integrate with a CVS, commonly GIT.

For Designer instances in ACEcc or probably also  in the new "IBM webmethods hybrid integration" platform, where you can't just sync the Designer's local filesystem with a Git repo, a direct integration from Designer to Git would deliver the following benefits:

- Backup and version history of development artifacts without additional system backups or manual flow downloads
- Reverting to a dedicated flow state / version, or just restore your last functioning flow version (as there is no "undo" in Designer)
- Tagging for explicit versioning
- Sync with CI/CD pipeline on tags / commits: stage and deploy without manually downloading your flow and manually uploading it somewhere else
- Enables a content- or a visual flow diff

This should also include the connection artifacts used by the flow, with externalized secrets variables. Depending on the way the secrets are managed, they need to be injected in the appropriate stage. But the name and type of the connections used by the flow should come with it.
In order to deploy the flow to the next stage, the BAR file also should be versioned OR there should be a tooling to build a Designer BAR file directly in a CI/CD Pipeline.
 

Idea priority High
  • Guest
    Jul 23, 2025

    Additional comment: 

    The initial requirement is quite well explained. 

    Let me add some further thoughts: 

    Using the Designer locally would allow to have a "git integration" outside of the IDE on a file / folder level. 
    So this would be a "workaround". 

    However this comes with some drawback / open question: 
    - the user needs to perform each git action outside of the Designer (commit. checking, tagging etc.). So the user needs an additional tooling - which becomes unhandy. 
    - the git integration on file / folder level would only work for local Designers - but not for any Designer deployed in Container or as SaaS. A "native git integration" in the product would be more beneficial as it would allow to share the artefacts across different Designer Authoring deployment flavors 
    (onprem, container, SaaS etc.) 

     

    Reply

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.