Introduction (Workpackages - Functionalities and Rules)
Workpackages replace the manual process of exporting and importing loc-kits to share work. By establishing a secure, one-way connection between two accounts, Account A (the sender) can allocate tasks directly to Account B (the receiver)
One-Way Flow: The Handshake connection is strictly one-way (Account A sends to Account B).
Approval Required: You can only send a Workpackage if your project is in the Approved status.
Exact State Transfer: When you send a Workpackage, the destination account receives the exact current state of the file, including any segments you have already confirmed or pre-translated.
Temporary Context: The system creates a temporary TM and Glossary in the receiving account for the duration of the project.
Phase 1: Setting up the Handshake
Before any files can be shared, both accounts must establish a "Handshake" agreement. You will need the exact UUID of the receiving account (Account B) to proceed.
Step 1: Sending the Invite (Account A)
Navigate to Settings > Translation Settings > Project Routing.
Click the Configurations tab, then select Handshake.
Click the + Invite Handshake button.
In the modal, paste the UUID of the receiving account (Account B) and click Confirm.
The invite status will appear as Pending. You can delete the invitation at any time before it is accepted.
Step 2: Accepting the Invite (Account B)
In Account B, navigate to the Handshake tab.
Locate the pending invitation and click Accept.
A configuration modal will appear. You must enter a Project Name Prefix. This prefix will be automatically added to the name of every project you receive via this Handshake.
Select the Authorized Org Units. Only the Org Units you select here will be allowed to receive Workpackage projects from Account A.
Note: Once accepted, you can click the edit icon to change the project prefix or adjust the authorized Org Units at any time.
Phase 2: Sending a Workpackage (Account A)
Once the Handshake is accepted, Account A can start sending work.
Open an Approved project.
Go to the Overview or Tasks tab and click the Import/Export dropdown menu.
Under the Work Package section, choose your sending scope:
Send Work Package for selected work units: Use this if you only want to outsource specific tasks or specific language pairs. You must select the desired tasks in the list first.
Send Work Package for all project work units: Use this to send the entire project scope to the receiving account.
How TM and Glossary are Handled
When you send the Workpackage, wxrks securely packages your context. The system automatically creates a new, temporary Translation Memory and Glossary exclusively for the destination project.
Comprehensive Matches: The exported package includes all relevant matches from your original Context tab, including fuzzy matches, ensuring the vendor has the best possible resources.
Phase 3: Receiving and Delivering (Account B)
Managing the Received Project
When Account A sends the Workpackage, a new project is automatically generated in Account B.
Project Naming: The project reference will follow the format: PREFIX - ORIGINAL PROJECT REFERENCE - PROJECT NAME.
Visual Indicators: The project will display a specific label/icon indicating it is a Workpackage project.
Inherited Settings: The project is created using the default settings (such as Price List and Contact Person) of the Org Unit you selected during the Handshake.
Temporary Context: You will see the temporary TM and Glossary attached to the project's Context tab.
Delivering the Workpackage Back to Account A
Once your team has completed the translation or review tasks, you need to deliver the package back to the sender.
Ensure all relevant segments are translated and the tasks are completed.
Open the Project Actions menu (three dots or top-right menu).
Click Deliver Work Package.
Phase 4: Troubleshooting and Exceptions
The Retry Mechanism
Occasionally, server delays or background process interruptions might cause the automated delivery or re-import steps to stall. If you notice that a Workpackage delivery did not reflect correctly in the original project, a manual retry mechanism is available.
Manual Reimport/Deliver: Users have access to manual Deliver Work Package and Reimport buttons. If an automated flow fails behind the scenes, you can click these buttons to manually trigger the system to push the completed tasks back to Account A or pull updates.
Partial Deliveries: The system supports partial deliveries. If you deliver a package but later need to send remaining work units, you can use the delivery button again. Work units that are already marked as "Delivered" in Account A will not be overwritten.