Integration requirements for Content Manager and File System
The following are items that will help you better understand the integration of Content Manager and File System and considerations when configuring translation and workflow.
Content Manager
Required for Content Manager integration:
- Languages are defined as described for source and pivot languages (see related topic). For example:
The following example defines a source language of English with target languages for German, Spanish, French, Italian and Chinese. The last group indicates that Chinese can be used as source language (pivot) for translating to Japanese and Korean.
<languagepaths> <languagepath from="nl" to="fr"/> <languagepath from="en" to="de"/> <languagepath from="en" to="es"/> <languagepath from="en" to="fr"/> <languagepath from="en" to="it"/> <languagepath from="en" to="zh"/> <languagepath from="zh" to="ja"/> <languagepath from="zh" to="ko"/> </languagepaths> - Translation templates are based on configured source and pivot languages, and are automatically pushed to Content Manager by TranslationOrganizer.
- Content Manager uses UTF-16 for the content.
- The dedicated user (typically ServiceUser) having the role TRANSLATORSERVICE.
- Statuses and status transitions, configured for the TRANSLATORSERVICE role, that defines a workflow for the integration:
- There is an initial status to indicate that the object is ready for translation: To be translated.
This status is used by TranslationBuilder to create new target language objects and by TranslationOrganizer to identify and include objects to send.
- With the status transition from the initial status, there is a status to indicate that the object is no longer under control of the CMS: In translation.
Status transition: To be translated to In translation.
TranslationJob option
Include 'In translation' itemsforces the re-sending of objects in this status. - With the status transition from the status above, there is a status to indicate that the object is back in CMS control: Translation in review.
Status transition: In translation to Translation in review.
- With a status transition from the Translation in review, there is a status indicating that a user approved the translation: Translation approved.
Status transition: Translation in review to Translation approved.
- With a status transition from the Translation in review, there is a status indicating that a user rejected the translation and the object needs to be re-translated: Translation rejected.
Status transition: Translation in review to Translation rejected.
- Status transitions allow for objects to be re-translated from several positions in the flow, thus making the process cancelled or rolled back to the status To be translated.
Status transitions:
- In translation to To be translated.
- Translation in review to To be translated.
- Translation rejected to To be translated.
- There is an initial status to indicate that the object is ready for translation: To be translated.
The TRANSLATORSERVICE role and the status transitions are configured accordingly out-of-the-box.
File System
Required for File System integration:
- The dedicated user (see above) configured for the integration has an access to the folder where the zip files should be created.