Schließen von Awork-Aufgaben mit offenen Abhängigkeiten verhindern

## Awork workaround for done tasks with subtasks or dependencies Currently, Awork does not offer direct support for the following functions: * If a task has subtasks, then it should not be able to be marked as completed while subtasks are still open * If a task is dependent on other tasks, then it should not be able to be marked as completed as long as these linked tasks are still open ### This n8n workflow offers the following functions: * Checking whether all subtasks of a task have been completed before it can be completed * Check whether tasks marked as prerequisites have been completed before the task can be marked as completed * If the condition for completing a task is not fulfilled, the workflow rolls back the status to the previous status * A comment is added to the task as to why this roll back occurred * This workflow does not use the Awork community nodes package, as this package does not support all API calls and is therefore not used by me. If you would like to use that package, you can find more information at https://support.awork.com/en/articles/9826591-n8n-integration and replace the http nodes with matching community nodes if applicable ### The following configuration settings are possible or required in the “Workflow config” node (following the webhook call): * finishedStateLabels (required): Label text of the task status entities that have the “Done” state. Must be stored as an array. Allows you to control whether the workflow is skipped for certain status changes, even if the task has been marked as completed. * useDependencies (optional): Boolean setting as to whether dependencies should be taken into account or not. If true, a task can only be marked as completed if the linked tasks have been marked as completed. * useTreeStructure (optional): Boolean setting whether parent and child tasks are taken into account. If true, then parent tasks can only be marked as completed if all child tasks have been marked as completed. * addComments (optional): Boolean setting as to whether a comment is added to a task if a status change has been undone by the workflow * commentTextDependencies (optional, required if addComments is true): Comment text that is added to a task when the status change is undone for uncompleted tasks on which the current task is dependent. Serves as a hint for the user. * commentTextTreeStructure (optional, required if ad