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 Aspera Ideas
Created by Guest
Created on May 29, 2026

RELATED IDEAS

Aspera Connect monitor overwrites user-defined Faspex form "Title" with local file/folder paths

There is a critical data-integration gap between the Faspex web front-end and the Aspera Connect desktop engine.

When sending a package, the web interface places the Title field explicitly at the very top of the form, signaling to the user that this text string is the global identifier for the transaction. However, during the actual upload, the Aspera Connect background app completely ignores this user-defined metadata. Instead, it blindly populates the "Title" field in the transfer monitor using raw local file paths or folder names (e.g., grabbing the first subfolder alphabetically, like "Avid bin (+2)").

The Impact: This causes severe user confusion, making it look like the wrong package name or data payload is being transmitted. It forces users to alter their clean local folder workflows (creating artificial "wrapper" parent directories) just to force the progress monitor to display a recognizable title.

Requested Fix: The Aspera Connect background transport app must be updated to dynamically inherit and display the string defined in the Faspex web form's "Title" field, rather than falling back to local folder path names.

Idea priority Urgent

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.