There are two different ways of automating the creation of translation Jobs by setting up customizable rules in the dashboard:
- Jobs Automation Rules batch up content that is already in Smartling, awaiting authorization, but not yet included in any Job, into a translation Job.
- Connector Automation Rules upload content from selected content platforms to Smartling and simultaneously batch it up into a Job.
In both methods, you can choose which content should be included in the resulting Jobs, on what schedule, and whether they should be automatically authorized for translation.
Automating Job creation should be based on the type of project.
Files can be uploaded to Smartling, either manually by drag and drop or automatically via an API integration. Regardless if the content enters manually or automatically, when it is awaiting authorization outside a Job, Jobs Automation Rules can automate batching strings into a Job and authorizing the Job for translation.
For your website content to be translated via the GDN, it must first be captured. Capturing content occurs when the localized website is browsed, which can be performed manually by an end user, or automatically by the GDN Crawler. Regardless if the content is captured manually or automatically, Jobs Automation Rules can automate batching strings into a Job and authorizing the Job for translation.
When using a connector, the content to translate is not actually uploaded to Smartling until a user requests translation of the asset.
For this reason, standard Jobs Automation rules are incompatible with connector projects*. However, some connectors have Automation Settings, which work similarly to standard Jobs Automation rules, except the rule also pulls the content into Smartling as an additional first step.
As well as that, previously translated content can be retranslated should the source content change after its initial translation.
*The Repo Connector is the only exception, and is compatible with Jobs Automation rules.