Packaging and Delegation

You will learn how you can create packages in the crossGrid module and delegate them from your Across Server to a remote Across Server. Your Across Server takes on the role of the Master Server. The Across Server to which the packages are delegated by your Across Server is the so-called Trusted Server.

  1. The delegation of packages is done in three steps:
  2. First you have to create a package in the crossGrid module. During the package creation, select the Trusted Server the package is to be transmitted to.
  3. Assign the corresponding tasks in the Tasks module as usual.
  4. Go to the crossGrid module and use the Build button to define which information (e.g. crossTank and crossTerm entries) should be transferred to the Trusted Server.

After the information is compiled, the package is made available for download by the Trusted Server.

The crossGrid Delegation Wizard and the crossGrid Package Wizard assist you in delegating packages from your Across Server to a Trusted Server and transmitting the respective data.


The connection and communication between the Across Servers that are linked by crossGrid are secured by Server Certificate Package files (SCP files). Please note that these files need to be exchanged outside Across and imported to Across via Tools > System Settings > General > crossGrid prior to connecting the Servers.


Please note that you need to have the appropriate rights.

By default, the project manager is designated for this type of task.

Delegating entire projects

You assign an entire project to a package by selecting the appropriate project and assigning all the tasks it contains. You can mark the tasks via multiple selection (e.g., by keeping the Ctrl key pressed and selecting the tasks one by one) and then you can assign them.

Assign languages

If a Trusted Server is only assigned tasks in certain languages, it is annoying to get packages of this language service provider offered when assigning tasks in other languages. You can avoid this by allocating languages to a Trusted Server:

  • To do this, select the corresponding Trusted Server via Tools > System Settings > General > crossGrid > Trusted Servers and click Edit.
  • Then go to the Languages tab and click New.
  • You can now define the needed language pair – e.g., English as source language and French as target language – as well as a subject and the language competence (rating). Thus, when assigning tasks, the packages of the respective Trusted Server will only be offered for selection for the allocated languages (English – French), but not for tasks with other languages (German – French).

Package version

You must first select the package version of the Trusted Server. You must get this information from the project manager on the Trusted Server side.


Among other things, the package version depends on the version of the Across database. The package version of your own Across installation is indicated in the information window that you can display with Help > About Across.

Expiration date

You can set an expiration date for the transmitted crossTank and crossTerm entries. After this date, the entries will no longer be available on the Trusted Server side. After the expiration date, the tasks can no longer be uploaded or opened Therefore you should take care of a substantial time buffer when defining the expiration date.

However, the entries will not be deleted and can be re-activated by updating the expiration date. To do this, the expiration date must first be changed on the Master Server side in the package properties (using the button of the same name). Subsequently, the expiration date must be updated on the Trusted Server side by clicking Update list.

Project settings

You can permit the project settings to be modified on the Trusted Server side. This option is relevant if you selected a project settings template when setting up the project.


In addition to the crossGrid packaging templates, you can also use the auto-packaging function. By means of this function, tasks can be assigned to a Trusted Server without manually creating a crossGrid package beforehand. After a task is assigned, the package is automatically compiled and packaged.

You can activate auto-packaging in the properties of a Trusted Server in the crossGrid section of the system settings. When assigning tasks, the respective server is offered, not a crossGrid package as usual.

When tasks are assigned to this Trusted Server, a package is automatically built and packaged according to the settings of the selected packaging template.

As the auto-packaged packages are usually used ad hoc for one or several tasks, they are automatically set to Closed after the auto-packaging. Thus, the packages can no longer be assigned any other tasks and they no longer appear in the Tasks module.


Please note that for using auto-packaging the package version of the Master Server and Trusted Server must match.


Among other things, the package version depends on the version of the Across database. The package version of your own Across installation is indicated in the information window that you can display with Help > About Across.

The version used during auto-packaging is not updated automatically. If the package version on the Trusted Server side has changed, e.g. due to the installation of a new Across version, the new package version must be adjusted once. To do this, deactivate auto-packaging temporarily. Subsequently, create and manually build a crossGrid package for the respective Trusted Server, selecting the new package version. Then reactivate auto-packaging. Henceforth, the new package version will be used for auto-packaging.

When selecting multiple tasks, all tasks are added to a single package. Otherwise, a separate package is created for each assigned task.

The name of automatically created packages consists of the name of the respective Trusted Server, the name of the involved project, and the date and time of the package creation.

Finished Delegated Packages

After processing delegated packages with crossGrid, all relevant data need to be sent back to the Across Server. This can happen with the direct transmission or with crossGrid classic.

With the direct transmission, document-related data are imported automatically to Across.

Moreover, in scenarios involving a v7.0 Master Server, the translation units are automatically extracted from the tasks and stored as TM entries. Term packages will be imported automatically.

In scenarios involving a v6.3 Master Server, crossTank and crossTerm entries need to be imported manually. The Import crossTank/Term Packages Wizard assists you in importing the crossTank and/or crossTerm entries that were transmitted to you upon completion of your work on crossGrid projects.

crossGrid classic

To provide the data in the form of a GWU file (crossGrid classic), click crossGrid classic OUT.

In the list, the status of the delegated packages is indicated under Status. For example, after the package is downloaded by the Trusted Server, the state changes from built to downloaded.

Further information about a delegated package can be viewed by clicking Properties.

After the processing of the delegated package is finished on the Trusted Server side and the data are uploaded to your Across Server or imported in the form of a Grid Response Unit (GRU file), you will be notified about the completion of the data transfer.

Thus, the processing of the package is finished. All tasks have been processed and are back on your Server.


Please note that the crossTank and crossTerm entries transmitted to a v6.3 Master Server additionally need to be imported manually.

Status closed

By default, all crossGrid packages created on the Master Server side are offered for selection within the scope of the task assignment. This is not always desired, particularly for crossGrid packages that can already be finished. Moreover, if there are many crossGrid packages, it may be difficult to keep track. For these reasons, crossGrid packages can be marked as Closed. To close a crossGrid package, select it in the crossGrid module and click Properties. Then go to the Involved tasks tab and activate the option for closing the package for further task assignments. From now on, the closed crossGrid package will only appear in connection with tasks assigned to the task, but will no longer be offered for selection for the assignment of other tasks.