Problem Statement

Currently, when a user opens an .sdlppx package in Trados Studio, they can only have one package dialog/wizard open at a time (can not select multiple .sdlppx packages).

1. Open package A → complete the import → close.

2. Open package B → complete the import → close.

3. Repeat for each package.

This is time-consuming and disrupts workflow, especially when comparing package contents or batch-processing packages.

Proposed Solution

A new app / utility that enables batch package handling within Trados Studio:

Core Features

1. Multi-package selection

   • Allow selecting multiple .sdlppx files from a folder via Ctrl+Click or Shift+Click.

   • Drag-and-drop multiple packages onto the app’s interface.

2. Queue manager

   • List all selected packages with metadata:

     • Package name

     • Status (Pending, In Progress, Completed, Error)

   • Buttons: Start All, Pause, Resume, Remove from queue.

3. Sequential but unattended processing

   • Open each package one after another automatically.

   • For each package, apply a default action 

   • If a package requires a decision (e.g., overwrite conflict), the queue pauses and highlights that package.

4. Session logging

   • After all packages are processed, generate a log:

     • Which packages succeeded/failed.

     • Errors or skipped items.

     • Time taken per package.

5. Optional dry-run mode

   • Preview what each package contains without actually importing – useful for checking before bulk processing.

Why This Is Valuable for Reviewers / Users

• Time-saving – process 20 packages in one go instead of 20 manual sessions.

• Less error-prone – avoids accidentally reopening the wrong package.

• Better for QA – compare multiple package contents side-by-side in the queue view.

• Ideal for power users – LSPs, project managers, or in-house teams receiving multiple packages daily.

Example User Workflow

1. PM receives 15 .sdlppx files from a client.

2. Opens the Multi-Package Workspace Manager app from the RWS AppStore.

3. Drags all 15 files into the app window.

4. Chooses default action

5. Clicks Start All → goes for coffee.

6. Returns to see a log: 14 succeeded, 1 failed due to missing language resource – easy to fix.

Technical Notes (for RWS review)

• The app would interface with the existing Sdl.Core.Package APIs.

• Should respect Studio’s existing package security (password-protected packages prompt once at start of queue).

• Must not violate the “one package wizard at a time” constraint – instead, it automates closing one and opening the next.

• Built as a Studio view (not a separate .exe) to stay inside Studio’s environment.