Using the web client, we request translations of various publications in various languages in one single translation job. When the translation job is finished, we want to release all translated topics in all requested languages. Instead of releasing the topics language by language (it is tedious), we would like to use the following feature:

Unfortunately, this simply doesn't work for us. Last month, Stephen Davey helped us understand why.

All of our publications contain a few objects that are "located in a folder with write permissions only given to user who belong to the System Management group". These objects are already released in several languages.

Most users do not belong to this System Management group. When we try to release all topics & objects from our publications, using this "release all" feature, the system first checks whether we have permission to release them (before checking whether they need to be released in the first place). The Release Translation therefore stops upon the first failure, mainly when:

1. The user does not have write permission to objects in a folder (whether the objects are already released or not).

2. The object or objects do not exist in the given language.

So, at the minute the system is facing these restricted (yet already translated and released) objects, the Release Translations is stopped completely. In our case, we therefore have to release "manually" most languages, one by one.

This shouldn't be the case: the system should completely ignore already released objects (whatever their restrictive status), or we should at least have the option to ask the system to ignore errors and continue releasing topics & objects that are not restricted.

NB : The following happens on both SDL KC Build 12.0.3215.1 and Tridion Docs 14.