-
Bug
-
Resolution: Fixed
-
None
-
Critical
-
Avoid duplicate optional workflow step labels in job's workflow steps list
-
Emptyshow more show less
Problem
With TRANSLATE-4728 a bug was fixed for prevention of showing wrong workflow step names in the application. Unfortunately that fix breaks the logic which tasks should go back via t5connect in non default workflows.
solution
- replace back the changes that roles/types are used instead of workflow steps to find out the finished / confirmed tasks in t5connect controller (see https://bitbucket.org/mittagqi/translate5/pull-requests/1938/diff)
- instead of relying on a fixed array in a const RELEVANT_CONFIRMED_STEPS the affected steps should come from a new config
- runtimeOptions.t5connect.relevantWorkflowSteps
- guiGroup: System setup: General
- guiName: T5Connect relevant workflowsteps
- description: the workflow steps which are evaluated to consider a task as finished or confirmed
- level: 1 - system
- initial value and default: reviewing,translatorCheck
- defaults: must be calculated, see runtimeOptions.authentication.ipbased.applets which uses a dedicated typeClass to load valid defaults on the fly - in this case this valid defaults are all workflowstepnames of all workflows
- is caused by
-
TRANSLATE-4728 Avoid duplicate workflow step labels in job's workflow steps list
- Done