MRO Objects (Client) - Revision history

LKR: /* Task */

2026-04-23T12:35:11Z

‎Task

2026-04-20T09:54:49Z

‎See also

2026-04-20T09:32:15Z

‎Task

2026-04-13T13:54:31Z

‎Numeric Task {{Version/MobileSince|5.1}}{{Version/WinXSince|5.1}}

2026-04-13T12:36:02Z

‎Numeric Task {{Version/MobileSince|5.1}}{{Version/WinXSince|5.1}}

2026-04-08T09:14:58Z

‎Task

2026-03-12T13:47:16Z

‎Picture Task {{Version/MobileSince|5.1}}{{Version/WinXSince|5.1}}

2026-03-11T10:41:36Z

2026-03-11T10:28:15Z

‎Technical Status

2026-03-11T10:21:49Z

@@ Line 206: / Line 206: @@
 {{Hint|Setting NA (not applicable) on a picture task is always possible, regardless of the condition of child documents.}}
 ==== Numeric Task {{Version/MobileSince|5.1}}{{Version/WinXSince|5.1}} ====
@@ Line 214: / Line 213: @@
 * If the configured value range is invalid (e.g. min > max) and the user enters a value, the [[#Tech Status|tech status]] will also be set to display an issue.
 * A numeric task also has a special value unit that can be set per task instance. If set, it overrides the standard value unit defined on the [[MetaProperty#Unit_Item|MetaProperty]].
 {{UnderConstructionStart}}

@@ Line 262: / Line 262: @@
 * [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)
 * [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)
 [[Category:Android|MRO Objects (UBIK WinX)]]

@@ Line 214: / Line 214: @@
 * If the configured value range is invalid (e.g. min > max) and the user enters a value, the [[#Tech Status|tech status]] will also be set to display an issue.
 * A numeric task also has a special value unit that can be set per task instance. If set, it overrides the standard value unit defined on the [[MetaProperty#Unit_Item|MetaProperty]].
 {{UnderConstructionEnd}}

@@ Line 211: / Line 211: @@
 A [[MROCLS_MRO_NUMERIC_TASK|numeric task]] is a task which records a double value (e.g. from a temperature sensor). Entering the value (including Not Applicable) completes the task.
 * The value is compared against an accaptable value range which is not editable on the client.
-* Deviation from this range results in visual feedback as well as the Tech Status being set to display an issue.
+* Deviation from this range results in visual feedback as well as the [[#Tech Status|tech status]] being set to display an issue.
-* An incorrectly set value range (e.g. min > max) also results in visual feed back and the Tech Status being set.
+* If the configured value range is invalid (e.g. min > max) and the user enters a value, the [[#Tech Status|tech status]] will also be set to display an issue.
-* A numeric task also has a special value unit that can be set per object and overrides the standard unit when it is set.
+* A numeric task also has a special value unit that can be set per task instance. If set, it overrides the standard value unit defined on the [[MetaProperty#Unit_Item|MetaProperty]].
 {{UnderConstructionEnd}}

@@ Line 213: / Line 213: @@
 * Deviation from this range results in visual feedback as well as the Tech Status being set to display an issue.
 * An incorrectly set value range (e.g. min > max) also results in visual feed back and the Tech Status being set.
-* A numeric task also has a special value unit that can be set per object and overrides the standard unit.
+* A numeric task also has a special value unit that can be set per object and overrides the standard unit when it is set.
 {{UnderConstructionEnd}}

← Older revision		Revision as of 09:14, 8 April 2026
Line 205:		Line 205:

	{{Hint\|Setting NA (not applicable) on a picture task is always possible, regardless of the condition of child documents.}}		{{Hint\|Setting NA (not applicable) on a picture task is always possible, regardless of the condition of child documents.}}
		+
		+	{{UnderConstructionStart}}
		+	==== Numeric Task {{Version/MobileSince\|5.1}}{{Version/WinXSince\|5.1}} ====
		+
		+	A [[MROCLS_MRO_NUMERIC_TASK\|numeric task]] is a task which records a double value (e.g. from a temperature sensor). Entering the value (including Not Applicable) completes the task.
		+	* The value is compared against an accaptable value range which is not editable on the client.
		+	* Deviation from this range results in visual feedback as well as the Tech Status being set to display an issue.
		+	* An incorrectly set value range (e.g. min > max) also results in visual feed back and the Tech Status being set.
		+	* A numeric task also has a special value unit that can be set per object and overrides the standard unit.
		+	{{UnderConstructionEnd}}

	[[Category:Android\|MRO Objects (UBIK WinX)]]		[[Category:Android\|MRO Objects (UBIK WinX)]]

@@ Line 190: / Line 190: @@
 ==== Picture Task {{Version/MobileSince|5.1}}{{Version/WinXSince|5.1}} ====
 A [[MROCLS_PICTURE_TASK|picture task]] is a check task which can only be finished when it has at least one child document containing a valid file. In the UI, an additional photo button is presented next to the check so users can easily take photos before finishing the tasks.
@@ Line 208: / Line 206: @@
 {{Hint|Setting NA (not applicable) on a picture task is always possible, regardless of the condition of child documents.}}
-{{UnderConstructionEnd}}
+[[Category:Android|MRO Objects (UBIK WinX)]]
+[[Category:Client|MRO Objects (Client)]]
+[[Category:Mobile|MRO Objects (Client)]]
+[[Category:Pages with broken file links|MRO Objects (Client)]]
+[[Category:WinX|MRO Objects (UBIK WinX)]]
-−
-−
 === MRO objects with project information (WinX only) {{Version/WinXSince|2.5.4}} ===

@@ Line 11: / Line 11: @@
 [[File:TechStats_WinX.png|100px|Technical Status Indicator (Winx & Mobile)]]
 === Organisational Status ===
@@ Line 22: / Line 16: @@
 <gallery>
 File:UI_WinX_MRO_OrganisationalStatusIndicator.png|Organisational Status Indicator (WinX)
-File:UI_WinX_MRO_WPConfirmedIndicator.png|MRO Workpackage Confirmed (Flag) Indicator (WinX)
+File:ConfirmedWP_WinX.png|MRO Workpackage Confirmed (Flag) Indicator (WinX)
 File:Android_orga_status.PNG|Organisational Status Indicator (Android)
-File:Android_orga_status_finished.PNG|MRO Workpackage Confirmed Indicator (Android)
+File:ConfirmedWP_MAUI.jpeg|MRO Workpackage Confirmed Indicator (Mobile)
 </gallery>
@@ Line 53: / Line 47: @@
 <gallery>
-File:UI_WinX_MRO_WPConfirmButton.png|MRO Workpackage confirm button (WinX)
+File:ConfirmingWP_WinX.png|MRO Workpackage confirm button (WinX)
-File:UI_WinX_MRO_WPRevokeConfirmButton.png|MRO Workpackage revoke confirmation button (WinX)
+File:MRORevoke_WinX.png|MRO Workpackage revoke confirmation button (WinX)
-File:Android_finish_workpackage.PNG|MRO Workpackage confirm button (Android)
+File:ConfirmingWP_MAUI.jpeg|MRO Workpackage confirm button (Android)
-File:Android reopen workpackage.PNG|MRO Workpackage revoke confirmation button (Android)
+File:MRORevoke_MAUI.jpeg|MRO Workpackage revoke confirmation button (Android)
 </gallery>

@@ Line 1: / Line 1: @@
 [[File:MRO_WinX.png|thumb|alt=MRO Child List UI (WinX)|MRO UI (WinX)]]
-[[File:MRO_MAUI.jpeg|thumb|alt=MRO Child List UI (Android)|MRO UI (Android)]]
+[[File:MRO_MAUI1.jpeg|thumb|alt=MRO Child List UI (Android)|MRO UI (Android)]]
 The WinX client UI displays MRO configured objects like any other root- or child-object enriched by some additional logic and features.