You might sometimes want to send some additional files through XTM Cloud, as reference for AEM end users, along with standard translation items. This is unusual, but it is possible. Those files are not meant to be translated, as they only contain subsidiary material (guidelines, descriptions, etc.).
One of the constraints imposed by the AEM connector is that every file/job in an XTM Cloud project must have its corresponding job in AEM. The connector itself stores job pairs (AEM job ID/XTM Cloud job ID) and only a specific pair can be imported back into AEM. It is therefore not possible send additional files of this kind by, for example, uploading them to an existing project in XTM Cloud, as “reference materials", since they do not originate from AEM, so there are no relevant jobs there.
The only solution is to create an extra folder on the AEM side with a dummy file (with the same format as the dedicated file!), which will act as a sort of "container" for our dedicated file from XTM Cloud, add that folder to a project and send the project for translation in XTM Cloud. During the translation process, our dedicated file is uploaded as the target to replace the dummy file. Finally, when that particular job is completed in XTM Cloud, our additional/dedicated file is delivered to AEM.
At this point, there is yet another constraint, imposed by the connector, that we need to be aware of. The source and target files must be in the same format. What this means is that, if an AEM source file is in "DOCX" format, its XTM Cloud target file also needs to come back as a “DOCX" file. While this does not pose any problem for formats as "DOCX" or "TEXT", things are different for PDF files. Once XTM Cloud receives a file in PDF format as a source file, the system automatically converts it to "DOCX" to extract text for translation correctly. However, once the job is finished, XTM Cloud does not convert generated target back to "PDF" so the target file is still in "DOCX" format. As a result, it cannot, and will not, be retrieved correctly by AEM.
For PDF files, there is a workaround for this problem that consists of sending a non-analyzable file and employing a workflow for non-analyzable files. This is a special feature in XTM Cloud. The whole process is described step-by-step in the next section.
To avoid setting an additional workflow for non-analyzable files on the XTM Cloud side, and to take this XTM Cloud constraint into account, we recommend that you use a different file format instead of “PDF". Example: "DOCX".
The guide below describes how to create a new translation project and add a dummy file. XTM Connect – AEM needs this dummy file to retrieve a dedicated additional file, in PDF format.
On the XTM Cloud side, go to Configuration → Settings → Workflow → Workflow options, check Workflow for non-analysable files, and save the changes (administrative privileges required!).
On the AEM side, go to Adobe Experience Manager → Navigation → Assets.
Go to Files.
On the right-hand side, click Create, and then select Folder.
Enter a Title, and then click Create. Both Private and Orderable options can be deselected.
Check a newly created folder, click on Create, and then select Files.
Upload a PDF file without content (this is our dummy file). XTM Cloud will treat it as a non-analyzable file.
Go back to Adobe Experience Manager → Navigation, and go to Projects.
Click on Create, and then select Project.
Select Translation Project, and then click Next.
Fill in the project details in the Basic and Advanced tabs, and then click on Create.
In the Translation Job pane, click on three dots at the bottom.
Click on Add, and then select Assets/Pages.
Add the source content that is to be translated and the dummy file you created in the previous steps.
Once the files have been added, click on Translation Job in the middle of the tab screen, and go back to your project.
Expand the dropdown in Translation Job and send the project to XTM Cloud in your usual way.
On the XTM Cloud side (Project editor → Workflow), you will see that the dummy file was not analyzed. Such a file is not present in the Files section, and we cannot manually upload target to it.
By enabling “workflow for non-analazyble files”, we can make use of the Set workflow option. Since this is a file without any translatable content, the Set workflow option will “bypass” the process of converting it into editable “DOCX” format, so it will remain in “PDF” format.
Choose the required workflow, and then click OK.
A newly created workflow for this dummy file is displayed.
Go to Files. In the Target column, you will see that the actual target file can now be uploaded.
Search for your file and then click Upload.
The name of your uploaded file must be the same as the name of the dummy file in XTM Cloud!
You should receive a confirmation message.
Go back to Workflow, and finish the job by going through all the workflow steps.
On the AEM side, go back to the relevant project, and, in the Translation Job pane, click three dots.
Your PDF file has already been returned to AEM. Select the file, and then click on Reveal in Assets.
Click on Download.
Enter a name, select desirable options, and finally click on Download to confirm the process.
Congratulations! You should now receive your additional PDF file from XTM Cloud.