-
Project Managers
-
Team, Ultimate and Enterprise plans
Get in touch with Sales for licensing questions.
Note
APC is built on an architecture with better performance and reliability than the legacy version as well as having a simpler setup.
APC is close to a full feature parity with the legacy version. It has been updated to support most legacy features including the ability to generate analyses and quotes and send notifications. It will be extended to support additional use cases in the latter part of 2022.
The legacy version is only recommended for use cases that require the service functionality.
Due to continuous improvements, the user interface may not be exactly the same as presented in the video.
The page provides an overview of currently available APCs.
APCs can be filtered by , , , and .
If a specific APC is selected:
-
Trigger monitor
Manually checks source files for updates and updates the date and time.
-
Force import
Imports all the files from the remote folder monitored by the selected APC.
-
Delete
APCs connected to active projects, as well as archived but unfinished projects cannot be deleted.
Automated project creation rules allow the configuration of how Phrase monitors specific folders via an integration connector and creates new projects if new or updated content is detected within them.
-
Most APC settings are handled in project templates. The project template defines file destinations, source and target languages and workflow steps. Process and financial details are also defined in the project template such as providers and the generation of quotes and analyses.
Exporting translations back to the repository:
-
Jobs are exported when the project status is set to .
-
Jobs can be manually exported by choosing > . Even unchanged files will be exported.
-
Each target file is stored in a target path specified in APC settings.
Re-importing:
-
Jobs can be re-imported from the menu on the jobs table.
Prerequisites:
-
At least one connector and a project template in a profile.
-
(Optional) An email template with either or selected as the type.
-
If using JobSync (Phrase Strings connector), multiple folders or files can be set for monitoring.
Follow these steps:
-
Create a new APC
-
From the Settings
page, click Automated project creation.
The page opens.
-
Click New.
The page opens.
-
Provide a name for the APC.
-
Set active/inactive status.
The Save button is active once all mandatory fields are filled.
-
-
Monitoring
-
Click Monitor folder or file to choose a folder to monitor for new or updated content.
The contents of the folder are listed.
-
Select specific folder or file to be monitored.
Not all options are available on all connectors.
-
If none are selected, the entire folder is monitored for a change or for new files.
-
Include subfolders to enable the monitoring of the selected folder and its subfolders.
-
can be used for file-based connectors to indicate which files were already used for translation.
lets customers define a regular expression to filter out files to be monitored within the folder.
-
-
Click Save.
The selected folder or file is listed. Click Browse to change the selection.
If using JobSync (Phrase Strings connector), more folders or files can be added to the list by clicking Monitor folder or file again.
-
Click Add monitor to select either a or trigger.
Provide webhook or schedule (or both) in the monitoring window.
-
Click Next.
The page opens.
-
-
Set creation & export
-
Choose how project is to be created.
-
Select a project template from the dropdown list.
-
Source language is defined in the project template and either all or a subset of target languages can be selected.
-
Select View project template details to preview the settings of the selected project template.
-
-
Select criteria for exporting translations.
is what workflow state translations are in when they are to be exported. User can decide which content to export; examples being translations from the final workflow step or a step before that.
provides the event that triggers the export.
-
The translations will be exported when a selected workflow step is completed; when a specified workflow step is completed for one target language, this triggers the export for that language without waiting for the rest of the target languages to be completed
-
The translations will be exported when the whole project is completed - i.e. when all the jobs from all the workflow steps are complete.
-
-
Click Next.
The page opens.
-
-
Set optional automations
-
Select required automations.
-
-
Analyses and quotes options
-
Email templates with the or will be available in this dropdown.
-
-
Select source update options (only enabled for continuous projects).
If has been selected in the part of the APC setup, the APC monitors remote folders for source updates, but a detailed configuration is not necessary, because a new project is created every time a change is detected.
For a continuous project, specify which workflow steps require reopening when a source update is detected, if new analyses and quotes are to generated, and if project owners are to be notified about a source update.
-
Select target update options (only enabled for continuous projects).
User can monitor the remote online repository for target updates. Any changes made to the target copy in the online repository will automatically update the translation memory.
-
Click Save.
The APC is added to the list on the page.
-
With the automation rules set, content can now be created in the designated folders. Based on frequency checks, Phrase looks into the specified folder and identifies new or updated content (based on file names, metadata, size, etc.).
Each target file is exported to a folder specified in project settings.
There are three ways to disable APC:
-
Manually disabled in settings.
-
Automatically disables after 90 days of inactivity.
-
Automatically after the organization profile has been deactivated (at the end of the subscription).
When a connector used as part of the Automated Project Creation rules detects three or more consecutive instances of a project not being created when it should be, notification is sent to affected users.
-
Multiple ZIP files can be imported to one project.
-
Translated files are exported back to ZIP files.
-
If one ZIP file is imported to multiple targets, the translated files will be exported to multiple ZIP files—one ZIP for each target language—using the target locale code in the ZIP name (for example Pack18.en_us.ZIP).
In multilingual localization, a pivot language can be used as bridge language to enable translation from the source language to any required number of target languages. The pivot language approach is especially valid when there are limited translation resources available in the source language for any reason.
Translation with pivot languages is one of the possible APC use cases to automate the translation process. The example below summarizes required steps to follow:
-
Create a folder in the desired online repository to store the source language content.
In this example, source files in French language are added to a Google Drive folder.
-
Set up APC monitoring options to monitor content updates in the desired online repository.
-
Set up APC to create a project with the required source language and the chosen pivot language to use as target language.
In this example, the APC is set up to create a project with French as source language and English as pivot target language.
-
Configure the APC export settings to export translated content into the corresponding target language folder on the same online repository.
In this example, the APC is set up to export the English translations into a target folder on the same Google Drive.
-
Once the project is completed, the export triggers APC to create another project for translating content from the pivot language into the desired target language.
In this example, the export triggers APC to create another project for translating content from English into German.
Note
Required connectors and project templates must be set up to apply the use case.
For large scale projects, translation with pivot languages can also be achieved by custom scripting via APIs.
Automated Project Creation rules allow the configuration of how Phrase monitors specific folders and creates new projects if new or updated content is detected in them. This provides full process automation; analysis, pre-translation, assignment to Linguists/Vendors, and the e-mailing of notifications.
As soon as a project status changes to Completed by Project Status Automation rules, the translated files are sent back to the Online Repository into newly created subfolders identified by language codes (en, es, ja, etc.). If a user triggers the export manually, the completed file is exported to the standard {targetLang} folder.
Exporting Translations Back to the Repository
-
Jobs are exported when the project status is set to Completed.
-
Jobs can be manually exported by choosing > . Even unchanged files will be exported.
-
Each target file is stored in a target path specified in APC settings.
Re-importing
-
Jobs can be re-imported from the menu on the jobs table.
Automated Project Creation rules allow the configuration of how Phrase TMS monitors specific folders and creates new projects if new or updated content is detected in them.
Prerequisites:
Note
When the service is created, ensure either Analyses only or Analyses and quotes is selected and the option is deselected in the section. If None is selected, Automated Project Creation will not create a new project for new or updated content in the monitored folder.
Follow these steps:
-
From the Settings
The page opens.
-
Click New.
The page opens.
-
Provide a name for the APC.
-
Set active/inactive status.
-
Select if required (the following options will change if selected).
-
Select if required.
-
Choose the Remote Folder to monitor for new or updated content.
The contents of the folder are listed
-
Select specific files to be monitored.
Not all options are available on all connectors.
-
If none selected, the entire folder is monitored for a change or for new files.
-
Include subfolders to enable the monitoring of the selected folder and its subfolders.
-
-
Select where to .
-
Depending on the pathname of the required target files, set and .
-
Designate a .
Imported files are moved to this folder providing visibility on which files are being processed. If disabled, source files stay in their original folder.
If this option is disabled and File Renaming is not used, original documents can be overwritten by their translations (depending on repository).
lets customers define a regular expression to filter out files to be monitored within the folder.
-
Set a frequency for how often Phrase should check for new content in the designated folder.
-
Choose required (with a specified Due Date Scheme if required).
-
Select the source and target languages that automatically created projects will be associated with.
-
To differentiate between projects coming from different automation rules, use a to define the automatically generated names of projects.
The macro
{filename}can be used in the Project's title. If multiple filenames are used in the project's name, only the first filename will be used. -
Set .
Project owner will always be notified when a new project is created using automation rules.
-
Customize Email Templates used for notifications if required.
Relative to the source file the target files can be exported to:
-
Same folder
If specific files are selected, then select Source file folder for and keep the empty. Not supported if the entire folder is monitored.
-
Language subfolder
Always keep the empty.
If specific files are monitored, then select Target language subfolder for .
-
Any folder
If specific files are monitored, then select Target language subfolder for .
Specify the folder name in the :
-
Use these macros to represent target language.
-
{targetLang}Based on language codes. -
{targetLangName}Based on language names. -
{targetLangRFC}-
Examples:
es,en-US,az-Latn-AZ -
Based on RFC 5646
-
-
{targetLangAndroid}-
Examples:
es,en-rUS
-
-
{targetLangAndroidBCP}-
Examples:
b+es,b+en+US
-
-
-
Subfolders can be created within the source folder.
Available for Amazon S3, Azure, FTP, SFTP, Dropbox, Google Drive, Box, OneDrive, Git, GitHub, GitLab, and Bitbucket Cloud.
-
For some repositories, an absolute path is available. Begin your path with / to indicate the absolute path.
Available for Amazon S3, Azure, FTP, SFTP, Dropbox, Google Drive, Box, OneDrive, Git, GitHub, GitLab, and SharePoint. When using Git connector, the leading / is followed by the branch name, and then by the root of the repository where .git folder is located. If the branch doesn’t exist, it will be created. When using other Git-based connectors (e.g. GitLab), the leading slash is followed by the root of the repository where .git folder is located.
-
Use
..to refer to the parent folder.
Tip
Examples
If the source file is
/files/loc/ui.propertiesand the target language is German (Germany):-
translations/{targetLang}will create /files/loc/translations/de_de -
/files-{targetLang}/locwill create /files-de_de/loc/<filename> -
../{targetLang}will create /files/de_de/<filename>
-
-
Multiple ZIP files can be imported to one project.
-
Translated files are exported back to ZIP files.
-
If one ZIP file is imported to multiple targets, the translated files will be exported to multiple ZIP files—one ZIP for each target language—using the target locale code in the ZIP name (for example Pack18.en_us.ZIP).