This came up recently with workflow 16890 (v4.9) task 29. The task is set up as a drawing task with several line tools, each tool has its own text task as a subtask. The workflow config script detects a line tool with text subtask as a transcription task, but that makes the assumption that there is only one drawing tool. As there are multiple tools in this case this is a false positive and should not be marked as a transaction task.
In the (near) future there will be a transcription tasks type that can be detected separate from other configs, but for backwards compatibility with projects like ASM, these kinds of auto-detections should not be removed from the code. I expect the easiest thing to do is add a command-line flag for turning on/off "special workflow" detection. The default should be off as these special workflows are less likely to be the case than typical setups.
This came up recently with workflow 16890 (v4.9) task 29. The task is set up as a drawing task with several line tools, each tool has its own text task as a subtask. The workflow config script detects a line tool with text subtask as a transcription task, but that makes the assumption that there is only one drawing tool. As there are multiple tools in this case this is a false positive and should not be marked as a transaction task.
In the (near) future there will be a transcription tasks type that can be detected separate from other configs, but for backwards compatibility with projects like ASM, these kinds of auto-detections should not be removed from the code. I expect the easiest thing to do is add a command-line flag for turning on/off "special workflow" detection. The default should be
off
as these special workflows are less likely to be the case than typical setups.