Use Case - Review and QA

The processes for external quality assurance and review scenarios are very similar and can be regarded together:

Step	Tool	Description
1	Across Language Server	A finished task triggers a corresponding event.
2	crossAutomate	crossAutomate triggers all workflows which listen to the Task finished event. For the solutions integrated via crossConnect for External Editing, corresponding standard workflows exist. These workflows can be configured by the user (e. g. filters that define which tasks to process and which not). The crossAutomate workflow creates an External Editing Work Unit (EWU) for the configured solution and puts the EWU file in the exchange folder FromAcross on the file system. EWU files are encrypted XLIFF files. Each vendor receives a vendor library from Across, which allows to read/decrypt EWU files.
3	Across Trusted Integration Solution	The Trusted Integration Solution watches for new files in the exchange folder and triggers the integration process.
4		The Across Trusted Integration Solution uses the provided vendor library to read the plain XLIFF from the encrypted EWU file. Tip The Across Trusted Integration Solution must ensure that the decrypted XLIFF file can only be processed in the Trusted Integration Solution. Exports must not be possible.
5		When the analysis results and/or target texts are added to the XLIFF stream, the vendor library comes into play again. The changed XLIFF content is written via the security functions to a so-called External Editing Response Unit (ERU) and stored in the exchange folder ToAcross.
6	crossAutomate	crossAutomate watches for new files in the ToAcross folder and triggers the import process.
7	crossAutomate	The import process imports the data in Across. Depending on the configuration, tasks can be set to a new state, rejected to the translator, etc.
8	Across Client	If analysis results information is added, it will be offered in a new tab External QA in crossDesk.