Difference between revisions of "MROCLS GROUPEDTASK"

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

Latest revision as of 11:23, 26 June 2024

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.

Interface and Custom Code

The MRO Grouped Task Classification necessitates knowledge about all the tasks in a group. From the point of view of one task, we can call the other tasks "siblings". These siblings are all other tasks that are in the same group as the current one.

As an engineer, you are free to choose how these siblings are evaluated, but we have to tell UBIK about the result. Therefore, the classification requires an implementation of the following method:

public IEnumerable<UBIK.MRO.IGroupedTask> Siblings();

It can be added in the respective MetaClass's custom code using UBIK.Studio's Code Editor.

@@ Line 1: / Line 1: @@
 {{ClassificationInfoBox
-| title = Selective Task classification object
+| title = Grouped Task classification object
 | name = {{PAGENAMEE}}
 | inheritance = [[MROCLS_MRO_TASK]]
 | namespace = MRO.Classification
-| purpose = Classify tasks as sequential tasks
+| purpose = Classify tasks as grouped tasks
 | version = 3.7.1+
 | id = {4130333A-93A2-4F35-AFBC-B4AB7AC7856E}
 }}
-Classifies an object as Selective Task.
+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 [[MRO_Objects_(Client)#Grouped_Task|Grouped Tasks]].
-This classification is an [[AutonomousClassification|Autonomous Classification]] where some of the required properties are autonomously added to the MetaDefinitions (ACM).
+The Grouped Task classification classifies an object as Grouped Task.
+This Grouped Task classification is an [[AutonomousClassification|Autonomous Classification]] where some of the required properties are autonomously added to the MetaDefinitions (ACM).
 == MetaProperties ==
@@ Line 17: / Line 20: @@
 ! width=30% | Name !! width=20% | Data type !! Comment
 |-
-| SIBLING_IDS|| {{Guid}} || List of sibling Selective Tasks. This property is autonomous. It must not be added to the Task - Metaclass. It is managed by the MRO Kernel.
+| 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 Selective 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.
+| 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.
 |-
-| SIBLING_LIMIT|| {{Integer}} || Defines the number of Selective 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.
+| 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.
 |}
+== Interface and Custom Code ==
+The MRO Grouped Task Classification necessitates knowledge about all the tasks in a group. From the point of view of one task, we can call the other tasks "siblings". These siblings are all other tasks that are in the same group as the current one.
+As an engineer, you are free to choose how these siblings are evaluated, but we have to tell UBIK about the result.
+Therefore, the classification requires an implementation of the following method:
+<syntaxhighlight lang="csharp">
+public IEnumerable<UBIK.MRO.IGroupedTask> Siblings();
+</syntaxhighlight>
+It can be added in the respective MetaClass's custom code using UBIK.Studio's Code Editor.
 == See also ==
+* [[MRO_Objects_(Client)#Grouped_Task]]
+* [[MRO_(Plugin)]]
+* [[MROCLS_MRO_TASK|Task]] (Classification)
+* [[MROCLS_MRO_MEASUREMENT_TASK#Measurement Task]] (Classification)
+* [[MROCLS_MRO_PROGRESS_TASK# Progress Task]] (Classification)
+* [[MROCLS_MRO_CHECK_TASK#Check Task]] (Classification)
+* [[MROCLS_MRO_INSPECTION_TASK#Inspection Task]] (Classification)
+[[Category:Classifications|M]]