Project Management

Continuous Projects

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_Localization.png

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

Automated Project Creation can be configured to continuously update an existing project. When enabled, a new project is created and used continuously for all updates to the source files already in that project instead of creating a new project every time a source file change is detected.

When source files are updated, linguist are notified by email and in the editor in which options to immediately reload the source Reload now or to wait until the source is updated again Reload later are available. The source can also be updated manually with Update job.

Job Status Updates:

  • If the status is New, Emailed, Accepted, Declined, or Rejected the job is reloaded and status maintained.

  • If the status is Completed or Delivered the job is reloaded and the status is changed to Emailed.

  • If the status of first workflow step is Cancelled, the job is left unchanged.

  • When the project is continuous, jobs are exported when the last workflow step is Completed.

  • Before updating, unchanged segments are copied together with the translation in the target.

  • If a job in continuous project is deleted and an update of the source file in the online repository is made, a new job is created.

Reopening of completed continuous projects when new work is detected:

  • If a project is set to Completed and Continuous Project scans a repository to find processable work, it sets the project to Assigned to indicate new work.

  • If the status of an existing project is Cancelled and a file has been modified or a new one is detected, the continuous project status is set to Assigned.

Integrations:

  • If a due date scheme is defined for a service associated with a continuous project, it is applied to new or updated jobs.

  • If a price list is defined for a service associated with a continuous project, it is used to generate quotes for new or updated jobs.

Was this article helpful?

Sorry about that! In what way was it not helpful?

The article didn’t address my problem.
I couldn’t understand the article.
The feature doesn’t do what I need.
Other reason.

Note that feedback is provided anonymously so we aren't able to reply to questions.
If you'd like to ask a question you can leave a public comment below or Submit a request to our Support team.
Thank you for your feedback.

Comments

0 comments

Article is closed for comments.