-
Bug
-
Resolution: Fixed
-
None
-
Critical
-
-
Emptyshow more show less
problem
We have 4 Major Import start points:
- ImportService::import
- ImportService::importSingleTask
- WorldServer connector
- plunet connector
In all 4 places the defaults are evaluated at different points, and at the wrong place.
Defaults must be evaluated after task preparation and before worker queuing.
This must be unified and fixed.
Due hotfixes in that area, we had the following problems: no pre-translation for language resources added by default. Using Terminology in this context, this triggered duplicate key errors due task meta usage
Therefore we have to test
- Proper Import and defaults usage (users / generated workflow step out of assigned users / pre-translation as mentioned from TM / MT / Terminology)
- Im in all available Import ways:
- Manually
- via API (task type default)
- Across Hotfolder
- PlunetConnector
- WorldserverConnector
Best would be to have integrations tests for all of that, testing the defaults and pre-translation.
Currently there is probably no test testing the pre-translation triggered by task defaults.