Problem

Basic usage

Currently it is not possible for PMs to define, what language resources are used for InstantTranslate. 

Right now,

• when a resource is assigned to a client without read nor write default, it will be used in InstantTranslate for text translation
• when a file is translated, the resource will not be used
• however, when the InstantTranslate user has the role "editor", too, and opens the file in the editor, the resource will be assigned with read access to the task (assignments change!)

This is very misleading. For text translation assigning the client is enough, for file translation at least read default is required, and the most confusing behaviour is assigning the resource, once the user opens the file in editor.

TQE usage

Right now we have a config "Use as TQE for InstantTranslate by default". This only applies for file translations.

Solution

Add InstantTranslate usage definition to the 2 following areas as shown in the screenshots (in language resource edit window and in client language resource overview grid). Nothing is selected there by default.

Add the config "Use as TQE for InstantTranslate text field".

Important:

runtimeOptions.plugins.OpenAI.tqeForInstantTranslateTextTranslation (set to level 1 change it to correct level 4 )is already created as config. When implementing this issue, we need to remove this and instead add a config "TQE for InstantTranslate text field", that works completely analogous to the current TQE for InstantTranslate configuration (and of course only available for AI resources). TQE for InstantTranslate configuration  needs to be renamed to  "TQE for InstantTranslate file translations"

Backwards incompatible change handling regarding usage for InstantTranslate field (NOT applicable for TQE fields)

The explicit handling of resource assignment for InstantTranslate is an important backwards-incompatible change.

Point the admins in the important release notes to the fact, that they have to set those fields correctly.

Do not use the definition in effect the first feature release, where this feature is rolled out. Simply offer them for defining the values.

Only in the following feature release activate them. This gives the PMs the opportunity and time to set the values correctly before with the next update they are actually used.

This means:

1. introduce the new field for the language resources "Use in InstantTranslate" without actually using the field, behavior remains unchanged. But add important release notes: "With the next release only those language resources in InstantTranslate that have the necessary configuration in the new field will be used. Please adjust your settings accordingly."
2. When this is released, in the next release, the new field should become active. Still add important release notes: "Only those language resources configured for the use in InstantTranslate will be used in InstantTranslate."