UBIK Wiki / Augmensys - Recent changes [en]

Mobile XAML

CWI — Wed, 26 Aug 2026 12:56:33 GMT

‎DataTrigger permanently blocks manual changes {{Version/MobileSince|5.0.0}}

HowTo:Convert Xamarin XAMLs to Maui

CWI — Wed, 26 Aug 2026 12:34:52 GMT

‎Pre-selecting a tab based on a metaclass or property

Mobile XAML

CWI — Wed, 26 Aug 2026 10:33:18 GMT

‎DataTrigger permanently blocks manual changes {{Version/MobileSince|5.0.0}}

HowTo:Convert Xamarin XAMLs to Maui

CWI — Wed, 26 Aug 2026 07:27:41 GMT

‎DataTrigger permanently blocks manual changes (use DataChangedBehavior instead)

Version 5.1.0 (Server)

MHM — Tue, 25 Aug 2026 15:30:04 GMT

Version 5.2.0 (Server)

MHM — Tue, 25 Aug 2026 15:14:04 GMT

‎5.2.0.10009 - 2026-08-25 (Initial Release)

List of Versions

MHM — Tue, 25 Aug 2026 14:56:52 GMT

Version 5.2.0 (Server)

MHM — Tue, 25 Aug 2026 14:55:46 GMT

HowTo:Convert Xamarin XAMLs to Maui

CWI — Tue, 25 Aug 2026 12:13:25 GMT

‎Highly Recommended

Client Feature Table

ARU — Tue, 25 Aug 2026 11:40:39 GMT

‎Documents

Version 5.3 (Mobile)

REP — Tue, 25 Aug 2026 08:14:34 GMT

‎5.3.? on 202?-??-??

Version 5.3 (WinX)

REP — Tue, 25 Aug 2026 08:14:15 GMT

‎5.3.? on 202?-??-??

MROCLS INTEGER TASK

JKN — Mon, 24 Aug 2026 15:19:34 GMT

MROCLS INTEGER TASK

LMA — Mon, 24 Aug 2026 11:29:05 GMT

Created page with "{{ClassificationInfoBox | title = Integer Task classification | name = {{PAGENAMEE}} | inheritance = MROCLS MRO TASK | namespace = UBIK.MRO.Classification | purp..."

New page

{{ClassificationInfoBox
| title = Integer Task classification
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_MRO_TASK#Task]]
| namespace = UBIK.MRO.Classification
| purpose = Classify objects as Integer Tasks
| version = 5.2.0+
| id = {2CE8E155-3E52-4C88-BE21-36F0C44484D2}
}}

