Regarding the TP specification, if you need to model two parallel tasks, one is a daily medication and the other some lab tests, and you want to interrupt the medication when the lab tests are ready, would a repeatable task be the right way to represent the medication with a terminate-condition (either a system or manual notification from the lab)? is there any other (better) way to represent that? I have seen that task-waits delay the start of the task, but in this case a task in branch B must interrupts a task in branch A in a parallel group.
As an extension to this question, is there a way other than task-waits (or period in repeatable tasks), of maintaining tasks in sync, with time spacers before, or after the task? For example, a task that starts with a given delay only when other task is initiated. I have seen that the event_relation task attribute allows specifying whether the task should start before, with or after the triggering event, and this could be enough for that, especially if extensions are added to these operators (before, with or after any event or absolute/relative times).
Another example would be when a group of tasks needs to meet the same (end) deadline. In this last case would the and-all paths decision branch be the right representation for this?
Finally, where can I find more information about the possibility of associating rules to a task or task group? The specification mentions that if a task Group needs more complex execution logic, this can be achieved by adding a rule to the task group using the TASK_GROUP.execution_rules attribute.
Thanks in advance,