Understand translation issues with locked target files
Translation jobs should not fail if a target file has an approval lock (signed, approved). This scenario occurs when you set the optional features related to locking files, approve the target file after it's translated, and then try to resend the source file to translation after it updating it.
Project Director has been renamed to GlobalLink Enterprise.
You must have permission to be a Translation coordinator or an Administrator before you can work with translation jobs
Prerequisites
- Before you send translation requests from Inspire, you must make sure your translation project is configured in GlobalLink Enterprise (formerly called Project Director).
- Your project configuration will contain information such as the source and target languages you use.
By default, a translation coordinator can select any unlocked component and send it to translation.
- However, an administrator can remove the ability to send a component to translation unless it has been approved.
Setting locks for files sent to translation
If you use the following locks AND approve Target components after translation, you should still be able to send source files back to translation without errors.
- LockForApprove = true (After a component is approved or signed, it is locked.)
Control if a lock is set after approval
- TranslationLockSourceDisabled = true (After a component is sent to translation, it is not locked. The Target file is locked automatically.)
- TranslationApprovedOnly = true (A component can only be sent to translation if it is approved or signed.)
Sending updated source files to translation
Inspire supports the following scenario: