Workflows

Every project in Across has an underlying workflow. A workflow comprises a sequence of work steps to be processed in the form of tasks. By selecting a workflow, you define which tasks are to be carried out within the scope of processing the project.

Workflows are created and managed in the Workflows module, which can be accessed via Administration > Workflows in the Across module bar to the left of the screen.

Standard Workflows

Eight predefined standard workflows are available for your work with Across. These workflows cover the usual work that is done in the translation context. The simplest workflow merely comprises the translation of a source document. In addition, there are other workflows, e.g. for the translation and subsequent correction of a document or for mapping the international standard ISO 17100.

User-defined workflows

In addition to the standard workflows, the integrated workflow modeling enables the definition of user-defined workflows in Across to map translation workflows that differ from the predefined standard workflows.

Overview of the predefined standard workflows

The following overview shows the predefined standard workflows:

Translation
				Translation
Translation and Correction
				Translation
				Correction
Advanced
				Document preparation
				Term Extraction
				Term Translation
				Translation
				Correction
Terminology Work and Translation
				Term Extraction
				Term Translation
				Translation
External editing
				External document editing
Terminology work, translation, and correction
				Term Extraction
				Term Translation
				Translation
				Correction
Translation, review, and correction
				Translation
				Review
				Correction
EN 15038
				Preparation
				Translation
				Correction
				Review
				Release
ISO 17100
				Preparation
				Translation
				Correction
				Review
				Correction
				Release

Overview of the icons used

The following icons are used for the various predefined tasks and task types in Across:

Icon	Description
	Tasks carried out on the project level
	Tasks to be performed on the source document
	Tasks to be performed at target language or target document level
	Project Management
	Document preparation
	Term Extraction
	Term Translation
	Document translation
	Document review
	Document correction
	Document verification
	External document editing
	Tasks that can be partitioned
	Tasks that can be worked on immediately
	Tasks that can only be worked on once one of the preliminary tasks has been completed

Automatically Setting the Status of crossTank Entries to Released

In the task settings, you can determine that new crossTank entries that are created while processing tasks are to be automatically set to the Released status. Thus, manual release of these new crossTank entries is no longer necessary.

The Released status of crossTank entries is relevant e.g. in connection with the protection of translations.

By means of an additional option, you can have crossTank entries automatically stored as Released only when set to a target state (e.g. Translated for a translation task). The option only makes sense if translations in crossDesk are stored even when set to an intermediate editing state (e.g. Touched). Normally, storing only takes place when the final paragraph state is reached. To save non-final paragraph states, the option Store only at target state under Tools > System Settings > General > Project Settings Templates > crossTank > Storing Settings must be disabled. Thus, activating the option enables distinction (and filtering, etc.) between crossTank entries from a non-final-state paragraph and those from a final-state paragraph on the basis of the attribute Released or Unreleased.

Changing this option affects all tasks based on the particular task template, including tasks whose processing has already started.

Staggered Processing of Tasks

Usually, a task can only be processed after an upstream task has been processed and finished. For example, it is normally only possible to commence with a document correction task after the preceding translation has been finished. However, staggered processing of a correction task and a translation task is also possible: As soon as the upstream translator has assigned the Translated () editing state to a paragraph, the paragraph is released for the corrector, enabling the corrector to process it.

To enable staggered processing of tasks, open the properties of the downstream task, and disable the option Task can only be started if all preceding tasks have been finished in the General tab.