Automated Translations
Translate content on demand or through workflows using the built-in translation service. The current implementation uses Google Translate, stores source-language preference in session, and can translate only the fields that changed in the source locale.
Translation Queue
| Entity | Progress | Action |
|---|---|---|
|
Spring Collection 2026
124 Products • EN → DA, DE
|
65% complete
|
Resume → |
|
Technical Manuals
12 Documents • EN → FR, ES
|
10% complete
|
Resume → |
Translation is implemented both as a direct UI service and as a workflow action. The translation controller accepts text, source language, and target language, stores the selected source language in session, and returns translated text through the translation service.
Workflow-driven translation goes further. The workflow executor checks the revision locale against the configured source locale, inspects which fields actually changed, and only translates configured fields that match the revision criteria into the selected target locales.
Bulk product updates can also call the translation service across filtered products, so teams can apply one-off translation runs without building a dedicated workflow first.
Need localization to happen when source content changes?
Use workflow translation actions and direct translation tools to push content into other locales without retyping every field manually.