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 Not under consideration
Workspace App Connect
Created by Guest
Created on May 17, 2023

Add the long description for bar files

by adding a long description in the bar file in an environments with multiple deployed applications it is used to describe the deployed resource so the owner can easily see what the application is used for. 

Idea priority High
  • Admin
    Ben Thompson
    May 23, 2023

    Idea review. Thank you for taking the time to raise this suggestion, which for now we are placing into status Not Under Consideration, pending further feedback ... Unfortunately it wasn't clear from the suggestion whether the desire for a description field relates to Message Flow level, Application level ... or to be attached to the BAR file itself? Given that a message flow has description fields, which are also reported back through the admin REST API (and displayed in both Toolkit and WebUI), we assume that the request doesn't relate to flows? For application-wide description fields, we don't currently have a natural artifact file to which we would attach the property (conceptually we can consider the application like a "folder" or directory on the system), but this aspect of implementation could potentially be overcome if this was the intention. Regarding the third possibility of a BAR file, we would not be in favour of carrying a description field to be persisted in the runtime on the BAR file ... The BAR file is sometimes described as a "carrier bag" which has help and meaning in moving artifacts from source to server, but is not a concept which is persisted in the runtime - once its artifacts are deployed (which could be iterative) the BAR file is "discarded". As mentioned, for now we are returning the idea but please feel free to add further information if we've misunderstood and we can comment further.