Approve For Language Jobs | Overview & Expected Behavior

Basics

• This article aims to demystify how the "Approve For Language Jobs" button and asset tag work in OM/Ce6.
• This is intended as a reference guide for all Localization Ops.
• Across clients, Client Ops manages this button.
• IMPORTANT: to ensure this workflow operates as intended, we MUST remember to name each proxy asset version (e.g. "Lock") -- if the name is missing, many different things break (such as automatic application of the Approved for Language Jobs tag on first pass for non-Alula Jobs, or English reopening CQC1 resulting in downstream Language Jobs becoming not workable)

Index

Use the links below to jump to a specific point in the article:

• Background Information
  • Workability Requirements for Translation with Template Jobs
• At First Pass: What Happens If I Press the Button?
• English Reopened Template: What Happens If I Press the Button?
• Revision Pass: What Happens If I Press the Button?

Background

• This button is always located on the English Template Jobs, within the final (PM) Task:

• Pressing this button marks an English Template as approved for downstream translation jobs -- depending on when it is pressed, the expected results will vary.
  • These expected results are fully detailed in this article.
• This button did not exist in Localization Scheduler.

Workability Requirements for Translation with Template Jobs

Translation with Template Jobs have their workability controlled by their "Sentinel" Task. This is ALWAYS Task 1:

Subsequent Tasks within the Translation with Template Jobs (Translation, Linguistic QC, Post-Processing) derive their workability and asset versioning from the Sentinel Task.

Workability Requirements - Sentinel Task

The following are only FULLY visible in the Input Requirements section of the Sentinel Task (Task 1):

Here is a fulfilled "Template" Asset Shell in the Input Requirements of the Sentinel Task:

Here is a fulfilled "Language MTO" Asset Shell in the Input Requirements of the Sentinel Task:

Expected Behavior

First Pass

IMPORTANT: As mentioned at the top of this article -- if the proxy asset version does not have a name (e.g., "Lock"), then the following will NOT happen. If the proxy asset version is nameless, the Approve For Language Jobs button will need to be manually pushed, regardless of the client. We still recommend naming the proxy before doing so.

• For non-Alula jobs, the Approve for Language Jobs button does not need to be manually pressed
  • Once the English Template Asset Shell is created (marked "Available"), the system will automatically apply the "Approved for Language Jobs" tag.
  • This button should not need to be pressed to enable downstream Translation with Template Jobs.
  • Note: If this is ever NOT the case and your proxy does contain a version name, please send a support ticket. Include a screenshot of the English Template Asset Shell from the Sentinel Task from the affected Translation with Template job.
• For Alula:
  • The Approve for Language Jobs button can be pressed at any time after the English Template and downstream Language Jobs are published -- before the English Template is workable, while it's pending, while it's in progress, during its QC, or after completion. NB this is only applicable if the proxy asset contains a version name.
  • Translation with Template jobs will be not workable if the button has not been pressed.

English Reopens Template without a New Proxy

In this scenario:

• English Template is complete.
• Approve for Language Jobs button has been pressed.
• Downstream Language Jobs are workable and are in various states of progress.
• We have NOT received a new proxy.

Then: English receives a flag from a linguist. English reopens the CQC1 Task in the English Template Job to review the flag and potentially make updates.

Upon English reopening the CQC1 Task:

IMPORTANT: If the proxy asset version does not have a name (e.g., "Lock"), then the following will NOT happen. The downstream Language Jobs will become not workable. Fixing it will require naming the proxy version, English submitting the Template, and PM pressing the Approve for Language Jobs button.

• The workability of the Language Tasks (translation, linguistic QC, post-processing) will not be affected, regardless of the stage that job is in (with ONE exception -- outlined below) -- however:
  • The Sentinel Task on downstream Translation with Template Jobs becomes not workable. Again, this does not affect the subsequent Tasks (e.g., translation).
  • Within the Sentinel Task, the English Template Asset Shell versions up and changes to 'Awaiting'.
  • The Approved For Language Jobs tag is removed from the English Template Asset Shell.
• If the downstream Language Tasks are rendered not workable - it is very likely this Job was published prior to an OM Job Template update (executed on July 31, 2026).
  • In this case, please send a support ticket. Explain that reopening the CQC1 English Task incorrectly rendered downstream Language Tasks not workable, and that we likely need to update that individual Job's code.

Exception

• If Language Job is in the following state: Linguistic QC is complete, 'Needs Review' by Creation linguist...
• The Creation Task will become not workable.
• To fix this:
  1. Go to the Creation Task within the Translation with Template Job (not the Sentinel Task).
  2. Find the English Template Asset Shell.
  3. Change the Asset Shell back to the earlier Asset Version:

• Note: you should NOT need to manually change this Asset Shell's version back to "Latest" down the line -- when the Sentinel Task becomes workable again, it should update the Asset Shell's version automatically.

Once the CQC1 Task is resubmitted by English (whether or not updates were made):

• The Approve for Language Jobs button must be manually pushed to release the English Template to the downstream Language Jobs.

Revision Pass

IMPORTANT: Do NOT press Approve for Language Jobs button without confirming the new proxy has an Asset Version name (e.g. "Final").

For all clients, Approve for Language Jobs button must be pressed manually on revision passes.

The Approve for Language Jobs button can be pressed at any time after re-running for new proxy. However:

• If the other workability conditions for the downstream Translation with Template Jobs are met (i.e. English Template complete, QC submitted, MTO completed, CAPES completed)...
• Pressing the button will trigger different expected behavior depending on where each Translation with Template Job is in the process: