imbahub
Menu +
EN
Talk to us
IMBAHUB / Knowledge & guides

Do not let an old review decision hide a new source edit.

A language version can look complete even though its source changed during the work. Test version comparison at completion, rather than only task creation. Use synthetic records and controlled test recipients; existing translations need not be overwritten to exercise the workflow.

Compare the source when review completes
  1. Same version

    The decision can refer to its intended evidence.

  2. Newer version

    A new review need must be addressed.

  3. Unknown version

    Freshness is unproven; investigate before marking current.

Current is a content decision, rather than just a closed task.

The queue is empty, but a language reviewed A and the source is C. What does that show?

That the queue alone does not establish currency. Investigate the missing signal, relationship or completion rule and retest.

Prepare source and language baselines

Create a test source and two language records with agreed relationships. Identify fields sharing business meaning and fields owned locally. Record the source version each language last assessed.

Fictional example: two languages reviewed version A of a service condition. The source becomes B and creates a task. The translator needs to identify the change, affected language and person who decides its relevance.

Change the source while review is open

Have the language owner begin against B. Create C with another important edit before completion. Attempt to finish the old task and observe the language's current-status marker.

Write the expected outcome explicitly: perhaps a stop for reassessment or a remaining need against C. Reviewers must not accidentally approve text outside their evidence. A timestamp with unclear meaning is insufficient version evidence.

ExerciseRiskExpected evidence
New source during translationOld decision hides a new editRemaining need or renewed review
Same signal twiceConflicting duplicate tasksOne coherent case under the chosen model
Local field changeLocal offer gets overwrittenField ownership respected
Wrong language or record relationshipChange reaches the wrong recipientExplicit exception outcome
Missing signalQueue looks falsely emptyAgreed comparison detects the difference

Exercise duplicates and incorrect relationships

Deliver the same synthetic change signal again through the test route. Check whether the task updates or is handled without unintended duplication. Include a missing relationship and a language intentionally independent of the source.

Then edit a local field. A broad synchronisation rule must not replace it without a decision. Change tracking and translating content are different actions needing their own permissions and checks.

Show how a missing signal becomes visible

In the test environment, simulate an important edit that creates no expected task. Run the agreed comparison between source and last-reviewed version. Record how an owner learns the evidence may be stale.

Report source ID, relationship, versions, event, language state and retest. Actual language and factual review still follows before content acceptance. This exercise establishes the sampled change workflow, rather than correct translation or publication.

Sources and further reading

Questions, answered

Is latest modification time the approved source version?

Not automatically. The time field's meaning and version model must be known and tested.

Does an empty review queue mean every language is current?

Only if tasks and comparisons actually cover the changes. Missing signals or incorrect relationships can otherwise remain hidden.

IMBAHUB

What would you like to make possible?

Open a review against B, create C and establish that completing B does not acknowledge C.

Talk to us
Product interface set to English in an isolated environment with fictional English demo content.

Product interface set to English in an isolated environment with fictional English demo content.