Last modified on 26 July 2023, at 13:55

MROCLS GROUPEDTASK

Revision as of 13:55, 26 July 2023 by MHM (Talk | contribs)

IC CLASSIFICATION.gif Grouped Task classification object
Name MROCLS_GROUPEDTASK
Inheritance MROCLS MRO TASK
Namespace MRO.Classification
ID {4130333A-93A2-4F35-AFBC-B4AB7AC7856E}
Purpose Classify tasks as sequential tasks
Version 3.7.1+

Sometimes, not all tasks of one work package 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 Grouped Tasks.

The Grouped Task classification classifies an object as Grouped Task.

This Grouped Task classification is an Autonomous Classification where some of the required properties are autonomously added to the MetaDefinitions (ACM).

MetaProperties

Name Data type Comment
SIBLING_IDS Guid List of sibling Grouped Tasks. This property is autonomous. It must not be added to the Task - Metaclass. It is managed by the MRO Kernel.
NOT_NECESSARY Boolean Identifies a Grouped Task as Not Necessary as its siblings tasks are already finished. This Property is NOT autonomous. It is necessary to add it to the Task MetaClass.
GROUP_LIMIT Integer Defines the number of Grouped Tasks that must be finished until its siblings tasks are considered as "Not Necessary". This Property is NOT autonomous. It is necessary to add it to the Task MetaClass.


See also