Continuous Jobs

Available for

Team, Ultimate and Enterprise editions

Get in touch with Sales for licensing questions.

Continuous Localization

Continuous localization helps in projects and jobs that have incremental changes and require a continuous delivery of updated translated texts. It is the integration of the localization workflow into the development process instead of the tradition of it happening after the development process. As an example, in the software development environment, updated text strings are automatically handed off to the TMS and processed in time with the release cycle.

Continuous Jobs vs Continuous Projects

Continuous jobs and continuous projects do not have the same abilities.

Feature	Continuous Jobs	Continuous Projects
Monitors	Single Files	A folder of files
Single project	Files from different repositories and locations	One folder in one repository (excepting Git and Sitecore when multiple folders can be monitored)
File types	Limited	All
Workflows	Yes	Yes
Unchanged segments carried forward to updated file	Yes	Yes
Pre-translation	No	Yes
Due date calculations	No	Yes
Analyses/quotes	No	Yes

Using the Continuous Jobs feature, updated versions of an original file from a repository are uploaded to an existing project, overwriting the older version of the same file.

When new strings are added to a file in a repository, the modified source strings are updated and any deleted source strings are deleted as well. Unchanged strings that are already translated are copied to the updated version of the job.

Job Updates:

The job is monitored periodically based on the Continuous Job settings.
If a change in the source file is detected, the job in Memsource is updated.
If the job that is being updated is opened in the Web Editor (i.e. someone is working on it), a notification is displayed to the user, and they are prompted to reload the job.
Segments are updated based on the changes made in the source file.
Before updating, unchanged segments are copied together with the translation in the target.
The target is cleared for segments with the changed source. (The previous translation for confirmed segments isn't lost because it's saved in the translation memory.)
Segments deleted from the source file are also deleted from the job in Memsource.

Job Status Updates:

When a source file is updated, then:

If the job status is Completed or Delivered, the status is updated to Emailed.
If status is Cancelled, job content and status is unchanged.
All other statuses stay unchanged.
If a multi-step workflow is used, the status of each step is treated independently.

Example:

If the first step is Completed, and the second Accepted, after a file update the first step is set to Emailed, while the second remains Accepted.

Exporting Translations Back to the Repository:

The translation is periodically pushed back to the repository based on the frequency set in the Continuous Job settings.
Translated target segments are exported only if they have been modified.
Even unconfirmed modified segments are exported.
If a multi-step workflow is used, only changes in last workflow step are exported; the status of previous steps must be set to Completed but the step from which the changes are exported does not.
Each target file is stored in a language-code subfolder (e.g. ./en_us). Multilingual files are stored in a subfolder with a name that is concatenation of all target language codes (e.g. ./cs-de-zh_cn)

Restrictions:

Only available for specified file formats.
The file must be uploaded from an online repository using a connector.

Continuous jobs are presented in the project page with . The tooltip indicates when the job was last updated.

Note

If there are problems with a continuous job, hovering over the ellipses displays job information. Click See history to display a detailed history of the job to help troubleshoot where and when the problem may have occurred.

Continuous Job Supported File Formats

RESX
XML, Multilingual XML
PO, Multilingual PO
XLSX, Multilingual XLSX
Properties
CSV, Multilingual CSV
JSON
YAML
Android XML
iOS strings

Set Frequencies

To set continuous job frequencies, follow these steps:

Job frequencies can be set globally or on a project level.
- Globally
  
  From the Setup page, scroll down to the Automation section and click on Continuous Job Settings.
  
  The Continuous Job Settings page opens.
- Project
  
  From a Project page, click Edit.
  
  The Edit Project page opens.
  
  Click Continuous Job.
  
  The frequency settings are displayed.
Select Frequencies
- Source Update Frequency
  
  This controls how often the repository is checked for updates. (The shortest interval available is every 30 minutes.)
- Translation Export Frequency
  
  This controls how often the translated content is exported back to the repository. (The shortest interval available is every 30 minutes.)
Provide Target Subfolder Path if required. See Automatic Project Creation for more information.
Click Save.

Settings are applied to any new jobs.

Once settings are chosen for a particular job, they cannot be changed for that job. If changed at a later time, they will not apply to jobs that have already been set up. New settings will only apply to new jobs.

Import Continuous Jobs to a Project

To import continuous jobs to a project, follow these steps:

When creating a job, in step two, click on Add from Online Repository , select a repository/file and click OK.

The selected file is displayed on the New Job page.
Select the Import files as continuous jobs radio button.
- This option only appears if at least one of the selected files is supported for Continuous Jobs.
Finish creating the job.