So we wanted to force Components into workflow before any changes are made to them. For this we use the checkbox “Any changes made to a Component based on this Schema require approval by a Bundle Workflow Process” in the Component Schema as shown below:
It works as expected and forces the component to the Bundle Workflow Process before it can be approved but it exposes an issue which is related to translation.
We support Translation in our workflow process and there is a “Send For Translation” workflow activity for this. This activity creates a translation job of type “Push” and sends items for translation. when the job is sent, the component is localized and checked-out in target publications. When the translation is retrieved by the translation management system it's checked back in. (This works like this when the above checkbox is unchecked in schema)
Now when we force Bundle Workflow Process on Components using the checkbox shown above, after completion of translation, the component is NOT localized with the local content in the target publication.
We're wondering if this is because when TMS tries to localize the component, it can’t because Tridion expects the component to be locked by a “Bundle Workflow Process”. And so the component is not localized and remains untranslated.
We have tried below options to make this work:
Localize the schema at local publication level and uncheck the checkbox
This works, but it would mean we need to localize all the schemas at translation target publication level (of which there are many publications for many clients). Also, we need to take care of syncing the schema from the parent if any change happens at the parent publication.
Disable workflow for local Publication
This works but we need workflow at the target level so can't go with this approach.
Can you suggest better options to support translation with the workflow enforcing checkbox?