Process Overview

The communication between the CMS and Elanion via Generic File Connector works as follows:

Step	Trigger	Description
1	Translation requested in CMS	CMS exports a package for translation Package is uploaded to ToElanion folder on MS OneDrive
2	Package detected in ToElanion folder	Generic File Connector imports the package
3a	Package import was successful	Generic File Connector creates a project in Elanion for the package Generic File Connector moves the package to ArchiveToElanion folder on MS OneDrive
3b	Package import failed	Generic File Connector moves the package to Rejected folder on MS OneDrive
4	Project created in Elanion	Elanion delegates the project to Across
5	Translation finished in Across	Elanion receives translation results from Across
6	Translation received in Elanion	Generic File Connector packages the translation results
7		Generic File Connector creates a result package in FromElanion folder on MS OneDrive Generic File Connector creates a copy of the result package in ArchiveFromElanion folder on MS OneDrive
8	Package detected in FromElanion folder by CMS	CMS downloads and imports result package