Changes

==== Selective Grouped Task {{Version/WinXSince|4.2}}{{Version/XamarinSince|4.2}} ====Sometimes, not all tasks have to be finished. More specifically, there might be a predefined condition where you only need to finish a certain number of tasks among a group of them. These are known in {{UBIK}} as [[MROCLS_SELECTIVETASKMROCLS_GROUPEDTASK|selective grouped tasks]].

{{Hint|Technically speaking, the finished status is completely independent from the not necessary status on a task. A selective grouped task which is no longer necessary can be both finished or not yet finished. In other words, users don't have to finish a not necessary selective grouped task, but they still can.}}

{{Hint|The precise status calculation for selective grouped tasks and their task owners requires the knowledge of all siblings tasks. Imagine 2 out of 3 tasks must be finished but the client only knows 1 in total and the others are only available at the server at that time. This makes it impossible to draw conclusions whether the task(s) should be necessary or not. Under such circumstances, the local status calculation is done as if these are just regular tasks.}}

{{Hint|Like with the other MRO objects, the client always chooses the best available statuses for selective grouped tasks to present to the users. More specifically, it uses the statuses calculated by the server when the client is not offline and there are no uncommitted local changes on the involved objects. Otherwise, it uses the statuses calculated locally to the best of its knowledge.}}

A task can also be a selective grouped and a sequential one at the same time. In such a case, the selective grouped nature of the sibling tasks will affect the way the task sequence completes.

For example, task A1, A2 and A3 are 3 selective grouped sibling tasks and only 1 of them needs to be finished. At the same time, they are all predecessors of task B. Normally, all predecessors must be finished (and locked) before task B becomes the next one in the sequence and therefore unlocked. In this case, however, as soon as one of the predecessors is finished, all three become unnecessary (and locked) and task B unlocks as a result of that.