Add a flatten option to Aspera for Desktop so downloaded packages and files land directly in the configured download location

What is the idea:

Aspera for Desktop should offer an option, per download location or per automation task, to write package contents directly into the configured download path without creating intermediate folders. Today Aspera for Desktop creates two extra levels under the download location, the inbox name and the package name, so files arrive at <download location>/<inbox>/<package name>/<content> rather than at <download location>/<content>.

Why it matters:

Automated post processing pipelines watch a fixed directory for arriving content. When the client inserts folder levels that vary per package, every downstream tool that consumes that directory has to be rewritten to walk an unpredictable tree, or a separate script has to move files out of the generated folders after every download. IBM Aspera Connect 4.2.19 wrote content directly into the configured path, so migrating from Connect to Aspera for Desktop breaks these pipelines with no supported way to restore the previous layout.

What we would like:

An explicit setting, available in the UI and in the automation task configuration, with values such as preserve package structure, which is today's behaviour and stays the default, and flatten to download location, which writes package contents straight into the configured path. Ideally with a defined behaviour for filename collisions.

Who is affected:

Any customer running unattended package automation into an existing media or data pipeline, particularly customers migrating from Connect where the previous layout is assumed by tooling already in production.