MROCLS GROUPEDTASK - Revision history

LMA: /* See also */

2025-05-14T06:01:07Z

‎See also

2024-06-26T11:23:11Z

2023-10-12T13:55:55Z

2023-10-12T07:59:24Z

2023-10-12T07:59:09Z

2023-07-26T13:55:42Z

2023-07-26T13:54:20Z

2023-07-26T13:48:41Z

2023-07-26T13:48:13Z

2022-12-19T14:27:47Z

@@ Line 48: / Line 48: @@
 * [[MROCLS_MRO_CHECK_TASK#Check Task]] (Classification)
 * [[MROCLS_MRO_INSPECTION_TASK#Inspection Task]] (Classification)
 [[Category:Classifications|M]]

@@ Line 42: / Line 42: @@
 == See also ==
 * [[MRO_Objects_(Client)#Grouped_Task]]
 * [[MROCLS_MRO_TASK|Task]] (Classification)
 * [[MROCLS_MRO_MEASUREMENT_TASK#Measurement Task]] (Classification)

@@ Line 4: / Line 4: @@
 | 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}

@@ Line 27: / Line 27: @@
 |}
-=== Interface and Custom Code ===
+== 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.

← Older revision		Revision as of 07:59, 12 October 2023
Line 27:		Line 27:
	\|}		\|}

		+	=== 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 ==		== See also ==

@@ Line 9: / Line 9: @@
 }}
-Classifies an object as Grouped 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]].
 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 [[MRO_Objects_(Client)#Grouped_Task|Grouped Tasks]].
 This Grouped Task classification is an [[AutonomousClassification|Autonomous Classification]] where some of the required properties are autonomously added to the MetaDefinitions (ACM).

← Older revision		Revision as of 13:48, 26 July 2023
Line 31:		Line 31:
	* [[MROCLS_MRO_CHECK_TASK#Check Task]] (Classification)		* [[MROCLS_MRO_CHECK_TASK#Check Task]] (Classification)
	* [[MROCLS_MRO_INSPECTION_TASK#Inspection Task]] (Classification)		* [[MROCLS_MRO_INSPECTION_TASK#Inspection Task]] (Classification)
		+
		+	[[Category:Classifications\|M]]

← Older revision		Revision as of 13:48, 26 July 2023
Line 26:		Line 26:

	== See also ==		== See also ==
		+	* [[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)

← Older revision	Revision as of 14:27, 19 December 2022
(No difference)