Preparing and Exporting crossWAN Data

Across offers you as the project manager two ways of preparing data required by crossWAN load or crossWAN classic users for processing their tasks: you can compile the data and automatically make them available for download from the Server (crossWAN load), or you can export the relevant data in the form of Client Working Units (CWU files) (crossWAN classic) and send them to the crossWAN user on suitable data media (e.g. a USB stick), by e-mail, or via download on an FTP server.

As soon as you have assigned a task to a crossWAN load or crossWAN classic user in the Tasks module, a dialog box opens that you can use to determine the data you want to make available to the user while working on the task.

As a matter of principle, only the crossTank and/or crossTerm entries that exist in the source language and the target language of the translation will be transmitted. For example, for a translation from English to German, only translation units and/or terms in English and German, but not in French, will be transmitted. By default, the crossTank and/or crossTerm entries in all sublanguages will be transmitted. However, the sublanguage filter can be used to limit the transmitted entries to certain sublanguages of the source and/or target language.

After you click OK to confirm the settings the data is collected and made available to the crossWAN load user for download from the Server.


While data is being compiled for offline tasks, Across must not be shut down. Click the Status button in the status bar at the bottom of the window to get information on the progress of the procedure.

crossWAN Packaging Templates

With the help of packaging templates, the compilation of the data to be transmitted to offline users for the processing of tasks assigned to them can be predefined. The data to be transmitted are defined in the packaging templates:

The templates can be created under Tools > System Settings > General > crossWAN Packaging Templates. As the number of templates is not limited, a separate template can be created for each offline user.

Whenever an offline user who has been assigned a packaging template is assigned tasks, the selected template is automatically used for packaging, and the package is created automatically.

Template assignment

By linking the templates to the respective offline users, you can make sure that only the desired data will be transmitted to each offline user.

When creating a new offline user, the user can be assigned a crossWAN packaging template.

Packaging templates can be changed or determined at all times in the properties of existing offline users in the crossWAN Settings tab (via Administration > Users > Properties > crossWAN Settings). Any changes do not affect tasks already assigned, but only tasks assigned thereafter.

You can also access the crossWAN settings directly over the context menu of a user. This is also possible for several users at the same time by selecting the users via multiple selection (e.g. by keeping the Ctrl key pressed and selecting the users one by one). In this way, you can adapt the packaging templates for several users at the same time.

Availability of crossTank and crossTerm Entries

When assigning tasks to offline users, you compile the data to be provided to the offline users for processing the tasks. These data especially include the crossTank and crossTerm entries. These entries are available to the offline users until the last task assigned to the respective offline user is finished and sent back to the Across Server. Only after the last tasks have been sent to the Across Server, the entries will be deleted on the side of the respective offline user.


Please note that crossTank and crossTerm entries that are deleted on the Across Server side will not be removed from the offline user if these entries already exist there during the next transmission of crossTank/crossTerm entries to the offline user. Complete deletion of all crossTank and crossTerm data is possible at a time when all assigned tasks have been finished and uploaded to the Across Server. On the Across server side, all the tasks must be revoked from the offline user. Then the offline user must normally connect to the Across Server in order to sync the tasks and confirm the message "The project manager has unassigned you from task: 'Name of the task. The task will be removed from your local database. Confirm "Would you like to continue?" with Yes. In this way, all tasks will be deleted on the offline user side. The deletion of the last task is accompanied by the deletion of the entries. Depending on the amount of crossTank/crossTerm data, this can take some time.

If tasks are continually assigned to the offline user, the crossTank entries can, instead of being deleted, be marked with an additional user-defined system attribute (e.g. the attribute "State" with the attribute value "Outdated"). Similarly, crossTerm entries can be marked with an additional attribute (e.g. "Outdated"). The attribute change will be transmitted to the offline user the next time crossTank/crossTerm entries are sent, provided that the marked crossTank/crossTerm entries are part of the respective task(s).