Translation Center
Purpose: Find missing translations, prepare drafts, and review localized content for IMI Life Science.
What You Can Do Here
- Navigate a wide matrix: Scroll inside the translation table or use its left/right arrows to reach other language columns. Headers remain visible; the key column stays pinned on larger screens. On phones, the workbench views form a horizontal tab strip. Open a translation cell for the full value.
- Batch selected rows: Select rows individually or select the current page, then choose one Batch language when viewing all languages. AI translate selected launches a background job for the captured missing or outdated rows after confirmation. Approve selected remains a separate action for current, tracked drafts and preserves their text, provenance and original translator. Approval rechecks only selected resources in small chunks and rejects intervening edits. Approved rows leave Proofing's Draft filter; an empty last page returns to the remaining drafts without closing results. Failed rows stay selected and earlier successful approvals remain saved. Stop cancels pending reads and prevents later saves; a save already in flight may finish. A connection, session or service interruption stops the batch; verify saved statuses before retrying. If selected-resource reload or draft revision is unavailable, ask the administrator to update Resources and the back office together, then reload. Manual filter/page changes clear selection without changing the running background job. Inspect failures before retrying.
- Discover content: Run Scan content. Discovery includes code-defined website strings and both published form audience schemas. Review the scanned items, new keys, updated values, and any failed content types. A partial scan does not mean all content is covered.
- Find missing work: Select a missing count in Content Coverage to open that language and content type. All Translations includes UI strings, CMS and catalog resources. Search source text, translated text, or keys; filter by language, area, type, and status.
- Translate: All Translations, Content, and Proofing use the same saved resource values. Structured rows show actual text and filled-field counts. Open a target cell to compare source and translation; missing target fields remain blank. Use the field AI icon to suggest one translation without replacing neighboring text, or Suggest translation for the complete resource. Save draft remains explicit.
- Translate at the content owner: Page, article, form, mail, brand, document, menu, and attribute language tabs show registered unified values. Node translation editors expose scalar text, rich text, lists, and schema-marked nested attributes beside their source. Layout blocks offer Translate block content with AI. Source IDs, links, units, and layout settings remain unchanged.
- Resolve synchronization warnings: A stale attribute projection stays visible as a warning rather than replacing changed source fields. A legacy content save can succeed before its Translation Center synchronization fails; retain the draft and retry the reported field. Saved translations and Back Office visibility do not automatically enable storefront delivery or approve content.
- Translate node content: Discovery includes active node attribute text, string lists, and schema-marked nested fields. In a node translation editor, Translate all node content generates its name, formatted description, and those attribute values; Save Translation remains explicit. Routing slugs, item IDs, numbers, units, and links are preserved.
- Keep translations current after saving: Saving an already translated source item offers Update existing translations? Select the existing languages to refresh, then choose Refresh with AI to replace their translatable content. Not now makes no AI request and leaves translations unchanged. Pages and layouts include their child blocks. The original item is already saved; refreshed resource values are drafts requiring review.
- Check delivery: A staged-delivery notice means the selected content type still uses legacy translations on the storefront. Delivery settings opens the existing advanced feature controls. Review and validate the migration before enabling the read flag; saving a draft does not enable delivery.
- Check node layouts: Product delivery includes dynamic attribute text, but node layout names and blocks use separate NodePageLayout and NodeLayoutBlock controls. These start disabled. Stale attribute projections and missing layout translations retain existing content instead of changing source data.
- Test AI: In Languages, choose Translate on the target language row to open AI translation with that language selected. In All Translations, use AI Translate for the current filtered scope. Choose Test AI to check the provider with synthetic text without saving. Provider configuration is managed in AI services settings.
- Set translation batch size: Open Settings > AI services, enter Translation batch size, and choose Save batch size. Use a whole number from 1 to 50; the default is 10 text items per AI request. Smaller batches can reduce timeouts. The next translation run uses the saved value; a running bulk job keeps its starting size. A page or block can contain several text items.
- Set translation parallelism: In AI services, enter Translation parallelism and choose Save parallelism. Use a whole number from 1 to 8; the default is 1 concurrent batch per operation. Higher values increase provider load. New runs use the saved value; active runs keep their starting limit. Only one background translation job runs at a time. Other individual editor operations are separate and can still add provider load.
- Prepare AI drafts: Suggest translation previews one unsaved suggestion. Translate missing launches a background job that discovers content, processes every missing-key page in the captured scope, and saves drafts. Discovery failures stop translation until resolved. Empty English sources are excluded; configuration-only resources and empty markup are skipped. Rich text keeps its source markup and links.
- Monitor background translation: Translation Center shows the active or latest translation job with progress, status, and expandable output. Managed Jobs opens the same run in its Live view. Closing the dialog, navigating away, or reloading the browser does not stop it. Reopen Translation Center to reconnect. Output identifies pending text requests and reports waits every 30 seconds; the percentage advances when resource batches finish. Use Stop explicitly to cancel pending work; drafts already accepted remain saved. A failed job can still have saved drafts. Live output is not restored after an Automation service restart; terminal summaries remain in Journal.
- Pause and resume: Choose Pause in Translation Center or Background Jobs to stop new translation work at its next checkpoint. In-flight requests and an already-started save phase may finish. Resume continues the same job without repeating completed work; paused jobs still prevent duplicate launches and can be stopped. Pausing does not reset request timeouts, change captured batch settings, or survive an Automation restart.
- Recover slow generation: A timed-out multi-item request is retried as smaller sequential requests. If an individual text still times out, or the provider is rate-limited or temporarily unavailable, the job pauses with a reason. Restore provider availability, then choose Resume to retry unfinished generation. Completed text and saved drafts are retained. Saves are never automatically retried. An already failed job cannot resume; inspect its drafts before a deliberate new missing-only run. Smaller batch size and parallelism settings help reduce provider load on new runs.
- Refresh outdated copy: Select Refresh outdated translations to include targets whose source has changed. This option starts off. Translate missing and outdated creates or refreshes drafts across the current scope, including page blocks, product descriptions, attributes, and layouts. Current translations are not selected for replacement. In Languages, the unfiltered action covers all registered storefront content, not only UI labels.
- Review: Save draft retains unapproved work. Approve confirms a reviewed translation. Proofing opens draft resources; All statuses includes missing, approved, outdated, and rejected values.
- Recover from errors: Failed saves retain the draft. The progress log names failed keys and their API reasons. An invalid multi-item AI response is retried once as individual text requests before saving that batch. When the source changes, reload it before saving. Prior successful drafts remain saved; rejected values do not mean the run is complete.
- Review unchanged AI output: When identical source and target text is the only rejection reason, it appears as information without a toast. Bulk and selected runs count it as unchanged, not saved or failed. Single-resource drafts remain open. Review shared terms deliberately; other validation and service failures still appear as errors.
- Refresh safeguards: No prompt appears for untranslated items or translation-only writes. Back Office AI and translation-management permission are required. Discovery failures, changed source/translation snapshots, and session changes stop refresh. Earlier successful translation writes remain saved if a later operation fails; review them before retrying.
- Versioned content: Publish a saved article or form draft before refreshing its translations. Those translation values are shared with the live version; the prompt prevents unpublished draft text from replacing live translations. Publishing offers a fresh translation check.
Key Concepts
- Coverage: Languages and Content Coverage use the same registered resource inventory across UI strings and content types. Each language shows populated and approved resource counts against the shared total. Completeness includes drafts and outdated values; it does not guarantee translated nested fields or storefront delivery. The average includes only active target languages, not the source or disabled languages. No resources means the inventory is empty; a failed coverage request offers Retry. New custom fields require developer registration and runtime tests; absent English sources need investigation before AI translation.
- Language status: Disabling a language hides it from the storefront without deleting translations. Disabled languages can still be selected individually for preparation.
- AI quality: Provider connectivity and populated-value counts do not guarantee linguistic accuracy or storefront delivery. With no filters, AI translation covers every registered content type; existing populated drafts still need field-level review for missed nested text. Review technical terms, placeholders, links, and formatting before approval. Some identifiers and French terms legitimately remain unchanged; do not invent translations for placeholder source content.
Last Updated: 2026-10-12
Search, Recovery and Unsaved Translations
- Find translations: Combine the target language, area, content type and status filters. Submit search with the magnifying glass or Enter. Clear search removes the search only; Clear filters also resets the language and content scope. Links and browser history retain the applied URL filters.
- Refresh safely: The result range identifies the current page. Refresh translations reloads that scope; Updating indicates a pending read and selected approval is unavailable until it finishes. A language loading failure offers Retry languages rather than reporting an empty inventory.
- Protect edits: Cancel, Escape and Close ask before discarding a changed translation or AI suggestion. Keep editing retains the draft; Discard changes closes without saving. Save draft and Approve remain separate explicit actions. Failed saves retain your text. Browser exit warns while changes remain unsaved; this is not automatic draft storage.
- Navigate: Use the workbench views to switch between coverage, Languages, All Translations and Proofing. Arrow keys move between focused views; Home and End select the first and last views. Source, translated text and save actions remain accessible on narrow screens.
- Check delivery: Coverage counts populated resources, including drafts; it does not certify linguistic quality or live storefront delivery. Review staged-delivery warnings before changing existing delivery settings.
Overview and Translation Work Queues
- Start with Overview: Review missing and outdated counts by language, alongside translated and approved totals. Choose a missing or outdated count to open that exact language and status. Review drafts opens the unified draft inventory; no draft count is inferred from summary percentages. Content-type coverage remains available below the language queues.
- Choose the language: All active languages compares enabled targets. The overview language selector can deliberately select a disabled language for preparation; it does not enable storefront delivery. Translate opens explicit AI controls for that locale and never starts generation by itself.
- Move between work views: Overview, All Translations and Review drafts are the main workflow. Review drafts replaces the former Proofing label. Moving between translation and review views retains language, content type, content item, area and search, resets pagination and selects the appropriate status. Clicking the active view does not reset filters.
- Filter the queue: All, Missing, Drafts, Outdated, Approved and Rejected are visible status controls. More filters contains area, content type and page size, and starts expanded for a deep-linked content scope. Search still supports Enter and the search button.
- Find specialist tools: Languages, Glossary and Import / Export are grouped under Configuration. Content, Editorial review and Missing key reports remain under More tools. Missing key reports are storefront-reported keys, not the complete inventory of untranslated values.
- Keep review deliberate: Opening queues makes no translation or approval writes. AI drafts, human approval, saved source revisions and storefront delivery remain separate. A failed overview load offers Retry overview rather than invented zero coverage. Existing unsaved-edit and partial-approval protections still apply.
Review Exact Translation Matches Once
- Merge exact matches: Open All Translations or Review drafts, choose one target language and enable Merge exact matches below the status queues. The switch is visible but disabled until a target language is selected; it is not shown on Overview. Current tracked drafts with exactly identical source text, translation text and content kind share one row across all pages in the filtered queue. Different translations, whitespace, markup and stale or untracked drafts stay separate. This does not merge or delete stored resources.
- Inspect the group: Expand the exact-match count to see the affected resource keys. Page size now counts groups; selecting a group selects every occurrence. Opening an individual translation still edits only that resource.
- Approve once: Choose Approve group and Confirm approval to validate all occurrences of the reviewed pair. Each resource is rechecked and saved separately with its own source hash, target revision, provenance and confidence. Changed drafts are not overwritten. Successful saves remain saved; failures stay selected for review.
- Recover safely: Loading or failed queue reads block approval. Refresh or Retry after an incomplete or changing queue. Disabling Merge exact matches restores individual rows without writing translations. Approval is deliberate, not AI generation or storefront-delivery activation.
Form Confirmation Messages
- Form confirmation text is registered as cms.form.<form-id>.successMessage. Filter All Translations to Form and search successMessage, then edit the target language.
- Change the default-language text from Forms, open the form, and select Translations, Confirmation message, Save confirmation message. Source discovery refreshes after saving; existing target translations are not automatically replaced or approved.
- Confirm storefront delivery separately through the existing Resources.ReadFrom.Form rollout setting. A saved draft translation is not evidence that the storefront is using unified form resources.
Resource Scan Results
Last updated: 2026-09-14. Scan Resource Keys uses the same discovery service as Scan content.
- Read the results: Created keys and upserted values count saved changes. Unchanged source values and skipped empty optional fields are reported separately. Rescanning unchanged content does not duplicate keys or replace existing target translations.
- Handle partial scans: A failed content type makes the background job fail, even when other changes were saved. Inspect its output, correct the cause, and rerun. Earlier saved changes remain valid.
- Preview safely: Integrations can request a read-only discovery preview. Its candidate counts describe what would change; no keys, values, namespaces or retirement changes are saved. Preview is not the default Scan Resource Keys button action.
- Cancellation and timeouts: Cancel stops further work but does not undo saved changes. A timeout leaves the remote outcome unconfirmed; inspect the inventory before rerunning. Missing service configuration or authorization is a failure, never successful coverage.
Edit Rich Text as HTML
- Edit HTML: Use the code icon in an editable rich-text toolbar to open its current HTML. Visual editing remains the default, including compact fields and labels.
- Apply: Return supported HTML to the visual editor, then use the parent record's normal Save or Publish action. Applying source alone does not save the record.
- Supported markup: Source uses the same rich-text format as the field. Unsupported tags or attributes may be removed or normalized. Scripts, unsafe links, and event handlers are removed; existing server validation and design rules still apply.
- Cancel: Cancel, close, or press Escape to discard the source draft. Opening source or applying unchanged source does not change the record. If content changes elsewhere while the dialog is open, cancel and reopen it before editing.
- Mail variables: Keep placeholders such as {{firstName}} and {{accountUrl}} intact, including placeholders in link addresses. The source dialog does not expose internal variable-chip markup.
- Read-only content: HTML editing is unavailable when the field is read-only. Plain-text fields and structured block settings are not HTML editors. A failed Apply retains the source draft for correction.