Variant criteria fall-back paths for translation jobs - On Premises 7

Localize

When you send content for translation you can choose the primary objects or variant objects. The variant criteria values you choose and the fall-back structure determine the content that will be sent. Note, the content included in the jobs is also affected by release states.

Release states in the translation job

Objects will only be included in the translation job if they are in the correct release state at the time the translation job is created.

Q: What if we only wanted to send 3 topics of a 10-topic book for translation... with the fall-back, wouldn't everything be selected?

A: We would need to exclude the other 7 topics by controlling their release states.

Let's look at three scenarios for adding content to your translation job using simple examples of criteria selections and how they are affected by fall-back paths.

  • Using a flat structure to include variant objects
  • Using a hierarchical structure to include variant objects
  • Choosing primary objects only by not selecting any variant values

Scenario 1: Falling-back using a flat structure

Example: I want to create a translation job where the source content is "AUS":

Criteria:

Meaning:

VariantCriteriaExamples-SimplestValue

"Send for translation all objects from the selected books that are in the correct release state, and that have the variant criteria value of Region=AUS."

But, there is a bit more complexity to the logic...

In most cases, we want to send an entire book for translation so that all topics and objects are included. In the above example, we checked Region=AUS, but if the system cannot find this value for each object in the translation job, it falls back to the equivalent of none (or no variant values are selected), and so will send the primary object for translation.

Criteria:

Fall-back path logic:

Meaning:

VariantCriteriaExamples-SimpleAUSB

VariantCriteriaExamples-SimpleAUSB(2)

"Send for translation all objects from the selected books that are in the correct release state, and that have the variant criteria value of Region=AUS.

Where objects from the books do not have this value, then fall-back to Region=None (that is, send the primary object)."

Scenario 2: Falling-back using a grouped or hierarchical structure

When the values are arranged hierarchically, if you specify a variant criterion value and an object in your translation job does not have that particular value, the system progressively falls back one level until it finds a value, or until it reverts to the equivalent of none (no variant values are selected) for that object.

Example: I want to send objects where the source content is "Version 2.0":

Criteria:

Fall-back path logic:

Meaning:

VariantCriteriaExamples-SimplestFallback

VariantCriteriaExamples-SimplestFallback(2)

"Send for translation all objects from the selected books that are in the correct release state, and that have the variant criteria value of Version=2.0.

Where objects from the books do not have this Value, fall back to Version=1.0, and if this does not exist, fall back to Version= None (primary object)."

Scenario 3: What happens if no values are selected

When no variant criteria values are specified at all, the system falls back to the equivalent of none (no variant values are selected). That is, all primary objects in your selected books that are in the correct release state will be sent for translation.

Example: I want to send the primary objects, not the variants:

Criteria:

Fall-back path logic:

Meaning:

VariantCriteriaExamples-None

VariantCriteriaExamples-None(2)

"Send for translation all objects from the selected books that are in the correct release state, and that have the variant criteria value of Operating System=None."

In this situation, with nothing checked, you will see an on-screen warning, as the system will suspect that you made a mistake:

WebLM-Error-VariantCriteriaNotDefined