Project Managers
Team, Ultimate and Enterprise editions
Get in touch with Sales for licensing questions.
Automated Project Creation rules allow the configuration of how Memsource 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.
Prerequisites:
Follow these steps:
-
From the Setup
page, click Automated Project Creation.The page opens.
-
Click New.
The page opens.
Provide a name for the project.
Set active/inactive status.
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 .
See Set Target Files Pathname for more information.
-
Designate a .
Files imported to Memsource 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 Memsource should check for new content in the designated folder.
Choose 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 .
Default Project Owner will always be notified when a new project is created using automation rules.
Customize Email Templates used for notifications if required.
With the automation rules set, content can now be created in the designated folders. Based on frequency checks, Memsource looks into the specified folder and identifies new or updated content (based on file names, metadata, size, etc.).
The status of a monitored repository can be updated immediately by selecting an automation rule and clicking Check now.
On the page, Memsource displays currently available rules, connection status and the and k dates and times.
If new content is identified, new projects are created with either default settings or settings taken from the selected project template.
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 .
Note
APC using Git
If relative path is used (doesn't start with
/) in the target folder, it is interpreted as relative to the file and not the monitored folder.Specify the folder name in the :
Use
{targetLang}macro to represent target language.-
Subfolders can be created within the source folder.
Available for 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 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 by Memsource. 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 langauge 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>
Name of the actual file is based on File Renaming as set in the Project Template associated with the APC Service.
There are three ways to disable APC:
Manually disabled in settings.
Automatically disables after 90 days of inactivity.
Automatically after the organization account 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 Memsource 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).