An [[MRO_(Plugin)#Integer_Task|Integer Task]] object is an {{UBIK}} content object which is used to document work by entering an integer value.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=30% | Data type !! Comment
|-
| ''VALUE'' || {{Integer}} || The integer value entered for the task
|-
|}

== See also ==
* [[MROCLS_MRO_TASK#Task]] (Classification)
* [[MROCLS_MRO_MEASUREMENT_TASK#Measurement Task]] (Classification)
* [[MROCLS_MRO_CHECK_TASK#Check Task]] (Classification)
* [[MROCLS_MRO_INSPECTION_TASK#Inspection Task]] (Classification)
* [[MRO_Objects_(Client)#Integer_Task]]
* [[MRO_(Plugin)#Integer_Task]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)

MRO (Plugin)

LMA — Mon, 24 Aug 2026 11:28:10 GMT

MROCLS INTERFACE TASK

LMA — Mon, 24 Aug 2026 11:23:48 GMT

MROCLS INTERFACE TASK

LMA — Mon, 24 Aug 2026 11:22:22 GMT

Created page with "{{ClassificationInfoBox | title = Interface Task classification | name = {{PAGENAMEE}} | inheritance = MROCLS MRO CHECK TASK | namespace = UBIK.MRO.Classifi..."

New page

{{ClassificationInfoBox
| title = Interface Task classification
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_MRO_CHECK_TASK#Check Task]]
| namespace = UBIK.MRO.Classification
| purpose = Classify objects as Interface Tasks
| version = 5.2.0+
| id = {C109AA2F-D37E-47F7-A5C9-FD8C4556C61D}
}}

An [[MRO_Objects_(Client)#Interface_Task|Interface Task]] object is an {{UBIK}} content object which is used to document work using a boolean value.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=30% | Data type !! Comment
|-
| ''VALUE'' || {{Boolean}} || The boolean value of the task (inherited from [[MROCLS_MRO_CHECK_TASK#Check Task]])
|-
|}

== See also ==
* [[MROCLS_MRO_TASK#Task]] (Classification)
* [[MROCLS_MRO_CHECK_TASK#Check Task]] (Classification)
* [[MROCLS_MRO_MEASUREMENT_TASK#Measurement Task]] (Classification)
* [[MROCLS_MRO_INSPECTION_TASK#Inspection Task]] (Classification)
* [[MRO_Objects_(Client)#Interface_Task]]
* [[MRO_(Plugin)#Interface_Task]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)

MRO (Plugin)

LMA — Mon, 24 Aug 2026 11:21:46 GMT

‎Interface Task

Configure Comos for CUI

FMW — Thu, 20 Aug 2026 09:04:18 GMT

Version 5.2 (Mobile)

LGE — Wed, 19 Aug 2026 09:55:35 GMT

Version 5.2.0 (Server)

MHM — Tue, 18 Aug 2026 13:58:38 GMT

‎Features

MRO (Plugin)

MHM — Tue, 18 Aug 2026 13:57:35 GMT

‎Interface Task

MRO (Plugin)

LMA — Tue, 18 Aug 2026 13:50:36 GMT

‎Work Package

MROCLS SIGNATURE TASK

LMA — Tue, 18 Aug 2026 12:47:09 GMT

Created page with "{{ClassificationInfoBox | title = Signature Task classification | name = {{PAGENAMEE}} | inheritance = MROCLS MRO TASK | namespace = UBIK.MRO.Classification | purpose..."

New page

{{ClassificationInfoBox
| title = Signature Task classification
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_MRO_TASK#Task]]
| namespace = UBIK.MRO.Classification
| purpose = Classify objects as Signature Tasks
| version = 5.2.0+
| id = {37CC32F9-0113-4AF1-8A02-E21F5E7472F0}
}}

A [[MRO_Objects_(Client)#Signature_Task|Signature Task]] object is an {{UBIK}} content object which is used to document work by providing a signature.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=30% | Data type !! Comment
|-
| ''VALUE'' || Signature || The signature entered for the task
|-
|}

== See also ==

* [[MROCLS_MRO_TASK#Task]] (Classification)
* [[MROCLS_MRO_MEASUREMENT_TASK#Measurement Task]] (Classification)
* [[MROCLS_MRO_CHECK_TASK#Check Task]] (Classification)
* [[MROCLS_MRO_INSPECTION_TASK#Inspection Task]] (Classification)
* [[MRO_Objects_(Client)#Signature_Task]]
* [[MRO_(Plugin)#Signature_Task]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)

MROCLS TEXT TASK

LMA — Tue, 18 Aug 2026 12:46:44 GMT

Created page with "{{ClassificationInfoBox | title = Text Task classification | name = {{PAGENAMEE}} | inheritance = MROCLS MRO TASK | namespace = UBIK.MRO.Classification | purpose = Cl..."

New page

{{ClassificationInfoBox
| title = Text Task classification
| name = {{PAGENAMEE}}
| inheritance = [[MROCLS_MRO_TASK#Task]]
| namespace = UBIK.MRO.Classification
| purpose = Classify objects as Text Tasks
| version = 5.2.0+
| id = {6042083C-54A2-434C-8318-2CFC8A2BCEE2}
}}

A [[MRO_Objects_(Client)#Text_Task|Text Task]] object is an {{UBIK}} content object which is used to document work by entering text.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=30% | Data type !! Comment
|-
| ''VALUE'' || {{String}} || The text entered for the task
|-
|}

== See also ==

* [[MROCLS_MRO_TASK#Task]] (Classification)
* [[MROCLS_MRO_MEASUREMENT_TASK#Measurement Task]] (Classification)
* [[MROCLS_MRO_CHECK_TASK#Check Task]] (Classification)
* [[MROCLS_MRO_INSPECTION_TASK#Inspection Task]] (Classification)
* [[MRO_Objects_(Client)#Text_Task]]
* [[MRO_(Plugin)#Text_Task]]
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)

MRO (Plugin)

LMA — Tue, 18 Aug 2026 09:38:17 GMT

UBIK Client Getting Started

JKN — Tue, 18 Aug 2026 09:34:20 GMT

Reporting (Plugin)

MHM — Tue, 18 Aug 2026 08:59:14 GMT

‎Version 5.2

MRO Implemented Objects

LMA — Mon, 17 Aug 2026 14:35:04 GMT

Redirected page to MRO (Plugin)

Show changes

MRO Objects (Client)

LMA — Mon, 17 Aug 2026 14:31:15 GMT

‎Work Progress

MRO (Plugin)

LMA — Mon, 17 Aug 2026 14:22:51 GMT

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

Show changes

MRO Objects (Client)

LMA — Mon, 17 Aug 2026 13:56:26 GMT

‎Work Progress

MRO (Plugin)

LMA — Mon, 17 Aug 2026 13:29:13 GMT

Show changes

MRO Objects (Client)

LMA — Mon, 17 Aug 2026 11:31:50 GMT

Show changes

@@ Line 606: / Line 606: @@
 {{Hint|Maui ranks a value applied by an active DataTrigger's Setter higher than a manual property write (e.g. a user's tap). Every manual write attempt is silently discarded while the trigger's condition remains true.}}
-In the example below a DataTrigger is used to set the selected tab based on the record's metaclass. The initial selection works correctly, but afterwards the user can never manually switch to a different tab. Tapping another tab header highlights it, but the content never switches, and SelectedIndex silently reverts.
+One common use case that cannot be used directly in Maui is [[HowTo:Convert_Xamarin_XAMLs_to_Maui#Pre-selecting_a_tab_based_on_a_metaclass_or_property|Pre-selecting a tab based on a metaclass or property]].
-As a workaround, do not use DataTrigger for a property that should be data-driven once and then freely user-editable afterwards. Use the existing '''DataChangedBehavior''' and '''SetPropertyAction''' pattern instead.
+As a workaround, do not use DataTrigger for a property that should be data-driven once and then freely user-editable afterwards. Use the existing '''DataChangedBehavior''' and '''SetPropertyAction''' pattern instead. For an example click [[HowTo:Convert_Xamarin_XAMLs_to_Maui#Pre-selecting_a_tab_based_on_a_metaclass_or_property|here]].
-−
-{| class="wikitable" style="width:100%; table-layout:fixed;"
-! style="width:50%;" | Xamarin
-! style="width:50%;" | MAUI
-|-
-−
-<syntaxhighlight lang="xml">
-<controls:UBIKTabView.Triggers>
-    <DataTrigger TargetType="controls:UBIKTabView"
-                 Binding="{Binding Content.MetaUID, Converter={StaticResource EqualityToBool}, ConverterParameter='b82accb3-7437-429d-aed9-08dfdd5a9e59'}"
-                 Value="True">
-        <Setter Property="SelectedIndex" Value="1" />
-    </DataTrigger>
-</controls:UBIKTabView.Triggers>
-</syntaxhighlight>
-||
-<syntaxhighlight lang="xml">
-xmlns:behaviors="clr-namespace:UBIK.MAUI.Behaviors;assembly=UBIK.MAUI"
-...
-<controls:UBIKTabView.Behaviors>
-    <behaviors:DataChangedBehavior
-        Binding="{Binding Content.MetaUID, Converter={StaticResource EqualityToBool}, ConverterParameter='b82accb3-7437-429d-aed9-08dfdd5a9e59'}"
-        ComparisonCondition="Equal"
-        Value="True">
-        <behaviors:SetPropertyAction
-            PropertyName="SelectedIndex"
-            TargetObject="{Binding Source={x:Reference ContentTabs}}"
-            Value="1" />
-    </behaviors:DataChangedBehavior>
-</controls:UBIKTabView.Behaviors>
-</syntaxhighlight>
-|-
-|}
 {{Attention|This is not limited to tab selection. The same problem can occur wherever a DataTrigger, Trigger, MultiTrigger sets a property that a user (or code-behind) is also meant to change afterwards, for example:}}

@@ Line 801: / Line 801: @@
 {{UnderConstructionStart}}
-=== DataTrigger permanently blocks manual changes (use DataChangedBehavior instead) ===
+==== Pre-selecting a tab based on a metaclass or property ====
-In .NET MAUI, a DataTrigger that sets a property the user can also change interactively will permanently block that manual change as long as the trigger's condition stays true. This did not happen in Xamarin - it is a MAUI-specific behavior change.
+In Maui, an active DataTrigger permanently blocks the user from manually switching tabs. For this reason, instead of using a DataTrigger to set the SelectedIndex, a DataChangedBehavior with SetPropertyAction should be used, which sets SelectedIndex once when the relevant data changes and leaves the tab freely user-changeable afterwards.
-{{Hint|MAUI ranks a value applied by an active DataTrigger's Setter higher than a plain manual property write (e.g. a user's tap). Every manual write attempt is silently discarded while the trigger's condition remains true.}}
+See [[Mobile_XAML#DataTrigger_permanently_blocks_manual_changes|XAML Known Issues: DataTrigger permanently blocks manual changes]] for the full explanation.
-−
-In the example below a DataTrigger is used to set the selected tab based on the record's metaclass. The initial selection works correctly, but afterwards the user can never manually switch to a different tab. Tapping another tab header highlights it, but the content never switches, and SelectedIndex silently reverts.
-−
-'''Workaround:''' Do not use DataTrigger for a property that should be data-driven once and then freely user-editable afterwards. Use the existing DataChangedBehavior and SetPropertyAction pattern instead.
 {| class="wikitable" style="width:100%; table-layout:fixed;"
@@ Line 844: / Line 840: @@
 |}
-{{Attention|This is not limited to tab selection. The same problem can occur wherever a DataTrigger, Trigger, MultiTrigger sets a property that a user (or code-behind) is also meant to change afterwards, e.g.:}}
+The DataChangedBehavior and SetPropertyAction Binding, ConverterParameter, and Value need to match the target tab index and condition for the specific customizing. The SetPropertyAction TargetObject must reference the UBIKTabView via x:Reference (e.g. x:Name="ContentTabs" on the UBIKTabView).
-* Selection controls: Picker.SelectedIndex/SelectedItem, CollectionView/ListView.SelectedItem, RadioButton.IsChecked, Shell.CurrentItem
-* Toggle/input controls: Switch.IsToggled, CheckBox.IsChecked, Entry/Editor.Text
+{{Attention|This replacement applies to any property a DataTrigger sets that should stay user-changeable afterwards, not just SelectedIndex on a TabView, see [[Mobile_XAML#DataTrigger_permanently_blocks_manual_changes|XAML Known Issues: DataTrigger permanently blocks manual changes]] for other affected controls and scenarios.}}
-* Expand/collapse state on any control the user can also expand/collapse manually
-* Implicit/global Style.Triggers - the riskiest case, since it silently affects every control of that type on a page
-* Code-behind writes executed after the trigger has already applied a value (not just touch input)
 {{UnderConstructionEnd}}

@@ Line 596: / Line 596: @@
 <br>
 <br>
 === Incorrect glyphs may be shown on buttons ===

@@ Line 805: / Line 805: @@
 In .NET MAUI, a DataTrigger that sets a property the user can also change interactively will permanently block that manual change as long as the trigger's condition stays true. This did not happen in Xamarin - it is a MAUI-specific behavior change.
-'''Symptom:''' A DataTrigger is used to set e.g. the selected tab based on the record's metaclass. The initial selection works correctly, but afterwards the user can never manually switch to a different tab - tapping another tab header highlights it, but the content never switches and SelectedIndex silently reverts.
+{{Hint|MAUI ranks a value applied by an active DataTrigger's Setter higher than a plain manual property write (e.g. a user's tap). Every manual write attempt is silently discarded while the trigger's condition remains true.}}
-'''Cause (short version):''' MAUI ranks a value applied by an active DataTrigger's Setter higher than a plain manual property write (e.g. a user's tap). Every manual write attempt is silently discarded while the trigger's condition remains true - no error, no exception, it just never takes effect.
+In the example below a DataTrigger is used to set the selected tab based on the record's metaclass. The initial selection works correctly, but afterwards the user can never manually switch to a different tab. Tapping another tab header highlights it, but the content never switches, and SelectedIndex silently reverts.
-'''Workaround:''' Do not use DataTrigger for a property that should be data-driven once and then freely user-editable afterwards. Use the existing DataChangedBehavior and SetPropertyAction pattern instead - it performs a single, plain, imperative write the moment the underlying data changes, and never competes with later manual changes.
+'''Workaround:''' Do not use DataTrigger for a property that should be data-driven once and then freely user-editable afterwards. Use the existing DataChangedBehavior and SetPropertyAction pattern instead.
 {| class="wikitable" style="width:100%; table-layout:fixed;"
@@ Line 843: / Line 843: @@
 |-
 |}
 {{Attention|This is not limited to tab selection. The same problem can occur wherever a DataTrigger, Trigger, MultiTrigger sets a property that a user (or code-behind) is also meant to change afterwards, e.g.:}}
@@ Line 852: / Line 851: @@
 * Code-behind writes executed after the trigger has already applied a value (not just touch input)
-'''Rule of thumb:''' when converting a Xamarin DataTrigger, if the property it sets should remain user-changeable afterwards, convert it into a DataChangedBehavior with SetPropertyAction. Keep DataTrigger/Style.Triggers only for properties that should stay continuously data-driven and don't conflict with user input.
+{{Hint|When converting a Xamarin DataTrigger, if the property it sets should remain user-changeable afterwards, convert it into a DataChangedBehavior with SetPropertyAction. Keep DataTrigger/Style.Triggers only for properties that should stay continuously data-driven and don't conflict with user input.}}
 {{UnderConstructionEnd}}

@@ Line 17: / Line 17: @@
 * System.DataExchange
 * System.DataExchange.Relation }}
 = 5.1.0.10013 - 2026-07-13 (Service Pack) =

@@ Line 11: / Line 11: @@
 * UBIK Studio's [[Bulk Editor]] now supports a Query mode, allowing content to be pre-filtered for more efficient loading and finding relevant objects faster.
 * It is now possible to [[Injection_Management#Version_5.2.0.2B|install Plugins in UBIK Studio]].
-<!--
 === Bug Fixes ===
 === Enhancements ===
 === Known Issues ===
@@ Line 26: / Line 31: @@
 * UBIK now introduces a new file storage capability, enabling more efficient and reliable management of large number of files within the system.
 * Enhanced Exclusive Access notifications by introducing standardized check-in (Released) and check-out events (CheckedOut), enabling more flexible customization and integration scenarios.
 <!-- === Bug Fixes === -->
@@ Line 55: / Line 62: @@
 <div class="mw-collapsible-content">
 === Features ===
 * [[#Numeric Task|Numeric Task]] now retain their configured minimum and maximum source values and automatically apply them during replication, ensuring consistent validation and behavior across replicated tasks.
 * The same procedure can now be used multiple times in one super procedure.
 * The replication of procedures is able to handle Calculation tasks and switch tasks (with only one branch configured) correctly now.
@@ Line 113: / Line 119: @@
 * Support for CMW-Event-Notifications enables creation, updates, and deletion of COMOS data directly within UBIK—streamlining synchronization using optimized data synchronization.
 * CUI supports to update or override the file content of existing external COMOS documents—keeping documents in sync when their content changes.
 === Bug Fixes ===
 * Ex- and imports now fully support DateTime fields by including the time component, ensuring more accurate and complete data when generating interface runs.

@@ Line 2: / Line 2: @@
 <hr/>
 <div class="table" style="width:100%;">
-{{Item/Version|2026-??-??| {{Version/Server|5.2.0}}}}
+{{Item/Version|2026-12-??| {{Version/Server|5.3.0}}}}
 {{Item/Version|202?-??-??| {{Version/WinX|5.3}}}}
 {{Item/Version|202?-??-??| {{Version/Mobile|5.3}}}}
@@ Line 9: / Line 9: @@
 <hr/>
 <div class="table" style="width:100%;">
 {{Item/Version|2026-07-21| {{Version/WinX|5.2}}}}
 {{Item/Version|2026-07-21| {{Version/Mobile|5.2}}}}

@@ Line 1: / Line 1: @@
 __NOTOC__
-= 5.2.0.??? - 2026-??-?? (Initial Release) =
+= 5.2.0.10009 - 2026-08-25 (Initial Release) =
 <div class="toccolours mw-collapsible mw-collapsed" style="width:100%; overflow:auto;">
@@ Line 59: / Line 59: @@
 * The replication of procedures is able to handle Calculation tasks and switch tasks (with only one branch configured) correctly now.
-[[Category:Release notes|Version 5.2.0 (Server)]]
-[[Category:Server|Version 5.2.0 (Server)]]
-[[Category:Version 5.2|Version 5.2.0 (Server)]]
 === Bug Fixes ===

@@ Line 798: / Line 798: @@
 |-
 |}
 [[Category:How-To|Convert Xamarin XAMLs to Maui]]

@@ Line 449: / Line 449: @@
 | [[HowTo:Make_a_Document_editable_on_Mobile_Client|Editing]]
 || [[Image:IC_Bullet_Full.png|8px|link=]]
-|| [[Image:IC_Bullet_Full.png|8px|link=]]
+|| -
 || -
 ||
@@ Line 461: / Line 461: @@
 |}
+[[Category:Client|Client Feature Table]]
+[[Category:Mobile|Client Feature Table]]
 ==Navigation==

@@ Line 31: / Line 31: @@
 === 5.3.? on 202?-??-?? ===
 * Fixed an issue where documents did not load properly when switching the sync mode.
+[[Category:Client|Version 5.3 (Mobile)]]
 == Known issues ==

@@ Line 2: / Line 2: @@
 | title = Integer Task classification
 | name = {{PAGENAMEE}}
-| inheritance = [[MROCLS_MRO_TASK#Task]]
+| inheritance = [[MROCLS_MRO_TASK]]
 | namespace = UBIK.MRO.Classification
 | purpose = Classify objects as Integer Tasks

@@ Line 42: / Line 42: @@
 For Work Package presentation and confirmation in the clients, see [[MRO Objects (Client)#Work Package|Work Package]].
-[[Category:Android|MRO (Plugin)]]
-[[Category:Client|MRO (Plugin)]]
-[[Category:Mobile|MRO (Plugin)]]
-[[Category:Module|MRO (Plugin)]]
-[[Category:WinX|MRO (Plugin)]]
 === Task ===
@@ Line 98: / Line 98: @@
 |-
 | [[#Interface Task|Interface Task]] || INTERFACE_TASK || Waits for completion information from another software system
 |-
 | [[#Joint Task|Joint Task]] || JOINT_TASK || Documents the state of a joint location
@@ Line 263: / Line 265: @@
 |}
-[[Category:Android|MRO (Plugin)]]
+=== Integer Task ===
-[[Category:Client|MRO (Plugin)]]
-[[Category:Mobile|MRO (Plugin)]]
+Technical object name: '''INTEGER_TASK'''
-[[Category:Module|MRO (Plugin)]]
-[[Category:WinX|MRO (Plugin)]]
+Classification: [[MROCLS_INTEGER_TASK]]
 === Joint Task ===
@@ Line 357: / Line 370: @@
 Classification: [[MROCLS_PICK_LIST_TASK]]
-A Pick List Task allows the user to select one value from an [[UBIK Active Lists|Active List]] configured on the task instance. It behaves similarly to a standard Integer Task with a Selective List, but the selectable values are supplied by the Active List rather than being defined globally.
+A Pick List Task allows the user to select one value from an [[UBIK Active Lists|Active List]] configured on the task instance. It behaves similarly to a standard [[#Integer Task|Integer Task]] with a Selective List, but the selectable values are supplied by the Active List rather than being defined globally.
 Every list item has an Integer value. Selecting an item or selecting ''Not Applicable'' completes the task.
@@ Line 626: / Line 639: @@
 * [[MROCLS_MRO_CHECK_TASK]] (Classification)
 * [[MROCLS_MRO_INSPECTION_TASK]] (Classification)
 * [[MROCLS_SEQUENTIALTASK]] (Classification)
 * [[MROCLS_GROUPEDTASK]] (Classification)
@@ Line 640: / Line 654: @@
 * [[MROCLS_TEXT_TASK]] (Classification)
 [[Category:Android|MRO (Plugin)]]
 [[Category:Client|MRO (Plugin)]]
 [[Category:WinX|MRO (Plugin)]]

@@ Line 9: / Line 9: @@
 }}
-An [[MRO_Objects_(Client)#Interface_Task|Interface Task]] object is an {{UBIK}} content object which is used to document work using a boolean value.
+An [[MRO_(Plugin)#Interface_Task|Interface Task]] object is an {{UBIK}} content object which is used to document work using a boolean value.
 == MetaProperties ==

@@ Line 249: / Line 249: @@
 Technical object name: '''INTERFACE_TASK'''
-Classification: [[MROCLS_MRO_CHECK_TASK]]
+Classification: [[MROCLS_INTERFACE_TASK]]
 An Interface Task cannot be completed directly on the client and typically depends on an external software system to provide its completion value. This is common for long-running asynchronous processes, such as waiting for analysis results from a laboratory

← Older revision		Revision as of 09:55, 19 August 2026
Line 28:		Line 28:

	== Release ==		== Release ==
		+
		+	=== 5.2.? on 2026-08-?? {{key press\|Android: Store}}{{key press\|iOS: Store}} ===
		+	* {{UBIK}} now supports credentials containing accented (and other special) characters, enabling users to authenticate successfully with a wider range of credential formats.
		+

	=== 5.2.3 on 2026-08-04 {{key press\|Android: Store}}{{key press\|iOS: Store}} ===		=== 5.2.3 on 2026-08-04 {{key press\|Android: Store}}{{key press\|iOS: Store}} ===

@@ Line 1: / Line 1: @@
-To run or extend the Comos – {{UBIK}} – Interface => CUI you have to do some settings on {{Comos}} side or at least get some Data for Configuration from {{Comos}}.
+[[File:Wiki_Under_Construction_Start.PNG|1000px]]<noinclude>
 Because {{Comos}} is not a Product from Augmensys, please request all {{Comos}} changes or adaptions at your local Siemens or Siemens Partner.
@@ Line 6: / Line 8: @@
 = Idea and Concept =
 <!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED -->
-The Interfacing of Data is depending on 3 Parts
+The interfacing of data depends on 3 Parts
 * the possible representation of data from {{Comos}}
 * the transfer media, like *.xml file or REST API Interface
-* the processing of the given Information in {{UBIK}}
+* the processing of the given information in {{UBIK}}
-To hand over the primary needed Information from {{Comos}} to {{UBIK}} there are only *.xml Files to use, cause the {{Comos}} side is writing a the Data to a fixed *.xml scheme witch {{UBIK}} is able to read in.
+To hand over the primary needed information from {{Comos}} to {{UBIK}} there are only *.xml files to use, cause the {{Comos}} side is writing a the data to a fixed *.xml scheme witch {{UBIK}} is able to read in.
 This is called Metadata transfer, and hands over data about CDevices, Attributes, StandardTables, PhysicalUnits, and DocumentTypes form Comos to a .xml file.
-When {{UBIK}} Smart Studio is Importing this, it will generate ComosMetaProxy's with Traget MetaClasse's, ComosMetaProxyProperty's with Target MetaProperty's, Selective Lists and Items, SI Units and Unit Items, and some ComosDocumentTypeProxy's
+When {{UBIK}} SmartStudio is importing this, it will generate ComosMetaProxy's with Traget MetaClasse's, ComosMetaProxyProperty's with Target MetaProperty's, SelectiveLists and SelectiveItems, SIUnits and UnitItems, and some ComosDocumentTypeProxy's.
-For detailed Information's about the {{UBIK}} Classes please see
+For detailed information's about the {{UBIK}} Metaclasses please see
 * [[MetaProxy]]
@@ Line 26: / Line 28: @@
 <!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED -->
-For Connection between Comos® and UBIK® via REST API please make sure that Comos-WEB is installed and the License called “COMOS_Mobile_Worker_Server” is available on Comos®.
+For connection between Comos® and UBIK® via REST API please make sure that Comos-WEB is installed and the License called “COMOS_Mobile_Worker_Server” is available on Comos®.
-For Interfacing we need The ComosEvents, ComosGatewayServices and the ComosWebStartPage.
+Comos-WEB will need The ComosEvents, ComosGatewayServices and the ComosWebStartPage.
 [[File:Screenshot 2026-08-13 091304.png]]
-In the Comos® Project Settings in the Section: "Mobile Solutions" you have to care about that URL to you ComosWebStartPage (including port) is set and also the Comos Web database key is set.
+In the Comos® project settings in the section: "Mobile Solutions" you have to care about that URL to you ComosWebStartPage (including port) is set and also the Comos-Web database key is set.
 [[File:Screenshot 2026-08-13 093803.png]]
@@ Line 38: / Line 40: @@
 NOTE: on One Domain the database key has to be Unique!
-Also in the Project Settings in the Section: "COMOS Mobile Worker Interface" You will find the setting and the Values for the Active Comos Project and if the Workinglayer Key is empty the Released Area is Connected if not one Workinglayer per Project can be Connected to UBIK®.
+Also in the project settings in the section: "COMOS Mobile Worker Interface" you will find the setting and the values for the active "Comos Project" and if the "Workinglayer" key is empty the released area is connected if not one Workinglayer per project can be connected to UBIK®.
 [[File:Screenshot 2026-08-13 094922.png|1000px]]
@@ Line 52: / Line 54: @@
 <!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED -->
-For more detailed Information please check you Comos® Documentation for "Guide COMOS Mobile Worker"
+For more detailed information please check you Comos® documentation for "Guide COMOS Mobile Worker"
-Or ask Siemens: [https://www.siemens.com/en-us/products/comos/mobile-worker/ comos-mobile-worker]
+or ask Siemens: [https://www.siemens.com/en-us/products/comos/mobile-worker/ comos-mobile-worker]

@@ Line 251: / Line 251: @@
 Classification: [[MROCLS_MRO_CHECK_TASK]]
-An Interface Task waits for another software system to provide its completion value. The task is complete when its Boolean '''VALUE''' becomes true. If the client is offline, the task waits until connectivity and synchronization are available again.
+An Interface Task cannot be completed directly on the client and typically depends on an external software system to provide its completion value. This is common for long-running asynchronous processes, such as waiting for analysis results from a laboratory
 '''Properties'''
@@ Line 261: / Line 262: @@
 | VALUE || {{Boolean}} || Task completion supplied by the external software system
 |}
 === Joint Task ===

@@ Line 38: / Line 38: @@
 === Work Package ===
-A [[MROCLS_MRO_WORKPACKAGE|Work Package]] collects and summarizes Task Owners, other Work Packages, or Tasks. A Work Package can be confirmed when all associated Tasks have reached the required progress and all subordinate Work Packages have been confirmed.
+A [[MROCLS_MRO_WORKPACKAGE|Work Package]] collects and summarizes other Work Packages or Tasks. A Work Package can be confirmed when all associated Tasks have reached the required progress and all subordinate Work Packages have been confirmed.
 For Work Package presentation and confirmation in the clients, see [[MRO Objects (Client)#Work Package|Work Package]].
 === Task ===

@@ Line 428: / Line 428: @@
 |}
-[[Category:Module|MRO (Plugin)]]
 === Supervisor Check Task {{Version/XamarinSince|4.8}} ===
@@ Line 628: / Line 628: @@
 [[Category:Module|MRO (Plugin)]]

@@ Line 20: / Line 20: @@
 === [[:Category:Xamarin|All pages in this category]] ===
-[[Category:Client|UBIK Client Getting Started]]
-[[Category:Mobile|UBIK Client Getting Started]]
 = UBIK.Hololens =
@@ Line 29: / Line 29: @@
 = UBIK.Android =
 === [[UBIK_Client_Basics|Basics about UBIK.Android]] ===
 === [[:Category:Android|All pages in this category]] ===

@@ Line 32: / Line 32: @@
 * fullPdfFileName: The full path to where a PDF version of the report should be created at. This parameter is optional and can be null.
 The resulting HTML code is returned by the method.
 === Template ===
 [https://github.com/scriban/scriban Scriban] is a scripting engine that can be used to parse text templates. In our case, this means we can create an HTML file and put placeholders into parts of the file where we want report data to show up. We also can use the scripting features to create many rows of a table in a loop, for example. In the Scriban code, the default object is called "report_object". If this report_object has properties, you can access them by writing report_object.property_name (fill in the actual name starting with a lower case and with underscores separating the words). For more detailed information about Scriban, please refer to the "see also" section.

@@ Line 80: / Line 80: @@
 For the common Task model and value-validation requirement, see [[MRO (Plugin)#Task|Task]].
-{{Hint|For the complete list of MRO task types, their properties, and their task-specific client behaviour, see [[MRO (Plugin)#MRO Task Types|MRO Task Types]].}}
+{{Hint|For the complete list of MRO task types, their properties, and their task-specific client behaviour, see [[MRO (Plugin)#MRO Task Types|MRO Task Types]]. For the available Procedure variants and their workflow execution, see [[MRO (Plugin)#Procedure Task Variants and Workflow Execution|Procedure Task Variants and Workflow Execution]].}}
 ==== Sequential Task ====
@@ Line 117: / Line 117: @@
 For example, Tasks A1, A2, and A3 can form a group in which only one Task has to be finished. If all three are predecessors of Task B, finishing one of them causes the group threshold to be reached. All three predecessors become no longer necessary and locked, and Task B becomes unlocked.
 === MRO Objects with Project Information (WinX only) {{Version/WinXSince|2.5.4}} ===
@@ Line 141: / Line 147: @@
 * [[MROCLS_SEQUENTIALTASK]]
 * [[MROCLS_GROUPEDTASK]]
 * [[MROCLS_MRO_TASK]]
 * [[MROCLS_MRO_TASKOWNER]]

@@ Line 14: / Line 14: @@
 | '''MRO Objects (Client)''' || Common client presentation, status indicators, locking, and behaviour shared by multiple MRO objects
 |}
 == Basic User Interface ==
@@ Line 41: / Line 39: @@
 Work progress is calculated from the object's current progress and the progress accumulated from subsequent objects in the underlying data branch. The indicator shows the amount of work completed in that branch.
-{{Version/WinXSince|5.0}} {{Version/MobileSince|5.0}} By default, progress is displayed with no more than one decimal place. For example, 99.75% is displayed as 99.8%. The format string used for this is ''{0:0.#}%''.
+{{Version/WinXSince|5.0}} {{Version/MobileSince|5.0}} By default, progress is displayed with no more than one decimal place. For example, 99.75% is displayed as 99.8%. The format string used for this is <code>{0:0.#}%</code>.
 For other numeric formats, see [https://learn.microsoft.com/en-us/dotnet/standard/base-types/custom-numeric-format-strings custom numeric format strings]. The template used to customize the presentation is '''UBIKMROProgressBadge''' in '''UBIKThemes'''.
 {{Clear}}
 == MRO Objects ==