The AEM Connector for the Translation Framework enables you to initiate translation projects directly within the AEM interface.
1. Step one: Access the CRX Package Manager
2. Step two: Upload the Package
3. Step three: Install the Package
4. Step four: Create Translation Configuration Folders
5. Step five: Create Translation Configurations
6. Step six: Setting the configurations
Step 1: Access the CRX Package Manager
Open your AEM instance.
Navigate to the "Tools" menu.
Select "Deployment" and then "Packages". This will open the CRX Package Manager.
Step 2: Upload the Package
1. You can download the latest version of our package from the AEM Connector page.
2. Click on "Upload Package".
3. The following will be displayed:
4. The package contains the code necessary for creating and executing translation projects in Bureau Works.
5. The Bureau Works AEM Connector will appear in the package list.
Step 3: Install the Package
1. Click "Install" to start the installation process.
2. In the "Install Package" dialog, advanced settings are available but not needed for default installation.
3. After successful installation, a green marker will indicate the connector is ready to use.
Step 4: Create Translation Configuration Folders
1. Open the "Tools" menu, then go to "General" and select "Configuration Browser".
2. Click on "Create" to create a new folder.
3. Name the folders and click "Create". It is recommended to create a separate folder for each organizational unit you plan to use, in case you have multiple project types/requirements or work with multiple Translation Agencies.
Step 5: Create Translation Configurations
1. Select the "Tools" menu, then go to "Cloud Services" and choose "Translation Cloud Services".
2. Open the “Conf” folder, select the folder you want to use, and click on "Create".
3. Choose the Bureau Works AEM Connector from the drop-down menu.
4. Enter a title for the configuration—preferably using the name of the Organizational Unit or translation agency that will be responsible for translating the content.
5. Input the Bureau Works URL, API Key, and ID, and set up Workflows.
Refer to the guide for API authentication.
6. Click on "Test configuration" to verify. A message, "API Key verification passed. Configuration is valid" will confirm a successful setup.
Step 6: Creating and configuring a translation project
1. On the AEM homepage, click on Projects and then Create, to create a Translation Project.
2. Under the Basic tab, add a Title for the project.
3. Then, on the Advanced tab:
a) Add a name to the configuration.
b) Select the Target Language.
c) Enter the path to the folder where the configuration was created.
The content for that language will be automatically routed to the respective Organizational Unit in Bureau Works based on the configuration you selected.
d) Select Human Translation, which should automatically change the provider to Bureau Works as your Translation Provider for Human Translation.
e) Unselect the options to Automatically Promote and Approve the translations unless this is expected.
4. Click on Create to complete the project creation.
5. Click on Open to open the project and submit translation jobs.
Note: According to AEM 6.5, each project should have only one target language. It is recommended to create one translation project per iteration, with jobs having a single target language.
Each job in AEM maps 1x1 to a project in Bureau Works.
For a complete reference on Translation Project management, please visit this link.
Step 7: Submitting jobs for translation
1. From the Project created, click on Add.
2. Select Translation Job and Submit, to create a new translation job.
3. Back to the Project, on the Translation job just created, click on the ... button.
4. Now, click Add and select the type of assets you will submit for translation.
5. On this screen, select the pages/campaigns you want to add to the translation job.
6. Back to the translation job, make sure that any Image, Metadata or dictionaries are removed from the translatable file list since they do not contain editable content for translation and may interfere with the automation and completion of the localization process.
7. Once you are all set with the content selection, go back to the main page of your translation job and click on the following button and then Request scope.
8. This will create a translation project in Bureau Works in Draft status, and on AEM, the status will change to Scope Requested.
Once all files are parsed in Bureau Works, Bureau Works will automatically calculate the costs and change the status to Pending*. On AEM, the status of the job will change to Scope Completed.
*The automated cost calculation and status transition require the Quote automation feature to be activated in Bureau Works and a price list associated with the Organizational unit
9. Click the appropriate button on the translation job screen (refer to the screenshot), then select Start.
This will approve the project in Bureau Works* and change the status on AEM to Commited for Translation
*If the project is manually approved in Bureau Works, you must still start the job in AEM; otherwise, AEM will not be able to pull the translated content once it is completed
10. Once all content is fully translated - meaning: All files are fully translated, and all segments are confirmed in the last workflow step in Bureau Works - AEM will pull the content automatically in a few minutes (make sure to refresh the page on AEM to update the status).
*The project below has just one workflow step (translation), so once it was fully completed, AEM pulled the translated content. If additional workflow steps were available (Review, ICR, Proofreading, etc) AEM would have pulled the content only once all those workflows were fully completed
After the translated content is pulled by AEM, the status on AEM will transition to Ready for Review (unless auto-approval is turned on).
11. The next step is to accept or reject the translations in AEM.
AEM also allows the content to be previewed in context, if necessary.
a) Click on the ... button on the translation job to access the file list.
b) You can then select a page from the list and Preview this page and/or Accept/Reject it.
12. Rejected pages will add a tag to the Work Unit in Bureau Works so it can be reassigned to the translator for edition
13. Approved pages are considered as Completed on AEM and can no longer be modified.
Once all pages in a translation job are approved, the translation job status will change to Approved on AEM, and in Bureau Works, the project status will change to Delivered, completing this translation job.