https://wiki.augmensys.com/api.php?action=feedcontributions&feedformat=atom&user=LGEUBIK Wiki / Augmensys - User contributions [en]2026-04-24T19:57:35ZUser contributionsMediaWiki 1.24.2https://wiki.augmensys.com/index.php?title=Version_5.1_(WinX)&diff=29717Version 5.1 (WinX)2026-04-21T15:49:07Z<p>LGE: </p>
<hr />
<div>{{Attention|This version requires [https://en.wikipedia.org/wiki/Windows_10_version_history#Version_1809_(October_2018_Update) Windows 10 build 17763] or higher}}<br />
<br />
== Availability ==<br />
{{key press|Store}}: Publicly available in Microsoft Store.<br />
<br />
{{key press|Store Beta}} / {{key press|Store Preview}}: Publicly available in Microsoft Store as beta or preview versions to those whose account email is participating in our beta or preview test. To join, please send an email to testing@augmensys.com and provide an email address to add to the list as well as the information which test you want to join. Alternatively you can contact the Augmensys staff and submit your chosen email address.<br />
<br />
Example: Please add my email account example@example.com to the '''Beta''' test group for the '''WinX''' client.<br />
<br />
<br/><br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
=== 5.1.?? on 2026-??-?? ===<br />
* Introduced a new [[MRO_Objects_(Client)#Picture_Task|picture task]] type which can only be finished when there's at least one valid child document.<br />
* Replaced app closing after repeated failed login attempts with a client-side temporary login block, including user feedback that indicates when login becomes available again.<br />
* Added French localization to the app.<br />
* Provided a visual difference between suggested and actual values in DateTime and Geo property direct edit fields via a [[XAML#Custom_VisualState_Trigger|Custom VisualState Trigger]].<br />
* Fixed an issue where the [[Object_hierarchy_in_XAML:_NextLevel,_ParentLevel,_LinkedLevel#LoadNextLevelCommand|LoadNextLevelCommand]] did not work under specific conditions (invoked in offline and then in online mode).<br />
* Fixed an issue where [[SYSCLS_CHILDINFOOWNER|child count]] indicators did not update when you delete its child objects which only exist locally.<br />
* Fixed an issue where line breaks (in strings property values) from Windows are not recognized as such on other systems.<br />
<br />
<br />
=== 5.1.9 on 2026-04-22 ===<br />
* Fixed an issue that prevented any documents from being uploaded when connecting to 5.1 webservices.<br />
<br />
<br />
=== 5.1.6 on 2026-02-10 ===<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where certain documents couldn't be loaded anymore.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed an issue where the UI did not update properly when committing a direct edit input task.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Added a [[XAML#UBIKWebView|UBIKWebView]] control that includes a fix in the WebView2 where some links could not be opened.<br />
* Fixed issue that caused input fields to be focused but not editable.<br />
* Fixed an issue where document creation might not be properly enabled in certain customizing scenarios. For example, a media creation button might be disabled until a page refresh.<br />
* Fixed an issue where batch creating documents (by multi selecting files to attach) can be interrupted if you leave the page.<br />
<br />
<br />
<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Free Text Annotations that where created in former sessions cannot be selected and therefore cannot be edited any more.<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* Known issues regarding the [[Documents_(Client)#Remember_Document_Settings|Remember Document Settings]] feature:<br />
** Saving the Zoom value via touch gestures is not supported.<br />
** Due to a third-party framework issue it can't be guaranteed that saving the Zoom level is always working properly. We reported this issue and will update our solution as soon as it is resolved on their side.<br />
<br/><br />
<br />
= ⚠️ XAML Notes =<br />
<br />
<br />
<br />
<headertabs /><br />
<br />
<br />
{{Category/Version2|{{PAGENAME}}}}<br />
<br />
[[Category:Client|Version 5.1 (WinX)]]<br />
[[Category:Version 5.1|Version 5.1 (WinX)]]<br />
[[Category:WinX|Version 5.1 (WinX)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=XAML_Tips&diff=29668XAML Tips2026-04-16T14:18:20Z<p>LGE: </p>
<hr />
<div>== Attachable behaviors ==<br />
It's quite often that you need to attach behaviors to certain XAML elements. For example, on a Grid, you want to attach a behavior which executes a command upon a Tapped event, or you want to execute a command when a certain property on a UBIK object changes.<br />
<br />
Notice that in the following examples, "Interactivity" and "Core" are both namespaces and you have to make sure that they are defined at the root of your XAMLs:<br />
<br />
<source lang = "xml"><br />
<DataTemplate<br />
...<br />
xmlns:Core="using:Microsoft.Xaml.Interactions.Core"<br />
xmlns:Interactivity="using:Microsoft.Xaml.Interactivity"><br />
...<br />
</DataTemplate><br />
</source><br />
<br><br />
<br />
=== Event Triggered ===<br />
With an EventTriggerBehavior, you can react on changes/events of UI Elements:<br />
<br />
<source lang = "xml"><br />
<Grid><br />
<Interactivity:Interaction.Behaviors><br />
<Core:EventTriggerBehavior EventName="Tapped"><br />
<Core:InvokeCommandAction Command="{Binding NavigateToChildrenCommand}" /><br />
</Core:EventTriggerBehavior><br />
</Interactivity:Interaction.Behaviors><br />
</Grid><br />
</source><br />
<br><br />
<br />
=== Data Triggered ===<br />
If you want to react on changes of the underlying data (ViewModel), you can use DataTriggerBehavior instead. The following example, when used in the ''UBIKSplashArea'' template, automatically navigates to the root objects once the login process is finished and the user was successfully authenticated:<br />
<br />
<source lang = "xml"><br />
<Grid><br />
<Interactivity:Interaction.Behaviors><br />
<Core:DataTriggerBehavior Binding="{Binding IsLoggedIn}" Value="True"><br />
<Core:InvokeCommandAction Command="{Binding NavigateToRootPageCommand}" /><br />
</Core:DataTriggerBehavior><br />
</Interactivity:Interaction.Behaviors><br />
</Grid><br />
</source><br />
<br><br />
<br><br />
<br />
== Content creation ==<br />
=== Child item creation ===<br />
{{Version/WinXSince|3.5.5}}<br />
To directly create an object on a child of the current object, you can define a Button as follows. The method "Item.IsTypeCreationAllowed" used in the expression gets the uid of the type that should be created below a child, if a child does not allow the creation of that type underneath it, the child will be hidden in the selection dialog. To actually create the object, the "CreateChildItemCommand" needs to be passed a KeyValueList with two parameters: The Parent-key is the UID or the ContentViewModel of the child underneath the object should be created, the Type-key is the type of object which should be created--this should match the uid passed to the "Item.IsTypeCreationAllowed" method.<br />
<br />
<source lang = "xml"><br />
xmlns:uc="using:UBIK.WinX.Controls"<br />
xmlns:cv="using:UBIK.WinX.UI.CollectionView"<br />
</source><br />
<br />
<source lang = "xml"><br />
<x:String x:Key="PlantMap">Item.IsTypeCreationAllowed(&quot;21fc990a-d064-4bee-8d48-3293351f827a&quot;)</x:String><br />
<cv:ListCollectionView x:Key="PlantMapView" Expression="{StaticResource PlantMap}" ItemsSource="{Binding Children.Items}" /><br />
<br />
<AppBarButton><br />
<AppBarButton.Flyout><br />
<Flyout Placement="Full"><br />
<ListView ItemsSource="{Binding Source={StaticResource PlantMapView}}"><br />
<ListView.ItemTemplate><br />
<DataTemplate><br />
<Button Content="{Binding Header}" Command="{Binding CreateChildItemCommand}" x:Name="CreateButton" Tag="{Binding}"><br />
<Button.CommandParameter><br />
<uc:KeyValueList><br />
<uc:KeyValueParameter Key="Parent" Value="6D733909-1742-4110-8619-237849BFE453"/><br />
<uc:KeyValueParameter Key="Type" Value="21fc990a-d064-4bee-8d48-3293351f827a"/><br />
</uc:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</DataTemplate><br />
</ListView.ItemTemplate><br />
</ListView><br />
</Flyout><br />
</AppBarButton.Flyout><br />
</AppBarButton><br />
</source><br />
<br />
<source lang = "xml"><br />
<x:String x:Key="PlantMap">Item.IsTypeCreationAllowed(&quot;21fc990a-d064-4bee-8d48-3293351f827a&quot;)</x:String><br />
<cv:ListCollectionView x:Key="PlantMapView" Expression="{StaticResource PlantMap}" ItemsSource="{Binding Children.Items}" /><br />
<br />
<AppBarButton><br />
<AppBarButton.Flyout><br />
<Flyout Placement="Full"><br />
<ListView ItemsSource="{Binding Source={StaticResource PlantMapView}}"><br />
<ListView.ItemTemplate><br />
<DataTemplate><br />
<Button Content="{Binding Header}" Command="{Binding CreateChildItemCommand}" x:Name="CreateButton" Tag="{Binding}"><br />
<Button.CommandParameter><br />
<uc:KeyValueList><br />
<uc:KeyValueParameter Key="Parent" Value="{Binding Tag, ElementName=CreateButton}"/><br />
<uc:KeyValueParameter Key="Type" Value="21fc990a-d064-4bee-8d48-3293351f827a"/><br />
</uc:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</DataTemplate><br />
</ListView.ItemTemplate><br />
</ListView><br />
</Flyout><br />
</AppBarButton.Flyout><br />
</AppBarButton><br />
</source><br />
<br />
<br/><br />
Additionally, the following optional parameters can be added as well.<br />
* CreateOnly (optional, defaults to false): When set to true, the client will not automatically navigate to the created content, rather automatically save and commit it. If set to true, this overrides the following parameters;<br />
* AutoNavigate (optional, defaults to true): When set to false, the client will not automatically navigate to the created content;<br />
* AutoCommit (optional, defaults to false): When set to true, the change(s) will be saved to the local cache and the database, and then committed to the server.<br />
<br><br />
<br />
=== Creating multiple documents ===<br />
To upload multiple documents at once, the CreateChildItemsCommand can be used. The list of supported command parameters are similar to those of the CreateChildItemCommand (single item). Except that anything other than AutoNavigate=false and AutoCommit=true do not make sense in multi-creation scenario. Therefore, those parameters are fixed and any received from XAML will be ignored.<br />
<br />
<!-- <tabs><br />
<br />
<tab name="UWP">--><br />
<source lang = "xml"><br />
<Button ...<br />
xmlns:uc="using:UBIK.WinX.Controls"<br />
Command="{Binding CreateChildItemsCommand}"<br />
Content="Create multiple documents"><br />
<Button.CommandParameter><br />
<uc:KeyValueList><br />
<uc:KeyValueParameter Key="Type" Value="6170a068-2314-4444-ad62-0da99769a048" /><br />
</uc:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
<!--</tab><br />
<br />
<tab name="Mobile(Xamarin)"><br />
<source lang = "xml"><br />
<Button ...<br />
xmlns:classes="clr-namespace:UBIK.CPL.Classes;assembly=UBIK.CPL"<br />
Command="{Binding CreateChildItemsCommand}"<br />
Content="Create multiple documents"><br />
<Button.CommandParameter><br />
<classes:KeyValueList><br />
<classes:KeyValueParameter Key="Type" Value="6170a068-2314-4444-ad62-0da99769a048" /><br />
</classes:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
</tab><br />
<br />
</tabs>--><br />
<br><br />
<br><br />
<br />
=== Disable FilloutCriteria ===<br />
{{Version/WinXSince|3.5}}<br />
To enable/disable the automatic filtering of a query based on the ParentObject, there is the possibility to specify EnableFillOutCriteria--if it is not set, it defaults to false. Additionaly "SkipDialog" can be set to true, to not display a dialog.<br />
<br />
<source lang="xml"><br />
<Grid x:Name="selectionGrid" Tag="{Binding MetaUID}"><br />
<Interactivity:Interaction.Behaviors><br />
<Core:EventTriggerBehavior EventName="Tapped"><br />
<Core:InvokeCommandAction Command="{Binding ElementName=ChildAreaGrid, Path=DataContext.AddTemplatableDataCommand}" ><br />
<Core:InvokeCommandAction.CommandParameter><br />
<uc:KeyValueList><br />
<uc:KeyValueParameter Key="Uid" Value="{Binding Tag,ElementName=selectionGrid}"/><br />
<uc:KeyValueParameter Key="EnableFillOutCriteria" Value="false"/><br />
<uc:KeyValueParameter Key="SkipDialog" Value="false"/><br />
</uc:KeyValueList><br />
</Core:InvokeCommandAction.CommandParameter><br />
</Core:InvokeCommandAction><br />
</Core:EventTriggerBehavior><br />
</Interactivity:Interaction.Behaviors><br />
</Grid><br />
</source><br />
<br><br />
<br><br />
<br />
== Hotspotting ==<br />
{{Attention|To use a binding in the KeyValueParameter, it has to be applied like in the example provided here: [[KeyValueList]]}}<br />
The hotspotting command is used for hotspotting as well as for annotating, to configure the button for hotspotting, the commandparameter "Mode" should be set to "HotSpotting", for annotating the "Mode" should be "Annotate". The parameter commit is optional, if set to true, the changes get automatically persisted when leaving the editing mode.<br />
<br />
<source lang = "xml"><br />
<AppBarToggleButton<br />
IsChecked="{Binding EditingAnnotation, Mode=TwoWay}"<br />
IsEnabled="{Binding IsAnnotatable}"<br />
Command="{Binding HotSpottingCommand}"><br />
<AppBarToggleButton.CommandParameter><br />
<uc:KeyValueList><br />
<uc:KeyValueParameter Key="Mode" Value="Annotate"/><br />
<uc:KeyValueParameter Key="Commit" Value="true"/><br />
</uc:KeyValueList><br />
</AppBarToggleButton.CommandParameter><br />
</AppBarToggleButton><br />
</source><br />
<br><br />
<br><br />
<br />
== Remember scroll positions of list views ==<br />
<br />
=== Version 3.7 & later {{Version/WinXSince|3.7}} ===<br />
Starting from this version,<br />
* The precision of scroll position remembering is improved(by pixel offsets instead of by items);<br />
* It also works for other scrollable lists (instead of just for content object lists).<br />
<br /><br />
To enable this feature, you should make sure the following.<br />
* The SelectionBoundListView is used instead of the standard ListView. Its {{UBIK}} namespace is <code>UBIK.WinX.Controls</code>;<br />
* The SelectionBoundListView's <code>RememberScrollPosition</code> property is not set to "false"; (It's "true" by default.)<br />
* The SelectionBoundListView's <code>x:Name</code> property value is unique.<br />
<br><br />
<br />
=== Version 3.6 {{Version/WinXSince|3.6}} ===<br />
The UBIK-Client does include a function to remember the position in a list (ListView) when navigating away from it. This function is only available when the list (ListView) has a unique name as a property (x:Name). When browsing back to the previously visited list UBIK scrolls back to the last position. The function does not save scroll positions over different sessions.<br />
Implementing the function to remember the scroll position in a ListView one has to consider that the list elements (Children) could depend on a other UI-element. If the list elements do depend on a other UI-elemente, this element has to be created above the ListView in the XAML.<br />
<br />
<source lang = "xml"><br />
<DataTemplate xmlns:behaviors="using:UBIK.WinX.Behaviors" xmlns:uc="using:UBIK.WinX.Controls"><br />
...<br />
<uc:SelectionBoundListView x:Name="ChildListView"><br />
<Interactivity:Interaction.Behaviors><br />
<behaviors:FirstVisibleItemPersistenceBehavior FirstVisibleItems="{Binding ScrollItems}" /><br />
</Interactivity:Interaction.Behaviors><br />
</uc:SelectionBoundListView><br />
</DataTemplate><br />
</source><br />
<br><br />
<br><br />
<br />
<br />
== MultiBinding {{Version/WinXSince|3.6}} ==<br />
Very often we want to display some UI elements (e.g. a Grid) depending on whether multiple criteria are met. It's much easier to achieve this by using a MultiBindingBehavior like the following.<br />
<source lang = "xml"><br />
<DataTemplate<br />
xmlns:Interactivity="using:Microsoft.Xaml.Interactivity"<br />
xmlns:behaviors="using:UBIK.WinX.Behaviors"><br />
...<br />
<Grid><br />
<Interactivity:Interaction.Behaviors><br />
<behaviors:MultiBindingBehavior Converter="{StaticResource VisLogicAndConverter}" PropertyName="Visibility"><br />
<behaviors:MultiBindingItem Value="{Binding MassEditViewModel, Converter={StaticResource NullToVisConverter}}" /><br />
<behaviors:MultiBindingItem Value="{Binding Documents.Items.Count, Converter={StaticResource ItemCountToVisConverter}}" /><br />
</behaviors:MultiBindingBehavior><br />
</Interactivity:Interaction.Behaviors><br />
</Grid><br />
</DataTemplate><br />
</source><br />
The behavior makes sure the container Grid is set to Visibile only if the mass editing mode is not turned on (MassEditViewModel is null) and the context object has child document(s) (Documents.Items.Count is greater than 0. You can combine any number of binding results (MultiBindingItem) using the VisLogicAndConverter (the name should be self explanatory).<br />
<br><br />
<br><br />
<br />
== Other Commands ==<br />
=== InvokeOnItemsCommand {{Version/WinXSince|3.6}} ===<br />
Available on all ListViewModels, this command allows executing a specified command on a collection of list items. It can be used in combination with features such as [[Mass_Edit_(UBIK_WinX)|mass editing]] and [[XAML_Changes_in_UBIK_WinX_3.5#After_3.5|expression based collection filtering]]. Examples for both combinations are provided below.<br />
<br />
{{Attention|The command specified through the "Command" parameter is executed on list items and, therefore, must be available in the list item contexts (view models). If in doubt, the [[Developer_Mode|developer mode]] can be used to inspect if a command is available in a certain context.}}<br />
<br />
{{Hint|Parameter "Command" and "SelectedItemsOnly" are specific to the InvokeOnItemsCommand. What other parameters to define or whether to define them at all depends on the type of command to be executed on the items.}}<br />
<br><br />
<br />
==== Invoke on selected items ====<br />
{{Attention|To use a binding in the KeyValueParameter, it has to be applied like in the example provided here: [[KeyValueList]]}}<br />
This example demonstrates how you can use the mass editing feature to select certain objects from the child list and then execute the SetPropertyValueCommand for those selected.<br />
* The example code assumes that the child objects have an editable property called "VALUE" and tries to set 50 as their value;<br />
* You should insert the following code snippet into the default UBIKChildArea template;<br />
* If the parameter "SelectedItemsOnly" is missed or set to "False", the command will be executed on all child items;<br />
* To enable selection, click on the "Mass Edit" button below the property list.<br />
<br /><br />
<br />
<tabs><br />
<tab name="UWP"><br />
<source lang = "xml"><br />
<Button<br />
xmlns:example="using:UBIK.WinX.Controls"<br />
Command="{Binding Children.InvokeOnItemsCommand}"<br />
Content="Set to 50%"><br />
<Button.CommandParameter><br />
<example:KeyValueList><br />
<example:KeyValueParameter Key="Command" Value="SetPropertyValueCommand" /><br />
<example:KeyValueParameter Key="SelectedItemsOnly" Value="False" /><br />
<example:KeyValueParameter Key="PropertyName" Value="VALUE" /><br />
<example:KeyValueParameter Key="PropertyValue"><br />
<example:KeyValueParameter.Value><br />
<x:Double>50</x:Double><br />
</example:KeyValueParameter.Value><br />
</example:KeyValueParameter><br />
</example:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
</tab><br />
<br />
<tab name="Mobile(Xamarin)"><br />
<source lang = "xml"><br />
<Button<br />
xmlns:example="clr-namespace:UBIK.CPL.Classes;assembly=UBIK.CPL"<br />
Command="{Binding Children.InvokeOnItemsCommand}"<br />
Text="Set to 50%"><br />
<Button.CommandParameter><br />
<example:KeyValueList><br />
<example:KeyValueParameter Key="Command" Value="SetPropertyValueCommand" /><br />
<example:KeyValueParameter Key="SelectedItemsOnly" Value="False" /><br />
<example:KeyValueParameter Key="PropertyName" Value="VALUE" /><br />
<example:KeyValueParameter Key="PropertyValue"><br />
<example:KeyValueParameter.Value><br />
<x:Double>50</x:Double><br />
</example:KeyValueParameter.Value><br />
</example:KeyValueParameter><br />
</example:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
</tab><br />
</tabs><br />
<br><br />
<br><br />
<br />
==== Invoke on filtered results ====<br />
{{Attention|To use a binding in the KeyValueParameter, it has to be applied like in the example provided here: [[KeyValueList]]}}<br />
<br />
* First, you need to setup a filtered list<br />
**UWP: Setup a ListCollectionView in the Resources section of a UI element (e.g. Grid). This list is only available/visible within that UI element (the Grid in this case).<br />
**Mobile: Setup a String with a filtering expression & a SfDataSourceExt in the ResourceDictionary of the ContentView. For the Expression property of the SfDataSourceExt refer to the created expression String.<br />
<br />
* The ItemsSource uses Children.Items. Use the [[Developer_Mode|developer mode]] if necessary to find out if this is available where you intend to define the list;<br />
* The example expression filters for any items that don't contain the text "EXAMPLE" in their Title texts. You can filter differently by altering the expression.<br />
<br /><br />
<br />
<tabs><br />
<tab name="UWP"><br />
<source lang = "xml"><br />
<Grid xmlns:CV="using:UBIK.WinX.UI.CollectionView"><br />
<Grid.Resources><br />
<CV:ListCollectionView<br />
x:Key="Filtered"<br />
Expression="!Item.Title.Contains(&quot;EXAMPLE&quot;)"<br />
ItemsSource="{Binding Children.Items}" /><br />
</Grid.Resources><br />
...<br />
</Grid><br />
</source><br />
</tab><br />
<br />
<tab name="Mobile(Xamarin)"><br />
<source lang = "xml"><br />
<ContentView<br />
xmlns:controls="clr-namespace:UBIK.CPL.Controls;assembly=UBIK.CPL"<br />
...><br />
<ContentView.Resources><br />
<ResourceDictionary><br />
<x:String x:Key="Expresssion">!Item.Title.Contains(&quot;EXAMLPLE&quot;)</x:String><br />
<controls:SfDataSourceExt x:Key="Filtered" Expression="{StaticResource Expresssion}" ItemsSource="{Binding Children.Items}" /><br />
</ResourceDictionary><br />
</ContentView.Resources><br />
</ContentView><br />
</source><br />
</tab><br />
</tabs><br />
<br />
<br /><br />
With the filtered list configured, you can then insert the following code snippet to execute the SetPropertyValueCommand for the filtered result items.<br />
* The example code assumes that the child objects have an editable property called "VALUE" and tries to set 50 as their value;<br />
* The "Filtered" refers to the ListCollectionView (UWP) or SfDataSourceExt (Mobile) configured above.<br />
<br /><br />
<br />
<tabs><br />
<tab name="UWP"><br />
<source lang = "xml"><br />
<AppBarButton<br />
xmlns:example="using:UBIK.WinX.Controls"<br />
Command="{Binding Source={StaticResource Filtered}, Path=ListViewModel.InvokeOnItemsCommand}"<br />
Icon="AllApps"<br />
Label="Set to 50"<br />
Style="{ThemeResource UBIKActionAppBarButton}"><br />
<AppBarButton.CommandParameter><br />
<example:KeyValueList><br />
<example:KeyValueParameter Key="Command" Value="SetPropertyValueCommand" /><br />
<example:KeyValueParameter Key="PropertyName" Value="VALUE" /><br />
<example:KeyValueParameter Key="PropertyValue" Value="50" /><br />
</example:KeyValueList><br />
</AppBarButton.CommandParameter><br />
</AppBarButton><br />
</source><br />
</tab><br />
<br />
<tab name="Mobile(Xamarin)"><br />
<source lang = "xml"><br />
<Button<br />
xmlns:example="clr-namespace:UBIK.CPL.Classes;assembly=UBIK.CPL"<br />
Command="{Binding Source={StaticResource Filtered}, Path=ListViewModel.InvokeOnItemsCommand}"<br />
Text="Set to 50"><br />
<Button.CommandParameter><br />
<example:KeyValueList><br />
<example:KeyValueParameter Key="Command" Value="SetPropertyValueCommand" /><br />
<example:KeyValueParameter Key="PropertyName" Value="VALUE" /><br />
<example:KeyValueParameter Key="PropertyValue" Value="50" /><br />
</example:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
</tab><br />
</tabs><br />
<br />
{{Attention|The binding <code>ListViewModel.InvokeOnItemsCommand</code> should be updated to <code>BulkOperation.InvokeOnItemsCommand</code> starting from version 4.3.}}<br />
<br><br />
<br />
==== Support for old styled commands ====<br />
Some old commands might not support KeyValueLists as parameters. In that case, just define the parameter value under the "CommandParameter" key, e.g.<br />
<br /><br />
<source lang = "xml"><example:KeyValueParameter Key="CommandParameter" Value="some string value for example" /></source>.<br />
This single value is then passed as the command parameter instead of the entire KeyValueList.<br />
<br><br />
<br><br />
<br />
=== SetPropertyValueCommand {{Version/WinXSince|3.6}} ===<br />
{{Attention|To use a binding in the KeyValueParameter, it has to be applied like in the example provided here: [[KeyValueList]]}}<br />
<br />
This command existed before but was implemented differently. In the newer version(s), it is improved to provide customizers more control over the things that happen during/after the property value changes.<br />
The available command parameters are:<br />
* PropertyName: the name of the property to set a new value to;<br />
* PropertyValue: the value to be set to the above mentioned property;<br />
* OnlyForUnvalidated (optional, defaults to false): When set to true, the value will only be set if the property is not yet validated;<br />
* AutoSave (optional, defaults to false): When set to true, the change(s) will be saved to the local cache and database;<br />
* AutoCommit (optional, defaults to false): When set to true, the change(s) will be committed to the server.<br />
<br />
{{Hint|There's no way to commit changes without saving them locally first. Therefore, the "AutoSave" parameter will be ignored when "AutoCommit" is set to true.}}<br />
<br />
<br />
Here's an example of the command usage. It tries to set the property called "VALUE" to a double value 50 regardless of its current state and then automatically save and commit the change.<br />
<br /><br />
<source lang = "xml"><br />
xmlns:controls="using:UBIK.WinX.Controls"<br />
...<br />
<Button<br />
Command="{Binding SetPropertyValueCommand}"<br />
Style="{StaticResource UBIKButtonStyle}"<br />
Content="Set Property"><br />
<Button.CommandParameter><br />
<controls:KeyValueList><br />
<controls:KeyValueParameter Key="PropertyName" Value="MP_PROPERTY" /><br />
<controls:KeyValueParameter Key="PropertyValue" Value="My Value" /><br />
<controls:KeyValueParameter Key="OnlyForUnvalidated" Value="false" /><br />
<controls:KeyValueParameter Key="AutoSave" Value="true" /><br />
<controls:KeyValueParameter Key="AutoCommit" Value="true" /><br />
</controls:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
<br />
{{Hint|For simple types, you can try writing them in the text format like <nowiki><controls:KeyValueParameter Key="PropertyValue" Value="50"/></nowiki> and {{UBIK}} will try to find the right type. For advanced property types, it is advised to provide typed values like <nowiki><x:Boolean>true</x:Boolean></nowiki>.}}<br />
<br><br />
<br />
==== Set a Binding as PropertyValue ====<br />
There is a known issue in XAML where Behaviors and KeyValueLists do not inherit the binding context of the control they are attached to. Simply put, trying to use a binding directly in the PropertyValue part of the command; '''<nowiki><controls:KeyValueParameter Key="PropertyValue" Value="{Binding BindingPath}" /></nowiki>''', would lead to the client setting the value of MP_PROPERTY to null.<br />
<br />
Luckily, there is a simple way to link this Binding to a context. Using the above example as a foundation, adapt the button as shown below:<br />
<tabs><br />
<tab name="UWP"><br />
<source lang = "xml"><br />
<Button<br />
x:Name="SetDynamicPropertyButton"<br />
Tag="{Binding}"<br />
... ><br />
<Button.CommandParameter><br />
<controls:KeyValueList><br />
...<br />
<controls:KeyValueParameter Key="PropertyValue" Value="{Binding Tag.BindingPath, ElementName=SetDynamicPropertyButton}" /><br />
...<br />
</controls:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
</tab><br />
<br />
<tab name="Mobile"><br />
<source lang = "xml"><br />
<Button<br />
x:Name="SetDynamicPropertyButton"<br />
... ><br />
<Button.CommandParameter><br />
<classes:KeyValueList><br />
...<br />
<classes:KeyValueParameter Key="PropertyValue" Value="{Binding BindingContext.BindingPath, Source={x:Reference SetDynamicPropertyButton}}" /><br />
...<br />
</classes:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
</tab><br />
<br />
{{Hint|Replace ''BindingPath'' in the above snippets with your required binding path, for example, ''AppStatus.CurrentUser.RawDetails[...]''. }}<br />
</tabs><br />
<br />
The above code uses the x:Name of the button to specify the viewmodel from which we wish to begin our binding path.<br><br />
You do not need to follow this exact syntax, all that is necessary is to provide a connection to the BindingContext of an observable control.<br />
<br><br />
<br><br />
<br />
<br />
<br />
<br />
<br />
<br />
==== Set Current DateTime ====<br />
The current DateTime stamp can be retrieved from '''AppStatus.LiveDateTime'''.<br><br />
Since the known issue described in the section above prevents direct binding to this, below are examples for how to implement it.<br />
<br />
<tabs><br />
<tab name="UWP"><br />
<source lang = "xml"><br />
xmlns:example="using:UBIK.WinX.Controls"<br />
...<br />
<Button<br />
x:Name="SetCurrentDateTimeButton"<br />
Tag="{Binding}"<br />
Command="{Binding SetPropertyValueCommand}"<br />
Style="{StaticResource UBIKButtonStyle}"<br />
Content="Set Property"><br />
<Button.CommandParameter><br />
<controls:KeyValueList><br />
<controls:KeyValueParameter Key="PropertyName" Value="MP_PROPERTY" /><br />
<controls:KeyValueParameter Key="PropertyValue" Value="{Binding Tag.AppStatus.LiveDateTime, ElementName=SetCurrentDateTimeButton}" /><br />
<controls:KeyValueParameter Key="OnlyForUnvalidated" Value="false" /><br />
<controls:KeyValueParameter Key="AutoSave" Value="true" /><br />
<controls:KeyValueParameter Key="AutoCommit" Value="true" /><br />
</controls:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
{{Hint|The DateTime can be set to the desired format by adding a StringFormatConverter to the LiveDateTime binding:<br><nowiki>"{Binding Tag.AppStatus.LiveDateTime, ElementName=SetCurrentDateTimeButton, </nowiki>'''<nowiki>Converter={StaticResource StringFormatConverter}, ConverterParameter={0:yyyy-MM-dd HH:mm}</nowiki>'''<nowiki>}" </nowiki>.}}<br />
</tab><br />
<br />
<tab name="Mobile"><br />
<source lang="xml"><br />
<Button<br />
x:Name="SetCurrentDateTimeButton"<br />
Command="{Binding SetPropertyValueCommand}"<br />
Text="Set Property"><br />
<Button.CommandParameter><br />
<classes:KeyValueList><br />
<classes:KeyValueParameter Key="PropertyName" Value="MP_PROPERTY" /><br />
<classes:KeyValueParameter Key="PropertyValue" Value="{Binding BindingContext.AppStatus.LiveDateTime, Source={x:Reference SetCurrentDateTimeButton}}" /><br />
<classes:KeyValueParameter Key="OnlyForUnvalidated" Value="false" /><br />
<classes:KeyValueParameter Key="AutoSave" Value="true" /><br />
<classes:KeyValueParameter Key="AutoCommit" Value="true" /><br />
</classes:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
</tab><br />
</tabs><br />
<br />
<br><br />
<br />
<br />
<br />
<br />
<br />
<br />
=== SaveAndCommitCommand ===<br />
With the ''SaveAndCommitCommand'' it is possible to save and commit unsaved changes on a ContentViewModel.<br />
<br />
* ForceCommit CommandParameter (optional, defaults to false): Normally when the App is in Online mode, changes are automatically committed when saved. This is not the case when the App is in Manual mode. Setting the ''ForceCommit'' parameter to true makes it possible to commit the changes when saved in Manual mode.<br />
* {{Version/WinXSince|4.7}} {{Version/XamarinSince|4.7}} PropertyNameToSave CommandParameter (optional, defaults to null): Delivers the Property Name as String of a specific Property that should be saved. E.g. when called via PropertyViewModel.ResetCommand or PropertyViewModel.DeleteCommand, the ''PropertyNameToSave'' parameter is used to only apply the SaveAndCommitCommand on the related PropertyViewModel called from, and not on other unsaved changes on this ContentViewModel.<br />
<br/><br />
<tabs><br />
<tab name="UWP"><br />
<source lang = "xml"><br />
<Button<br />
xmlns:example="using:UBIK.WinX.Controls"<br />
Command="{Binding SaveAndCommitCommand}"><br />
<Button.CommandParameter><br />
<example:KeyValueList><br />
<example:KeyValueParameter Key="ForceCommit" Value="True" /><br />
</example:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
</tab><br />
<tab name="Mobile(Xamarin)"><br />
<source lang = "xml"><br />
<Button<br />
xmlns:example="using:clr-namespace:UBIK.CPL.Classes;assembly=UBIK.CPL"<br />
Command="{Binding SaveAndCommitCommand}"><br />
<Button.CommandParameter><br />
<example:KeyValueList><br />
<example:KeyValueParameter Key="ForceCommit" Value="True" /><br />
</example:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
</tab><br />
</tabs><br />
<br><br />
<br />
=== DisplayViewCommand ===<br />
This command can be used to [[Custom_View_(Client)|display cutom views]].<br />
<br><br />
<br />
=== TeachInCommand ===<br />
With the '''TeachInCommand''' you're allowed to set your device's current location ("teach-in", "TeachIn") as the value of the context object's [[SYSCLS_GEO|geo property]].<br />
This command is available in both '''ContentViewModel''' and '''PropertyViewModel'''.<br />
* ContentViewModel.TeachInCommand: If possible, sets the current location of the device as the value of the context object's [[SYSCLS_GEO|geo property]]. Saves and commits the change;<br />
* PropertyViewModel.TeachInCommand: If possible, sets the current location of the device as the value of the current property if it's a geo property (not necessarily the [[SYSCLS_GEO|geo property]]). Addtionally supports a boolean command parameter:<br />
** False (default): The change is not automatically saved. <br />
** True: The change is saved.<br />
<br/> {{hint| Make sure you use the correct binding path for your command depending on your current context view model. E.g., if the context view model is already the ContentViewModel then your binding path should simply be TeachInCommand. You can use the [[Developer_Mode|developer mode]] to find out the current view model in a view.}}<br />
<br><br />
<br />
===UpdateArbitraryObjectCommand {{Version/WinXSince|4.7}}===<br />
The "UpdateArbitraryObjectCommand" is responsible for updating an arbitrary object based on a set of provided parameters. The command is accessible in the AppStatusViewModel (as '''ViewModel.AppStatus'''). <br />
<br /><br />
The available command parameters are:<br />
* Uid (Mandatory): UID of the object to be updated;<br />
* UpdateChildDepth (Optional): Child depth/level to update (defaults to 1);<br />
* UpdateParentDepth (Optional): Parent depth/level to update (defaults to 0);<br />
* UpdateIgnoreExpiry (Optional): Ignore update expiry (defaults to false); <br />
<br />
{{Hint|Note that if you set the UpdateChildDepth property to "-1" you are also able to update a whole branch with this command.}}<br />
<br />
Here is an example of the command usage: <br />
<br /><br />
<tabs><br />
<tab name="UWP"><br />
<source lang = "xml"><br />
<Button ...<br />
xmlns:uc="using:UBIK.WinX.Controls"<br />
Command="{Binding UpdateArbitraryObjectCommand}"<br />
Content="Update Arbitrary Object"><br />
<Button.CommandParameter><br />
<uc:KeyValueList><br />
<uc:KeyValueParameter Key="Uid" Value="...valid UID..." /><br />
<uc:KeyValueParameter Key="UpdateChildDepth" Value="2" /><br />
<uc:KeyValueParameter Key="UpdateParentDepth" Value="0" /><br />
<uc:KeyValueParameter Key="UpdateIgnoreExpiry" Value="true" /><br />
</uc:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
</tab><br />
<br />
<tab name="Mobile(Xamarin)"><br />
<source lang = "xml"><br />
<Button ...<br />
xmlns:uc="using:clr-namespace:UBIK.CPL.Classes;assembly=UBIK.CPL"<br />
Command="{Binding UpdateArbitraryObjectCommand}"<br />
Content="Update Arbitrary Object"><br />
<Button.CommandParameter><br />
<uc:KeyValueList><br />
<uc:KeyValueParameter Key="Uid" Value="...valid UID..." /><br />
<uc:KeyValueParameter Key="UpdateChildDepth" Value="2" /><br />
<uc:KeyValueParameter Key="UpdateParentDepth" Value="0" /><br />
<uc:KeyValueParameter Key="UpdateIgnoreExpiry" Value="true" /><br />
</uc:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
</tab><br />
</tabs><br />
<br><br />
<br />
=== Access to an arbitrary object {{Version/WinXSince|4.6}} {{Version/XamarinSince|4.6}} ===<br />
With the ObjectByUID feature it is possible to access any local arbitrary object by its UID and, for example, display a value of it.<br />
It can be accessed from ContentViewModel, AuthenticationViewModel, and RootPageViewModel levels.<br />
<br />
To display a string of e.g. a property of an arbitrary object from ContentViewModel, AuthenticationViewModel & RootPageViewModel, the following syntax can be used in related XAMLs:<br />
<tabs><br />
<tab name="UWP"><br />
<source lang = "xml"><br />
<TextBlock Text="{Binding ObjectByUID[paste-your-uid].Properties.VisibleItems[add-your-property-name].DisplayValue}" /><br />
</source><br />
</tab><br />
<br />
<tab name="Mobile(Xamarin)"><br />
<source lang = "xml"><br />
<Label Text="{Binding ObjectByUID[paste-your-uid].Properties.VisibleItems[add-your-property-name].DisplayValue}" /><br />
</source><br />
</tab><br />
</tabs><br />
<br />
For Property Dialogs the CallingViewModel prefix is needed to access an arbitrary object:<br />
<tabs><br />
<tab name="UWP"><br />
<source lang = "xml"><br />
<TextBlock Text="{Binding CallingViewModel.ObjectByUID[paste-your-uid].Properties.VisibleItems[add-your-property-name].DisplayValue}" /><br />
</source><br />
</tab><br />
<br />
<tab name="Mobile(Xamarin)"><br />
<source lang = "xml"><br />
<Label Text="{Binding CallingViewModel.ObjectByUID[paste-your-uid].Properties.VisibleItems[add-your-property-name].DisplayValue}" /><br />
</source><br />
</tab><br />
</tabs><br />
<br><br />
<br><br />
<br />
==== Localizing UI Texts ====<br />
The most efficient practice is to use pre-localized texts from the standard client, however, this is not always possible, especially in custom UIs. The ObjectByUID indexer was therefore initially developed as a technique to allow localization of custom UI label texts. <br />
<br />
The concept is to create an infrastructure object that carries metaproperties for localized texts, then bind to this infrastructure object using ObjectByUID, and bind to a specific metaproperty to receive it's localized Description text as follows:<br />
<source lang = "xml"><br />
"{Binding ObjectByUID[paste-your-uid].Properties.VisibleItems[add-your-property-name].Description}"<br />
</source><br />
<br />
From here there are two approaches; the database-leaning one is to add one metaproperty per UI label, and simply bind to the Description of it. However, this shifts maintenance effort to the UBIK Studio after the initial adding of the label in XAML. Another approach would be to use the metaproperty to provide a "tag" that the xaml customizer can then use to differentiate between hardcoded labels.<br />
<br />
A third approach would be to create one infrastructure object per label, however, this can lead to many objects being loaded upon startup.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Approach !! Implementation !! Maintenance Effort !! Recommendation<br />
|-<br />
| One metaproperty per UI Label || Bind the label text to the metaproperty Description || Database / UBIK Studio || Recommended for UWP, customizings with fewer UI texts, finalized customizings.<br />
|-<br />
| One metaproperty delivering a localization "tag" (such as: "EN" / "DE") || Use something like DataTrigger (Mobile) to hardcode a different localized text per tag (such as: "eg." / "zb.") || XAML || Recommended for Mobile, highly customized UIs with many texts, customizings that tend to change often.<br />
|}<br />
<br><br />
<br><br />
<br />
<br />
<br />
<br />
<br />
<br />
== Showing Images and Icons ==<br />
In UBIK, there are two types of image;<br />
* The thumbnail image assigned to a UBIK object, delivered using the <nowiki>{Binding Icon...}</nowiki> binding, in combination with a ByteToImageConverter. Examples can commonly be found on UBIKChildItem templates.<br />
* Custom image shown with a specific purpose, such as a company logo or icon on a button/UI element.<br />
<br><br />
<br />
==== Paths as string resources ====<br />
When using custom images in your UI, it is a good idea not to hardcode path data into your Image control but instead to create a string resource in UBIKThemes that holds the image path, and use this string resource in your Image control. The benefit of the indirect connection between image file and usage is that the "file is in use" issue (sometimes experienced when either manual, or auto-deployment of xamls, tries to change image files when UBIK is running) is avoided this way.<br />
<br />
Sample:<br />
<tabs><br />
<tab name="UWP"><br />
'''UBIKThemes:'''<br />
<source lang = "xml"><x:String x:Key="MainLogo">ms-appdata:///local/xaml/Images/MainLogo.png</x:String><br />
</source><br />
<br><br />
'''Usage:'''<br />
<source lang = "xml"><br />
<Image<br />
x:Name="LogoImage"<br />
Height="32"<br />
Stretch="Uniform"<br />
Source="{Binding Source={StaticResource MainLogo}, Converter={StaticResource PathToImageConverter}}" /><br />
</source><br />
</tab><br />
<br />
<tab name="Mobile(Xamarin)"> <br />
'''UBIKThemes:'''<br />
<source lang = "xml"><br />
<x:String x:Key="Logo_Image">IMG_Logo.png</x:String><br />
</source><br />
<br><br />
'''Usage:'''<br />
<source lang = "xml"><br />
xmlns:customimage="clr-namespace:UBIK.CPL.Controls;assembly=UBIK.CPL"<br />
...<br />
<customimage:FileImage<br />
HeightRequest="140"<br />
Aspect="AspectFit"<br />
FileName="{StaticResource BorealisLogo_Image}" <br />
FolderName="xaml" /><br />
</source><br />
</tab><br />
</tabs><br />
<br><br />
<br />
=== Icons ===<br />
UBIK comes equipped with a collection of icons that can be easily used in your customizing. [[Icon_Font|Here is an indepth explanation on usage]].<br />
<br />
In the case that you require an icon that is not included in our icon font file, there is the possibility to use SVG path data to render your required icon in the UI.<br />
<br><br />
<br />
==== Custom Icons ====<br />
Here referring to icons which are not included as standard icons un UBIK.<br />
<br />
'''Path data''' is a collection of points, which combined together form a vector image. Vector images, compared to raster images like a PNG or JPG, are scalable, because they are always rendered from path data, and not from a bitmap, which has to be stretched or squished to fit your defined size. Described below two approaches. <br />
<br />
===== Using (SVG) Files =====<br />
<br><br />
The '''UWP approach''' involves adding an SVG icon file to your xaml project and render it using an Image control. <br />
<source lang = "xml"> <br />
<Image Width="14" Height="14" Margin="0,0,0,1"><br />
<Image.Source ><br />
<SvgImageSource UriSource="{StaticResource PP_Issued}" /><br />
</Image.Source><br />
</Image><br />
</source><br />
<br><br><br />
<br />
===== Using Path Data =====<br />
<br><br />
The '''Mobile(Xamarin) approach''' shows how to use svg data directly using a Path control.<br />
<br />
The first step is to generate path data for your icon. The easiest way is to download the [https://apps.microsoft.com/detail/9wzdncrdxf41?hl=en-US&gl=US| Character Map] tool from Microsoft. This can be used to browse all installed icon files for your icon of choice. Once selected, use Tools > Xaml / Xamarin Forms to show various useful aspects of the icon. With an icon selected, the Path Geometry section can be used to generate a path data that can be pasted directly in your xaml as follows:<br />
<br />
<source lang = "xml"><br />
<Path Fill="{StaticResource UBIKAccentColor}" Data="F1 M 8.75 1.25 L 18.75 1.25 L 18.75 18.75 L 1.25 18.75 L 1.25 8.75 L 5 8.75 L 5 6.25 L 1.25 6.25 L 1.25 1.25 L 6.25 1.25 L 6.25 5 L 8.75 5 Z M 10 2.5 L 10 5 L 12.5 5 L 12.5 2.5 Z M 2.5 5 L 5 5 L 5 2.5 L 2.5 2.5 Z M 6.25 6.25 L 6.25 8.75 L 8.75 8.75 L 8.75 6.25 Z M 2.5 10 L 2.5 12.5 L 5 12.5 L 5 10 Z M 17.5 17.5 L 17.5 2.5 L 13.75 2.5 L 13.75 6.25 L 10 6.25 L 10 10 L 6.25 10 L 6.25 13.75 L 2.5 13.75 L 2.5 17.5 Z " /> <br />
</source><br />
<br />
Once you have your Path control, you can customize it as [https://learn.microsoft.com/en-us/previous-versions/xamarin/xamarin-forms/user-interface/shapes/path| documented by Microsoft] (Maui documentation: [https://learn.microsoft.com/en-us/dotnet/maui/user-interface/controls/shapes/path?view=net-maui-9.0| see here]). Path data generated using the above method will most likely need a Fill attribute, for example <nowiki>Fill="{StaticResource UBIKAccentColor}"</nowiki>.<br />
<br />
{{Hint|More complicated icons will have longer and more complicated paths.}}<br />
<br />
<br><br />
<br><br />
<br />
<br />
<br />
<br />
<br />
<br />
== TabView ==<br />
<br />
=== UI virtualization ===<br />
When using the TabView control in your XAML code, UI virtualization can greatly improve initial loading performance, based on the scenario.Here's how to enable it:<br />
<br />
<tabs><br />
<tab name="Mobile(Xamarin)"><br />
<source lang = "xml"><br />
<tabView:SfTabView EnableVirtualization="true"><br />
...<br />
</tabView:SfTabView><br />
</source><br />
</tab><br />
</tabs><br />
<br />
=== Default Tab Selection ===<br />
The tab selection in UBIKContentView defaults to the first tab, which is Children objects. However, for cases where it makes more sense to display Properties or Documents by default, it is possible to change the tab selection using the following classifications:<br />
* [[SYSCLS_SHOWDOCUMENTS]]<br />
* [[SYSCLS_SHOWPROPERTIES]]<br />
<br />
<tabs><br />
<tab name="UWP"><br />
Adding the classification to a metaclass is enough for UWP.<br />
</tab><br />
<tab name="Mobile(Xamarin)"><br />
Xamarin currently requires additional customizing to make use of the TabSelector property. One approach is to add a DataTrigger to the SfTabView found in UBIKContentArea that is triggered by the value of the TabSelector property, as shown below;<br />
<source lang = "xml"><br />
<tabView:SfTabView VisibleHeaderCount="3" ><br />
<!-- tabView:SfTabItems ... --><br />
<tabView:SfTabView.Triggers><br />
<DataTrigger TargetType="tabView:SfTabView" Binding="{Binding TabSelector}" Value="PropertiesTab"><br />
<Setter Property="SelectedIndex" Value="1"/><br />
</DataTrigger><br />
<DataTrigger TargetType="tabView:SfTabView" Binding="{Binding TabSelector}" Value="DocumentsTab"><br />
<Setter Property="SelectedIndex" Value="2"/><br />
</DataTrigger><br />
</tabView:SfTabView.Triggers><br />
</tabView:SfTabView><br />
</source><br />
</tab><br />
</tabs><br />
<br><br />
<br><br />
<br />
<br />
<br />
<br />
<br />
<br />
== FlipView ==<br />
<br />
=== UI virtualization ===<br />
When using the FlipView control in your XAML code, it's better to enable [https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/optimize-gridview-and-listview#ui-virtualization UI virtualization]. The difference in performance gets more obvious as the number of items in the FlipView increases. Here's how to enable it.<br />
<br />
<source lang = "xml"><br />
<FlipView<br />
...<br />
VirtualizingStackPanel.VirtualizationMode="Standard"><br />
<Flipview.ItemsPanel><br />
<ItemsPanelTemplate><br />
<VirtualizingStackPanel Orientation="Horizontal" /><br />
</ItemsPanelTemplate><br />
</Flipview.ItemsPanel><br />
</FlipView><br />
</source><br />
<br />
VirtualizingStackPanel.VirtualizationMode offers two possibilities: Standard & Recycling. In case you are interested, here are their [https://docs.microsoft.com/en-us/dotnet/api/system.windows.controls.virtualizationmode?view=netframework-4.7.2 differences].<br />
<br />
=== Delayed loading {{Version/WinXSince|4.7}} ===<br />
By default the FlipView control (UWP only) doesn't have a delayed loading mechanism.<br />
Imagine if you flip through a large list of documents quickly, the control would actually end up loading every single one of them even if you just want to look at the content of the last one. This has a very negative effect that the app wastes a lot of resources loading documents for nothing, while struggling to display the content you care about. In some extreme case, this can even lead to an app hang/crash.<br />
<br />
We added such a delayed loading mechanism to this control. With it, the item content only starts to load when you stay on it for a while (1 second). If you are using the content of UBIKDocumentFlipView.xaml from an older version (before 4.7) and therefore experience such a performance/stability issue, please check the FlipView related section in the newer default templates of it.<br />
<br />
=== Auto saving {{Version/WinXSince|4.6}} ===<br />
Unsaved changes on the document (e.g. Annotations) are gonna be saved and committed automatically when flipping the page in the FlipView.<br />
<br />
{{Attention|Changes are lost when leaving the page without flipping the document first.}}<br />
<br />
{{Version/WinXSince|4.7}} {{Version/XamarinSince|4.7}} If you want to keep the changes when leaving the page by e.g. navigating away without flipping the document first, there is a boolean property called ''AutoSaveDocumentsOnPageClose'' (default value: false) which enables this behavior. It can be activated by adding the property to (or editing it in) the custom UBIKThemes as follows:<br />
<tabs><br />
<tab name="UWP"><br />
<source lang = "xml"><br />
<x:String x:Key="AutoSaveDocumentsOnPageClose">true</x:String><br />
</source><br />
</tab><br />
<br />
<tab name="Mobile(Xamarin)"><br />
<source lang = "xml"><br />
<x:String x:Key="AutoSaveDocumentsOnPageClose">true</x:String><br />
</source><br />
</tab><br />
</tabs><br />
<br />
<br />
<br />
<br />
<br />
<br />
== Platform and Device-specific UI with OnPlatform and OnIdiom {{Version/MobileSince|5.0}} ==<br />
<br />
'''OnPlatform''' can be used to define different property values based on the platform. Valid Platform names are:<br />
* iOS<br />
* Android<br />
* WinUI (for Mobile Windows)<br />
* further ones see [https://learn.microsoft.com/en-us/dotnet/maui/platform-integration/customize-ui-appearance?view=net-maui-9.0#customize-ui-appearance-with-a-markup-extension-based-on-the-platform here]<br />
<br><br />
'''OnIdom''' can be used to define different property values based on the device type (e.g. Phone, Tablet, Desktop).<br />
<br />
When it comes to the proper syntax, we should stick with the approaches mentioned in the [https://learn.microsoft.com/en-us/dotnet/maui/platform-integration/customize-ui-appearance?view=net-maui-9.0 official documentation].<br />
Means, we should '''avoid''' using the single-tag syntax like ''<OnPlatform Android="..." iOS="..." />'' or ''<OnIdiom Phone="..." Desktop="..." />'' like it was usual in Xamarin.<br />
<br />
Instead, we should either use the '''multi-tag syntax''' or the '''inline syntax''' for OnPlatform / OnIdiom.<br />
<br />
==== Multi-tag syntax ====<br />
Here it is mandatory to add '''x:TypeArguments="TheType"''' with the proper type to OnPlatfrom/OnIdiom. ''Default="..."'' is optional and can be added like in the following example if a default value needs to be defined.<br />
<tabs><br />
<tab name="OnPlatform"><br />
<source lang = "XML"><br />
<OnPlatform x:TypeArguments="Thickness" Default="20"><br />
<On Platform="iOS, WinUI" Value="0,20,0,0" /><br />
<On Platform="Android" Value="10,20,20,10" /><br />
</OnPlatform><br />
</source><br />
</tab><br />
<tab name="OnIdiom"><br />
<source lang = "XML"><br />
<OnIdiom x:TypeArguments="Thickness" Default="20"><br />
<OnIdiom.Desktop>0,60,0,0</OnIdiom.Desktop><br />
</OnIdiom><br />
</source><br />
</tab><br />
</tabs><br />
<br />
If OnPlatform Values contain multiple subtags, the following syntax can be used:<br />
<source lang = "XML"><br />
<ControlTemplate x:Key="ExampleControlTemplate"><br />
<Grid><br />
<OnPlatform x:TypeArguments="View"><br />
<On Platform="Android"><br />
<Button<br />
...<br />
Text="Button A" /><br />
...<br />
</On><br />
<On Platform="iOS"><br />
<Button<br />
...<br />
Text="Button B" /><br />
...<br />
</On><br />
<On Platform="WinUI"><br />
<Grid><br />
<Button<br />
...<br />
Text="Button C" /><br />
<Label Text="Example" /><br />
...<br />
</Grid><br />
</On><br />
</OnPlatform><br />
</Grid><br />
</ControlTemplate><br />
</source><br />
<br />
{{Attention|When using ''GridLength'' as a type in OnPlatform/OnIdiom, it should only be used in combination with the inline syntax.}}<br />
<br />
==== Inline syntax ====<br />
When using the inline syntax, the type should not be specified. ''Default='' is optional.<br />
<tabs><br />
<tab name="OnPlatform"><br />
<source lang = "XML"><br />
<BoxView Color="{OnPlatform Default=Yellow, iOS=Red, Android=Green}" /><br />
</source><br />
</tab><br />
<tab name="OnIdiom"><br />
<source lang = "XML"><br />
<BoxView Color="{OnIdiom Default=Yellow, Phone=Red, Tablet=Green}" /><br />
</source><br />
</tab><br />
</tabs><br />
<br />
If the value contains any special characters like <code>"</code> or <code>,</code> or a '''string''' when using the OnIdiom or OnPlatform inline variant, it needs to be wrapped between <code>' '</code>. But be careful with using apostrophes - when using them around curly brackets {} it can lead to an error.<br />
<tabs><br />
<tab name="Don't"><br />
<source lang = "XML"><br />
Margin="{OnIdiom 10,2, Phone=2,0}"<br />
</source><br />
</tab><br />
<tab name="Instead do"><br />
<source lang = "XML"><br />
Margin="{OnIdiom '10,2', Phone='2,0'}"<br />
</source><br />
</tab><br />
</tabs><br />
<br />
=== Complex values ===<br />
If the OnPlatform/OnIdiom value contains a '''Binding''', '''StaticResource''' or any other complex value in curly brackets, it is recommended to use the '''inline syntax'''. Although it's not confirmed in any official documentation, it seems to work according to our experience. However, the multi-tag syntax doesn't always seem to work for such cases. DynamicResource values seem to be not supported at all in OnIdiom / OnPlatform.<br />
<br />
<tabs><br />
<tab name="Don't"><br />
<source lang = "XML"><br />
<OnIdiom x:TypeArguments="..." Default="{Binding ...}"><br />
<OnIdiom.Phone>{Binding ...}</OnIdiom.Phone><br />
</OnIdiom><br />
</source><br />
</tab><br />
<tab name="Instead do"><br />
<source lang = "XML"><br />
Header="{OnIdiom Default={Binding ...}, Phone={Binding ...}}"<br />
</source><br />
</tab><br />
</tabs><br />
<br />
{{Attention|Unreliable Support: Behavior may vary when using bindings or complex resources. Although it seems to work with the inline syntax according to our experiences, it is recommended to test these edge cases thoroughly.}}<br />
<br />
[[Category:Client|XAML Tips]]<br />
[[Category:Mobile|XAML Tips]]<br />
[[Category:WinX|XAML Tips]]<br />
[[Category:XAML|XAML Tips]]</div>LGEhttps://wiki.augmensys.com/index.php?title=MRO_Objects_(Client)&diff=29652MRO Objects (Client)2026-04-13T13:54:31Z<p>LGE: /* Numeric Task {{Version/MobileSince|5.1}}{{Version/WinXSince|5.1}} */</p>
<hr />
<div>[[File:MRO_WinX.png|thumb|alt=MRO Child List UI (WinX)|MRO UI (WinX)]]<br />
[[File:MRO_MAUI1.jpeg|thumb|alt=MRO Child List UI (Android)|MRO UI (Android)]]<br />
The WinX client UI displays MRO configured objects like any other root- or child-object enriched by some additional logic and features.<br />
<br />
== Basic User Interface ==<br />
The representation of MRO features comprises some indicators and interactive controls. In the {{UBIK}} child list, the main object displays cumulated technical and organisational status as well as the overall work progress based on the underlying data branch. Objects classified as MRO objects in general provide indicators for the MRO status. This means the status is shown next to the main icon of a child-/details-/documents-page as well as next to the icons of the child list items:<br />
<br />
=== Technical Status ===<br />
<br />
The technical status indicator is shown on all objects that represent a technical state or receive the technical status from subsequent objects in the underlying data branch. If e.g. a inventory object is reported as damaged, its parent objects will all display the exclamation mark symbol to indicate that a problem was reported in the child items.<br />
<br />
[[File:TechStats_WinX.png|100px|Technical Status Indicator (Winx & Mobile)]]<br />
<br />
=== Organisational Status ===<br />
The organisational status indicates the amount of confirmed work within the data branch, including already confirmed work packages as well as tasks that are locked by their owning work package. The organisational status indicator is displayed on all objects that represent an organisational state or receive the organisational status from subsequent objects in the underlying data branch, and visualizes the amount of confirmed work performed within that branch.<br />
<gallery><br />
File:UI_WinX_MRO_OrganisationalStatusIndicator.png|Organisational Status Indicator (WinX)<br />
File:ConfirmedWP_WinX.png|MRO Workpackage Confirmed (Flag) Indicator (WinX)<br />
File:Android_orga_status.PNG|Organisational Status Indicator (Android)<br />
File:ConfirmedWP_MAUI.jpeg|MRO Workpackage Confirmed Indicator (Mobile)<br />
</gallery><br />
<br />
<br />
=== Work Progress ===<br />
The work progress is calculated from the current work progress and from the progress cumulated from subsequent objects in the underlying data branch. This indicator shows the amount of work done in the data branch.<br />
<br />
{{Version/WinXSince|5.0}} {{Version/MobileSince|5.0}} By default, the progress is displayed with maximum one decimal place. For example, 99.75% is displayed as 99.8%. The format string used to achieve this is <code>{0:0.#}%</code>.<br />
<br />
If other numeric formats are preferred in your usecases, you can refer to [https://learn.microsoft.com/en-us/dotnet/standard/base-types/custom-numeric-format-strings custom numeric format strings] for more information. The template to customize for this is the UBIKMROProgressBadge within UBIKThemes.<br />
<br />
{{Clear}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== MRO Objects ==<br />
A set of specific objects can be used to provide the required structure for MRO:<br />
<br />
=== Task Owner ===<br />
A [[MROCLS_MRO_TASKOWNER|Task Owner]] is an object having a substructure of jobs to be done. It can have a tree of other task owners or work packages underneath that will update the status of the task owner. This status consists of technical, organisational and progress information. With a task owner a user can get an overview of all the work to be done in the underlying job structure.<br />
<br />
=== Work Package===<br />
A [[MROCLS_MRO_WORKPACKAGE|Work Package]] is a collection of objects to collect and summarize other task owning objects, workpackages, or tasks. A simple workpackage has a certain amount of tasks that have to be finished in order to confirm the workpackage as done. More complex workpackages can also own other underlying workpackages that have to be confirmed. Confirming a workpackage itself requires a progress of 100% of all related tasks, as well as 100% confirmed sub work packages.<br />
<br />
<gallery><br />
File:ConfirmingWP_WinX.png|MRO Workpackage confirm button (WinX)<br />
File:MRORevoke_WinX.png|MRO Workpackage revoke confirmation button (WinX)<br />
File:ConfirmingWP_MAUI.jpeg|MRO Workpackage confirm button (Android)<br />
File:MRORevoke_MAUI.jpeg|MRO Workpackage revoke confirmation button (Android)<br />
</gallery><br />
<br />
=== Task ===<br />
A [[MROCLS_MRO_TASK|Task]] is an object reporting a certain progress to the owning workpackage. There are several specialized types of task objects. All kinds of tasks have a property called '''VALUE''' in common. It is very important, that this property is able to be validated. Therefore, a MetaAttribute (providing a validation timestamp by default) has to be attached on the used MetaProperty.<br />
<br />
On both clients, a Task can be reverted by clicking twice on the Not Applicable button.<br />
<br />
<br />
<br />
{{Attention|The MetaProperty ''VALUE'' has to use [[Attributes]] in order to be validated. Otherwise, the calculation of work progress will not be possible.}}<br />
<br />
==== Measurement Task ====<br />
<br />
A [[MROCLS_MRO_MEASUREMENT_TASK|Measurement Task]] inherits from [[MROCLS_MRO_TASK|Task]] and documents a measured value (e.g. read from a pressure gauge). Therefore, clicking the value on the shown task opens an editor to enter the desired value. If no value was entered before, an empty line will be shown. Once a value has been entered, the task is finished. Alternatively, the task can also be closed by the option ''Not Applicable'' to document the situation of not being able to fullfill the measurement (e.g. the pressure gauge is broken). An additional small value indicator below the main value can report e.g. the previously entered value. The behaviour of this previous value indicator has to be specified separately in the customizing.<br />
{{Clear}}<br />
<br />
<gallery widths=497px heights=69px><br />
File:Measurment Task Empty UWP.png|Measurement Task without a reported value (WinX)<br />
File:Measurment Task Not Empty UWP.png|Measurement Task with a reported value (WinX)<br />
File:Measurment Task Empty Android.jpg|Measurement Task without a reported value (Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
==== Progress Task ====<br />
<br />
[[MROCLS_MRO_PROGRESS_TASK| Progress Task]] inherits from [[MROCLS_MRO_MEASUREMENT_TASK|Task]] and reports a certain progress while fullfilling a task. The progress will influence the overall progress of the owning workpackage. If the task cannot be fullfilled, it can also be finished with the option ''Not Applicable''.<br />
<br />
There is also an [[MRO_PROGRESS_TASK_EDITOR|alternative editor]] available for progress tasks.{{Version/WinXSince|2.5.4}}<br />
{{Clear}}<br />
<br />
<gallery widths=497px heights=69px><br />
File:Progress Task UWP.png|Progress Task with a reported work progress (WinX)<br />
File:Progress Task Android.jpg|Progress Task with a reported work progress and a previous progress(Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
==== Check Task ====<br />
<br />
A [[MROCLS_MRO_CHECK_TASK|Check Task]] inherits from [[MROCLS_MRO_TASK|Task]] and is finished by reporting ''Done'' or ''Not Applicable''. This is intended for a simple To-Do task that is either done or not.<br />
{{Clear}}<br />
<br />
<gallery widths=497px heights=69px><br />
File:Check Task finished UWP.png|Unfinished MRO CheckTask (WinX)<br />
File:Check Task android.jpg|Not Applicable MRO CheckTask (Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
==== Inspection Task ====<br />
<br />
[[MROCLS_MRO_INSPECTION_TASK|Inspection Task]] inherits from [[MROCLS_MRO_TASK|Task]] and is finished, when the user reports with a positive or negative answer or ''Not Applicable'' (e.g. reporting a yes/no answer for existing equipment).<br />
{{Clear}}<br />
<br />
<gallery widths=497px heights=69px><br />
File:Finished Inspection Task UWP.png|Finished MRO InspectionTask (WinX)<br />
File:Inspection task android.jpg|Finished MRO InspectionTask (Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
==== Sequential Task ====<br />
The [[MROCLS_SEQUENTIALTASK|sequential task classification]] allows you to pre-define a sequence in which tasks are to be resolved by users. This means that it is required for one or multiple tasks to be finished in order for other tasks to become "unlocked" and editable. A task can have any number of "predecessors". Predecessors are the tasks that are required to be finished first.<br />
<br />
A task can have predecessors that live anywhere else in the object hierarchy. It is not necessary for a task and its predecessors to be part of the same work package, even though this is likely the most common use case.<br />
<br />
The state of a sequential task is evaluated both offline and online to get the best possible user experience. The user will see dependent tasks update immediately if their successors were finished, if those tasks are currently visible in the UI. There is 1 case in which the server-side state will override the client-side (offline) evaluation, discussed below.<br />
The state of each sequential task is evaluated the following way:<br />
<br />
# If the server-side state says the task is open, we consider this as the truthful state and don't do any other evaluation.<br />
# Check if the task has any predecessors.<br />
# Try to load each predecessor task.<br />
#* If loading of any predecessor fails (the object is not available offline), the task will be locked.<br />
# If all predecessor tasks are finished, the task is open and can be edited. Otherwise, the task is locked.<br />
<br />
The customizer setting up the task dependency relations needs to ensure that the dependencies are not cyclical. In this case, it would be impossible for any tasks in the "cycle" to be finished.<br />
<br />
'''Example'''<br />
<br />
As a demonstration of this feature, see [[Media:Sequential_tasks_winx.mp4|this video]]. The relations between tasks are defined as in [[Media:Task_relations.png|this image]], starting at A1 and A2, which are not dependent on any other tasks. The lines (from left to right) indicate dependencies. This means that B2 has tasks A1 and A2 as its predecessors, for example.<br />
<br />
<br />
==== Grouped Task {{Version/WinXSince|4.2}}{{Version/XamarinSince|4.2}} ====<br />
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 [[MROCLS_GROUPEDTASK|grouped tasks]].<br />
<br />
The idea is, a group of tasks can be defined as siblings to each other and they also share the same server configured threshold. When the number of finished tasks among that group exceeds the threshold, the entire group is considered as no longer necessary. When reflected in the overall status of the task owner(s), these tasks would appear as if they are finished.<br />
<br />
{{Hint|Technically speaking, the finished status is completely independent from the not necessary status on a task. A grouped task which is no longer necessary can be both finished or not yet finished. In other words, users don't have to finish a not necessary grouped task, but they still can.}}<br />
<br />
{{Hint|The precise status calculation for grouped tasks and their task owners requires the knowledge of all siblings tasks. Imagine 2 out of 3 tasks must be finished but the client only knows 1 in total and the others are only available at the server at that time. This makes it impossible to draw conclusions whether the task(s) should be necessary or not. Under such circumstances, the local status calculation is done as if these are just regular tasks.}}<br />
<br />
{{Hint|Like with the other MRO objects, the client always chooses the best available statuses for grouped tasks to present to the users. More specifically, it uses the statuses calculated by the server when the client is not offline and there are no uncommitted local changes on the involved objects. Otherwise, it uses the statuses calculated locally to the best of its knowledge.}}<br />
<br />
A task can also be a grouped and a sequential one at the same time. In such a case, the grouped nature of the sibling tasks will affect the way the task sequence completes.<br />
<br />
For example, task A1, A2 and A3 are 3 grouped sibling tasks and only 1 of them needs to be finished. At the same time, they are all predecessors of task B. Normally, all predecessors must be finished (and locked) before task B becomes the next one in the sequence and therefore unlocked. In this case, however, as soon as one of the predecessors is finished, all three become unnecessary (and locked) and task B unlocks as a result of that.<br />
<br />
<br />
==== Supervisor Task {{Version/XamarinSince|4.8}} ====<br />
As the name suggests, supervisor tasks are those that must be finished under supervision. When users want to finish a [[MROCLS_MRO_SUPERVISOR_TASK|supervisor task]], they must hand over their work devices to a supervisor. The latter checks the work status and scans an NFC tag if the work is approved. If the [[MROCLS_MRO_SUPERVISOR|supervisor]] has sufficient permissions for the task and the correct supervisor PIN is given, the task gets unlocked and the users can proceed to finish it.<br />
<br />
<gallery widths=300px heights=300px><br />
File:UI_Xamarin_Supervisor_Task_Before_Verification.jpg|Supervisor Task Before Verification/Unlocking (Mobile)<br />
File:UI_Xamarin_Supervisor_Task_Enter_PIN.jpg|Supervisor Task Enter PIN (Mobile)<br />
File:UI_Xamarin_Supervisor_Task_After_Verification.jpg|Supervisor Task After Verification/Unlocking (Mobile)<br />
</gallery><br />
<br />
A thing to note is that while the need to verify a supervisor task can be seen as a type of locking, it's certainly not the only reason for a [[Locked_Objects|locked object]]. This means a supervisor task can remain locked (although for different reasons) even after a supervisor has successfully verified it. This can often be the case if you use it in combination with other features such as [[MRO_Objects_(Client)#Sequential_Task|sequential tasks]], [[User_Rights|user rights]].<br />
<br />
{{Hint|For security reasons, the verification process is cancelled if the supervisor enters the wrong PIN for three times. Scanning the tag again is required in that case.}}<br />
{{Hint|A setting controls [[RFID_tags#Choose_which_information_to_use_from_a_tag|which information in a scanned tag is used]] during this process.}}<br />
<br />
==== Signature Task {{Version/MobileSince|5.1}}{{Version/WinXSince|5.1}} ====<br />
<br />
The Signature Task is a task type that is completed by capturing a handwritten signature from the user. The task contains an editor field that serves as the entry point for the signing process. When the user clicks (or taps) on the editor field, a signature dialog opens. Within this dialog, the user can provide their signature. After confirming the input, the signature is saved and the task is automatically marked as completed.<br />
<br />
If the task is signed while the client is online:<br />
* The User (signee) is resolved immediately by the server and displayed.<br />
* The ValidationTimestamp is generated and displayed.<br />
* Both values are shown directly in the editor field after signing.<br />
<br />
{{Hint|The User only gets resolved by the server and displayed once you're in online mode}}<br />
<br />
If the displayed User and/or ValidationTimestamp cannot be fully shown due to limited space in the editor field, the complete information can be accessed via a tooltip.<br />
<br />
* In '''UBIK WinX (UWP)''', hover over the editor field with the mouse.<br />
* In '''UBIK Mobile''', perform a long press on the editor field.<br />
A tooltip will appear, displaying the full User and ValidationTimestamp without truncation.<br />
<br />
==== Picture Task {{Version/MobileSince|5.1}}{{Version/WinXSince|5.1}} ====<br />
<br />
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.<br />
* As any other objects, picture tasks can carry and display [[SYSCLS_CHILDINFOOWNER|child count information]]. But that is not a mandatory part of the feature. Even when it's not configured and not visible in the UI, you can still finish the tasks.<br />
* In WinX/UWP, the UI also presents an expander which allows you to display the child documents of picture tasks. This is not present by default in the Mobile app due to the screen size limit but [[Object_hierarchy_in_XAML:_NextLevel,_ParentLevel,_LinkedLevel#Show_NextLevel_Children.2FDocuments|can be easily customized]].<br />
<br />
{{Hint|The task is named as such because pictures are the most commonly used types, but the child documents can be of other types as well. }}<br />
<br />
When a user tries to finish a picture task by tapping the check, the app might perform some data synchronization first if in online mode, which includes<br />
* Syncing the child objects (including documents) of the task.<br />
* Downloading the file(s) of the child documents.<br />
During data synchronization, the check button on that task turns into a wait indicator. Afterwards, the app checks if the prerequisites to finish the task are met.<br />
* If there are no child documents or no local files for the child documents, the task remains unfinished and the user gets informed about the reasons.<br />
* Otherwise, the task gets finished and the photo button gets disabled.<br />
<br />
{{Hint|Setting NA (not applicable) on a picture task is always possible, regardless of the condition of child documents.}}<br />
<br />
{{UnderConstructionStart}}<br />
==== Numeric Task {{Version/MobileSince|5.1}}{{Version/WinXSince|5.1}} ====<br />
<br />
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.<br />
* The value is compared against an accaptable value range which is not editable on the client.<br />
* Deviation from this range results in visual feedback as well as the [[#Tech Status|tech status]] being set to display an issue.<br />
* 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.<br />
* 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]].<br />
{{UnderConstructionEnd}}<br />
<br />
[[Category:Android|MRO Objects (UBIK WinX)]]<br />
[[Category:Client|MRO Objects (Client)]]<br />
[[Category:Mobile|MRO Objects (Client)]]<br />
[[Category:Pages with broken file links|MRO Objects (Client)]]<br />
[[Category:WinX|MRO Objects (UBIK WinX)]]<br />
<br />
=== MRO objects with project information (WinX only) {{Version/WinXSince|2.5.4}} ===<br />
[[File:UI_WinX_MRO_ProjectInfo.png|thumb|MRO Object with Project Info (WinX)]]<br />
An MRO object (except tasks) might also bring along [[MROCLS_PROJECTINFORMATION|project information]]. In this case, the project information together with the MRO progress are displayed in a bar chart. The start & end dates of the MRO object are displayed on the progress bar. The length and the position of the progress bar, together with the current date mark indicate the timeline.<br />
{{Clear}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Locking ==<br />
When an (MRO) object is locked, editing it becomes impossible. More details about [[Locked_Objects|locked objects]].<br />
<br />
<br />
<br />
<br />
== See also ==<br />
* [[MRO (Plugin)]]<br />
* [[MROCLS_PROJECT]]<br />
* [[MROCLS_PROJECTINFORMATION]]<br />
* [[MROCLS_SEQUENTIALTASK]]<br />
* [[MROCLS_GROUPEDTASK]]<br />
* [[MROCLS_MRO_CHECK_TASK]]<br />
* [[MROCLS_MRO_INSPECTION_TASK]]<br />
* [[MROCLS_MRO_MEASUREMENT_TASK]]<br />
* [[MROCLS_MRO_PROGRESS_TASK]]<br />
* [[MROCLS_MRO_TASK]]<br />
* [[MROCLS_MRO_TASKOWNER]]<br />
* [[MROCLS_MRO_WORKPACKAGE]]<br />
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)<br />
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)<br />
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)<br />
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)<br />
<br />
[[Category:Android|MRO Objects (UBIK WinX)]]<br />
[[Category:Client|MRO Objects (Client)]]<br />
[[Category:Mobile|MRO Objects (Client)]]<br />
[[Category:Pages with broken file links|MRO Objects (Client)]]<br />
[[Category:WinX|MRO Objects (UBIK WinX)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(WinX)&diff=29635Version 5.1 (WinX)2026-03-31T12:34:50Z<p>LGE: </p>
<hr />
<div>{{Attention|This version requires [https://en.wikipedia.org/wiki/Windows_10_version_history#Version_1809_(October_2018_Update) Windows 10 build 17763] or higher}}<br />
<br />
== Availability ==<br />
{{key press|Store}}: Publicly available in Microsoft Store.<br />
<br />
{{key press|Store Beta}} / {{key press|Store Preview}}: Publicly available in Microsoft Store as beta or preview versions to those whose account email is participating in our beta or preview test. To join, please send an email to testing@augmensys.com and provide an email address to add to the list as well as the information which test you want to join. Alternatively you can contact the Augmensys staff and submit your chosen email address.<br />
<br />
Example: Please add my email account example@example.com to the '''Beta''' test group for the '''WinX''' client.<br />
<br />
<br/><br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
=== 5.1.?? on 2026-??-?? ===<br />
* Introduced a new [[MRO_Objects_(Client)#Picture_Task|picture task]] type which can only be finished when there's at least one valid child document.<br />
* Replaced app closing after repeated failed login attempts with a client-side temporary login block, including user feedback that indicates when login becomes available again.<br />
* Added French localization to the app.<br />
* Provided a visual difference between suggested and actual values in DateTime and Geo property direct edit fields via a [[XAML#Custom_VisualState_Trigger|Custom VisualState Trigger]].<br />
* Fixed an issue where the [[Object_hierarchy_in_XAML:_NextLevel,_ParentLevel,_LinkedLevel#LoadNextLevelCommand|LoadNextLevelCommand]] did not work under specific conditions (invoked in offline and then in online mode).<br />
* Fixed an issue where [[SYSCLS_CHILDINFOOWNER|child count]] indicators did not update when you delete its child objects which only exist locally.<br />
* Fixed an issue where line breaks (in strings property values) from Windows are not recognized as such on other systems.<br />
<br />
<br />
=== 5.1.6 on 2026-02-10 ===<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where certain documents couldn't be loaded anymore.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed an issue where the UI did not update properly when committing a direct edit input task.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Added a [[XAML#UBIKWebView|UBIKWebView]] control that includes a fix in the WebView2 where some links could not be opened.<br />
* Fixed issue that caused input fields to be focused but not editable.<br />
* Fixed an issue where document creation might not be properly enabled in certain customizing scenarios. For example, a media creation button might be disabled until a page refresh.<br />
* Fixed an issue where batch creating documents (by multi selecting files to attach) can be interrupted if you leave the page.<br />
<br />
<br />
<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Free Text Annotations that where created in former sessions cannot be selected and therefore cannot be edited any more.<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* Known issues regarding the [[Documents_(Client)#Remember_Document_Settings|Remember Document Settings]] feature:<br />
** Saving the Zoom value via touch gestures is not supported.<br />
** Due to a third-party framework issue it can't be guaranteed that saving the Zoom level is always working properly. We reported this issue and will update our solution as soon as it is resolved on their side.<br />
<br/><br />
<br />
= ⚠️ XAML Notes =<br />
<br />
<br />
<br />
<headertabs /><br />
<br />
<br />
{{Category/Version2|{{PAGENAME}}}}<br />
<br />
[[Category:Client|Version 5.1 (WinX)]]<br />
[[Category:Version 5.1|Version 5.1 (WinX)]]<br />
[[Category:WinX|Version 5.1 (WinX)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(Mobile)&diff=29634Version 5.1 (Mobile)2026-03-31T12:34:24Z<p>LGE: </p>
<hr />
<div>{{Attention|Existing pre 5.0 XAMLs are not compatible with UBIK Mobile client 5.1. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.}}<br />
<br />
{{Attention|UBIK 5 clients can only connect to {{UBIK}} Servers of [[Version 3.6(Server)|version 3.6]] and higher!}}<br />
<br />
{{Attention|The minimum supported OS versions are:<br />
* Android 9;<br />
* iOS 12.}}<br />
<br />
== Availability ==<br />
{{key press|Android: Store}}{{key press|iOS: Store}}: Publicly available in Google Play Store / Apple App Store.<br />
<br />
{{key press|Android: Store Beta}}: Publicly available in Google Play Store as beta versions. You can opt in or out of the beta at any time in the store.<br />
<br />
{{key press|Android: Store Preview}}: Available through Google Play Store's [https://play.google.com/store/apps/details?id=com.augmensys.ubik.go invitation link].<br />
<br />
{{key press|iOS: Store Beta}}: Available through Apple App Store's [https://testflight.apple.com/join/Kmb1HG9E invitation link].<br />
<br />
{{key press|iOS: Store Preview}}: Available through Apple App Store's [https://testflight.apple.com/join/yHRnbYbt invitation link].<br />
<br />
{{key press|Windows: Store Preview}}: The mobile Windows client is not an official product and is only distributed as test versions upon request and/or in our [https://release.augmensys.com/download/modules/client/mobile/ release portal].<br />
<br/><br />
<br />
<br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with a ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
=== 5.1.?? 2026-??-?? {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Introduced a new [[MRO_Objects_(Client)#Picture_Task|picture task]] type which can only be finished when there's at least one valid child document.<br />
* The system flashlight can now also be enabled or disabled via XAML customization. For detailed information, see [[Mobile XAML#Flashlight|Flashlight]]<br />
* Replaced app closing after repeated failed login attempts with a client-side temporary login block, including user feedback that indicates when login becomes available again.<br />
* Added French localization to the app.<br />
* [[MRO_Objects_(Client)#Signature_Task|MRO Signature Tasks]] have been introduced, which automatically displays the signee as well as the validation timestamp after the task has been signed.<br />
* Fixed an issue where changes in property editing were not discarded when using the default Back button.<br />
* Fixed an issue where the application crashed on Windows when navigating back from the VideoPlayer.<br />
* Icon set Addition 8: Added Show/Hide, AI, Info, and various Procedure icons.<br />
* Fixed an issue where the [[Object_hierarchy_in_XAML:_NextLevel,_ParentLevel,_LinkedLevel#LoadNextLevelCommand|LoadNextLevelCommand]] did not work under specific conditions (invoked in offline and then in online mode).<br />
* Fixed an issue where [[SYSCLS_CHILDINFOOWNER|child count]] indicators did not update when you delete its child objects which only exist locally.<br />
* Fixed an issue where MRO task items displayed an incorrect DataTemplate after scrolling within a list.<br />
* Fixed an issue where the client could fail at large file uploads (or even crash) due to device running out of memory.<br />
* Fixed an issue where line breaks (in strings property values) from Windows are not recognized as such on other systems. The standard UI is not yet redesigned to show multi-line texts, though. But you can do so in customizing if necessary.<br />
<br />
<br />
=== 5.1.30 2026-03-02 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Fixed an issue that prevented any documents from being uploaded when connecting to 5.1 webservices.<br />
<br />
<br />
=== 5.1.29 on 2026-02-26 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Fixed an issue where the POI button was only visible under certain condition (ShowUnreleasedFeatures in the profile is set to true).<br />
<br />
<br />
=== 5.1.28 on 2026-02-10 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* The following features which existed in pre 5.0 versions are now available again in 5.1.<br />
** [[Map_View|Map view]].<br />
** [[POI_View_(Mobile)|POI view]]. (Aruco and OCR are not yet supported)<br />
** Location service.<br />
** [[Native_Push_(Client)|Native push]].<br />
** [[Charts]].<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Complete UI overhaul introduces a cleaner, more modern and adaptive user interface with various quality of life improvements.<br />
* UBIKTabView supports both dynamic and static items in combination with lazy loading.<br />
* Files in the app's data folder can now be opened or deleted directly in the developer settings.<br />
* Introduced a fully resource-driven UI theming system enabling fast, safe customization (dark mode, resizing, and consistent styling) by adapting a small set of centralized resources.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* Fixed an issue where remembered scroll positions were lost when the ItemsSource property of an SfListViewExt changed (e.g., Properties.ShowAllProperties).<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed issue that caused app to be stuck on splash screen after resuming from background.<br />
* Fixed an issue where StatusColor was not shown in the UI for objects that didn't additionally have a Progress.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Fixed an issue that caused content of the custom ContentControl to not be rendered sometimes.<br />
* (Android) Fixed an issue in the WebView where some links could not be opened.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the deletion of some objects was not reflected in the UI until refresh.<br />
* Fixed an issue where document creation might not be properly enabled in certain customizing scenarios. For example, a media creation button might be disabled until a page refresh.<br />
* Fixed an issue where batch creating documents (by multi selecting files to attach) can be interrupted if you leave the page.<br />
<br />
<br />
<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true. In Mobile, deleting the last annotation does not correctly update the editor's internal edit state. As a result, the Save button may remain visible even though no edits exist.<br />
* When changing the device orientation during attaching a photo on iOS, the app gets stuck. This is an issue Microsoft confirmed in .NET9 and will fix in .NET10.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Currently, the Samsung keyboard doesn't show {{key press|,}} at all, regardless of the current language/locale setting of the device. Please use a different virtual keyboard (e.g. Gboard from Google) instead if {{key press|.}} is unacceptable.<br />
* The periodic execution of background pushes is not guaranteed on iOS (the native push feature doesn't have this issue).<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* It is currently not possible to select which camera to use for AR views (e.g. scan page) on Windows.<br />
* SfPullToRefresh was removed due to [[Mobile_XAML#Issues_with_SfPullToRefresh_in_Mobile_client|existing issues]], and replaced with a Refresh option in the Context menu.<br />
<br />
<br />
= ⚠️ XAML Notes =<br />
Due to the change of the underlying XAML technology, the existing XAMLs for the old mobile clients (pre 5.0) are no longer compatible. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.<br />
<br />
<br />
<headertabs /><br />
<br />
[[Category:Client|Version 5.1 (Mobile)]]<br />
[[Category:Mobile|Version 5.1 (Mobile)]]<br />
[[Category:Version 5.1|Version 5.1 (Mobile)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(Mobile)&diff=29615Version 5.1 (Mobile)2026-03-23T15:38:18Z<p>LGE: </p>
<hr />
<div>{{Attention|Existing pre 5.0 XAMLs are not compatible with UBIK Mobile client 5.1. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.}}<br />
<br />
{{Attention|UBIK 5 clients can only connect to {{UBIK}} Servers of [[Version 3.6(Server)|version 3.6]] and higher!}}<br />
<br />
{{Attention|The minimum supported OS versions are:<br />
* Android 9;<br />
* iOS 12.}}<br />
<br />
== Availability ==<br />
{{key press|Android: Store}}{{key press|iOS: Store}}: Publicly available in Google Play Store / Apple App Store.<br />
<br />
{{key press|Android: Store Beta}}: Publicly available in Google Play Store as beta versions. You can opt in or out of the beta at any time in the store.<br />
<br />
{{key press|Android: Store Preview}}: Available through Google Play Store's [https://play.google.com/store/apps/details?id=com.augmensys.ubik.go invitation link].<br />
<br />
{{key press|iOS: Store Beta}}: Available through Apple App Store's [https://testflight.apple.com/join/Kmb1HG9E invitation link].<br />
<br />
{{key press|iOS: Store Preview}}: Available through Apple App Store's [https://testflight.apple.com/join/yHRnbYbt invitation link].<br />
<br />
{{key press|Windows: Store Preview}}: The mobile Windows client is not an official product and is only distributed as test versions upon request and/or in our [https://release.augmensys.com/download/modules/client/mobile/ release portal].<br />
<br/><br />
<br />
<br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with a ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
=== 5.1.?? 2026-??-?? {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Introduced a new [[MRO_Objects_(Client)#Picture_Task|picture task]] type which can only be finished when there's at least one valid child document.<br />
* The system flashlight can now also be enabled or disabled via XAML customization. For detailed information, see [[Mobile XAML#Flashlight|Flashlight]]<br />
* Replaced app closing after repeated failed login attempts with a client-side temporary login block, including user feedback that indicates when login becomes available again.<br />
* Added French localization to the app.<br />
* [[MRO_Objects_(Client)#Signature_Task|MRO Signature Tasks]] have been introduced, which automatically displays the signee as well as the validation timestamp after the task has been signed.<br />
* Fixed an issue where changes in property editing were not discarded when using the default Back button.<br />
* Fixed an issue where the application crashed on Windows when navigating back from the VideoPlayer.<br />
* Icon set Addition 8: Added Show/Hide, AI, Info, and various Procedure icons.<br />
* Fixed an issue where the [[Object_hierarchy_in_XAML:_NextLevel,_ParentLevel,_LinkedLevel#LoadNextLevelCommand|LoadNextLevelCommand]] did not work under specific conditions (invoked in offline and then in online mode).<br />
* Fixed an issue where [[SYSCLS_CHILDINFOOWNER|child count]] indicators did not update when you delete its child objects which only exist locally.<br />
* Fixed an issue where MRO task items displayed an incorrect DataTemplate after scrolling within a list.<br />
* Fixed an issue where the client could fail at large file uploads (or even crash) due to device running out of memory.<br />
<br />
<br />
=== 5.1.30 2026-03-02 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Fixed an issue that prevented any documents from being uploaded when connecting to 5.1 webservices.<br />
<br />
<br />
=== 5.1.29 on 2026-02-26 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Fixed an issue where the POI button was only visible under certain condition (ShowUnreleasedFeatures in the profile is set to true).<br />
<br />
<br />
=== 5.1.28 on 2026-02-10 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* The following features which existed in pre 5.0 versions are now available again in 5.1.<br />
** [[Map_View|Map view]].<br />
** [[POI_View_(Mobile)|POI view]]. (Aruco and OCR are not yet supported)<br />
** Location service.<br />
** [[Native_Push_(Client)|Native push]].<br />
** [[Charts]].<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Complete UI overhaul introduces a cleaner, more modern and adaptive user interface with various quality of life improvements.<br />
* UBIKTabView supports both dynamic and static items in combination with lazy loading.<br />
* Files in the app's data folder can now be opened or deleted directly in the developer settings.<br />
* Introduced a fully resource-driven UI theming system enabling fast, safe customization (dark mode, resizing, and consistent styling) by adapting a small set of centralized resources.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* Fixed an issue where remembered scroll positions were lost when the ItemsSource property of an SfListViewExt changed (e.g., Properties.ShowAllProperties).<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed issue that caused app to be stuck on splash screen after resuming from background.<br />
* Fixed an issue where StatusColor was not shown in the UI for objects that didn't additionally have a Progress.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Fixed an issue that caused content of the custom ContentControl to not be rendered sometimes.<br />
* (Android) Fixed an issue in the WebView where some links could not be opened.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the deletion of some objects was not reflected in the UI until refresh.<br />
* Fixed an issue where document creation might not be properly enabled in certain customizing scenarios. For example, a media creation button might be disabled until a page refresh.<br />
* Fixed an issue where batch creating documents (by multi selecting files to attach) can be interrupted if you leave the page.<br />
<br />
<br />
<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true. In Mobile, deleting the last annotation does not correctly update the editor's internal edit state. As a result, the Save button may remain visible even though no edits exist.<br />
* When changing the device orientation during attaching a photo on iOS, the app gets stuck. This is an issue Microsoft confirmed in .NET9 and will fix in .NET10.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Currently, the Samsung keyboard doesn't show {{key press|,}} at all, regardless of the current language/locale setting of the device. Please use a different virtual keyboard (e.g. Gboard from Google) instead if {{key press|.}} is unacceptable.<br />
* The periodic execution of background pushes is not guaranteed on iOS (the native push feature doesn't have this issue).<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* It is currently not possible to select which camera to use for AR views (e.g. scan page) on Windows.<br />
* SfPullToRefresh was removed due to [[Mobile_XAML#Issues_with_SfPullToRefresh_in_Mobile_client|existing issues]], and replaced with a Refresh option in the Context menu.<br />
<br />
<br />
= ⚠️ XAML Notes =<br />
Due to the change of the underlying XAML technology, the existing XAMLs for the old mobile clients (pre 5.0) are no longer compatible. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.<br />
<br />
<br />
<headertabs /><br />
<br />
[[Category:Client|Version 5.1 (Mobile)]]<br />
[[Category:Mobile|Version 5.1 (Mobile)]]<br />
[[Category:Version 5.1|Version 5.1 (Mobile)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(Mobile)&diff=29571Version 5.1 (Mobile)2026-03-13T15:12:28Z<p>LGE: </p>
<hr />
<div>{{Attention|Existing pre 5.0 XAMLs are not compatible with UBIK Mobile client 5.1. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.}}<br />
<br />
{{Attention|UBIK 5 clients can only connect to {{UBIK}} Servers of [[Version 3.6(Server)|version 3.6]] and higher!}}<br />
<br />
{{Attention|The minimum supported OS versions are:<br />
* Android 9;<br />
* iOS 12.}}<br />
<br />
== Availability ==<br />
{{key press|Android: Store}}{{key press|iOS: Store}}: Publicly available in Google Play Store / Apple App Store.<br />
<br />
{{key press|Android: Store Beta}}: Publicly available in Google Play Store as beta versions. You can opt in or out of the beta at any time in the store.<br />
<br />
{{key press|Android: Store Preview}}: Available through Google Play Store's [https://play.google.com/store/apps/details?id=com.augmensys.ubik.go invitation link].<br />
<br />
{{key press|iOS: Store Beta}}: Available through Apple App Store's [https://testflight.apple.com/join/Kmb1HG9E invitation link].<br />
<br />
{{key press|iOS: Store Preview}}: Available through Apple App Store's [https://testflight.apple.com/join/yHRnbYbt invitation link].<br />
<br />
{{key press|Windows: Store Preview}}: The mobile Windows client is not an official product and is only distributed as test versions upon request and/or in our [https://release.augmensys.com/download/modules/client/mobile/ release portal].<br />
<br/><br />
<br />
<br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with a ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
=== 5.1.?? 2026-??-?? {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Introduced a new [[MRO_Objects_(Client)#Picture_Task|picture task]] type which can only be finished when there's at least one valid child document.<br />
* The system flashlight can now also be enabled or disabled via XAML customization. For detailed information, see [[Mobile XAML#Flashlight|Flashlight]]<br />
* Replaced app closing after repeated failed login attempts with a client-side temporary login block, including user feedback that indicates when login becomes available again.<br />
* Added French localization to the app.<br />
* [[MRO_Objects_(Client)#Signature_Task|MRO Signature Tasks]] have been introduced, which automatically displays the signee as well as the validation timestamp after the task has been signed.<br />
* Fixed an issue where changes in property editing were not discarded when using the default Back button.<br />
* Fixed an issue where the application crashed on Windows when navigating back from the VideoPlayer.<br />
* Icon set Addition 8 adds Show/Hide, AI, Info, and various Procedure icons.<br />
* Fixed an issue where the [[Object_hierarchy_in_XAML:_NextLevel,_ParentLevel,_LinkedLevel#LoadNextLevelCommand|LoadNextLevelCommand]] did not work under specific conditions (invoked in offline and then in online mode).<br />
* Fixed an issue where [[SYSCLS_CHILDINFOOWNER|child count]] indicators did not update when you delete its child objects which only exist locally.<br />
<br />
<br />
<br />
=== 5.1.30 2026-03-02 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Fixed an issue that prevented any documents from being uploaded when connecting to 5.1 webservices.<br />
<br />
<br />
=== 5.1.29 on 2026-02-26 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Fixed an issue where the POI button was only visible under certain condition (ShowUnreleasedFeatures in the profile is set to true).<br />
<br />
<br />
=== 5.1.28 on 2026-02-10 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* The following features which existed in pre 5.0 versions are now available again in 5.1.<br />
** [[Map_View|Map view]].<br />
** [[POI_View_(Mobile)|POI view]]. (Aruco and OCR are not yet supported)<br />
** Location service.<br />
** [[Native_Push_(Client)|Native push]].<br />
** [[Charts]].<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Complete UI overhaul introduces a cleaner, more modern and adaptive user interface with various quality of life improvements.<br />
* UBIKTabView supports both dynamic and static items in combination with lazy loading.<br />
* Files in the app's data folder can now be opened or deleted directly in the developer settings.<br />
* Introduced a fully resource-driven UI theming system enabling fast, safe customization (dark mode, resizing, and consistent styling) by adapting a small set of centralized resources.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* Fixed an issue where remembered scroll positions were lost when the ItemsSource property of an SfListViewExt changed (e.g., Properties.ShowAllProperties).<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed issue that caused app to be stuck on splash screen after resuming from background.<br />
* Fixed an issue where StatusColor was not shown in the UI for objects that didn't additionally have a Progress.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Fixed an issue that caused content of the custom ContentControl to not be rendered sometimes.<br />
* (Android) Fixed an issue in the WebView where some links could not be opened.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the deletion of some objects was not reflected in the UI until refresh.<br />
* Fixed an issue where document creation might not be properly enabled in certain customizing scenarios. For example, a media creation button might be disabled until a page refresh.<br />
* Fixed an issue where batch creating documents (by multi selecting files to attach) can be interrupted if you leave the page.<br />
<br />
<br />
<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true. In Mobile, deleting the last annotation does not correctly update the editor's internal edit state. As a result, the Save button may remain visible even though no edits exist.<br />
* When changing the device orientation during attaching a photo on iOS, the app gets stuck. This is an issue Microsoft confirmed in .NET9 and will fix in .NET10.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Currently, the Samsung keyboard doesn't show {{key press|,}} at all, regardless of the current language/locale setting of the device. Please use a different virtual keyboard (e.g. Gboard from Google) instead if {{key press|.}} is unacceptable.<br />
* The periodic execution of background pushes is not guaranteed on iOS (the native push feature doesn't have this issue).<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* It is currently not possible to select which camera to use for AR views (e.g. scan page) on Windows.<br />
* SfPullToRefresh was removed due to [[Mobile_XAML#Issues_with_SfPullToRefresh_in_Mobile_client|existing issues]], and replaced with a Refresh option in the Context menu.<br />
<br />
<br />
= ⚠️ XAML Notes =<br />
Due to the change of the underlying XAML technology, the existing XAMLs for the old mobile clients (pre 5.0) are no longer compatible. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.<br />
<br />
<br />
<headertabs /><br />
<br />
[[Category:Client|Version 5.1 (Mobile)]]<br />
[[Category:Mobile|Version 5.1 (Mobile)]]<br />
[[Category:Version 5.1|Version 5.1 (Mobile)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(WinX)&diff=29570Version 5.1 (WinX)2026-03-13T15:11:35Z<p>LGE: </p>
<hr />
<div>{{Attention|This version requires [https://en.wikipedia.org/wiki/Windows_10_version_history#Version_1809_(October_2018_Update) Windows 10 build 17763] or higher}}<br />
<br />
== Availability ==<br />
{{key press|Store}}: Publicly available in Microsoft Store.<br />
<br />
{{key press|Store Beta}} / {{key press|Store Preview}}: Publicly available in Microsoft Store as beta or preview versions to those whose account email is participating in our beta or preview test. To join, please send an email to testing@augmensys.com and provide an email address to add to the list as well as the information which test you want to join. Alternatively you can contact the Augmensys staff and submit your chosen email address.<br />
<br />
Example: Please add my email account example@example.com to the '''Beta''' test group for the '''WinX''' client.<br />
<br />
<br/><br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
=== 5.1.?? on 2026-??-?? ===<br />
* Introduced a new [[MRO_Objects_(Client)#Picture_Task|picture task]] type which can only be finished when there's at least one valid child document.<br />
* Replaced app closing after repeated failed login attempts with a client-side temporary login block, including user feedback that indicates when login becomes available again.<br />
* Added French localization to the app.<br />
* Provided a visual difference between suggested and actual values in DateTime and Geo property direct edit fields via a [[XAML#Custom_VisualState_Trigger|Custom VisualState Trigger]].<br />
* Fixed an issue where the [[Object_hierarchy_in_XAML:_NextLevel,_ParentLevel,_LinkedLevel#LoadNextLevelCommand|LoadNextLevelCommand]] did not work under specific conditions (invoked in offline and then in online mode).<br />
* Fixed an issue where [[SYSCLS_CHILDINFOOWNER|child count]] indicators did not update when you delete its child objects which only exist locally.<br />
<br />
<br />
=== 5.1.6 on 2026-02-10 ===<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where certain documents couldn't be loaded anymore.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed an issue where the UI did not update properly when committing a direct edit input task.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Added a [[XAML#UBIKWebView|UBIKWebView]] control that includes a fix in the WebView2 where some links could not be opened.<br />
* Fixed issue that caused input fields to be focused but not editable.<br />
* Fixed an issue where document creation might not be properly enabled in certain customizing scenarios. For example, a media creation button might be disabled until a page refresh.<br />
* Fixed an issue where batch creating documents (by multi selecting files to attach) can be interrupted if you leave the page.<br />
<br />
<br />
<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Free Text Annotations that where created in former sessions cannot be selected and therefore cannot be edited any more.<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* Known issues regarding the [[Documents_(Client)#Remember_Document_Settings|Remember Document Settings]] feature:<br />
** Saving the Zoom value via touch gestures is not supported.<br />
** Due to a third-party framework issue it can't be guaranteed that saving the Zoom level is always working properly. We reported this issue and will update our solution as soon as it is resolved on their side.<br />
<br/><br />
<br />
= ⚠️ XAML Notes =<br />
<br />
<br />
<br />
<headertabs /><br />
<br />
<br />
{{Category/Version2|{{PAGENAME}}}}<br />
<br />
[[Category:Client|Version 5.1 (WinX)]]<br />
[[Category:Version 5.1|Version 5.1 (WinX)]]<br />
[[Category:WinX|Version 5.1 (WinX)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(WinX)&diff=29569Version 5.1 (WinX)2026-03-13T10:00:21Z<p>LGE: </p>
<hr />
<div>{{Attention|This version requires [https://en.wikipedia.org/wiki/Windows_10_version_history#Version_1809_(October_2018_Update) Windows 10 build 17763] or higher}}<br />
<br />
== Availability ==<br />
{{key press|Store}}: Publicly available in Microsoft Store.<br />
<br />
{{key press|Store Beta}} / {{key press|Store Preview}}: Publicly available in Microsoft Store as beta or preview versions to those whose account email is participating in our beta or preview test. To join, please send an email to testing@augmensys.com and provide an email address to add to the list as well as the information which test you want to join. Alternatively you can contact the Augmensys staff and submit your chosen email address.<br />
<br />
Example: Please add my email account example@example.com to the '''Beta''' test group for the '''WinX''' client.<br />
<br />
<br/><br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
=== 5.1.?? on 2026-??-?? ===<br />
* Introduced a new [[MRO_Objects_(Client)#Picture_Task|picture task]] type which can only be finished when there's at least one valid child document.<br />
* Replaced app closing after repeated failed login attempts with a client-side temporary login block, including user feedback that indicates when login becomes available again.<br />
* Added French localization to the app.<br />
* Provided a visual difference between suggested and actual values in DateTime and Geo property direct edit fields via a [[XAML#Custom_VisualState_Trigger|Custom VisualState Trigger]].<br />
* Fixed an issue where the [[Object_hierarchy_in_XAML:_NextLevel,_ParentLevel,_LinkedLevel#LoadNextLevelCommand|LoadNextLevelCommand]] did not work under specific conditions (invoked in offline and then in online mode).<br />
<br />
<br />
=== 5.1.6 on 2026-02-10 ===<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where certain documents couldn't be loaded anymore.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed an issue where the UI did not update properly when committing a direct edit input task.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Added a [[XAML#UBIKWebView|UBIKWebView]] control that includes a fix in the WebView2 where some links could not be opened.<br />
* Fixed issue that caused input fields to be focused but not editable.<br />
* Fixed an issue where document creation might not be properly enabled in certain customizing scenarios. For example, a media creation button might be disabled until a page refresh.<br />
* Fixed an issue where batch creating documents (by multi selecting files to attach) can be interrupted if you leave the page.<br />
<br />
<br />
<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Free Text Annotations that where created in former sessions cannot be selected and therefore cannot be edited any more.<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* Known issues regarding the [[Documents_(Client)#Remember_Document_Settings|Remember Document Settings]] feature:<br />
** Saving the Zoom value via touch gestures is not supported.<br />
** Due to a third-party framework issue it can't be guaranteed that saving the Zoom level is always working properly. We reported this issue and will update our solution as soon as it is resolved on their side.<br />
<br/><br />
<br />
= ⚠️ XAML Notes =<br />
<br />
<br />
<br />
<headertabs /><br />
<br />
<br />
{{Category/Version2|{{PAGENAME}}}}<br />
<br />
[[Category:Client|Version 5.1 (WinX)]]<br />
[[Category:Version 5.1|Version 5.1 (WinX)]]<br />
[[Category:WinX|Version 5.1 (WinX)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(Mobile)&diff=29568Version 5.1 (Mobile)2026-03-13T09:59:38Z<p>LGE: </p>
<hr />
<div>{{Attention|Existing pre 5.0 XAMLs are not compatible with UBIK Mobile client 5.1. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.}}<br />
<br />
{{Attention|UBIK 5 clients can only connect to {{UBIK}} Servers of [[Version 3.6(Server)|version 3.6]] and higher!}}<br />
<br />
{{Attention|The minimum supported OS versions are:<br />
* Android 9;<br />
* iOS 12.}}<br />
<br />
== Availability ==<br />
{{key press|Android: Store}}{{key press|iOS: Store}}: Publicly available in Google Play Store / Apple App Store.<br />
<br />
{{key press|Android: Store Beta}}: Publicly available in Google Play Store as beta versions. You can opt in or out of the beta at any time in the store.<br />
<br />
{{key press|Android: Store Preview}}: Available through Google Play Store's [https://play.google.com/store/apps/details?id=com.augmensys.ubik.go invitation link].<br />
<br />
{{key press|iOS: Store Beta}}: Available through Apple App Store's [https://testflight.apple.com/join/Kmb1HG9E invitation link].<br />
<br />
{{key press|iOS: Store Preview}}: Available through Apple App Store's [https://testflight.apple.com/join/yHRnbYbt invitation link].<br />
<br />
{{key press|Windows: Store Preview}}: The mobile Windows client is not an official product and is only distributed as test versions upon request and/or in our [https://release.augmensys.com/download/modules/client/mobile/ release portal].<br />
<br/><br />
<br />
<br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with a ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
=== 5.1.?? 2026-??-?? {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Introduced a new [[MRO_Objects_(Client)#Picture_Task|picture task]] type which can only be finished when there's at least one valid child document.<br />
* The system flashlight can now also be enabled or disabled via XAML customization. For detailed information, see [[Mobile XAML#Flashlight|Flashlight]]<br />
* Replaced app closing after repeated failed login attempts with a client-side temporary login block, including user feedback that indicates when login becomes available again.<br />
* Added French localization to the app.<br />
* [[MRO_Objects_(Client)#Signature_Task|MRO Signature Tasks]] have been introduced, which automatically displays the signee as well as the validation timestamp after the task has been signed.<br />
* Fixed an issue where changes in property editing were not discarded when using the default Back button.<br />
* Fixed an issue where the application crashed on Windows when navigating back from the VideoPlayer.<br />
* Icon set Addition 8 adds Show/Hide, AI, Info, and various Procedure icons.<br />
* Fixed an issue where the [[Object_hierarchy_in_XAML:_NextLevel,_ParentLevel,_LinkedLevel#LoadNextLevelCommand|LoadNextLevelCommand]] did not work under specific conditions (invoked in offline and then in online mode).<br />
<br />
<br />
<br />
<br />
=== 5.1.30 2026-03-02 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Fixed an issue that prevented any documents from being uploaded when connecting to 5.1 webservices.<br />
<br />
<br />
=== 5.1.29 on 2026-02-26 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Fixed an issue where the POI button was only visible under certain condition (ShowUnreleasedFeatures in the profile is set to true).<br />
<br />
<br />
=== 5.1.28 on 2026-02-10 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* The following features which existed in pre 5.0 versions are now available again in 5.1.<br />
** [[Map_View|Map view]].<br />
** [[POI_View_(Mobile)|POI view]]. (Aruco and OCR are not yet supported)<br />
** Location service.<br />
** [[Native_Push_(Client)|Native push]].<br />
** [[Charts]].<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Complete UI overhaul introduces a cleaner, more modern and adaptive user interface with various quality of life improvements.<br />
* UBIKTabView supports both dynamic and static items in combination with lazy loading.<br />
* Files in the app's data folder can now be opened or deleted directly in the developer settings.<br />
* Introduced a fully resource-driven UI theming system enabling fast, safe customization (dark mode, resizing, and consistent styling) by adapting a small set of centralized resources.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* Fixed an issue where remembered scroll positions were lost when the ItemsSource property of an SfListViewExt changed (e.g., Properties.ShowAllProperties).<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed issue that caused app to be stuck on splash screen after resuming from background.<br />
* Fixed an issue where StatusColor was not shown in the UI for objects that didn't additionally have a Progress.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Fixed an issue that caused content of the custom ContentControl to not be rendered sometimes.<br />
* (Android) Fixed an issue in the WebView where some links could not be opened.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the deletion of some objects was not reflected in the UI until refresh.<br />
* Fixed an issue where document creation might not be properly enabled in certain customizing scenarios. For example, a media creation button might be disabled until a page refresh.<br />
* Fixed an issue where batch creating documents (by multi selecting files to attach) can be interrupted if you leave the page.<br />
<br />
<br />
<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true. In Mobile, deleting the last annotation does not correctly update the editor's internal edit state. As a result, the Save button may remain visible even though no edits exist.<br />
* When changing the device orientation during attaching a photo on iOS, the app gets stuck. This is an issue Microsoft confirmed in .NET9 and will fix in .NET10.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Currently, the Samsung keyboard doesn't show {{key press|,}} at all, regardless of the current language/locale setting of the device. Please use a different virtual keyboard (e.g. Gboard from Google) instead if {{key press|.}} is unacceptable.<br />
* The periodic execution of background pushes is not guaranteed on iOS (the native push feature doesn't have this issue).<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* It is currently not possible to select which camera to use for AR views (e.g. scan page) on Windows.<br />
* SfPullToRefresh was removed due to [[Mobile_XAML#Issues_with_SfPullToRefresh_in_Mobile_client|existing issues]], and replaced with a Refresh option in the Context menu.<br />
<br />
<br />
= ⚠️ XAML Notes =<br />
Due to the change of the underlying XAML technology, the existing XAMLs for the old mobile clients (pre 5.0) are no longer compatible. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.<br />
<br />
<br />
<headertabs /><br />
<br />
[[Category:Client|Version 5.1 (Mobile)]]<br />
[[Category:Mobile|Version 5.1 (Mobile)]]<br />
[[Category:Version 5.1|Version 5.1 (Mobile)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(WinX)&diff=29566Version 5.1 (WinX)2026-03-12T13:51:26Z<p>LGE: </p>
<hr />
<div>{{Attention|This version requires [https://en.wikipedia.org/wiki/Windows_10_version_history#Version_1809_(October_2018_Update) Windows 10 build 17763] or higher}}<br />
<br />
== Availability ==<br />
{{key press|Store}}: Publicly available in Microsoft Store.<br />
<br />
{{key press|Store Beta}} / {{key press|Store Preview}}: Publicly available in Microsoft Store as beta or preview versions to those whose account email is participating in our beta or preview test. To join, please send an email to testing@augmensys.com and provide an email address to add to the list as well as the information which test you want to join. Alternatively you can contact the Augmensys staff and submit your chosen email address.<br />
<br />
Example: Please add my email account example@example.com to the '''Beta''' test group for the '''WinX''' client.<br />
<br />
<br/><br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
=== 5.1.?? on 2026-??-?? ===<br />
* Introduced a new [[MRO_Objects_(Client)#Picture_Task|picture task]] type which can only be finished when there's at least one valid child document.<br />
* Replaced app closing after repeated failed login attempts with a client-side temporary login block, including user feedback that indicates when login becomes available again.<br />
* Added French localization to the app.<br />
* Provided a visual difference between suggested and actual values in DateTime and Geo property direct edit fields via a [[XAML#Custom_VisualState_Trigger|Custom VisualState Trigger]].<br />
<br />
<br />
=== 5.1.6 on 2026-02-10 ===<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where certain documents couldn't be loaded anymore.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed an issue where the UI did not update properly when committing a direct edit input task.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Added a [[XAML#UBIKWebView|UBIKWebView]] control that includes a fix in the WebView2 where some links could not be opened.<br />
* Fixed issue that caused input fields to be focused but not editable.<br />
* Fixed an issue where document creation might not be properly enabled in certain customizing scenarios. For example, a media creation button might be disabled until a page refresh.<br />
* Fixed an issue where batch creating documents (by multi selecting files to attach) can be interrupted if you leave the page.<br />
<br />
<br />
<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Free Text Annotations that where created in former sessions cannot be selected and therefore cannot be edited any more.<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* Known issues regarding the [[Documents_(Client)#Remember_Document_Settings|Remember Document Settings]] feature:<br />
** Saving the Zoom value via touch gestures is not supported.<br />
** Due to a third-party framework issue it can't be guaranteed that saving the Zoom level is always working properly. We reported this issue and will update our solution as soon as it is resolved on their side.<br />
<br/><br />
<br />
= ⚠️ XAML Notes =<br />
<br />
<br />
<br />
<headertabs /><br />
<br />
<br />
{{Category/Version2|{{PAGENAME}}}}<br />
<br />
[[Category:Client|Version 5.1 (WinX)]]<br />
[[Category:Version 5.1|Version 5.1 (WinX)]]<br />
[[Category:WinX|Version 5.1 (WinX)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(Mobile)&diff=29565Version 5.1 (Mobile)2026-03-12T13:50:54Z<p>LGE: </p>
<hr />
<div>{{Attention|Existing pre 5.0 XAMLs are not compatible with UBIK Mobile client 5.1. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.}}<br />
<br />
{{Attention|UBIK 5 clients can only connect to {{UBIK}} Servers of [[Version 3.6(Server)|version 3.6]] and higher!}}<br />
<br />
{{Attention|The minimum supported OS versions are:<br />
* Android 9;<br />
* iOS 12.}}<br />
<br />
== Availability ==<br />
{{key press|Android: Store}}{{key press|iOS: Store}}: Publicly available in Google Play Store / Apple App Store.<br />
<br />
{{key press|Android: Store Beta}}: Publicly available in Google Play Store as beta versions. You can opt in or out of the beta at any time in the store.<br />
<br />
{{key press|Android: Store Preview}}: Available through Google Play Store's [https://play.google.com/store/apps/details?id=com.augmensys.ubik.go invitation link].<br />
<br />
{{key press|iOS: Store Beta}}: Available through Apple App Store's [https://testflight.apple.com/join/Kmb1HG9E invitation link].<br />
<br />
{{key press|iOS: Store Preview}}: Available through Apple App Store's [https://testflight.apple.com/join/yHRnbYbt invitation link].<br />
<br />
{{key press|Windows: Store Preview}}: The mobile Windows client is not an official product and is only distributed as test versions upon request and/or in our [https://release.augmensys.com/download/modules/client/mobile/ release portal].<br />
<br/><br />
<br />
<br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with a ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
=== 5.1.?? 2026-??-?? {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Introduced a new [[MRO_Objects_(Client)#Picture_Task|picture task]] type which can only be finished when there's at least one valid child document.<br />
* The system flashlight can now also be enabled or disabled via XAML customization. For detailed information, see [[Mobile XAML#Flashlight|Flashlight]]<br />
* Replaced app closing after repeated failed login attempts with a client-side temporary login block, including user feedback that indicates when login becomes available again.<br />
* Added French localization to the app.<br />
* [[MRO_Objects_(Client)#Signature_Task|MRO Signature Tasks]] have been introduced, which automatically displays the signee as well as the validation timestamp after the task has been signed.<br />
* Fixed an issue where changes in property editing were not discarded when using the default Back button.<br />
* Fixed an issue where the application crashed on Windows when navigating back from the VideoPlayer.<br />
<br />
<br />
<br />
<br />
<br />
=== 5.1.30 2026-03-02 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Fixed an issue that prevented any documents from being uploaded when connecting to 5.1 webservices.<br />
<br />
<br />
=== 5.1.29 on 2026-02-26 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Fixed an issue where the POI button was only visible under certain condition (ShowUnreleasedFeatures in the profile is set to true).<br />
<br />
<br />
=== 5.1.28 on 2026-02-10 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* The following features which existed in pre 5.0 versions are now available again in 5.1.<br />
** [[Map_View|Map view]].<br />
** [[POI_View_(Mobile)|POI view]]. (Aruco and OCR are not yet supported)<br />
** Location service.<br />
** [[Native_Push_(Client)|Native push]].<br />
** [[Charts]].<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Complete UI overhaul introduces a cleaner, more modern and adaptive user interface with various quality of life improvements.<br />
* UBIKTabView supports both dynamic and static items in combination with lazy loading.<br />
* Files in the app's data folder can now be opened or deleted directly in the developer settings.<br />
* Introduced a fully resource-driven UI theming system enabling fast, safe customization (dark mode, resizing, and consistent styling) by adapting a small set of centralized resources.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* Fixed an issue where remembered scroll positions were lost when the ItemsSource property of an SfListViewExt changed (e.g., Properties.ShowAllProperties).<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed issue that caused app to be stuck on splash screen after resuming from background.<br />
* Fixed an issue where StatusColor was not shown in the UI for objects that didn't additionally have a Progress.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Fixed an issue that caused content of the custom ContentControl to not be rendered sometimes.<br />
* (Android) Fixed an issue in the WebView where some links could not be opened.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the deletion of some objects was not reflected in the UI until refresh.<br />
* Fixed an issue where document creation might not be properly enabled in certain customizing scenarios. For example, a media creation button might be disabled until a page refresh.<br />
* Fixed an issue where batch creating documents (by multi selecting files to attach) can be interrupted if you leave the page.<br />
<br />
<br />
<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true. In Mobile, deleting the last annotation does not correctly update the editor's internal edit state. As a result, the Save button may remain visible even though no edits exist.<br />
* When changing the device orientation during attaching a photo on iOS, the app gets stuck. This is an issue Microsoft confirmed in .NET9 and will fix in .NET10.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Currently, the Samsung keyboard doesn't show {{key press|,}} at all, regardless of the current language/locale setting of the device. Please use a different virtual keyboard (e.g. Gboard from Google) instead if {{key press|.}} is unacceptable.<br />
* The periodic execution of background pushes is not guaranteed on iOS (the native push feature doesn't have this issue).<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* It is currently not possible to select which camera to use for AR views (e.g. scan page) on Windows.<br />
* SfPullToRefresh was removed due to [[Mobile_XAML#Issues_with_SfPullToRefresh_in_Mobile_client|existing issues]], and replaced with a Refresh option in the Context menu.<br />
<br />
<br />
= ⚠️ XAML Notes =<br />
Due to the change of the underlying XAML technology, the existing XAMLs for the old mobile clients (pre 5.0) are no longer compatible. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.<br />
<br />
<br />
<headertabs /><br />
<br />
[[Category:Client|Version 5.1 (Mobile)]]<br />
[[Category:Mobile|Version 5.1 (Mobile)]]<br />
[[Category:Version 5.1|Version 5.1 (Mobile)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=MRO_Objects_(Client)&diff=29564MRO Objects (Client)2026-03-12T13:47:16Z<p>LGE: /* Picture Task {{Version/MobileSince|5.1}}{{Version/WinXSince|5.1}} */</p>
<hr />
<div>[[File:MRO_WinX.png|thumb|alt=MRO Child List UI (WinX)|MRO UI (WinX)]]<br />
[[File:MRO_MAUI1.jpeg|thumb|alt=MRO Child List UI (Android)|MRO UI (Android)]]<br />
The WinX client UI displays MRO configured objects like any other root- or child-object enriched by some additional logic and features.<br />
<br />
== Basic User Interface ==<br />
The representation of MRO features comprises some indicators and interactive controls. In the {{UBIK}} child list, the main object displays cumulated technical and organisational status as well as the overall work progress based on the underlying data branch. Objects classified as MRO objects in general provide indicators for the MRO status. This means the status is shown next to the main icon of a child-/details-/documents-page as well as next to the icons of the child list items:<br />
<br />
=== Technical Status ===<br />
<br />
The technical status indicator is shown on all objects that represent a technical state or receive the technical status from subsequent objects in the underlying data branch. If e.g. a inventory object is reported as damaged, its parent objects will all display the exclamation mark symbol to indicate that a problem was reported in the child items.<br />
<br />
[[File:TechStats_WinX.png|100px|Technical Status Indicator (Winx & Mobile)]]<br />
<br />
=== Organisational Status ===<br />
The organisational status indicates the amount of confirmed work within the data branch, including already confirmed work packages as well as tasks that are locked by their owning work package. The organisational status indicator is displayed on all objects that represent an organisational state or receive the organisational status from subsequent objects in the underlying data branch, and visualizes the amount of confirmed work performed within that branch.<br />
<gallery><br />
File:UI_WinX_MRO_OrganisationalStatusIndicator.png|Organisational Status Indicator (WinX)<br />
File:ConfirmedWP_WinX.png|MRO Workpackage Confirmed (Flag) Indicator (WinX)<br />
File:Android_orga_status.PNG|Organisational Status Indicator (Android)<br />
File:ConfirmedWP_MAUI.jpeg|MRO Workpackage Confirmed Indicator (Mobile)<br />
</gallery><br />
<br />
<br />
=== Work Progress ===<br />
The work progress is calculated from the current work progress and from the progress cumulated from subsequent objects in the underlying data branch. This indicator shows the amount of work done in the data branch.<br />
<br />
{{Version/WinXSince|5.0}} {{Version/MobileSince|5.0}} By default, the progress is displayed with maximum one decimal place. For example, 99.75% is displayed as 99.8%. The format string used to achieve this is <code>{0:0.#}%</code>.<br />
<br />
If other numeric formats are preferred in your usecases, you can refer to [https://learn.microsoft.com/en-us/dotnet/standard/base-types/custom-numeric-format-strings custom numeric format strings] for more information. The template to customize for this is the UBIKMROProgressBadge within UBIKThemes.<br />
<br />
{{Clear}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== MRO Objects ==<br />
A set of specific objects can be used to provide the required structure for MRO:<br />
<br />
=== Task Owner ===<br />
A [[MROCLS_MRO_TASKOWNER|Task Owner]] is an object having a substructure of jobs to be done. It can have a tree of other task owners or work packages underneath that will update the status of the task owner. This status consists of technical, organisational and progress information. With a task owner a user can get an overview of all the work to be done in the underlying job structure.<br />
<br />
=== Work Package===<br />
A [[MROCLS_MRO_WORKPACKAGE|Work Package]] is a collection of objects to collect and summarize other task owning objects, workpackages, or tasks. A simple workpackage has a certain amount of tasks that have to be finished in order to confirm the workpackage as done. More complex workpackages can also own other underlying workpackages that have to be confirmed. Confirming a workpackage itself requires a progress of 100% of all related tasks, as well as 100% confirmed sub work packages.<br />
<br />
<gallery><br />
File:ConfirmingWP_WinX.png|MRO Workpackage confirm button (WinX)<br />
File:MRORevoke_WinX.png|MRO Workpackage revoke confirmation button (WinX)<br />
File:ConfirmingWP_MAUI.jpeg|MRO Workpackage confirm button (Android)<br />
File:MRORevoke_MAUI.jpeg|MRO Workpackage revoke confirmation button (Android)<br />
</gallery><br />
<br />
=== Task ===<br />
A [[MROCLS_MRO_TASK|Task]] is an object reporting a certain progress to the owning workpackage. There are several specialized types of task objects. All kinds of tasks have a property called '''VALUE''' in common. It is very important, that this property is able to be validated. Therefore, a MetaAttribute (providing a validation timestamp by default) has to be attached on the used MetaProperty.<br />
<br />
On both clients, a Task can be reverted by clicking twice on the Not Applicable button.<br />
<br />
<br />
<br />
{{Attention|The MetaProperty ''VALUE'' has to use [[Attributes]] in order to be validated. Otherwise, the calculation of work progress will not be possible.}}<br />
<br />
==== Measurement Task ====<br />
<br />
A [[MROCLS_MRO_MEASUREMENT_TASK|Measurement Task]] inherits from [[MROCLS_MRO_TASK|Task]] and documents a measured value (e.g. read from a pressure gauge). Therefore, clicking the value on the shown task opens an editor to enter the desired value. If no value was entered before, an empty line will be shown. Once a value has been entered, the task is finished. Alternatively, the task can also be closed by the option ''Not Applicable'' to document the situation of not being able to fullfill the measurement (e.g. the pressure gauge is broken). An additional small value indicator below the main value can report e.g. the previously entered value. The behaviour of this previous value indicator has to be specified separately in the customizing.<br />
{{Clear}}<br />
<br />
<gallery widths=497px heights=69px><br />
File:Measurment Task Empty UWP.png|Measurement Task without a reported value (WinX)<br />
File:Measurment Task Not Empty UWP.png|Measurement Task with a reported value (WinX)<br />
File:Measurment Task Empty Android.jpg|Measurement Task without a reported value (Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
==== Progress Task ====<br />
<br />
[[MROCLS_MRO_PROGRESS_TASK| Progress Task]] inherits from [[MROCLS_MRO_MEASUREMENT_TASK|Task]] and reports a certain progress while fullfilling a task. The progress will influence the overall progress of the owning workpackage. If the task cannot be fullfilled, it can also be finished with the option ''Not Applicable''.<br />
<br />
There is also an [[MRO_PROGRESS_TASK_EDITOR|alternative editor]] available for progress tasks.{{Version/WinXSince|2.5.4}}<br />
{{Clear}}<br />
<br />
<gallery widths=497px heights=69px><br />
File:Progress Task UWP.png|Progress Task with a reported work progress (WinX)<br />
File:Progress Task Android.jpg|Progress Task with a reported work progress and a previous progress(Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
==== Check Task ====<br />
<br />
A [[MROCLS_MRO_CHECK_TASK|Check Task]] inherits from [[MROCLS_MRO_TASK|Task]] and is finished by reporting ''Done'' or ''Not Applicable''. This is intended for a simple To-Do task that is either done or not.<br />
{{Clear}}<br />
<br />
<gallery widths=497px heights=69px><br />
File:Check Task finished UWP.png|Unfinished MRO CheckTask (WinX)<br />
File:Check Task android.jpg|Not Applicable MRO CheckTask (Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
==== Inspection Task ====<br />
<br />
[[MROCLS_MRO_INSPECTION_TASK|Inspection Task]] inherits from [[MROCLS_MRO_TASK|Task]] and is finished, when the user reports with a positive or negative answer or ''Not Applicable'' (e.g. reporting a yes/no answer for existing equipment).<br />
{{Clear}}<br />
<br />
<gallery widths=497px heights=69px><br />
File:Finished Inspection Task UWP.png|Finished MRO InspectionTask (WinX)<br />
File:Inspection task android.jpg|Finished MRO InspectionTask (Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
==== Sequential Task ====<br />
The [[MROCLS_SEQUENTIALTASK|sequential task classification]] allows you to pre-define a sequence in which tasks are to be resolved by users. This means that it is required for one or multiple tasks to be finished in order for other tasks to become "unlocked" and editable. A task can have any number of "predecessors". Predecessors are the tasks that are required to be finished first.<br />
<br />
A task can have predecessors that live anywhere else in the object hierarchy. It is not necessary for a task and its predecessors to be part of the same work package, even though this is likely the most common use case.<br />
<br />
The state of a sequential task is evaluated both offline and online to get the best possible user experience. The user will see dependent tasks update immediately if their successors were finished, if those tasks are currently visible in the UI. There is 1 case in which the server-side state will override the client-side (offline) evaluation, discussed below.<br />
The state of each sequential task is evaluated the following way:<br />
<br />
# If the server-side state says the task is open, we consider this as the truthful state and don't do any other evaluation.<br />
# Check if the task has any predecessors.<br />
# Try to load each predecessor task.<br />
#* If loading of any predecessor fails (the object is not available offline), the task will be locked.<br />
# If all predecessor tasks are finished, the task is open and can be edited. Otherwise, the task is locked.<br />
<br />
The customizer setting up the task dependency relations needs to ensure that the dependencies are not cyclical. In this case, it would be impossible for any tasks in the "cycle" to be finished.<br />
<br />
'''Example'''<br />
<br />
As a demonstration of this feature, see [[Media:Sequential_tasks_winx.mp4|this video]]. The relations between tasks are defined as in [[Media:Task_relations.png|this image]], starting at A1 and A2, which are not dependent on any other tasks. The lines (from left to right) indicate dependencies. This means that B2 has tasks A1 and A2 as its predecessors, for example.<br />
<br />
<br />
==== Grouped Task {{Version/WinXSince|4.2}}{{Version/XamarinSince|4.2}} ====<br />
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 [[MROCLS_GROUPEDTASK|grouped tasks]].<br />
<br />
The idea is, a group of tasks can be defined as siblings to each other and they also share the same server configured threshold. When the number of finished tasks among that group exceeds the threshold, the entire group is considered as no longer necessary. When reflected in the overall status of the task owner(s), these tasks would appear as if they are finished.<br />
<br />
{{Hint|Technically speaking, the finished status is completely independent from the not necessary status on a task. A grouped task which is no longer necessary can be both finished or not yet finished. In other words, users don't have to finish a not necessary grouped task, but they still can.}}<br />
<br />
{{Hint|The precise status calculation for grouped tasks and their task owners requires the knowledge of all siblings tasks. Imagine 2 out of 3 tasks must be finished but the client only knows 1 in total and the others are only available at the server at that time. This makes it impossible to draw conclusions whether the task(s) should be necessary or not. Under such circumstances, the local status calculation is done as if these are just regular tasks.}}<br />
<br />
{{Hint|Like with the other MRO objects, the client always chooses the best available statuses for grouped tasks to present to the users. More specifically, it uses the statuses calculated by the server when the client is not offline and there are no uncommitted local changes on the involved objects. Otherwise, it uses the statuses calculated locally to the best of its knowledge.}}<br />
<br />
A task can also be a grouped and a sequential one at the same time. In such a case, the grouped nature of the sibling tasks will affect the way the task sequence completes.<br />
<br />
For example, task A1, A2 and A3 are 3 grouped sibling tasks and only 1 of them needs to be finished. At the same time, they are all predecessors of task B. Normally, all predecessors must be finished (and locked) before task B becomes the next one in the sequence and therefore unlocked. In this case, however, as soon as one of the predecessors is finished, all three become unnecessary (and locked) and task B unlocks as a result of that.<br />
<br />
<br />
==== Supervisor Task {{Version/XamarinSince|4.8}} ====<br />
As the name suggests, supervisor tasks are those that must be finished under supervision. When users want to finish a [[MROCLS_MRO_SUPERVISOR_TASK|supervisor task]], they must hand over their work devices to a supervisor. The latter checks the work status and scans an NFC tag if the work is approved. If the [[MROCLS_MRO_SUPERVISOR|supervisor]] has sufficient permissions for the task and the correct supervisor PIN is given, the task gets unlocked and the users can proceed to finish it.<br />
<br />
<gallery widths=300px heights=300px><br />
File:UI_Xamarin_Supervisor_Task_Before_Verification.jpg|Supervisor Task Before Verification/Unlocking (Mobile)<br />
File:UI_Xamarin_Supervisor_Task_Enter_PIN.jpg|Supervisor Task Enter PIN (Mobile)<br />
File:UI_Xamarin_Supervisor_Task_After_Verification.jpg|Supervisor Task After Verification/Unlocking (Mobile)<br />
</gallery><br />
<br />
A thing to note is that while the need to verify a supervisor task can be seen as a type of locking, it's certainly not the only reason for a [[Locked_Objects|locked object]]. This means a supervisor task can remain locked (although for different reasons) even after a supervisor has successfully verified it. This can often be the case if you use it in combination with other features such as [[MRO_Objects_(Client)#Sequential_Task|sequential tasks]], [[User_Rights|user rights]].<br />
<br />
{{Hint|For security reasons, the verification process is cancelled if the supervisor enters the wrong PIN for three times. Scanning the tag again is required in that case.}}<br />
{{Hint|A setting controls [[RFID_tags#Choose_which_information_to_use_from_a_tag|which information in a scanned tag is used]] during this process.}}<br />
<br />
==== Signature Task {{Version/MobileSince|5.1}}{{Version/WinXSince|5.1}} ====<br />
<br />
The Signature Task is a task type that is completed by capturing a handwritten signature from the user. The task contains an editor field that serves as the entry point for the signing process. When the user clicks (or taps) on the editor field, a signature dialog opens. Within this dialog, the user can provide their signature. After confirming the input, the signature is saved and the task is automatically marked as completed.<br />
<br />
If the task is signed while the client is online:<br />
* The User (signee) is resolved immediately by the server and displayed.<br />
* The ValidationTimestamp is generated and displayed.<br />
* Both values are shown directly in the editor field after signing.<br />
<br />
{{Hint|The User only gets resolved by the server and displayed once you're in online mode}}<br />
<br />
If the displayed User and/or ValidationTimestamp cannot be fully shown due to limited space in the editor field, the complete information can be accessed via a tooltip.<br />
<br />
* In '''UBIK WinX (UWP)''', hover over the editor field with the mouse.<br />
* In '''UBIK Mobile''', perform a long press on the editor field.<br />
A tooltip will appear, displaying the full User and ValidationTimestamp without truncation.<br />
<br />
==== Picture Task {{Version/MobileSince|5.1}}{{Version/WinXSince|5.1}} ====<br />
<br />
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.<br />
* As any other objects, picture tasks can carry and display [[SYSCLS_CHILDINFOOWNER|child count information]]. But that is not a mandatory part of the feature. Even when it's not configured and not visible in the UI, you can still finish the tasks.<br />
* In WinX/UWP, the UI also presents an expander which allows you to display the child documents of picture tasks. This is not present by default in the Mobile app due to the screen size limit but [[Object_hierarchy_in_XAML:_NextLevel,_ParentLevel,_LinkedLevel#Show_NextLevel_Children.2FDocuments|can be easily customized]].<br />
<br />
{{Hint|The task is named as such because pictures are the most commonly used types, but the child documents can be of other types as well. }}<br />
<br />
When a user tries to finish a picture task by tapping the check, the app might perform some data synchronization first if in online mode, which includes<br />
* Syncing the child objects (including documents) of the task.<br />
* Downloading the file(s) of the child documents.<br />
During data synchronization, the check button on that task turns into a wait indicator. Afterwards, the app checks if the prerequisites to finish the task are met.<br />
* If there are no child documents or no local files for the child documents, the task remains unfinished and the user gets informed about the reasons.<br />
* Otherwise, the task gets finished and the photo button gets disabled.<br />
<br />
{{Hint|Setting NA (not applicable) on a picture task is always possible, regardless of the condition of child documents.}}<br />
<br />
[[Category:Android|MRO Objects (UBIK WinX)]]<br />
[[Category:Client|MRO Objects (Client)]]<br />
[[Category:Mobile|MRO Objects (Client)]]<br />
[[Category:Pages with broken file links|MRO Objects (Client)]]<br />
[[Category:WinX|MRO Objects (UBIK WinX)]]<br />
<br />
=== MRO objects with project information (WinX only) {{Version/WinXSince|2.5.4}} ===<br />
[[File:UI_WinX_MRO_ProjectInfo.png|thumb|MRO Object with Project Info (WinX)]]<br />
An MRO object (except tasks) might also bring along [[MROCLS_PROJECTINFORMATION|project information]]. In this case, the project information together with the MRO progress are displayed in a bar chart. The start & end dates of the MRO object are displayed on the progress bar. The length and the position of the progress bar, together with the current date mark indicate the timeline.<br />
{{Clear}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Locking ==<br />
When an (MRO) object is locked, editing it becomes impossible. More details about [[Locked_Objects|locked objects]].<br />
<br />
<br />
<br />
<br />
== See also ==<br />
* [[MRO (Plugin)]]<br />
* [[MROCLS_PROJECT]]<br />
* [[MROCLS_PROJECTINFORMATION]]<br />
* [[MROCLS_SEQUENTIALTASK]]<br />
* [[MROCLS_GROUPEDTASK]]<br />
* [[MROCLS_MRO_CHECK_TASK]]<br />
* [[MROCLS_MRO_INSPECTION_TASK]]<br />
* [[MROCLS_MRO_MEASUREMENT_TASK]]<br />
* [[MROCLS_MRO_PROGRESS_TASK]]<br />
* [[MROCLS_MRO_TASK]]<br />
* [[MROCLS_MRO_TASKOWNER]]<br />
* [[MROCLS_MRO_WORKPACKAGE]]<br />
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)<br />
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)<br />
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)<br />
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)<br />
<br />
[[Category:Android|MRO Objects (UBIK WinX)]]<br />
[[Category:Client|MRO Objects (Client)]]<br />
[[Category:Mobile|MRO Objects (Client)]]<br />
[[Category:Pages with broken file links|MRO Objects (Client)]]<br />
[[Category:WinX|MRO Objects (UBIK WinX)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=MRO_Objects_(Client)&diff=29512MRO Objects (Client)2026-03-10T16:07:36Z<p>LGE: /* Picture Task {{Version/MobileSince|5.1}}{{Version/WinXSince|5.1}} */</p>
<hr />
<div>[[File:UI_WinX_MRO_ChildList.png|thumb|alt=MRO Child List UI (WinX)|MRO UI (WinX)]]<br />
[[File:Android_mro_ui.jpg|thumb|alt=MRO Child List UI (Android)|MRO UI (Android)]]<br />
The WinX client UI displays MRO configured objects like any other root- or child-object enriched by some additional logic and features.<br />
<br />
== Basic User Interface ==<br />
The representation of MRO features comprises some indicators and interactive controls. In the {{UBIK}} child list, the main object displays cumulated technical and organisational status as well as the overall work progress based on the underlying data branch. Objects classified as MRO objects in general provide indicators for the MRO status. This means the status is shown next to the main icon of a child-/details-/documents-page as well as next to the icons of the child list items:<br />
<br />
=== Technical Status ===<br />
<br />
The technical status indicator is shown on all objects that represent a technical state or receive the technical status from subsequent objects in the underlying data branch. If e.g. a inventory object is reported as damaged, its parent objects will all display the exclamation mark symbol to indicate that a problem was reported in the child items.<br />
<br />
<gallery><br />
File:UI_WinX_MRO_TechnicalStatusIndicator.png|thumb|Technical Status Indicator (WinX)<br />
File:Android_tech_status.PNG|thumb|Technical Status Indicator (Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
=== Organisational Status ===<br />
The organisational status indicates the amount of confirmed work within the data branch, including already confirmed work packages as well as tasks that are locked by their owning work package. The organisational status indicator is displayed on all objects that represent an organisational state or receive the organisational status from subsequent objects in the underlying data branch, and visualizes the amount of confirmed work performed within that branch.<br />
<gallery><br />
File:UI_WinX_MRO_OrganisationalStatusIndicator.png|Organisational Status Indicator (WinX)<br />
File:UI_WinX_MRO_WPConfirmedIndicator.png|MRO Workpackage Confirmed (Flag) Indicator (WinX)<br />
File:Android_orga_status.PNG|Organisational Status Indicator (Android)<br />
File:Android_orga_status_finished.PNG|MRO Workpackage Confirmed Indicator (Android)<br />
</gallery><br />
<br />
<br />
=== Work Progress ===<br />
The work progress is calculated from the current work progress and from the progress cumulated from subsequent objects in the underlying data branch. This indicator shows the amount of work done in the data branch.<br />
<br />
{{Version/WinXSince|5.0}} {{Version/MobileSince|5.0}} By default, the progress is displayed with maximum one decimal place. For example, 99.75% is displayed as 99.8%. The format string used to achieve this is <code>{0:0.#}%</code>.<br />
<br />
If other numeric formats are preferred in your usecases, you can refer to [https://learn.microsoft.com/en-us/dotnet/standard/base-types/custom-numeric-format-strings custom numeric format strings] for more information. The template to customize for this is the UBIKMROProgressBadge within UBIKThemes.<br />
<br />
{{Clear}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== MRO Objects ==<br />
A set of specific objects can be used to provide the required structure for MRO:<br />
<br />
=== Task Owner ===<br />
A [[MROCLS_MRO_TASKOWNER|Task Owner]] is an object having a substructure of jobs to be done. It can have a tree of other task owners or work packages underneath that will update the status of the task owner. This status consists of technical, organisational and progress information. With a task owner a user can get an overview of all the work to be done in the underlying job structure.<br />
<br />
=== Work Package===<br />
A [[MROCLS_MRO_WORKPACKAGE|Work Package]] is a collection of objects to collect and summarize other task owning objects, workpackages, or tasks. A simple workpackage has a certain amount of tasks that have to be finished in order to confirm the workpackage as done. More complex workpackages can also own other underlying workpackages that have to be confirmed. Confirming a workpackage itself requires a progress of 100% of all related tasks, as well as 100% confirmed sub work packages.<br />
<br />
<gallery><br />
File:UI_WinX_MRO_WPConfirmButton.png|MRO Workpackage confirm button (WinX)<br />
File:UI_WinX_MRO_WPRevokeConfirmButton.png|MRO Workpackage revoke confirmation button (WinX)<br />
File:Android_finish_workpackage.PNG|MRO Workpackage confirm button (Android)<br />
File:Android reopen workpackage.PNG|MRO Workpackage revoke confirmation button (Android)<br />
</gallery><br />
<br />
=== Task ===<br />
A [[MROCLS_MRO_TASK|Task]] is an object reporting a certain progress to the owning workpackage. There are several specialized types of task objects. All kinds of tasks have a property called '''VALUE''' in common. It is very important, that this property is able to be validated. Therefore, a MetaAttribute (providing a validation timestamp by default) has to be attached on the used MetaProperty.<br />
<br />
On both clients, a Task can be reverted by clicking twice on the Not Applicable button.<br />
<br />
<br />
<br />
{{Attention|The MetaProperty ''VALUE'' has to use [[Attributes]] in order to be validated. Otherwise, the calculation of work progress will not be possible.}}<br />
<br />
==== Measurement Task ====<br />
<br />
A [[MROCLS_MRO_MEASUREMENT_TASK|Measurement Task]] inherits from [[MROCLS_MRO_TASK|Task]] and documents a measured value (e.g. read from a pressure gauge). Therefore, clicking the value on the shown task opens an editor to enter the desired value. If no value was entered before, an empty line will be shown. Once a value has been entered, the task is finished. Alternatively, the task can also be closed by the option ''Not Applicable'' to document the situation of not being able to fullfill the measurement (e.g. the pressure gauge is broken). An additional small value indicator below the main value can report e.g. the previously entered value. The behaviour of this previous value indicator has to be specified separately in the customizing.<br />
{{Clear}}<br />
<br />
<gallery widths=497px heights=69px><br />
File:Measurment Task Empty UWP.png|Measurement Task without a reported value (WinX)<br />
File:Measurment Task Not Empty UWP.png|Measurement Task with a reported value (WinX)<br />
File:Measurment Task Empty Android.jpg|Measurement Task without a reported value (Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
==== Progress Task ====<br />
<br />
[[MROCLS_MRO_PROGRESS_TASK| Progress Task]] inherits from [[MROCLS_MRO_MEASUREMENT_TASK|Task]] and reports a certain progress while fullfilling a task. The progress will influence the overall progress of the owning workpackage. If the task cannot be fullfilled, it can also be finished with the option ''Not Applicable''.<br />
<br />
There is also an [[MRO_PROGRESS_TASK_EDITOR|alternative editor]] available for progress tasks.{{Version/WinXSince|2.5.4}}<br />
{{Clear}}<br />
<br />
<gallery widths=497px heights=69px><br />
File:Progress Task UWP.png|Progress Task with a reported work progress (WinX)<br />
File:Progress Task Android.jpg|Progress Task with a reported work progress and a previous progress(Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
==== Check Task ====<br />
<br />
A [[MROCLS_MRO_CHECK_TASK|Check Task]] inherits from [[MROCLS_MRO_TASK|Task]] and is finished by reporting ''Done'' or ''Not Applicable''. This is intended for a simple To-Do task that is either done or not.<br />
{{Clear}}<br />
<br />
<gallery widths=497px heights=69px><br />
File:Check Task finished UWP.png|Unfinished MRO CheckTask (WinX)<br />
File:Check Task android.jpg|Not Applicable MRO CheckTask (Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
==== Inspection Task ====<br />
<br />
[[MROCLS_MRO_INSPECTION_TASK|Inspection Task]] inherits from [[MROCLS_MRO_TASK|Task]] and is finished, when the user reports with a positive or negative answer or ''Not Applicable'' (e.g. reporting a yes/no answer for existing equipment).<br />
{{Clear}}<br />
<br />
<gallery widths=497px heights=69px><br />
File:Finished Inspection Task UWP.png|Finished MRO InspectionTask (WinX)<br />
File:Inspection task android.jpg|Finished MRO InspectionTask (Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
==== Sequential Task ====<br />
The [[MROCLS_SEQUENTIALTASK|sequential task classification]] allows you to pre-define a sequence in which tasks are to be resolved by users. This means that it is required for one or multiple tasks to be finished in order for other tasks to become "unlocked" and editable. A task can have any number of "predecessors". Predecessors are the tasks that are required to be finished first.<br />
<br />
A task can have predecessors that live anywhere else in the object hierarchy. It is not necessary for a task and its predecessors to be part of the same work package, even though this is likely the most common use case.<br />
<br />
The state of a sequential task is evaluated both offline and online to get the best possible user experience. The user will see dependent tasks update immediately if their successors were finished, if those tasks are currently visible in the UI. There is 1 case in which the server-side state will override the client-side (offline) evaluation, discussed below.<br />
The state of each sequential task is evaluated the following way:<br />
<br />
# If the server-side state says the task is open, we consider this as the truthful state and don't do any other evaluation.<br />
# Check if the task has any predecessors.<br />
# Try to load each predecessor task.<br />
#* If loading of any predecessor fails (the object is not available offline), the task will be locked.<br />
# If all predecessor tasks are finished, the task is open and can be edited. Otherwise, the task is locked.<br />
<br />
The customizer setting up the task dependency relations needs to ensure that the dependencies are not cyclical. In this case, it would be impossible for any tasks in the "cycle" to be finished.<br />
<br />
'''Example'''<br />
<br />
As a demonstration of this feature, see [[Media:Sequential_tasks_winx.mp4|this video]]. The relations between tasks are defined as in [[Media:Task_relations.png|this image]], starting at A1 and A2, which are not dependent on any other tasks. The lines (from left to right) indicate dependencies. This means that B2 has tasks A1 and A2 as its predecessors, for example.<br />
<br />
<br />
==== Grouped Task {{Version/WinXSince|4.2}}{{Version/XamarinSince|4.2}} ====<br />
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 [[MROCLS_GROUPEDTASK|grouped tasks]].<br />
<br />
The idea is, a group of tasks can be defined as siblings to each other and they also share the same server configured threshold. When the number of finished tasks among that group exceeds the threshold, the entire group is considered as no longer necessary. When reflected in the overall status of the task owner(s), these tasks would appear as if they are finished.<br />
<br />
{{Hint|Technically speaking, the finished status is completely independent from the not necessary status on a task. A grouped task which is no longer necessary can be both finished or not yet finished. In other words, users don't have to finish a not necessary grouped task, but they still can.}}<br />
<br />
{{Hint|The precise status calculation for grouped tasks and their task owners requires the knowledge of all siblings tasks. Imagine 2 out of 3 tasks must be finished but the client only knows 1 in total and the others are only available at the server at that time. This makes it impossible to draw conclusions whether the task(s) should be necessary or not. Under such circumstances, the local status calculation is done as if these are just regular tasks.}}<br />
<br />
{{Hint|Like with the other MRO objects, the client always chooses the best available statuses for grouped tasks to present to the users. More specifically, it uses the statuses calculated by the server when the client is not offline and there are no uncommitted local changes on the involved objects. Otherwise, it uses the statuses calculated locally to the best of its knowledge.}}<br />
<br />
A task can also be a grouped and a sequential one at the same time. In such a case, the grouped nature of the sibling tasks will affect the way the task sequence completes.<br />
<br />
For example, task A1, A2 and A3 are 3 grouped sibling tasks and only 1 of them needs to be finished. At the same time, they are all predecessors of task B. Normally, all predecessors must be finished (and locked) before task B becomes the next one in the sequence and therefore unlocked. In this case, however, as soon as one of the predecessors is finished, all three become unnecessary (and locked) and task B unlocks as a result of that.<br />
<br />
<br />
==== Supervisor Task {{Version/XamarinSince|4.8}} ====<br />
As the name suggests, supervisor tasks are those that must be finished under supervision. When users want to finish a [[MROCLS_MRO_SUPERVISOR_TASK|supervisor task]], they must hand over their work devices to a supervisor. The latter checks the work status and scans an NFC tag if the work is approved. If the [[MROCLS_MRO_SUPERVISOR|supervisor]] has sufficient permissions for the task and the correct supervisor PIN is given, the task gets unlocked and the users can proceed to finish it.<br />
<br />
<gallery widths=300px heights=300px><br />
File:UI_Xamarin_Supervisor_Task_Before_Verification.jpg|Supervisor Task Before Verification/Unlocking (Mobile)<br />
File:UI_Xamarin_Supervisor_Task_Enter_PIN.jpg|Supervisor Task Enter PIN (Mobile)<br />
File:UI_Xamarin_Supervisor_Task_After_Verification.jpg|Supervisor Task After Verification/Unlocking (Mobile)<br />
</gallery><br />
<br />
A thing to note is that while the need to verify a supervisor task can be seen as a type of locking, it's certainly not the only reason for a [[Locked_Objects|locked object]]. This means a supervisor task can remain locked (although for different reasons) even after a supervisor has successfully verified it. This can often be the case if you use it in combination with other features such as [[MRO_Objects_(Client)#Sequential_Task|sequential tasks]], [[User_Rights|user rights]].<br />
<br />
{{Hint|For security reasons, the verification process is cancelled if the supervisor enters the wrong PIN for three times. Scanning the tag again is required in that case.}}<br />
{{Hint|A setting controls [[RFID_tags#Choose_which_information_to_use_from_a_tag|which information in a scanned tag is used]] during this process.}}<br />
<br />
==== Signature Task {{Version/MobileSince|5.1}}{{Version/WinXSince|5.1}} ====<br />
<br />
The Signature Task is a task type that is completed by capturing a handwritten signature from the user. The task contains an editor field that serves as the entry point for the signing process. When the user clicks (or taps) on the editor field, a signature dialog opens. Within this dialog, the user can provide their signature. After confirming the input, the signature is saved and the task is automatically marked as completed.<br />
<br />
If the task is signed while the client is online:<br />
* The User (signee) is resolved immediately by the server and displayed.<br />
* The ValidationTimestamp is generated and displayed.<br />
* Both values are shown directly in the editor field after signing.<br />
<br />
{{Hint|The User only gets resolved by the server and displayed once you're in online mode}}<br />
<br />
If the displayed User and/or ValidationTimestamp cannot be fully shown due to limited space in the editor field, the complete information can be accessed via a tooltip.<br />
<br />
* In '''UBIK WinX (UWP)''', hover over the editor field with the mouse.<br />
* In '''UBIK Mobile''', perform a long press on the editor field.<br />
A tooltip will appear, displaying the full User and ValidationTimestamp without truncation.<br />
<br />
==== Picture Task {{Version/MobileSince|5.1}}{{Version/WinXSince|5.1}} ====<br />
<br />
{{UnderConstructionStart}}<br />
<br />
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.<br />
* As any other objects, picture tasks can carry and display [[SYSCLS_CHILDINFOOWNER|child count information]]. But that is not a mandatory part of the feature. Even when it's not configured and not visible in the UI, you can still finish the tasks.<br />
* In WinX/UWP, the UI also presents an expander which allows you to display the child documents of picture tasks. This is not present by default in the Mobile app due to the screen size limit but [[Object_hierarchy_in_XAML:_NextLevel,_ParentLevel,_LinkedLevel#Show_NextLevel_Children.2FDocuments|can be easily customized]].<br />
<br />
{{Hint|The task is named as such because pictures are the most commonly used types, but the child documents can be of other types as well. }}<br />
<br />
When a user tries to finish a picture task by tapping the check, the app might perform some data synchronization first if in online mode, which includes<br />
* Syncing the child objects (including documents) of the task.<br />
* Downloading the file(s) of the child documents.<br />
During data synchronization, the check button on that task turns into a wait indicator. Afterwards, the app checks if the prerequisites to finish the task are met.<br />
* If there are no child documents or no local files for the child documents, the task remains unfinished and the user gets informed about the reasons.<br />
* Otherwise, the task gets finished and the photo button gets disabled.<br />
<br />
{{Hint|Setting NA (not applicable) on a picture task is always possible, regardless of the condition of child documents.}}<br />
<br />
{{UnderConstructionEnd}}<br />
<br />
[[Category:Android|MRO Objects (UBIK WinX)]]<br />
[[Category:Client|MRO Objects (Client)]]<br />
[[Category:Mobile|MRO Objects (Client)]]<br />
[[Category:Pages with broken file links|MRO Objects (Client)]]<br />
[[Category:WinX|MRO Objects (UBIK WinX)]]<br />
<br />
=== MRO objects with project information (WinX only) {{Version/WinXSince|2.5.4}} ===<br />
[[File:UI_WinX_MRO_ProjectInfo.png|thumb|MRO Object with Project Info (WinX)]]<br />
An MRO object (except tasks) might also bring along [[MROCLS_PROJECTINFORMATION|project information]]. In this case, the project information together with the MRO progress are displayed in a bar chart. The start & end dates of the MRO object are displayed on the progress bar. The length and the position of the progress bar, together with the current date mark indicate the timeline.<br />
{{Clear}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Locking ==<br />
When an (MRO) object is locked, editing it becomes impossible. More details about [[Locked_Objects|locked objects]].<br />
<br />
<br />
<br />
<br />
== See also ==<br />
* [[MRO (Plugin)]]<br />
* [[MROCLS_PROJECT]]<br />
* [[MROCLS_PROJECTINFORMATION]]<br />
* [[MROCLS_SEQUENTIALTASK]]<br />
* [[MROCLS_GROUPEDTASK]]<br />
* [[MROCLS_MRO_CHECK_TASK]]<br />
* [[MROCLS_MRO_INSPECTION_TASK]]<br />
* [[MROCLS_MRO_MEASUREMENT_TASK]]<br />
* [[MROCLS_MRO_PROGRESS_TASK]]<br />
* [[MROCLS_MRO_TASK]]<br />
* [[MROCLS_MRO_TASKOWNER]]<br />
* [[MROCLS_MRO_WORKPACKAGE]]<br />
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)<br />
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)<br />
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)<br />
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)<br />
<br />
[[Category:Android|MRO Objects (UBIK WinX)]]<br />
[[Category:Client|MRO Objects (Client)]]<br />
[[Category:Mobile|MRO Objects (Client)]]<br />
[[Category:Pages with broken file links|MRO Objects (Client)]]<br />
[[Category:WinX|MRO Objects (UBIK WinX)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=MRO_Objects_(Client)&diff=29455MRO Objects (Client)2026-03-06T11:47:37Z<p>LGE: </p>
<hr />
<div>[[File:UI_WinX_MRO_ChildList.png|thumb|alt=MRO Child List UI (WinX)|MRO UI (WinX)]]<br />
[[File:Android_mro_ui.jpg|thumb|alt=MRO Child List UI (Android)|MRO UI (Android)]]<br />
The WinX client UI displays MRO configured objects like any other root- or child-object enriched by some additional logic and features.<br />
<br />
== Basic User Interface ==<br />
The representation of MRO features comprises some indicators and interactive controls. In the {{UBIK}} child list, the main object displays cumulated technical and organisational status as well as the overall work progress based on the underlying data branch. Objects classified as MRO objects in general provide indicators for the MRO status. This means the status is shown next to the main icon of a child-/details-/documents-page as well as next to the icons of the child list items:<br />
<br />
=== Technical Status ===<br />
<br />
The technical status indicator is shown on all objects that represent a technical state or receive the technical status from subsequent objects in the underlying data branch. If e.g. a inventory object is reported as damaged, its parent objects will all display the exclamation mark symbol to indicate that a problem was reported in the child items.<br />
<br />
<gallery><br />
File:UI_WinX_MRO_TechnicalStatusIndicator.png|thumb|Technical Status Indicator (WinX)<br />
File:Android_tech_status.PNG|thumb|Technical Status Indicator (Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
=== Organisational Status ===<br />
The organisational status indicates the amount of confirmed work within the data branch, including already confirmed work packages as well as tasks that are locked by their owning work package. The organisational status indicator is displayed on all objects that represent an organisational state or receive the organisational status from subsequent objects in the underlying data branch, and visualizes the amount of confirmed work performed within that branch.<br />
<gallery><br />
File:UI_WinX_MRO_OrganisationalStatusIndicator.png|Organisational Status Indicator (WinX)<br />
File:UI_WinX_MRO_WPConfirmedIndicator.png|MRO Workpackage Confirmed (Flag) Indicator (WinX)<br />
File:Android_orga_status.PNG|Organisational Status Indicator (Android)<br />
File:Android_orga_status_finished.PNG|MRO Workpackage Confirmed Indicator (Android)<br />
</gallery><br />
<br />
<br />
=== Work Progress ===<br />
The work progress is calculated from the current work progress and from the progress cumulated from subsequent objects in the underlying data branch. This indicator shows the amount of work done in the data branch.<br />
<br />
{{Version/WinXSince|5.0}} {{Version/MobileSince|5.0}} By default, the progress is displayed with maximum one decimal place. For example, 99.75% is displayed as 99.8%. The format string used to achieve this is <code>{0:0.#}%</code>.<br />
<br />
If other numeric formats are preferred in your usecases, you can refer to [https://learn.microsoft.com/en-us/dotnet/standard/base-types/custom-numeric-format-strings custom numeric format strings] for more information. The template to customize for this is the UBIKMROProgressBadge within UBIKThemes.<br />
<br />
{{Clear}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== MRO Objects ==<br />
A set of specific objects can be used to provide the required structure for MRO:<br />
<br />
=== Task Owner ===<br />
A [[MROCLS_MRO_TASKOWNER|Task Owner]] is an object having a substructure of jobs to be done. It can have a tree of other task owners or work packages underneath that will update the status of the task owner. This status consists of technical, organisational and progress information. With a task owner a user can get an overview of all the work to be done in the underlying job structure.<br />
<br />
=== Work Package===<br />
A [[MROCLS_MRO_WORKPACKAGE|Work Package]] is a collection of objects to collect and summarize other task owning objects, workpackages, or tasks. A simple workpackage has a certain amount of tasks that have to be finished in order to confirm the workpackage as done. More complex workpackages can also own other underlying workpackages that have to be confirmed. Confirming a workpackage itself requires a progress of 100% of all related tasks, as well as 100% confirmed sub work packages.<br />
<br />
<gallery><br />
File:UI_WinX_MRO_WPConfirmButton.png|MRO Workpackage confirm button (WinX)<br />
File:UI_WinX_MRO_WPRevokeConfirmButton.png|MRO Workpackage revoke confirmation button (WinX)<br />
File:Android_finish_workpackage.PNG|MRO Workpackage confirm button (Android)<br />
File:Android reopen workpackage.PNG|MRO Workpackage revoke confirmation button (Android)<br />
</gallery><br />
<br />
=== Task ===<br />
A [[MROCLS_MRO_TASK|Task]] is an object reporting a certain progress to the owning workpackage. There are several specialized types of task objects. All kinds of tasks have a property called '''VALUE''' in common. It is very important, that this property is able to be validated. Therefore, a MetaAttribute (providing a validation timestamp by default) has to be attached on the used MetaProperty.<br />
<br />
On both clients, a Task can be reverted by clicking twice on the Not Applicable button.<br />
<br />
<br />
<br />
{{Attention|The MetaProperty ''VALUE'' has to use [[Attributes]] in order to be validated. Otherwise, the calculation of work progress will not be possible.}}<br />
<br />
==== Measurement Task ====<br />
<br />
A [[MROCLS_MRO_MEASUREMENT_TASK|Measurement Task]] inherits from [[MROCLS_MRO_TASK|Task]] and documents a measured value (e.g. read from a pressure gauge). Therefore, clicking the value on the shown task opens an editor to enter the desired value. If no value was entered before, an empty line will be shown. Once a value has been entered, the task is finished. Alternatively, the task can also be closed by the option ''Not Applicable'' to document the situation of not being able to fullfill the measurement (e.g. the pressure gauge is broken). An additional small value indicator below the main value can report e.g. the previously entered value. The behaviour of this previous value indicator has to be specified separately in the customizing.<br />
{{Clear}}<br />
<br />
<gallery widths=497px heights=69px><br />
File:Measurment Task Empty UWP.png|Measurement Task without a reported value (WinX)<br />
File:Measurment Task Not Empty UWP.png|Measurement Task with a reported value (WinX)<br />
File:Measurment Task Empty Android.jpg|Measurement Task without a reported value (Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
==== Progress Task ====<br />
<br />
[[MROCLS_MRO_PROGRESS_TASK| Progress Task]] inherits from [[MROCLS_MRO_MEASUREMENT_TASK|Task]] and reports a certain progress while fullfilling a task. The progress will influence the overall progress of the owning workpackage. If the task cannot be fullfilled, it can also be finished with the option ''Not Applicable''.<br />
<br />
There is also an [[MRO_PROGRESS_TASK_EDITOR|alternative editor]] available for progress tasks.{{Version/WinXSince|2.5.4}}<br />
{{Clear}}<br />
<br />
<gallery widths=497px heights=69px><br />
File:Progress Task UWP.png|Progress Task with a reported work progress (WinX)<br />
File:Progress Task Android.jpg|Progress Task with a reported work progress and a previous progress(Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
==== Check Task ====<br />
<br />
A [[MROCLS_MRO_CHECK_TASK|Check Task]] inherits from [[MROCLS_MRO_TASK|Task]] and is finished by reporting ''Done'' or ''Not Applicable''. This is intended for a simple To-Do task that is either done or not.<br />
{{Clear}}<br />
<br />
<gallery widths=497px heights=69px><br />
File:Check Task finished UWP.png|Unfinished MRO CheckTask (WinX)<br />
File:Check Task android.jpg|Not Applicable MRO CheckTask (Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
==== Inspection Task ====<br />
<br />
[[MROCLS_MRO_INSPECTION_TASK|Inspection Task]] inherits from [[MROCLS_MRO_TASK|Task]] and is finished, when the user reports with a positive or negative answer or ''Not Applicable'' (e.g. reporting a yes/no answer for existing equipment).<br />
{{Clear}}<br />
<br />
<gallery widths=497px heights=69px><br />
File:Finished Inspection Task UWP.png|Finished MRO InspectionTask (WinX)<br />
File:Inspection task android.jpg|Finished MRO InspectionTask (Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
==== Sequential Task ====<br />
The [[MROCLS_SEQUENTIALTASK|sequential task classification]] allows you to pre-define a sequence in which tasks are to be resolved by users. This means that it is required for one or multiple tasks to be finished in order for other tasks to become "unlocked" and editable. A task can have any number of "predecessors". Predecessors are the tasks that are required to be finished first.<br />
<br />
A task can have predecessors that live anywhere else in the object hierarchy. It is not necessary for a task and its predecessors to be part of the same work package, even though this is likely the most common use case.<br />
<br />
The state of a sequential task is evaluated both offline and online to get the best possible user experience. The user will see dependent tasks update immediately if their successors were finished, if those tasks are currently visible in the UI. There is 1 case in which the server-side state will override the client-side (offline) evaluation, discussed below.<br />
The state of each sequential task is evaluated the following way:<br />
<br />
# If the server-side state says the task is open, we consider this as the truthful state and don't do any other evaluation.<br />
# Check if the task has any predecessors.<br />
# Try to load each predecessor task.<br />
#* If loading of any predecessor fails (the object is not available offline), the task will be locked.<br />
# If all predecessor tasks are finished, the task is open and can be edited. Otherwise, the task is locked.<br />
<br />
The customizer setting up the task dependency relations needs to ensure that the dependencies are not cyclical. In this case, it would be impossible for any tasks in the "cycle" to be finished.<br />
<br />
'''Example'''<br />
<br />
As a demonstration of this feature, see [[Media:Sequential_tasks_winx.mp4|this video]]. The relations between tasks are defined as in [[Media:Task_relations.png|this image]], starting at A1 and A2, which are not dependent on any other tasks. The lines (from left to right) indicate dependencies. This means that B2 has tasks A1 and A2 as its predecessors, for example.<br />
<br />
<br />
==== Grouped Task {{Version/WinXSince|4.2}}{{Version/XamarinSince|4.2}} ====<br />
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 [[MROCLS_GROUPEDTASK|grouped tasks]].<br />
<br />
The idea is, a group of tasks can be defined as siblings to each other and they also share the same server configured threshold. When the number of finished tasks among that group exceeds the threshold, the entire group is considered as no longer necessary. When reflected in the overall status of the task owner(s), these tasks would appear as if they are finished.<br />
<br />
{{Hint|Technically speaking, the finished status is completely independent from the not necessary status on a task. A grouped task which is no longer necessary can be both finished or not yet finished. In other words, users don't have to finish a not necessary grouped task, but they still can.}}<br />
<br />
{{Hint|The precise status calculation for grouped tasks and their task owners requires the knowledge of all siblings tasks. Imagine 2 out of 3 tasks must be finished but the client only knows 1 in total and the others are only available at the server at that time. This makes it impossible to draw conclusions whether the task(s) should be necessary or not. Under such circumstances, the local status calculation is done as if these are just regular tasks.}}<br />
<br />
{{Hint|Like with the other MRO objects, the client always chooses the best available statuses for grouped tasks to present to the users. More specifically, it uses the statuses calculated by the server when the client is not offline and there are no uncommitted local changes on the involved objects. Otherwise, it uses the statuses calculated locally to the best of its knowledge.}}<br />
<br />
A task can also be a grouped and a sequential one at the same time. In such a case, the grouped nature of the sibling tasks will affect the way the task sequence completes.<br />
<br />
For example, task A1, A2 and A3 are 3 grouped sibling tasks and only 1 of them needs to be finished. At the same time, they are all predecessors of task B. Normally, all predecessors must be finished (and locked) before task B becomes the next one in the sequence and therefore unlocked. In this case, however, as soon as one of the predecessors is finished, all three become unnecessary (and locked) and task B unlocks as a result of that.<br />
<br />
<br />
==== Supervisor Task {{Version/XamarinSince|4.8}} ====<br />
As the name suggests, supervisor tasks are those that must be finished under supervision. When users want to finish a [[MROCLS_MRO_SUPERVISOR_TASK|supervisor task]], they must hand over their work devices to a supervisor. The latter checks the work status and scans an NFC tag if the work is approved. If the [[MROCLS_MRO_SUPERVISOR|supervisor]] has sufficient permissions for the task and the correct supervisor PIN is given, the task gets unlocked and the users can proceed to finish it.<br />
<br />
<gallery widths=300px heights=300px><br />
File:UI_Xamarin_Supervisor_Task_Before_Verification.jpg|Supervisor Task Before Verification/Unlocking (Mobile)<br />
File:UI_Xamarin_Supervisor_Task_Enter_PIN.jpg|Supervisor Task Enter PIN (Mobile)<br />
File:UI_Xamarin_Supervisor_Task_After_Verification.jpg|Supervisor Task After Verification/Unlocking (Mobile)<br />
</gallery><br />
<br />
A thing to note is that while the need to verify a supervisor task can be seen as a type of locking, it's certainly not the only reason for a [[Locked_Objects|locked object]]. This means a supervisor task can remain locked (although for different reasons) even after a supervisor has successfully verified it. This can often be the case if you use it in combination with other features such as [[MRO_Objects_(Client)#Sequential_Task|sequential tasks]], [[User_Rights|user rights]].<br />
<br />
{{Hint|For security reasons, the verification process is cancelled if the supervisor enters the wrong PIN for three times. Scanning the tag again is required in that case.}}<br />
{{Hint|A setting controls [[RFID_tags#Choose_which_information_to_use_from_a_tag|which information in a scanned tag is used]] during this process.}}<br />
<br />
==== Signature Task {{Version/MobileSince|5.1}}{{Version/WinXSince|5.1}} ====<br />
<br />
The Signature Task is a task type that is completed by capturing a handwritten signature from the user. The task contains an editor field that serves as the entry point for the signing process. When the user clicks (or taps) on the editor field, a signature dialog opens. Within this dialog, the user can provide their signature. After confirming the input, the signature is saved and the task is automatically marked as completed.<br />
<br />
If the task is signed while the client is online:<br />
* The User (signee) is resolved immediately by the server and displayed.<br />
* The ValidationTimestamp is generated and displayed.<br />
* Both values are shown directly in the editor field after signing.<br />
<br />
{{Hint|The User only gets resolved by the server and displayed once you're in online mode}}<br />
<br />
If the displayed User and/or ValidationTimestamp cannot be fully shown due to limited space in the editor field, the complete information can be accessed via a tooltip.<br />
<br />
* In '''UBIK WinX (UWP)''', hover over the editor field with the mouse.<br />
* In '''UBIK Mobile''', perform a long press on the editor field.<br />
A tooltip will appear, displaying the full User and ValidationTimestamp without truncation.<br />
<br />
==== Picture Task {{Version/MobileSince|5.1}}{{Version/WinXSince|5.1}} ====<br />
<br />
{{UnderConstructionStart}}<br />
<br />
A picture task is a check task which can only be finished when it has at least one child document containing a valid file.<br />
<br />
{{Hint|The task is named as such because pictures are the most commonly used types, but child documents can be of other types as well. }}<br />
<br />
{{UnderConstructionEnd}} <br />
<br />
=== MRO objects with project information (WinX only) {{Version/WinXSince|2.5.4}} ===<br />
[[File:UI_WinX_MRO_ProjectInfo.png|thumb|MRO Object with Project Info (WinX)]]<br />
An MRO object (except tasks) might also bring along [[MROCLS_PROJECTINFORMATION|project information]]. In this case, the project information together with the MRO progress are displayed in a bar chart. The start & end dates of the MRO object are displayed on the progress bar. The length and the position of the progress bar, together with the current date mark indicate the timeline.<br />
{{Clear}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Locking ==<br />
When an (MRO) object is locked, editing it becomes impossible. More details about [[Locked_Objects|locked objects]].<br />
<br />
<br />
<br />
<br />
== See also ==<br />
* [[MRO (Plugin)]]<br />
* [[MROCLS_PROJECT]]<br />
* [[MROCLS_PROJECTINFORMATION]]<br />
* [[MROCLS_SEQUENTIALTASK]]<br />
* [[MROCLS_GROUPEDTASK]]<br />
* [[MROCLS_MRO_CHECK_TASK]]<br />
* [[MROCLS_MRO_INSPECTION_TASK]]<br />
* [[MROCLS_MRO_MEASUREMENT_TASK]]<br />
* [[MROCLS_MRO_PROGRESS_TASK]]<br />
* [[MROCLS_MRO_TASK]]<br />
* [[MROCLS_MRO_TASKOWNER]]<br />
* [[MROCLS_MRO_WORKPACKAGE]]<br />
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)<br />
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)<br />
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)<br />
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)<br />
<br />
[[Category:Android|MRO Objects (UBIK WinX)]]<br />
[[Category:Client|MRO Objects (Client)]]<br />
[[Category:Mobile|MRO Objects (Client)]]<br />
[[Category:Pages with broken file links|MRO Objects (Client)]]<br />
[[Category:WinX|MRO Objects (UBIK WinX)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(Mobile)&diff=29433Version 5.1 (Mobile)2026-03-02T14:43:59Z<p>LGE: </p>
<hr />
<div>{{Attention|Existing pre 5.0 XAMLs are not compatible with UBIK Mobile client 5.1. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.}}<br />
<br />
{{Attention|UBIK 5 clients can only connect to {{UBIK}} Servers of [[Version 3.6(Server)|version 3.6]] and higher!}}<br />
<br />
{{Attention|The minimum supported OS versions are:<br />
* Android 9;<br />
* iOS 12.}}<br />
<br />
== Availability ==<br />
{{key press|Android: Store}}{{key press|iOS: Store}}: Publicly available in Google Play Store / Apple App Store.<br />
<br />
{{key press|Android: Store Beta}}: Publicly available in Google Play Store as beta versions. You can opt in or out of the beta at any time in the store.<br />
<br />
{{key press|Android: Store Preview}}: Available through Google Play Store's [https://play.google.com/store/apps/details?id=com.augmensys.ubik.go invitation link].<br />
<br />
{{key press|iOS: Store Beta}}: Available through Apple App Store's [https://testflight.apple.com/join/Kmb1HG9E invitation link].<br />
<br />
{{key press|iOS: Store Preview}}: Available through Apple App Store's [https://testflight.apple.com/join/yHRnbYbt invitation link].<br />
<br />
{{key press|Windows: Store Preview}}: The mobile Windows client is not an official product and is only distributed as test versions upon request and/or in our [https://release.augmensys.com/download/modules/client/mobile/ release portal].<br />
<br/><br />
<br />
<br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with a ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
=== 5.1.?? 2026-??-?? {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* The system flashlight can now also be enabled or disabled via XAML customization. For detailed information, see [[Mobile XAML#Flashlight|Flashlight]]<br />
* Replaced app closing after repeated failed login attempts with a client-side temporary login block, including user feedback that indicates when login becomes available again.<br />
* Added French localization to the app.<br />
* A standard for MRO Signature Tasks has been introduced, which automatically displays the signee as well as the validation date after the task has been signed.<br />
* Fixed an issue where changes in property editing were not discarded when using the default Back button.<br />
<br />
<br />
=== 5.1.30 2026-03-02 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Fixed an issue that prevented any documents from being uploaded when connecting to 5.1 webservices.<br />
<br />
<br />
=== 5.1.29 on 2026-02-26 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Fixed an issue where the POI button was only visible under certain condition (ShowUnreleasedFeatures in the profile is set to true).<br />
<br />
<br />
=== 5.1.28 on 2026-02-10 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* The following features which existed in pre 5.0 versions are now available again in 5.1.<br />
** [[Map_View|Map view]].<br />
** [[POI_View_(Mobile)|POI view]]. (Aruco and OCR are not yet supported)<br />
** Location service.<br />
** [[Native_Push_(Client)|Native push]].<br />
** [[Charts]].<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Complete UI overhaul introduces a cleaner, more modern and adaptive user interface with various quality of life improvements.<br />
* UBIKTabView supports both dynamic and static items in combination with lazy loading.<br />
* Files in the app's data folder can now be opened or deleted directly in the developer settings.<br />
* Introduced a fully resource-driven UI theming system enabling fast, safe customization (dark mode, resizing, and consistent styling) by adapting a small set of centralized resources.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* Fixed an issue where remembered scroll positions were lost when the ItemsSource property of an SfListViewExt changed (e.g., Properties.ShowAllProperties).<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed issue that caused app to be stuck on splash screen after resuming from background.<br />
* Fixed an issue where StatusColor was not shown in the UI for objects that didn't additionally have a Progress.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Fixed an issue that caused content of the custom ContentControl to not be rendered sometimes.<br />
* (Android) Fixed an issue in the WebView where some links could not be opened.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the deletion of some objects was not reflected in the UI until refresh.<br />
* Fixed an issue where document creation might not be properly enabled in certain customizing scenarios. For example, a media creation button might be disabled until a page refresh.<br />
* Fixed an issue where batch creating documents (by multi selecting files to attach) can be interrupted if you leave the page.<br />
<br />
<br />
<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true. In Mobile, deleting the last annotation does not correctly update the editor's internal edit state. As a result, the Save button may remain visible even though no edits exist.<br />
* When changing the device orientation during attaching a photo on iOS, the app gets stuck. This is an issue Microsoft confirmed in .NET9 and will fix in .NET10.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Currently, the Samsung keyboard doesn't show {{key press|,}} at all, regardless of the current language/locale setting of the device. Please use a different virtual keyboard (e.g. Gboard from Google) instead if {{key press|.}} is unacceptable.<br />
* The periodic execution of background pushes is not guaranteed on iOS (the native push feature doesn't have this issue).<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* It is currently not possible to select which camera to use for AR views (e.g. scan page) on Windows.<br />
* SfPullToRefresh was removed due to [[Mobile_XAML#Issues_with_SfPullToRefresh_in_Mobile_client|existing issues]], and replaced with a Refresh option in the Context menu.<br />
<br />
<br />
= ⚠️ XAML Notes =<br />
Due to the change of the underlying XAML technology, the existing XAMLs for the old mobile clients (pre 5.0) are no longer compatible. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.<br />
<br />
<br />
<headertabs /><br />
<br />
[[Category:Client|Version 5.1 (Mobile)]]<br />
[[Category:Mobile|Version 5.1 (Mobile)]]<br />
[[Category:Version 5.1|Version 5.1 (Mobile)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(Mobile)&diff=29423Version 5.1 (Mobile)2026-03-02T08:56:52Z<p>LGE: /* 5.1.?? 2026-??-?? {{key press|Android: Store}}{{key press|iOS: Store}} */</p>
<hr />
<div>{{Attention|Existing pre 5.0 XAMLs are not compatible with UBIK Mobile client 5.1. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.}}<br />
<br />
{{Attention|UBIK 5 clients can only connect to {{UBIK}} Servers of [[Version 3.6(Server)|version 3.6]] and higher!}}<br />
<br />
{{Attention|The minimum supported OS versions are:<br />
* Android 9;<br />
* iOS 12.}}<br />
<br />
== Availability ==<br />
{{key press|Android: Store}}{{key press|iOS: Store}}: Publicly available in Google Play Store / Apple App Store.<br />
<br />
{{key press|Android: Store Beta}}: Publicly available in Google Play Store as beta versions. You can opt in or out of the beta at any time in the store.<br />
<br />
{{key press|Android: Store Preview}}: Available through Google Play Store's [https://play.google.com/store/apps/details?id=com.augmensys.ubik.go invitation link].<br />
<br />
{{key press|iOS: Store Beta}}: Available through Apple App Store's [https://testflight.apple.com/join/Kmb1HG9E invitation link].<br />
<br />
{{key press|iOS: Store Preview}}: Available through Apple App Store's [https://testflight.apple.com/join/yHRnbYbt invitation link].<br />
<br />
{{key press|Windows: Store Preview}}: The mobile Windows client is not an official product and is only distributed as test versions upon request and/or in our [https://release.augmensys.com/download/modules/client/mobile/ release portal].<br />
<br/><br />
<br />
<br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with a ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
=== 5.1.?? 2026-??-?? {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* The system flashlight can now also be enabled or disabled via XAML customization. For detailed information, see [[Mobile XAML#Flashlight|Flashlight]]<br />
* Replaced app closing after repeated failed login attempts with a client-side temporary login block, including user feedback that indicates when login becomes available again.<br />
* Added French localization to the app.<br />
<br />
=== 5.1.?? 2026-??-?? {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Fixed an issue that prevented any documents from being uploaded.<br />
* Fixed an issue where changes in property editing were not discarded when using the default Back button.<br />
<br />
[[Category:Client|Version 5.1 (Mobile)]]<br />
[[Category:Mobile|Version 5.1 (Mobile)]]<br />
[[Category:Version 5.1|Version 5.1 (Mobile)]]<br />
<br />
=== 5.1.29 on 2026-02-26 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Fixed an issue where the POI button was only visible under certain condition (ShowUnreleasedFeatures in the profile is set to true).<br />
<br />
<br />
=== 5.1.28 on 2026-02-10 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* The following features which existed in pre 5.0 versions are now available again in 5.1.<br />
** [[Map_View|Map view]].<br />
** [[POI_View_(Mobile)|POI view]]. (Aruco and OCR are not yet supported)<br />
** Location service.<br />
** [[Native_Push_(Client)|Native push]].<br />
** [[Charts]].<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Complete UI overhaul introduces a cleaner, more modern and adaptive user interface with various quality of life improvements.<br />
* UBIKTabView supports both dynamic and static items in combination with lazy loading.<br />
* Files in the app's data folder can now be opened or deleted directly in the developer settings.<br />
* Introduced a fully resource-driven UI theming system enabling fast, safe customization (dark mode, resizing, and consistent styling) by adapting a small set of centralized resources.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* Fixed an issue where remembered scroll positions were lost when the ItemsSource property of an SfListViewExt changed (e.g., Properties.ShowAllProperties).<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed issue that caused app to be stuck on splash screen after resuming from background.<br />
* Fixed an issue where StatusColor was not shown in the UI for objects that didn't additionally have a Progress.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Fixed an issue that caused content of the custom ContentControl to not be rendered sometimes.<br />
* (Android) Fixed an issue in the WebView where some links could not be opened.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the deletion of some objects was not reflected in the UI until refresh.<br />
* Fixed an issue where document creation might not be properly enabled in certain customizing scenarios. For example, a media creation button might be disabled until a page refresh.<br />
* Fixed an issue where batch creating documents (by multi selecting files to attach) can be interrupted if you leave the page.<br />
<br />
<br />
<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true. In Mobile, deleting the last annotation does not correctly update the editor's internal edit state. As a result, the Save button may remain visible even though no edits exist.<br />
* When changing the device orientation during attaching a photo on iOS, the app gets stuck. This is an issue Microsoft confirmed in .NET9 and will fix in .NET10.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Currently, the Samsung keyboard doesn't show {{key press|,}} at all, regardless of the current language/locale setting of the device. Please use a different virtual keyboard (e.g. Gboard from Google) instead if {{key press|.}} is unacceptable.<br />
* The periodic execution of background pushes is not guaranteed on iOS (the native push feature doesn't have this issue).<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* It is currently not possible to select which camera to use for AR views (e.g. scan page) on Windows.<br />
* SfPullToRefresh was removed due to [[Mobile_XAML#Issues_with_SfPullToRefresh_in_Mobile_client|existing issues]], and replaced with a Refresh option in the Context menu.<br />
<br />
<br />
= ⚠️ XAML Notes =<br />
Due to the change of the underlying XAML technology, the existing XAMLs for the old mobile clients (pre 5.0) are no longer compatible. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.<br />
<br />
<br />
<headertabs /><br />
<br />
[[Category:Client|Version 5.1 (Mobile)]]<br />
[[Category:Mobile|Version 5.1 (Mobile)]]<br />
[[Category:Version 5.1|Version 5.1 (Mobile)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(Mobile)&diff=29413Version 5.1 (Mobile)2026-02-26T11:09:41Z<p>LGE: </p>
<hr />
<div>{{Attention|Existing pre 5.0 XAMLs are not compatible with UBIK Mobile client 5.1. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.}}<br />
<br />
{{Attention|UBIK 5 clients can only connect to {{UBIK}} Servers of [[Version 3.6(Server)|version 3.6]] and higher!}}<br />
<br />
{{Attention|The minimum supported OS versions are:<br />
* Android 9;<br />
* iOS 12.}}<br />
<br />
== Availability ==<br />
{{key press|Android: Store}}{{key press|iOS: Store}}: Publicly available in Google Play Store / Apple App Store.<br />
<br />
{{key press|Android: Store Beta}}: Publicly available in Google Play Store as beta versions. You can opt in or out of the beta at any time in the store.<br />
<br />
{{key press|Android: Store Preview}}: Available through Google Play Store's [https://play.google.com/store/apps/details?id=com.augmensys.ubik.go invitation link].<br />
<br />
{{key press|iOS: Store Beta}}: Available through Apple App Store's [https://testflight.apple.com/join/Kmb1HG9E invitation link].<br />
<br />
{{key press|iOS: Store Preview}}: Available through Apple App Store's [https://testflight.apple.com/join/yHRnbYbt invitation link].<br />
<br />
{{key press|Windows: Store Preview}}: The mobile Windows client is not an official product and is only distributed as test versions upon request and/or in our [https://release.augmensys.com/download/modules/client/mobile/ release portal].<br />
<br/><br />
<br />
<br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with a ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
=== 5.1.?? 2026-??-?? {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* The system flashlight can now also be enabled or disabled via XAML customization. For detailed information, see [[Mobile XAML#Flashlight|Flashlight]]<br />
* Replaced app closing after repeated failed login attempts with a client-side temporary login block, including user feedback that indicates when login becomes available again.<br />
* Added French localization to the app.<br />
<br />
<br />
=== 5.1.29 on 2026-02-26 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Fixed an issue where the POI button was only visible under certain condition (ShowUnreleasedFeatures in the profile is set to true).<br />
<br />
<br />
=== 5.1.28 on 2026-02-10 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* The following features which existed in pre 5.0 versions are now available again in 5.1.<br />
** [[Map_View|Map view]].<br />
** [[POI_View_(Mobile)|POI view]]. (Aruco and OCR are not yet supported)<br />
** Location service.<br />
** [[Native_Push_(Client)|Native push]].<br />
** [[Charts]].<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Complete UI overhaul introduces a cleaner, more modern and adaptive user interface with various quality of life improvements.<br />
* UBIKTabView supports both dynamic and static items in combination with lazy loading.<br />
* Files in the app's data folder can now be opened or deleted directly in the developer settings.<br />
* Introduced a fully resource-driven UI theming system enabling fast, safe customization (dark mode, resizing, and consistent styling) by adapting a small set of centralized resources.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* Fixed an issue where remembered scroll positions were lost when the ItemsSource property of an SfListViewExt changed (e.g., Properties.ShowAllProperties).<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed issue that caused app to be stuck on splash screen after resuming from background.<br />
* Fixed an issue where StatusColor was not shown in the UI for objects that didn't additionally have a Progress.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Fixed an issue that caused content of the custom ContentControl to not be rendered sometimes.<br />
* (Android) Fixed an issue in the WebView where some links could not be opened.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the deletion of some objects was not reflected in the UI until refresh.<br />
* Fixed an issue where document creation might not be properly enabled in certain customizing scenarios. For example, a media creation button might be disabled until a page refresh.<br />
* Fixed an issue where batch creating documents (by multi selecting files to attach) can be interrupted if you leave the page.<br />
<br />
<br />
<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true. In Mobile, deleting the last annotation does not correctly update the editor's internal edit state. As a result, the Save button may remain visible even though no edits exist.<br />
* When changing the device orientation during attaching a photo on iOS, the app gets stuck. This is an issue Microsoft confirmed in .NET9 and will fix in .NET10.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Currently, the Samsung keyboard doesn't show {{key press|,}} at all, regardless of the current language/locale setting of the device. Please use a different virtual keyboard (e.g. Gboard from Google) instead if {{key press|.}} is unacceptable.<br />
* The periodic execution of background pushes is not guaranteed on iOS (the native push feature doesn't have this issue).<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* It is currently not possible to select which camera to use for AR views (e.g. scan page) on Windows.<br />
* SfPullToRefresh was removed due to [[Mobile_XAML#Issues_with_SfPullToRefresh_in_Mobile_client|existing issues]], and replaced with a Refresh option in the Context menu.<br />
<br />
<br />
= ⚠️ XAML Notes =<br />
Due to the change of the underlying XAML technology, the existing XAMLs for the old mobile clients (pre 5.0) are no longer compatible. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.<br />
<br />
<br />
<headertabs /><br />
<br />
[[Category:Client|Version 5.1 (Mobile)]]<br />
[[Category:Mobile|Version 5.1 (Mobile)]]<br />
[[Category:Version 5.1|Version 5.1 (Mobile)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(Mobile)&diff=29411Version 5.1 (Mobile)2026-02-26T09:23:15Z<p>LGE: </p>
<hr />
<div>{{Attention|Existing pre 5.0 XAMLs are not compatible with UBIK Mobile client 5.1. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.}}<br />
<br />
{{Attention|UBIK 5 clients can only connect to {{UBIK}} Servers of [[Version 3.6(Server)|version 3.6]] and higher!}}<br />
<br />
{{Attention|The minimum supported OS versions are:<br />
* Android 9;<br />
* iOS 12.}}<br />
<br />
== Availability ==<br />
{{key press|Android: Store}}{{key press|iOS: Store}}: Publicly available in Google Play Store / Apple App Store.<br />
<br />
{{key press|Android: Store Beta}}: Publicly available in Google Play Store as beta versions. You can opt in or out of the beta at any time in the store.<br />
<br />
{{key press|Android: Store Preview}}: Available through Google Play Store's [https://play.google.com/store/apps/details?id=com.augmensys.ubik.go invitation link].<br />
<br />
{{key press|iOS: Store Beta}}: Available through Apple App Store's [https://testflight.apple.com/join/Kmb1HG9E invitation link].<br />
<br />
{{key press|iOS: Store Preview}}: Available through Apple App Store's [https://testflight.apple.com/join/yHRnbYbt invitation link].<br />
<br />
{{key press|Windows: Store Preview}}: The mobile Windows client is not an official product and is only distributed as test versions upon request and/or in our [https://release.augmensys.com/download/modules/client/mobile/ release portal].<br />
<br/><br />
<br />
<br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with a ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
=== 5.1.?? 2026-??-?? {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* The system flashlight can now also be enabled or disabled via XAML customization. For detailed information, see [[Mobile XAML#Flashlight|Flashlight]]<br />
* Replaced app closing after repeated failed login attempts with a client-side temporary login block, including user feedback that indicates when login becomes available again.<br />
* Added French localization to the app.<br />
<br />
<br />
=== 5.1.29 on 2026-02-2? {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Fixed an issue where the POI button was only visible under certain condition (ShowUnreleasedFeatures in the profile is set to true).<br />
<br />
<br />
=== 5.1.28 on 2026-02-10 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* The following features which existed in pre 5.0 versions are now available again in 5.1.<br />
** [[Map_View|Map view]].<br />
** [[POI_View_(Mobile)|POI view]]. (Aruco and OCR are not yet supported)<br />
** Location service.<br />
** [[Native_Push_(Client)|Native push]].<br />
** [[Charts]].<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Complete UI overhaul introduces a cleaner, more modern and adaptive user interface with various quality of life improvements.<br />
* UBIKTabView supports both dynamic and static items in combination with lazy loading.<br />
* Files in the app's data folder can now be opened or deleted directly in the developer settings.<br />
* Introduced a fully resource-driven UI theming system enabling fast, safe customization (dark mode, resizing, and consistent styling) by adapting a small set of centralized resources.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* Fixed an issue where remembered scroll positions were lost when the ItemsSource property of an SfListViewExt changed (e.g., Properties.ShowAllProperties).<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed issue that caused app to be stuck on splash screen after resuming from background.<br />
* Fixed an issue where StatusColor was not shown in the UI for objects that didn't additionally have a Progress.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Fixed an issue that caused content of the custom ContentControl to not be rendered sometimes.<br />
* (Android) Fixed an issue in the WebView where some links could not be opened.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the deletion of some objects was not reflected in the UI until refresh.<br />
* Fixed an issue where document creation might not be properly enabled in certain customizing scenarios. For example, a media creation button might be disabled until a page refresh.<br />
* Fixed an issue where batch creating documents (by multi selecting files to attach) can be interrupted if you leave the page.<br />
<br />
<br />
<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true. In Mobile, deleting the last annotation does not correctly update the editor's internal edit state. As a result, the Save button may remain visible even though no edits exist.<br />
* When changing the device orientation during attaching a photo on iOS, the app gets stuck. This is an issue Microsoft confirmed in .NET9 and will fix in .NET10.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Currently, the Samsung keyboard doesn't show {{key press|,}} at all, regardless of the current language/locale setting of the device. Please use a different virtual keyboard (e.g. Gboard from Google) instead if {{key press|.}} is unacceptable.<br />
* The periodic execution of background pushes is not guaranteed on iOS (the native push feature doesn't have this issue).<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* It is currently not possible to select which camera to use for AR views (e.g. scan page) on Windows.<br />
* SfPullToRefresh was removed due to [[Mobile_XAML#Issues_with_SfPullToRefresh_in_Mobile_client|existing issues]], and replaced with a Refresh option in the Context menu.<br />
<br />
<br />
= ⚠️ XAML Notes =<br />
Due to the change of the underlying XAML technology, the existing XAMLs for the old mobile clients (pre 5.0) are no longer compatible. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.<br />
<br />
<br />
<headertabs /><br />
<br />
[[Category:Client|Version 5.1 (Mobile)]]<br />
[[Category:Mobile|Version 5.1 (Mobile)]]<br />
[[Category:Version 5.1|Version 5.1 (Mobile)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(WinX)&diff=29401Version 5.1 (WinX)2026-02-23T14:56:11Z<p>LGE: </p>
<hr />
<div>{{Attention|This version requires [https://en.wikipedia.org/wiki/Windows_10_version_history#Version_1809_(October_2018_Update) Windows 10 build 17763] or higher}}<br />
<br />
== Availability ==<br />
{{key press|Store}}: Publicly available in Microsoft Store.<br />
<br />
{{key press|Store Beta}} / {{key press|Store Preview}}: Publicly available in Microsoft Store as beta or preview versions to those whose account email is participating in our beta or preview test. To join, please send an email to testing@augmensys.com and provide an email address to add to the list as well as the information which test you want to join. Alternatively you can contact the Augmensys staff and submit your chosen email address.<br />
<br />
Example: Please add my email account example@example.com to the '''Beta''' test group for the '''WinX''' client.<br />
<br />
<br/><br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
=== 5.1.?? on 2026-??-?? ===<br />
* Replaced app closing after repeated failed login attempts with a client-side temporary login block, including user feedback that indicates when login becomes available again.<br />
* Added French localization to the app.<br />
<br />
<br />
=== 5.1.6 on 2026-02-10 ===<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where certain documents couldn't be loaded anymore.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed an issue where the UI did not update properly when committing a direct edit input task.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Added a [[XAML#UBIKWebView|UBIKWebView]] control that includes a fix in the WebView2 where some links could not be opened.<br />
* Fixed issue that caused input fields to be focused but not editable.<br />
* Fixed an issue where document creation might not be properly enabled in certain customizing scenarios. For example, a media creation button might be disabled until a page refresh.<br />
* Fixed an issue where batch creating documents (by multi selecting files to attach) can be interrupted if you leave the page.<br />
<br />
<br />
<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Free Text Annotations that where created in former sessions cannot be selected and therefore cannot be edited any more.<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* Known issues regarding the [[Documents_(Client)#Remember_Document_Settings|Remember Document Settings]] feature:<br />
** Saving the Zoom value via touch gestures is not supported.<br />
** Due to a third-party framework issue it can't be guaranteed that saving the Zoom level is always working properly. We reported this issue and will update our solution as soon as it is resolved on their side.<br />
<br/><br />
<br />
= ⚠️ XAML Notes =<br />
<br />
<br />
<br />
<headertabs /><br />
<br />
<br />
{{Category/Version2|{{PAGENAME}}}}<br />
<br />
[[Category:Client|Version 5.1 (WinX)]]<br />
[[Category:Version 5.1|Version 5.1 (WinX)]]<br />
[[Category:WinX|Version 5.1 (WinX)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(Mobile)&diff=29400Version 5.1 (Mobile)2026-02-23T14:55:58Z<p>LGE: </p>
<hr />
<div>{{Attention|Existing pre 5.0 XAMLs are not compatible with UBIK Mobile client 5.1. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.}}<br />
<br />
{{Attention|UBIK 5 clients can only connect to {{UBIK}} Servers of [[Version 3.6(Server)|version 3.6]] and higher!}}<br />
<br />
{{Attention|The minimum supported OS versions are:<br />
* Android 9;<br />
* iOS 12.}}<br />
<br />
== Availability ==<br />
{{key press|Android: Store}}{{key press|iOS: Store}}: Publicly available in Google Play Store / Apple App Store.<br />
<br />
{{key press|Android: Store Beta}}: Publicly available in Google Play Store as beta versions. You can opt in or out of the beta at any time in the store.<br />
<br />
{{key press|Android: Store Preview}}: Available through Google Play Store's [https://play.google.com/store/apps/details?id=com.augmensys.ubik.go invitation link].<br />
<br />
{{key press|iOS: Store Beta}}: Available through Apple App Store's [https://testflight.apple.com/join/Kmb1HG9E invitation link].<br />
<br />
{{key press|iOS: Store Preview}}: Available through Apple App Store's [https://testflight.apple.com/join/yHRnbYbt invitation link].<br />
<br />
{{key press|Windows: Store Preview}}: The mobile Windows client is not an official product and is only distributed as test versions upon request and/or in our [https://release.augmensys.com/download/modules/client/mobile/ release portal].<br />
<br/><br />
<br />
<br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with a ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
=== 5.1.?? 2026-??-?? {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* The system flashlight can now also be enabled or disabled via XAML customization. For detailed information, see [[Mobile XAML#Flashlight|Flashlight]]<br />
* Replaced app closing after repeated failed login attempts with a client-side temporary login block, including user feedback that indicates when login becomes available again.<br />
* Added French localization to the app.<br />
<br />
<br />
=== 5.1.28 on 2026-02-10 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* The following features which existed in pre 5.0 versions are now available again in 5.1.<br />
** [[Map_View|Map view]].<br />
** [[POI_View_(Mobile)|POI view]]. (Aruco and OCR are not yet supported)<br />
** Location service.<br />
** [[Native_Push_(Client)|Native push]].<br />
** [[Charts]].<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Complete UI overhaul introduces a cleaner, more modern and adaptive user interface with various quality of life improvements.<br />
* UBIKTabView supports both dynamic and static items in combination with lazy loading.<br />
* Files in the app's data folder can now be opened or deleted directly in the developer settings.<br />
* Introduced a fully resource-driven UI theming system enabling fast, safe customization (dark mode, resizing, and consistent styling) by adapting a small set of centralized resources.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* Fixed an issue where remembered scroll positions were lost when the ItemsSource property of an SfListViewExt changed (e.g., Properties.ShowAllProperties).<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed issue that caused app to be stuck on splash screen after resuming from background.<br />
* Fixed an issue where StatusColor was not shown in the UI for objects that didn't additionally have a Progress.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Fixed an issue that caused content of the custom ContentControl to not be rendered sometimes.<br />
* (Android) Fixed an issue in the WebView where some links could not be opened.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the deletion of some objects was not reflected in the UI until refresh.<br />
* Fixed an issue where document creation might not be properly enabled in certain customizing scenarios. For example, a media creation button might be disabled until a page refresh.<br />
* Fixed an issue where batch creating documents (by multi selecting files to attach) can be interrupted if you leave the page.<br />
<br />
<br />
<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true. In Mobile, deleting the last annotation does not correctly update the editor's internal edit state. As a result, the Save button may remain visible even though no edits exist.<br />
* When changing the device orientation during attaching a photo on iOS, the app gets stuck. This is an issue Microsoft confirmed in .NET9 and will fix in .NET10.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Currently, the Samsung keyboard doesn't show {{key press|,}} at all, regardless of the current language/locale setting of the device. Please use a different virtual keyboard (e.g. Gboard from Google) instead if {{key press|.}} is unacceptable.<br />
* The periodic execution of background pushes is not guaranteed on iOS (the native push feature doesn't have this issue).<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* It is currently not possible to select which camera to use for AR views (e.g. scan page) on Windows.<br />
* SfPullToRefresh was removed due to [[Mobile_XAML#Issues_with_SfPullToRefresh_in_Mobile_client|existing issues]], and replaced with a Refresh option in the Context menu.<br />
<br />
<br />
= ⚠️ XAML Notes =<br />
Due to the change of the underlying XAML technology, the existing XAMLs for the old mobile clients (pre 5.0) are no longer compatible. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.<br />
<br />
<br />
<headertabs /><br />
<br />
[[Category:Client|Version 5.1 (Mobile)]]<br />
[[Category:Mobile|Version 5.1 (Mobile)]]<br />
[[Category:Version 5.1|Version 5.1 (Mobile)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(WinX)&diff=29373Version 5.1 (WinX)2026-02-17T09:42:38Z<p>LGE: </p>
<hr />
<div>{{Attention|This version requires [https://en.wikipedia.org/wiki/Windows_10_version_history#Version_1809_(October_2018_Update) Windows 10 build 17763] or higher}}<br />
<br />
== Availability ==<br />
{{key press|Store}}: Publicly available in Microsoft Store.<br />
<br />
{{key press|Store Beta}} / {{key press|Store Preview}}: Publicly available in Microsoft Store as beta or preview versions to those whose account email is participating in our beta or preview test. To join, please send an email to testing@augmensys.com and provide an email address to add to the list as well as the information which test you want to join. Alternatively you can contact the Augmensys staff and submit your chosen email address.<br />
<br />
Example: Please add my email account example@example.com to the '''Beta''' test group for the '''WinX''' client.<br />
<br />
<br/><br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
<br />
=== 5.1.6 on 2026-02-10 ===<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where certain documents couldn't be loaded anymore.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed an issue where the UI did not update properly when committing a direct edit input task.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Added a [[XAML#UBIKWebView|UBIKWebView]] control that includes a fix in the WebView2 where some links could not be opened.<br />
* Fixed issue that caused input fields to be focused but not editable.<br />
* Fixed an issue where document creation might not be properly enabled in certain customizing scenarios. For example, a media creation button might be disabled until a page refresh.<br />
* Fixed an issue where batch creating documents (by multi selecting files to attach) can be interrupted if you leave the page.<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Free Text Annotations that where created in former sessions cannot be selected and therefore cannot be edited any more.<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* Known issues regarding the [[Documents_(Client)#Remember_Document_Settings|Remember Document Settings]] feature:<br />
** Saving the Zoom value via touch gestures is not supported.<br />
** Due to a third-party framework issue it can't be guaranteed that saving the Zoom level is always working properly. We reported this issue and will update our solution as soon as it is resolved on their side.<br />
<br/><br />
<br />
= ⚠️ XAML Notes =<br />
<br />
<br />
<br />
<headertabs /><br />
<br />
<br />
{{Category/Version2|{{PAGENAME}}}}<br />
<br />
[[Category:Client|Version 5.1 (WinX)]]<br />
[[Category:Version 5.1|Version 5.1 (WinX)]]<br />
[[Category:WinX|Version 5.1 (WinX)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(Mobile)&diff=29372Version 5.1 (Mobile)2026-02-17T09:42:23Z<p>LGE: /* 5.1.28 on 2026-02-10 {{key press|Android: Store}}{{key press|iOS: Store}} */</p>
<hr />
<div>{{Attention|Existing pre 5.0 XAMLs are not compatible with UBIK Mobile client 5.1. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.}}<br />
<br />
{{Attention|UBIK 5 clients can only connect to {{UBIK}} Servers of [[Version 3.6(Server)|version 3.6]] and higher!}}<br />
<br />
{{Attention|The minimum supported OS versions are:<br />
* Android 9;<br />
* iOS 12.}}<br />
<br />
== Availability ==<br />
{{key press|Android: Store}}{{key press|iOS: Store}}: Publicly available in Google Play Store / Apple App Store.<br />
<br />
{{key press|Android: Store Beta}}: Publicly available in Google Play Store as beta versions. You can opt in or out of the beta at any time in the store.<br />
<br />
{{key press|Android: Store Preview}}: Available through Google Play Store's [https://play.google.com/store/apps/details?id=com.augmensys.ubik.go invitation link].<br />
<br />
{{key press|iOS: Store Beta}}: Available through Apple App Store's [https://testflight.apple.com/join/Kmb1HG9E invitation link].<br />
<br />
{{key press|iOS: Store Preview}}: Available through Apple App Store's [https://testflight.apple.com/join/yHRnbYbt invitation link].<br />
<br />
{{key press|Windows: Store Preview}}: The mobile Windows client is not an official product and is only distributed as test versions upon request and/or in our [https://release.augmensys.com/download/modules/client/mobile/ release portal].<br />
<br/><br />
<br />
<br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with a ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
<br />
=== 5.1.28 on 2026-02-10 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* The following features which existed in pre 5.0 versions are now available again in 5.1.<br />
** [[Map_View|Map view]].<br />
** [[POI_View_(Mobile)|POI view]]. (Aruco and OCR are not yet supported)<br />
** Location service.<br />
** [[Native_Push_(Client)|Native push]].<br />
** [[Charts]].<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Complete UI overhaul introduces a cleaner, more modern and adaptive user interface with various quality of life improvements.<br />
* UBIKTabView supports both dynamic and static items in combination with lazy loading.<br />
* Files in the app's data folder can now be opened or deleted directly in the developer settings.<br />
* Introduced a fully resource-driven UI theming system enabling fast, safe customization (dark mode, resizing, and consistent styling) by adapting a small set of centralized resources.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* Fixed an issue where remembered scroll positions were lost when the ItemsSource property of an SfListViewExt changed (e.g., Properties.ShowAllProperties).<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed issue that caused app to be stuck on splash screen after resuming from background.<br />
* Fixed an issue where StatusColor was not shown in the UI for objects that didn't additionally have a Progress.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Fixed an issue that caused content of the custom ContentControl to not be rendered sometimes.<br />
* (Android) Fixed an issue in the WebView where some links could not be opened.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the deletion of some objects was not reflected in the UI until refresh.<br />
* Fixed an issue where document creation might not be properly enabled in certain customizing scenarios. For example, a media creation button might be disabled until a page refresh.<br />
* Fixed an issue where batch creating documents (by multi selecting files to attach) can be interrupted if you leave the page.<br />
<br />
[[Category:Client|Version 5.1 (Mobile)]]<br />
[[Category:Mobile|Version 5.1 (Mobile)]]<br />
[[Category:Version 5.1|Version 5.1 (Mobile)]]<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true. In Mobile, deleting the last annotation does not correctly update the editor's internal edit state. As a result, the Save button may remain visible even though no edits exist.<br />
* When changing the device orientation during attaching a photo on iOS, the app gets stuck. This is an issue Microsoft confirmed in .NET9 and will fix in .NET10.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Currently, the Samsung keyboard doesn't show {{key press|,}} at all, regardless of the current language/locale setting of the device. Please use a different virtual keyboard (e.g. Gboard from Google) instead if {{key press|.}} is unacceptable.<br />
* The periodic execution of background pushes is not guaranteed on iOS (the native push feature doesn't have this issue).<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* It is currently not possible to select which camera to use for AR views (e.g. scan page) on Windows.<br />
* SfPullToRefresh was removed due to [[Mobile_XAML#Issues_with_SfPullToRefresh_in_Mobile_client|existing issues]], and replaced with a Refresh option in the Context menu.<br />
<br />
<br />
= ⚠️ XAML Notes =<br />
Due to the change of the underlying XAML technology, the existing XAMLs for the old mobile clients (pre 5.0) are no longer compatible. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.<br />
<br />
<br />
<headertabs /><br />
<br />
[[Category:Client|Version 5.1 (Mobile)]]<br />
[[Category:Mobile|Version 5.1 (Mobile)]]<br />
[[Category:Version 5.1|Version 5.1 (Mobile)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(WinX)&diff=29343Version 5.1 (WinX)2026-02-10T16:31:26Z<p>LGE: </p>
<hr />
<div>{{Attention|This version requires [https://en.wikipedia.org/wiki/Windows_10_version_history#Version_1809_(October_2018_Update) Windows 10 build 17763] or higher}}<br />
<br />
== Availability ==<br />
{{key press|Store}}: Publicly available in Microsoft Store.<br />
<br />
{{key press|Store Beta}} / {{key press|Store Preview}}: Publicly available in Microsoft Store as beta or preview versions to those whose account email is participating in our beta or preview test. To join, please send an email to testing@augmensys.com and provide an email address to add to the list as well as the information which test you want to join. Alternatively you can contact the Augmensys staff and submit your chosen email address.<br />
<br />
Example: Please add my email account example@example.com to the '''Beta''' test group for the '''WinX''' client.<br />
<br />
<br/><br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
<br />
=== 5.1.6 on 2026-02-10 ===<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where certain documents couldn't be loaded anymore.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed an issue where the UI did not update properly when committing a direct edit input task.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Added a [[XAML#UBIKWebView|UBIKWebView]] control that includes a fix in the WebView2 where some links could not be opened.<br />
* Fixed issue that caused input fields to be focused but not editable.<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Free Text Annotations that where created in former sessions cannot be selected and therefore cannot be edited any more.<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* Known issues regarding the [[Documents_(Client)#Remember_Document_Settings|Remember Document Settings]] feature:<br />
** Saving the Zoom value via touch gestures is not supported.<br />
** Due to a third-party framework issue it can't be guaranteed that saving the Zoom level is always working properly. We reported this issue and will update our solution as soon as it is resolved on their side.<br />
<br/><br />
<br />
= ⚠️ XAML Notes =<br />
<br />
<br />
<br />
<headertabs /><br />
<br />
<br />
{{Category/Version2|{{PAGENAME}}}}<br />
<br />
[[Category:Client|Version 5.1 (WinX)]]<br />
[[Category:Version 5.1|Version 5.1 (WinX)]]<br />
[[Category:WinX|Version 5.1 (WinX)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=MRO_Objects_(Client)&diff=29339MRO Objects (Client)2026-02-10T10:14:38Z<p>LGE: </p>
<hr />
<div>[[File:UI_WinX_MRO_ChildList.png|thumb|alt=MRO Child List UI (WinX)|MRO UI (WinX)]]<br />
[[File:Android_mro_ui.jpg|thumb|alt=MRO Child List UI (Android)|MRO UI (Android)]]<br />
The WinX client UI displays MRO configured objects like any other root- or child-object enriched by some additional logic and features.<br />
<br />
== Basic User Interface ==<br />
The representation of MRO features comprises some indicators and interactive controls. In the {{UBIK}} child list, the main object displays cumulated technical and organisational status as well as the overall work progress based on the underlying data branch. Objects classified as MRO objects in general provide indicators for the MRO status. This means the status is shown next to the main icon of a child-/details-/documents-page as well as next to the icons of the child list items:<br />
<br />
=== Technical Status ===<br />
{{UnderConstructionStart}}<br />
<br />
The technical status indicates whether all tasks on an object or on its subsequent objects within the underlying data branch have been completed. It also aggregates additional state information, such as issues reported on child items. For example, if an inventory object is marked as damaged, this status is propagated to its parent objects, which will display a corresponding indicator (an exclamation mark) to signal a problem originating from a child item.<br />
<br />
{{UnderConstructionEnd}}<br />
<br />
<gallery><br />
File:UI_WinX_MRO_TechnicalStatusIndicator.png|thumb|Technical Status Indicator (WinX)<br />
File:Android_tech_status.PNG|thumb|Technical Status Indicator (Android)<br />
</gallery><br />
<br />
<br />
<br />
=== Organisational Status ===<br />
The organisational status indicates the amount of confirmed work within the data branch, including already confirmed work packages as well as tasks that are locked by their owning work package. The organisational status indicator is displayed on all objects that represent an organisational state or receive the organisational status from subsequent objects in the underlying data branch, and visualizes the amount of confirmed work performed within that branch.<br />
<gallery><br />
File:UI_WinX_MRO_OrganisationalStatusIndicator.png|Organisational Status Indicator (WinX)<br />
File:UI_WinX_MRO_WPConfirmedIndicator.png|MRO Workpackage Confirmed (Flag) Indicator (WinX)<br />
File:Android_orga_status.PNG|Organisational Status Indicator (Android)<br />
File:Android_orga_status_finished.PNG|MRO Workpackage Confirmed Indicator (Android)<br />
</gallery><br />
<br />
<br />
=== Work Progress ===<br />
The work progress is calculated from the current work progress and from the progress cumulated from subsequent objects in the underlying data branch. This indicator shows the amount of work done in the data branch.<br />
<br />
{{Version/WinXSince|5.0}} {{Version/MobileSince|5.0}} By default, the progress is displayed with maximum one decimal place. For example, 99.75% is displayed as 99.8%. The format string used to achieve this is <code>{0:0.#}%</code>.<br />
<br />
If other numeric formats are preferred in your usecases, you can refer to [https://learn.microsoft.com/en-us/dotnet/standard/base-types/custom-numeric-format-strings custom numeric format strings] for more information. The template to customize for this is the UBIKMROProgressBadge within UBIKThemes.<br />
<br />
{{Clear}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== MRO Objects ==<br />
A set of specific objects can be used to provide the required structure for MRO:<br />
<br />
=== Task Owner ===<br />
A [[MROCLS_MRO_TASKOWNER|Task Owner]] is an object having a substructure of jobs to be done. It can have a tree of other task owners or work packages underneath that will update the status of the task owner. This status consists of technical, organisational and progress information. With a task owner a user can get an overview of all the work to be done in the underlying job structure.<br />
<br />
=== Work Package===<br />
A [[MROCLS_MRO_WORKPACKAGE|Work Package]] is a collection of objects to collect and summarize other task owning objects, workpackages, or tasks. A simple workpackage has a certain amount of tasks that have to be finished in order to confirm the workpackage as done. More complex workpackages can also own other underlying workpackages that have to be confirmed. Confirming a workpackage itself requires a progress of 100% of all related tasks, as well as 100% confirmed sub work packages.<br />
<br />
<gallery><br />
File:UI_WinX_MRO_WPConfirmButton.png|MRO Workpackage confirm button (WinX)<br />
File:UI_WinX_MRO_WPRevokeConfirmButton.png|MRO Workpackage revoke confirmation button (WinX)<br />
File:Android_finish_workpackage.PNG|MRO Workpackage confirm button (Android)<br />
File:Android reopen workpackage.PNG|MRO Workpackage revoke confirmation button (Android)<br />
</gallery><br />
<br />
=== Task ===<br />
A [[MROCLS_MRO_TASK|Task]] is an object reporting a certain progress to the owning workpackage. There are several specialized types of task objects. All kinds of tasks have a property called '''VALUE''' in common. It is very important, that this property is able to be validated. Therefore, a MetaAttribute (providing a validation timestamp by default) has to be attached on the used MetaProperty.<br />
<br />
On both clients, a Task can be reverted by clicking twice on the Not Applicable button.<br />
<br />
<br />
<br />
{{Attention|The MetaProperty ''VALUE'' has to use [[Attributes]] in order to be validated. Otherwise, the calculation of work progress will not be possible.}}<br />
<br />
==== Measurement Task ====<br />
<br />
A [[MROCLS_MRO_MEASUREMENT_TASK|Measurement Task]] inherits from [[MROCLS_MRO_TASK|Task]] and documents a measured value (e.g. read from a pressure gauge). Therefore, clicking the value on the shown task opens an editor to enter the desired value. If no value was entered before, an empty line will be shown. Once a value has been entered, the task is finished. Alternatively, the task can also be closed by the option ''Not Applicable'' to document the situation of not being able to fullfill the measurement (e.g. the pressure gauge is broken). An additional small value indicator below the main value can report e.g. the previously entered value. The behaviour of this previous value indicator has to be specified separately in the customizing.<br />
{{Clear}}<br />
<br />
<gallery widths=497px heights=69px><br />
File:Measurment Task Empty UWP.png|Measurement Task without a reported value (WinX)<br />
File:Measurment Task Not Empty UWP.png|Measurement Task with a reported value (WinX)<br />
File:Measurment Task Empty Android.jpg|Measurement Task without a reported value (Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
==== Progress Task ====<br />
<br />
[[MROCLS_MRO_PROGRESS_TASK| Progress Task]] inherits from [[MROCLS_MRO_MEASUREMENT_TASK|Task]] and reports a certain progress while fullfilling a task. The progress will influence the overall progress of the owning workpackage. If the task cannot be fullfilled, it can also be finished with the option ''Not Applicable''.<br />
<br />
There is also an [[MRO_PROGRESS_TASK_EDITOR|alternative editor]] available for progress tasks.{{Version/WinXSince|2.5.4}}<br />
{{Clear}}<br />
<br />
<gallery widths=497px heights=69px><br />
File:Progress Task UWP.png|Progress Task with a reported work progress (WinX)<br />
File:Progress Task Android.jpg|Progress Task with a reported work progress and a previous progress(Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
==== Check Task ====<br />
<br />
A [[MROCLS_MRO_CHECK_TASK|Check Task]] inherits from [[MROCLS_MRO_TASK|Task]] and is finished by reporting ''Done'' or ''Not Applicable''. This is intended for a simple To-Do task that is either done or not.<br />
{{Clear}}<br />
<br />
<gallery widths=497px heights=69px><br />
File:Check Task finished UWP.png|Unfinished MRO CheckTask (WinX)<br />
File:Check Task android.jpg|Not Applicable MRO CheckTask (Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
==== Inspection Task ====<br />
<br />
[[MROCLS_MRO_INSPECTION_TASK|Inspection Task]] inherits from [[MROCLS_MRO_TASK|Task]] and is finished, when the user reports with a positive or negative answer or ''Not Applicable'' (e.g. reporting a yes/no answer for existing equipment).<br />
{{Clear}}<br />
<br />
<gallery widths=497px heights=69px><br />
File:Finished Inspection Task UWP.png|Finished MRO InspectionTask (WinX)<br />
File:Inspection task android.jpg|Finished MRO InspectionTask (Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
==== Sequential Task ====<br />
The [[MROCLS_SEQUENTIALTASK|sequential task classification]] allows you to pre-define a sequence in which tasks are to be resolved by users. This means that it is required for one or multiple tasks to be finished in order for other tasks to become "unlocked" and editable. A task can have any number of "predecessors". Predecessors are the tasks that are required to be finished first.<br />
<br />
A task can have predecessors that live anywhere else in the object hierarchy. It is not necessary for a task and its predecessors to be part of the same work package, even though this is likely the most common use case.<br />
<br />
The state of a sequential task is evaluated both offline and online to get the best possible user experience. The user will see dependent tasks update immediately if their successors were finished, if those tasks are currently visible in the UI. There is 1 case in which the server-side state will override the client-side (offline) evaluation, discussed below.<br />
The state of each sequential task is evaluated the following way:<br />
<br />
# If the server-side state says the task is open, we consider this as the truthful state and don't do any other evaluation.<br />
# Check if the task has any predecessors.<br />
# Try to load each predecessor task.<br />
#* If loading of any predecessor fails (the object is not available offline), the task will be locked.<br />
# If all predecessor tasks are finished, the task is open and can be edited. Otherwise, the task is locked.<br />
<br />
The customizer setting up the task dependency relations needs to ensure that the dependencies are not cyclical. In this case, it would be impossible for any tasks in the "cycle" to be finished.<br />
<br />
'''Example'''<br />
<br />
As a demonstration of this feature, see [[Media:Sequential_tasks_winx.mp4|this video]]. The relations between tasks are defined as in [[Media:Task_relations.png|this image]], starting at A1 and A2, which are not dependent on any other tasks. The lines (from left to right) indicate dependencies. This means that B2 has tasks A1 and A2 as its predecessors, for example.<br />
<br />
<br />
==== Grouped Task {{Version/WinXSince|4.2}}{{Version/XamarinSince|4.2}} ====<br />
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 [[MROCLS_GROUPEDTASK|grouped tasks]].<br />
<br />
The idea is, a group of tasks can be defined as siblings to each other and they also share the same server configured threshold. When the number of finished tasks among that group exceeds the threshold, the entire group is considered as no longer necessary. When reflected in the overall status of the task owner(s), these tasks would appear as if they are finished.<br />
<br />
{{Hint|Technically speaking, the finished status is completely independent from the not necessary status on a task. A grouped task which is no longer necessary can be both finished or not yet finished. In other words, users don't have to finish a not necessary grouped task, but they still can.}}<br />
<br />
{{Hint|The precise status calculation for grouped tasks and their task owners requires the knowledge of all siblings tasks. Imagine 2 out of 3 tasks must be finished but the client only knows 1 in total and the others are only available at the server at that time. This makes it impossible to draw conclusions whether the task(s) should be necessary or not. Under such circumstances, the local status calculation is done as if these are just regular tasks.}}<br />
<br />
{{Hint|Like with the other MRO objects, the client always chooses the best available statuses for grouped tasks to present to the users. More specifically, it uses the statuses calculated by the server when the client is not offline and there are no uncommitted local changes on the involved objects. Otherwise, it uses the statuses calculated locally to the best of its knowledge.}}<br />
<br />
A task can also be a grouped and a sequential one at the same time. In such a case, the grouped nature of the sibling tasks will affect the way the task sequence completes.<br />
<br />
For example, task A1, A2 and A3 are 3 grouped sibling tasks and only 1 of them needs to be finished. At the same time, they are all predecessors of task B. Normally, all predecessors must be finished (and locked) before task B becomes the next one in the sequence and therefore unlocked. In this case, however, as soon as one of the predecessors is finished, all three become unnecessary (and locked) and task B unlocks as a result of that.<br />
<br />
<br />
==== Supervisor Task {{Version/XamarinSince|4.8}} ====<br />
As the name suggests, supervisor tasks are those that must be finished under supervision. When users want to finish a [[MROCLS_MRO_SUPERVISOR_TASK|supervisor task]], they must hand over their work devices to a supervisor. The latter checks the work status and scans an NFC tag if the work is approved. If the [[MROCLS_MRO_SUPERVISOR|supervisor]] has sufficient permissions for the task and the correct supervisor PIN is given, the task gets unlocked and the users can proceed to finish it.<br />
<br />
<gallery widths=300px heights=300px><br />
File:UI_Xamarin_Supervisor_Task_Before_Verification.jpg|Supervisor Task Before Verification/Unlocking (Mobile)<br />
File:UI_Xamarin_Supervisor_Task_Enter_PIN.jpg|Supervisor Task Enter PIN (Mobile)<br />
File:UI_Xamarin_Supervisor_Task_After_Verification.jpg|Supervisor Task After Verification/Unlocking (Mobile)<br />
</gallery><br />
<br />
A thing to note is that while the need to verify a supervisor task can be seen as a type of locking, it's certainly not the only reason for a [[Locked_Objects|locked object]]. This means a supervisor task can remain locked (although for different reasons) even after a supervisor has successfully verified it. This can often be the case if you use it in combination with other features such as [[MRO_Objects_(Client)#Sequential_Task|sequential tasks]], [[User_Rights|user rights]].<br />
<br />
{{Hint|For security reasons, the verification process is cancelled if the supervisor enters the wrong PIN for three times. Scanning the tag again is required in that case.}}<br />
{{Hint|A setting controls [[RFID_tags#Choose_which_information_to_use_from_a_tag|which information in a scanned tag is used]] during this process.}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
=== MRO objects with project information (WinX only) {{Version/WinXSince|2.5.4}} ===<br />
[[File:UI_WinX_MRO_ProjectInfo.png|thumb|MRO Object with Project Info (WinX)]]<br />
An MRO object (except tasks) might also bring along [[MROCLS_PROJECTINFORMATION|project information]]. In this case, the project information together with the MRO progress are displayed in a bar chart. The start & end dates of the MRO object are displayed on the progress bar. The length and the position of the progress bar, together with the current date mark indicate the timeline.<br />
{{Clear}}<br />
<br />
<br />
== Locking ==<br />
When an (MRO) object is locked, editing it becomes impossible. More details about [[Locked_Objects|locked objects]].<br />
<br />
<br />
<br />
<br />
== See also ==<br />
* [[MRO (Plugin)]]<br />
* [[MROCLS_PROJECT]]<br />
* [[MROCLS_PROJECTINFORMATION]]<br />
* [[MROCLS_SEQUENTIALTASK]]<br />
* [[MROCLS_GROUPEDTASK]]<br />
* [[MROCLS_MRO_CHECK_TASK]]<br />
* [[MROCLS_MRO_INSPECTION_TASK]]<br />
* [[MROCLS_MRO_MEASUREMENT_TASK]]<br />
* [[MROCLS_MRO_PROGRESS_TASK]]<br />
* [[MROCLS_MRO_TASK]]<br />
* [[MROCLS_MRO_TASKOWNER]]<br />
* [[MROCLS_MRO_WORKPACKAGE]]<br />
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)<br />
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)<br />
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)<br />
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)<br />
<br />
[[Category:Android|MRO Objects (UBIK WinX)]]<br />
[[Category:Client|MRO Objects (Client)]]<br />
[[Category:Mobile|MRO Objects (Client)]]<br />
[[Category:Pages with broken file links|MRO Objects (Client)]]<br />
[[Category:WinX|MRO Objects (UBIK WinX)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(WinX)&diff=29338Version 5.1 (WinX)2026-02-10T09:57:56Z<p>LGE: </p>
<hr />
<div>{{Attention|This version requires [https://en.wikipedia.org/wiki/Windows_10_version_history#Version_1809_(October_2018_Update) Windows 10 build 17763] or higher}}<br />
<br />
== Availability ==<br />
{{key press|Store}}: Publicly available in Microsoft Store.<br />
<br />
{{key press|Store Beta}} / {{key press|Store Preview}}: Publicly available in Microsoft Store as beta or preview versions to those whose account email is participating in our beta or preview test. To join, please send an email to testing@augmensys.com and provide an email address to add to the list as well as the information which test you want to join. Alternatively you can contact the Augmensys staff and submit your chosen email address.<br />
<br />
Example: Please add my email account example@example.com to the '''Beta''' test group for the '''WinX''' client.<br />
<br />
<br/><br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
<br />
=== 5.1.5 on 2026-02-10 ===<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where certain documents couldn't be loaded anymore.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed an issue where the UI did not update properly when committing a direct edit input task.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Added a [[XAML#UBIKWebView|UBIKWebView]] control that includes a fix in the WebView2 where some links could not be opened.<br />
* Fixed issue that caused input fields to be focused but not editable.<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Free Text Annotations that where created in former sessions cannot be selected and therefore cannot be edited any more.<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* Known issues regarding the [[Documents_(Client)#Remember_Document_Settings|Remember Document Settings]] feature:<br />
** Saving the Zoom value via touch gestures is not supported.<br />
** Due to a third-party framework issue it can't be guaranteed that saving the Zoom level is always working properly. We reported this issue and will update our solution as soon as it is resolved on their side.<br />
<br/><br />
<br />
= ⚠️ XAML Notes =<br />
<br />
<br />
<br />
<headertabs /><br />
<br />
<br />
{{Category/Version2|{{PAGENAME}}}}<br />
<br />
[[Category:Client|Version 5.1 (WinX)]]<br />
[[Category:Version 5.1|Version 5.1 (WinX)]]<br />
[[Category:WinX|Version 5.1 (WinX)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(WinX)&diff=29337Version 5.1 (WinX)2026-02-10T09:54:21Z<p>LGE: </p>
<hr />
<div>{{Attention|This version requires [https://en.wikipedia.org/wiki/Windows_10_version_history#Version_1809_(October_2018_Update) Windows 10 build 17763] or higher}}<br />
<br />
== Availability ==<br />
{{key press|Store}}: Publicly available in Microsoft Store.<br />
<br />
{{key press|Store Beta}} / {{key press|Store Preview}}: Publicly available in Microsoft Store as beta or preview versions to those whose account email is participating in our beta or preview test. To join, please send an email to testing@augmensys.com and provide an email address to add to the list as well as the information which test you want to join. Alternatively you can contact the Augmensys staff and submit your chosen email address.<br />
<br />
Example: Please add my email account example@example.com to the '''Beta''' test group for the '''WinX''' client.<br />
<br />
<br/><br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
<br />
=== 5.1.5 on 2026-02-10 ===<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where certain documents couldn't be loaded anymore.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed an issue where the UI did not update properly when committing a direct edit input task.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Added a [[XAML#UBIKWebView|UBIKWebView]] control that includes a fix in the WebView2 where some links could not be opened.<br />
* Fixed issue that caused input fields to be focused but not editable.<br />
* Fixed an issue where MRO progress gets rounded up too aggressively.<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Free Text Annotations that where created in former sessions cannot be selected and therefore cannot be edited any more.<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* Known issues regarding the [[Documents_(Client)#Remember_Document_Settings|Remember Document Settings]] feature:<br />
** Saving the Zoom value via touch gestures is not supported.<br />
** Due to a third-party framework issue it can't be guaranteed that saving the Zoom level is always working properly. We reported this issue and will update our solution as soon as it is resolved on their side.<br />
<br/><br />
<br />
= ⚠️ XAML Notes =<br />
<br />
<br />
<br />
<headertabs /><br />
<br />
<br />
{{Category/Version2|{{PAGENAME}}}}<br />
<br />
[[Category:Client|Version 5.1 (WinX)]]<br />
[[Category:Version 5.1|Version 5.1 (WinX)]]<br />
[[Category:WinX|Version 5.1 (WinX)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=List_of_Versions&diff=29321List of Versions2026-02-09T16:35:06Z<p>LGE: </p>
<hr />
<div>[[File:IC_MainPage-20.png]] '''Future versions'''<br />
<hr/><br />
<div class="table" style="width:100%;"><br />
{{Item/Version|2025-??-??| {{Version/Server|5.0.0}}}}<br />
</div><br />
{{Check mark}} '''Released versions'''<br />
<hr/><br />
<div class="table" style="width:100%;"><br />
{{Item/Version|2026-02-10| {{Version/WinX|5.1}}}}<br />
{{Item/Version|2026-02-10| {{Version/Mobile|5.1}}}}<br />
{{Item/Version|2025-09-29| {{Version/WinX|5.0}}}}<br />
{{Item/Version|2025-09-27| {{Version/Mobile|5.0}}}}<br />
{{Item/Version|2025-03-14| {{Version/Server|4.9.0}}}}<br />
{{Item/Version|2025-02-05| {{Version/WinX|4.9}}}}<br />
{{Item/Version|2025-02-05| {{Version/Xamarin|4.9}}}}<br />
{{Item/Version|2024-09-14| {{Version/Server|4.8.1}}}}<br />
{{Item/Version|2024-09-11| {{Version/WinX|4.8}}}}<br />
{{Item/Version|2024-09-11| {{Version/Xamarin|4.8}}}}<br />
{{Item/Version|2024-05-16| {{Version/Xamarin|4.7}}}}<br />
{{Item/Version|2024-05-16| {{Version/WinX|4.7}}}}<br />
{{Item/Version|2024-05-07| {{Version/Server|4.7.0}}}}<br />
{{Item/Version|2024-02-05| {{Version/Server|4.6.0}}}}<br />
{{Item/Version|2024-02-15| {{Version/WinX|4.6}}}}<br />
{{Item/Version|2024-02-05| {{Version/Xamarin|4.6}}}}<br />
{{Item/Version|2023-11-06| {{Version/Server|4.5.0}}}}<br />
{{Item/Version|2023-11-02| {{Version/Xamarin|4.5}}}}<br />
{{Item/Version|2023-11-02| {{Version/WinX|4.5}}}}<br />
{{Item/Version|2023-09-12| {{Version/Server|4.4.0}}}}<br />
{{Item/Version|2023-09-04| {{Version/Xamarin|4.4}}}}<br />
{{Item/Version|2023-09-04| {{Version/WinX|4.4}}}}<br />
{{Item/Version|2022-04-11| [[Version_4.3.0_(Server)|Version 4.3.0 - Server]]}}<br />
{{Item/Version|2023-04-04| {{Version/Xamarin|4.3}}}}<br />
{{Item/Version|2023-04-04| {{Version/WinX|4.3}}}}<br />
{{Item/Version|2023-01.31| [[Version_3.7.1|Version 3.7.1 - Server]]}}<br />
{{Item/Version|2023-01-30| {{Version/Xamarin|4.2}}}}<br />
{{Item/Version|2023-01-30| {{Version/WinX|4.2}}}}<br />
{{Item/Version|2022-11-17| {{Version/Server|4.0}}}}<br />
{{Item/Version|2022-08-22| {{Version/Xamarin|4.1}}}}<br />
{{Item/Version|2022-08-09| [[Version_3.7.0_Server|Version 3.7.0 - Server]]}}<br />
{{Item/Version|2022-07-22| {{Version/WinX|4.1}}}}<br />
{{Item/Version|2022-05-31| [[Version_3.6.2_Server|Version 3.6.2 - Server]]}}<br />
{{Item/Version|2022-04-26| {{Version/WinX|4.0}}}}<br />
{{Item/Version|2022-03-23| [[Version_3.6.1_Server|Version 3.6.1 - Server]]}}<br />
{{Item/Version|2022-01-19| {{Version/Server|3.6}}}}<br />
{{Item/Version|2021-12-22| {{Version/Xamarin|1.3}}}}<br />
{{Item/Version|2021-05-31| {{Version/Xamarin|1.2}}}}<br />
{{Item/Version|2021-04-23| {{Version/WinX|3.8}}}}<br />
{{Item/Version|2020-11-12| {{Version/Xamarin|1.1}}}}<br />
{{Item/Version|2020-04-09| {{Version/Server|3.5}}}}<br />
{{Item/Version|2020-03-27| {{Version/WinX|3.7}}}}<br />
{{Item/Version|2020-02-13| {{Version/WinX|3.6}}}}<br />
{{Item/Version|2019-11-04| [[Version_1.0_(Xamarin.iOS)|Version 1.0&nbsp;&nbsp;&nbsp; - Xamarin.iOS]]}}<br />
{{Item/Version|2019-10-21| [[Version_1.0_(Xamarin.Android)|Version 1.0&nbsp;&nbsp;&nbsp; - Xamarin.Android]]}}<br />
{{Item/Version|2019-04-30| {{Version/WinX|3.5}}}}<br />
{{Item/Version|2018-12-10| {{Version/Server|2.6}}}}<br />
{{Item/Version|2018-12-10| {{Version/WinX|3.4}}}}<br />
{{Item/Version|2018-10-24| {{Version/WinX|3.3}}}}<br />
{{Item/Version|2018-07-06| {{Version/WinX|3.2.0}}}}<br />
{{Item/Version|2018-04-19| {{Version/Android|3.0.0}}}}<br />
{{Item/Version|2018-04-04| {{Version/Server|2.6}}}}<br />
{{Item/Version|2018-03-08| {{Version/Android|2.6.0}}}}<br />
{{Item/Version|2018-01-23| {{Version/WinX|3.1.0}}}}<br />
{{Item/Version|2017-10-13| {{Version/WinX|3.0.0}}}}<br />
{{Item/Version|2017-06-14| {{Version/Server|2.6}}}}<br />
{{Item/Version|2017-02-13| {{Version/WinX|2.6.0}}}}<br />
{{Item/Version|2016-07-21| {{Version/Android|2.5.5}}}}<br />
{{Item/Version|2016-07-21| {{Version/Android|2.5.4}}}}<br />
{{Item/Version|2016-04-01| {{Version/Android|2.5.3}}}}<br />
{{Item/Version|2016-05-13| {{Version/WinX|2.5.2}}}}<br />
{{Item/Version|2016-01-27| {{Version/Android|2.5.2}}}}<br />
{{Item/Version|2015-11-25| {{Version/Web|2.5.0}}}}<br />
{{Item/Version|2015-11-20| {{Version/Android|2.5.1}}}}<br />
{{Item/Version|2015-11-17| {{Version/Android|2.5.0}}}}<br />
{{Item/Version|2015-10-15| {{Version/Server|2.5}}}}<br />
</div><br />
[[File:IC_MainPage-20.png]] '''Available Release Candidates'''<br />
<hr/><br />
<div class="table" style="width:100%;"><br />
{{Item/Version|2020-01-01| {{Version/Android|3.1.0}}}}<br />
</div><br />
<hr/><br />
[[File:IC_MainPage-21.png]] '''[[:Category:Release notes|Previous versions]]'''</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(Mobile)&diff=29320Version 5.1 (Mobile)2026-02-09T16:33:35Z<p>LGE: </p>
<hr />
<div>{{Attention|Existing pre 5.0 XAMLs are not compatible with UBIK Mobile client 5.1. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.}}<br />
<br />
{{Attention|UBIK 5 clients can only connect to {{UBIK}} Servers of [[Version 3.6(Server)|version 3.6]] and higher!}}<br />
<br />
{{Attention|The minimum supported OS versions are:<br />
* Android 9;<br />
* iOS 12.}}<br />
<br />
== Availability ==<br />
{{key press|Android: Store}}{{key press|iOS: Store}}: Publicly available in Google Play Store / Apple App Store.<br />
<br />
{{key press|Android: Store Beta}}: Publicly available in Google Play Store as beta versions. You can opt in or out of the beta at any time in the store.<br />
<br />
{{key press|Android: Store Preview}}: Available through Google Play Store's [https://play.google.com/store/apps/details?id=com.augmensys.ubik.go invitation link].<br />
<br />
{{key press|iOS: Store Beta}}: Available through Apple App Store's [https://testflight.apple.com/join/Kmb1HG9E invitation link].<br />
<br />
{{key press|iOS: Store Preview}}: Available through Apple App Store's [https://testflight.apple.com/join/yHRnbYbt invitation link].<br />
<br />
{{key press|Windows: Store Preview}}: The mobile Windows client is not an official product and is only distributed as test versions upon request and/or in our [https://release.augmensys.com/download/modules/client/mobile/ release portal].<br />
<br/><br />
<br />
<br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with a ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
<br />
=== 5.1.28 on 2026-02-10 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* The following features which existed in pre 5.0 versions are now available again in 5.1.<br />
** [[Map_View|Map view]].<br />
** [[POI_View_(Mobile)|POI view]]. (Aruco and OCR are not yet supported)<br />
** Location service.<br />
** [[Native_Push_(Client)|Native push]].<br />
** [[Charts]].<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Complete UI overhaul introduces a cleaner, more modern and adaptive user interface with various quality of life improvements.<br />
* UBIKTabView supports both dynamic and static items in combination with lazy loading.<br />
* Files in the app's data folder can now be opened or deleted directly in the developer settings.<br />
* Introduced a fully resource-driven UI theming system enabling fast, safe customization (dark mode, resizing, and consistent styling) by adapting a small set of centralized resources.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* Fixed an issue where remembered scroll positions were lost when the ItemsSource property of an SfListViewExt changed (e.g., Properties.ShowAllProperties).<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed issue that caused app to be stuck on splash screen after resuming from background.<br />
* Fixed an issue where StatusColor was not shown in the UI for objects that didn't additionally have a Progress.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Fixed an issue that caused content of the custom ContentControl to not be rendered sometimes.<br />
* (Android) Fixed an issue in the WebView where some links could not be opened.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the deletion of some objects was not reflected in the UI until refresh.<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true. In Mobile, deleting the last annotation does not correctly update the editor's internal edit state. As a result, the Save button may remain visible even though no edits exist.<br />
* When changing the device orientation during attaching a photo on iOS, the app gets stuck. This is an issue Microsoft confirmed in .NET9 and will fix in .NET10.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Currently, the Samsung keyboard doesn't show {{key press|,}} at all, regardless of the current language/locale setting of the device. Please use a different virtual keyboard (e.g. Gboard from Google) instead if {{key press|.}} is unacceptable.<br />
* The periodic execution of background pushes is not guaranteed on iOS (the native push feature doesn't have this issue).<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* It is currently not possible to select which camera to use for AR views (e.g. scan page) on Windows.<br />
* SfPullToRefresh was removed due to [[Mobile_XAML#Issues_with_SfPullToRefresh_in_Mobile_client|existing issues]], and replaced with a Refresh option in the Context menu.<br />
<br />
<br />
= ⚠️ XAML Notes =<br />
Due to the change of the underlying XAML technology, the existing XAMLs for the old mobile clients (pre 5.0) are no longer compatible. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.<br />
<br />
<br />
<headertabs /><br />
<br />
[[Category:Client|Version 5.1 (Mobile)]]<br />
[[Category:Mobile|Version 5.1 (Mobile)]]<br />
[[Category:Version 5.1|Version 5.1 (Mobile)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(Mobile)&diff=29315Version 5.1 (Mobile)2026-02-09T15:46:33Z<p>LGE: </p>
<hr />
<div>{{Attention|Existing pre 5.0 XAMLs are not compatible with UBIK Mobile client 5.1. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.}}<br />
<br />
{{Attention|UBIK 5 clients can only connect to {{UBIK}} Servers of [[Version 3.6(Server)|version 3.6]] and higher!}}<br />
<br />
{{Attention|The minimum supported OS versions are:<br />
* Android 9;<br />
* iOS 12.}}<br />
<br />
== Availability ==<br />
{{key press|Android: Store}}{{key press|iOS: Store}}: Publicly available in Google Play Store / Apple App Store.<br />
<br />
{{key press|Android: Store Beta}}: Publicly available in Google Play Store as beta versions. You can opt in or out of the beta at any time in the store.<br />
<br />
{{key press|Android: Store Preview}}: Available through Google Play Store's [https://play.google.com/store/apps/details?id=com.augmensys.ubik.go invitation link].<br />
<br />
{{key press|iOS: Store Beta}}: Available through Apple App Store's [https://testflight.apple.com/join/Kmb1HG9E invitation link].<br />
<br />
{{key press|iOS: Store Preview}}: Available through Apple App Store's [https://testflight.apple.com/join/yHRnbYbt invitation link].<br />
<br />
{{key press|Windows: Store Preview}}: The mobile Windows client is not an official product and is only distributed as test versions upon request and/or in our [https://release.augmensys.com/download/modules/client/mobile/ release portal].<br />
<br/><br />
<br />
<br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with a ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
<br />
=== 5.1.28 on 2026-02-10 ===<br />
* The following features which existed in pre 5.0 versions are now available again in 5.1.<br />
** [[Map_View|Map view]].<br />
** [[POI_View_(Mobile)|POI view]]. (Aruco and OCR are not yet supported)<br />
** Location service.<br />
** [[Native_Push_(Client)|Native push]].<br />
** [[Charts]].<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Complete UI overhaul introduces a cleaner, more modern and adaptive user interface with various quality of life improvements.<br />
* UBIKTabView supports both dynamic and static items in combination with lazy loading.<br />
* Files in the app's data folder can now be opened or deleted directly in the developer settings.<br />
* Introduced a fully resource-driven UI theming system enabling fast, safe customization (dark mode, resizing, and consistent styling) by adapting a small set of centralized resources.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* Fixed an issue where remembered scroll positions were lost when the ItemsSource property of an SfListViewExt changed (e.g., Properties.ShowAllProperties).<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed issue that caused app to be stuck on splash screen after resuming from background.<br />
* Fixed an issue where StatusColor was not shown in the UI for objects that didn't additionally have a Progress.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Fixed an issue that caused content of the custom ContentControl to not be rendered sometimes.<br />
* (Android) Fixed an issue in the WebView where some links could not be opened.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the deletion of some objects was not reflected in the UI until refresh.<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true. In Mobile, deleting the last annotation does not correctly update the editor's internal edit state. As a result, the Save button may remain visible even though no edits exist.<br />
* When changing the device orientation during attaching a photo on iOS, the app gets stuck. This is an issue Microsoft confirmed in .NET9 and will fix in .NET10.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Currently, the Samsung keyboard doesn't show {{key press|,}} at all, regardless of the current language/locale setting of the device. Please use a different virtual keyboard (e.g. Gboard from Google) instead if {{key press|.}} is unacceptable.<br />
* The periodic execution of background pushes is not guaranteed on iOS (the native push feature doesn't have this issue).<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* It is currently not possible to select which camera to use for AR views (e.g. scan page) on Windows.<br />
* SfPullToRefresh was removed due to [[Mobile_XAML#Issues_with_SfPullToRefresh_in_Mobile_client|existing issues]], and replaced with a Refresh option in the Context menu.<br />
<br />
<br />
= ⚠️ XAML Notes =<br />
Due to the change of the underlying XAML technology, the existing XAMLs for the old mobile clients (pre 5.0) are no longer compatible. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.<br />
<br />
<br />
<headertabs /><br />
<br />
[[Category:Client|Version 5.1 (Mobile)]]<br />
[[Category:Mobile|Version 5.1 (Mobile)]]<br />
[[Category:Version 5.1|Version 5.1 (Mobile)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(WinX)&diff=29314Version 5.1 (WinX)2026-02-09T15:46:16Z<p>LGE: </p>
<hr />
<div>{{Attention|This version requires [https://en.wikipedia.org/wiki/Windows_10_version_history#Version_1809_(October_2018_Update) Windows 10 build 17763] or higher}}<br />
<br />
== Availability ==<br />
{{key press|Store}}: Publicly available in Microsoft Store.<br />
<br />
{{key press|Store Beta}} / {{key press|Store Preview}}: Publicly available in Microsoft Store as beta or preview versions to those whose account email is participating in our beta or preview test. To join, please send an email to testing@augmensys.com and provide an email address to add to the list as well as the information which test you want to join. Alternatively you can contact the Augmensys staff and submit your chosen email address.<br />
<br />
Example: Please add my email account example@example.com to the '''Beta''' test group for the '''WinX''' client.<br />
<br />
<br/><br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
<br />
=== 5.1.5 on 2026-02-10 ===<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where certain documents couldn't be loaded anymore.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed an issue where the UI did not update properly when committing a direct edit input task.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Added a [[XAML#UBIKWebView|UBIKWebView]] control that includes a fix in the WebView2 where some links could not be opened.<br />
* Fixed issue that caused input fields to be focused but not editable.<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Free Text Annotations that where created in former sessions cannot be selected and therefore cannot be edited any more.<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* Known issues regarding the [[Documents_(Client)#Remember_Document_Settings|Remember Document Settings]] feature:<br />
** Saving the Zoom value via touch gestures is not supported.<br />
** Due to a third-party framework issue it can't be guaranteed that saving the Zoom level is always working properly. We reported this issue and will update our solution as soon as it is resolved on their side.<br />
<br/><br />
<br />
= ⚠️ XAML Notes =<br />
<br />
<br />
<br />
<headertabs /><br />
<br />
<br />
{{Category/Version2|{{PAGENAME}}}}<br />
<br />
[[Category:Client|Version 5.1 (WinX)]]<br />
[[Category:Version 5.1|Version 5.1 (WinX)]]<br />
[[Category:WinX|Version 5.1 (WinX)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(WinX)&diff=29310Version 5.1 (WinX)2026-02-09T13:15:01Z<p>LGE: </p>
<hr />
<div>{{Attention|This version requires [https://en.wikipedia.org/wiki/Windows_10_version_history#Version_1809_(October_2018_Update) Windows 10 build 17763] or higher}}<br />
<br />
== Availability ==<br />
{{key press|Store}}: Publicly available in Microsoft Store.<br />
<br />
{{key press|Store Beta}} / {{key press|Store Preview}}: Publicly available in Microsoft Store as beta or preview versions to those whose account email is participating in our beta or preview test. To join, please send an email to testing@augmensys.com and provide an email address to add to the list as well as the information which test you want to join. Alternatively you can contact the Augmensys staff and submit your chosen email address.<br />
<br />
Example: Please add my email account example@example.com to the '''Beta''' test group for the '''WinX''' client.<br />
<br />
<br/><br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
<br />
=== 5.1.?? on 2026-02-?? ===<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where certain documents couldn't be loaded anymore.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed an issue where the UI did not update properly when committing a direct edit input task.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Added a [[XAML#UBIKWebView|UBIKWebView]] control that includes a fix in the WebView2 where some links could not be opened.<br />
* Fixed issue that caused input fields to be focused but not editable.<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Free Text Annotations that where created in former sessions cannot be selected and therefore cannot be edited any more.<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* Known issues regarding the [[Documents_(Client)#Remember_Document_Settings|Remember Document Settings]] feature:<br />
** Saving the Zoom value via touch gestures is not supported.<br />
** Due to a third-party framework issue it can't be guaranteed that saving the Zoom level is always working properly. We reported this issue and will update our solution as soon as it is resolved on their side.<br />
<br/><br />
<br />
= ⚠️ XAML Notes =<br />
<br />
<br />
<br />
<headertabs /><br />
<br />
<br />
{{Category/Version2|{{PAGENAME}}}}<br />
<br />
[[Category:Client|Version 5.1 (WinX)]]<br />
[[Category:Version 5.1|Version 5.1 (WinX)]]<br />
[[Category:WinX|Version 5.1 (WinX)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(Mobile)&diff=29309Version 5.1 (Mobile)2026-02-09T13:14:56Z<p>LGE: </p>
<hr />
<div>{{Attention|Existing pre 5.0 XAMLs are not compatible with UBIK Mobile client 5.1. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.}}<br />
<br />
{{Attention|UBIK 5 clients can only connect to {{UBIK}} Servers of [[Version 3.6(Server)|version 3.6]] and higher!}}<br />
<br />
{{Attention|The minimum supported OS versions are:<br />
* Android 9;<br />
* iOS 12.}}<br />
<br />
== Availability ==<br />
{{key press|Android: Store}}{{key press|iOS: Store}}: Publicly available in Google Play Store / Apple App Store.<br />
<br />
{{key press|Android: Store Beta}}: Publicly available in Google Play Store as beta versions. You can opt in or out of the beta at any time in the store.<br />
<br />
{{key press|Android: Store Preview}}: Available through Google Play Store's [https://play.google.com/store/apps/details?id=com.augmensys.ubik.go invitation link].<br />
<br />
{{key press|iOS: Store Beta}}: Available through Apple App Store's [https://testflight.apple.com/join/Kmb1HG9E invitation link].<br />
<br />
{{key press|iOS: Store Preview}}: Available through Apple App Store's [https://testflight.apple.com/join/yHRnbYbt invitation link].<br />
<br />
{{key press|Windows: Store Preview}}: The mobile Windows client is not an official product and is only distributed as test versions upon request and/or in our [https://release.augmensys.com/download/modules/client/mobile/ release portal].<br />
<br/><br />
<br />
<br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with a ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
<br />
=== 5.1.??? on 2026-02-?? ===<br />
* The following features which existed in pre 5.0 versions are now available again in 5.1.<br />
** [[Map_View|Map view]].<br />
** [[POI_View_(Mobile)|POI view]]. (Aruco and OCR are not yet supported)<br />
** Location service.<br />
** [[Native_Push_(Client)|Native push]].<br />
** [[Charts]].<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Complete UI overhaul introduces a cleaner, more modern and adaptive user interface with various quality of life improvements.<br />
* UBIKTabView supports both dynamic and static items in combination with lazy loading.<br />
* Files in the app's data folder can now be opened or deleted directly in the developer settings.<br />
* Introduced a fully resource-driven UI theming system enabling fast, safe customization (dark mode, resizing, and consistent styling) by adapting a small set of centralized resources.<br />
* Added support for [[File_Upload_Size_Restriction|configurable file-upload size restrictions]], preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* Fixed an issue where remembered scroll positions were lost when the ItemsSource property of an SfListViewExt changed (e.g., Properties.ShowAllProperties).<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed issue that caused app to be stuck on splash screen after resuming from background.<br />
* Fixed an issue where StatusColor was not shown in the UI for objects that didn't additionally have a Progress.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Fixed an issue that caused content of the custom ContentControl to not be rendered sometimes.<br />
* (Android) Fixed an issue in the WebView where some links could not be opened.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the deletion of some objects was not reflected in the UI until refresh.<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true. In Mobile, deleting the last annotation does not correctly update the editor's internal edit state. As a result, the Save button may remain visible even though no edits exist.<br />
* When changing the device orientation during attaching a photo on iOS, the app gets stuck. This is an issue Microsoft confirmed in .NET9 and will fix in .NET10.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Currently, the Samsung keyboard doesn't show {{key press|,}} at all, regardless of the current language/locale setting of the device. Please use a different virtual keyboard (e.g. Gboard from Google) instead if {{key press|.}} is unacceptable.<br />
* The periodic execution of background pushes is not guaranteed on iOS (the native push feature doesn't have this issue).<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* It is currently not possible to select which camera to use for AR views (e.g. scan page) on Windows.<br />
* SfPullToRefresh was removed due to [[Mobile_XAML#Issues_with_SfPullToRefresh_in_Mobile_client|existing issues]], and replaced with a Refresh option in the Context menu.<br />
<br />
<br />
= ⚠️ XAML Notes =<br />
Due to the change of the underlying XAML technology, the existing XAMLs for the old mobile clients (pre 5.0) are no longer compatible. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.<br />
<br />
<br />
<headertabs /><br />
<br />
[[Category:Client|Version 5.1 (Mobile)]]<br />
[[Category:Mobile|Version 5.1 (Mobile)]]<br />
[[Category:Version 5.1|Version 5.1 (Mobile)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.1_(WinX)&diff=29308Version 5.1 (WinX)2026-02-09T13:08:42Z<p>LGE: </p>
<hr />
<div>{{Attention|This version requires [https://en.wikipedia.org/wiki/Windows_10_version_history#Version_1809_(October_2018_Update) Windows 10 build 17763] or higher}}<br />
<br />
== Availability ==<br />
{{key press|Store}}: Publicly available in Microsoft Store.<br />
<br />
{{key press|Store Beta}} / {{key press|Store Preview}}: Publicly available in Microsoft Store as beta or preview versions to those whose account email is participating in our beta or preview test. To join, please send an email to testing@augmensys.com and provide an email address to add to the list as well as the information which test you want to join. Alternatively you can contact the Augmensys staff and submit your chosen email address.<br />
<br />
Example: Please add my email account example@example.com to the '''Beta''' test group for the '''WinX''' client.<br />
<br />
<br/><br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
<br />
=== 5.1.?? on 2026-02-?? ===<br />
* UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection.<br />
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.<br />
* Added support for configurable file-upload size restrictions, preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.<br />
* Fixed an issue where certain documents couldn't be loaded anymore.<br />
* Fixed an issue where annotated image documents do not appear as changed until the UI refreshes.<br />
* Fixed an issue where displayed file content does not update after you revert its changes.<br />
* The UI now updates correctly after mass deletion in multi-selection mode.<br />
* Fixed an issue where the UI did not update properly when committing a direct edit input task.<br />
* Fixed an issue where toggling NA in the String Editor did not behave correctly.<br />
* Fixed an issue where the Chart Thresholds didn't update.<br />
* Added a [[XAML#UBIKWebView|UBIKWebView]] control that includes a fix in the WebView2 where some links could not be opened.<br />
* Fixed issue that caused input fields to be focused but not editable.<br />
<br />
<br />
== Known issues ==<br />
* Due to third-party limitations, the feature that shows the ImageEditor Save button only when edits have been made is only active when MergeAnnotationsOnSave is set to true.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Free Text Annotations that where created in former sessions cannot be selected and therefore cannot be edited any more.<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* Known issues regarding the [[Documents_(Client)#Remember_Document_Settings|Remember Document Settings]] feature:<br />
** Saving the Zoom value via touch gestures is not supported.<br />
** Due to a third-party framework issue it can't be guaranteed that saving the Zoom level is always working properly. We reported this issue and will update our solution as soon as it is resolved on their side.<br />
<br/><br />
<br />
= ⚠️ XAML Notes =<br />
<br />
<br />
<br />
<headertabs /><br />
<br />
<br />
{{Category/Version2|{{PAGENAME}}}}<br />
<br />
[[Category:Client|Version 5.1 (WinX)]]<br />
[[Category:Version 5.1|Version 5.1 (WinX)]]<br />
[[Category:WinX|Version 5.1 (WinX)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.0_(WinX)&diff=29277Version 5.0 (WinX)2026-01-26T12:23:49Z<p>LGE: </p>
<hr />
<div>{{Attention|This version requires [https://en.wikipedia.org/wiki/Windows_10_version_history#Version_1809_(October_2018_Update) Windows 10 build 17763] or higher}}<br />
<br />
== Availability ==<br />
{{key press|Store}}: Publicly available in Microsoft Store.<br />
<br />
{{key press|Store Beta}} / {{key press|Store Preview}}: Publicly available in Microsoft Store as beta or preview versions to those whose account email is participating in our beta or preview test. To join, please send an email to testing@augmensys.com and provide an email address to add to the list as well as the information which test you want to join. Alternatively you can contact the Augmensys staff and submit your chosen email address.<br />
<br />
Example: Please add my email account example@example.com to the '''Beta''' test group for the '''WinX''' client.<br />
<br />
<br/><br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
<br />
=== 5.0.42 on 2026-01-27 {{key press|Store}} ===<br />
* Fixed an issue where confirmed work packages are not automatically committed when you switch from offline to online mode.<br />
<br />
<br />
=== 5.0.41 on 2026-01-14 {{key press|Store}} ===<br />
* Fixed an issue where [[MRO_Objects_(Client)#Work_Progress|MRO progress]] is rounded up too aggressively and inconsistent with the mobile clients.<br />
<br />
<br />
=== 5.0.40 on 2025-12-18 {{key press|Store}} ===<br />
* Fixed an issue where the deletion of some objects was not reflected in the UI until refresh.<br />
<br />
<br />
=== 5.0.36 on 2025-10-02 {{key press|Store}} ===<br />
* Fixed an issue where task direct editing doesn't work the first time.<br />
<br />
<br />
=== 5.0.35 on 2025-09-29 {{key press|Store}} ===<br />
* Updated some translations.<br />
* Updated the default Demo profile.<br />
* Updated the notification message about branch download to avoid misunderstanding. When a branch download is in progress, you can work with the offline data which is already available at the time of the download, but any communication with the content server will be scheduled after the branch download is finished.<br />
* Fixed issue that rendered authentication when editing a geo property impossible.<br />
* Fixed an issue that triggered a license warning even on a failed login.<br />
* Fixed an issue where the wizard is shown again when you navigate to a new but saved object offline.<br />
* Fixed an issue where duplicate notifications are shown when you scan an NFC tag for a supervisor task and no fitting supervisor is found.<br />
<br />
<br />
== Known issues ==<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Free Text Annotations that where created in former sessions cannot be selected and therefore cannot be edited any more.<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* Known issues regarding the [[Documents_(Client)#Remember_Document_Settings|Remember Document Settings]] feature:<br />
** Saving the Zoom value via touch gestures is not supported.<br />
** Due to a third-party framework issue it can't be guaranteed that saving the Zoom level is always working properly. We reported this issue and will update our solution as soon as it is resolved on their side.<br />
<br />
<br/><br />
<br />
= ⚠️ XAML Notes =<br />
<br />
<br />
<br />
<headertabs /><br />
<br />
<br />
{{Category/Version2|{{PAGENAME}}}}<br />
<br />
[[Category:Client|Version 5.0 (WinX)]]<br />
[[Category:Version 5.0|Version 5.0 (WinX)]]<br />
[[Category:WinX|Version 5.0 (WinX)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.0_(Mobile)&diff=29260Version 5.0 (Mobile)2026-01-14T15:06:53Z<p>LGE: </p>
<hr />
<div>{{Attention|Existing pre 5.0 XAMLs are not compatible with UBIK Mobile client 5.0. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.}}<br />
<br />
{{Attention|UBIK 5 clients can only connect to {{UBIK}} Servers of [[Version 3.6(Server)|version 3.6]] and higher!}}<br />
<br />
{{Attention|The minimum supported OS versions are:<br />
* Android 9;<br />
* iOS 12.}}<br />
<br />
== Availability ==<br />
{{key press|Android: Store}}{{key press|iOS: Store}}: Publicly available in Google Play Store / Apple App Store.<br />
<br />
{{key press|Android: Store Beta}}: Publicly available in Google Play Store as beta versions. You can opt in or out of the beta at any time in the store.<br />
<br />
{{key press|Android: Store Preview}}: Available through Google Play Store's [https://play.google.com/store/apps/details?id=com.augmensys.ubik.go invitation link].<br />
<br />
{{key press|iOS: Store Beta}}: Available through Apple App Store's [https://testflight.apple.com/join/Kmb1HG9E invitation link].<br />
<br />
{{key press|iOS: Store Preview}}: Available through Apple App Store's [https://testflight.apple.com/join/yHRnbYbt invitation link].<br />
<br />
{{key press|Windows: Store Preview}}: The mobile Windows client is not an official product and is only distributed as test versions upon request and/or in our [https://release.augmensys.com/download/modules/client/mobile/ release portal].<br />
<br/><br />
<br />
<br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with a ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
<br />
=== 5.0.223 on 2025-11-17 {{key press|iOS: Store}} ===<br />
* (iOS) Fixed an issue where [[EvalExpression]] doesn't produce expected results for expressions containing "Condition ? A : B".<br />
<br />
<br />
=== 5.0.221 on 2025-11-05 {{key press|Android: Store}} ===<br />
* (Android) Fixed an issue where creating new objects when there are already a lot of existing ones leads to an app freeze or even crash.<br />
<br />
<br />
=== 5.0.218 on 2025-10-10 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Added logging of the authentication headers in UBIKWebserviceDebug.log for better diagnostics.<br />
* A third party issue was fixed where some text Annotations in the ImageEditor weren't visible on iOS.<br />
* A third party issue was fixed where stream bytes increased exponentially when saving Annotations in the ImageEditor.<br />
<br />
<br />
=== 5.0.212 on 2025-10-03 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Fixed an issue where task direct editing doesn't work the first time.<br />
* Updated the notification message about branch download to avoid misunderstanding. When a branch download is in progress, you can work with the offline data which is already available at the time of the download, but any communication with the content server will be scheduled after the branch download is finished.<br />
<br />
<br />
=== 5.0.209 on 2025-09-27 {{key press|Android: Store}} 5.0.207 on 2025-09-25 {{key press|iOS: Store}} ===<br />
* UBIK GO is the cutting-edge evolution of Augmensys' trusted mobile client — rebuilt from the ground up with a modern architecture that unlocks unprecedented flexibility.<br />
* Improved the branch download performance especially when there are duplicate objects in multiple branches.<br />
* Updated some translations.<br />
* Updated the default Demo profile.<br />
* Fixed an issue that triggered a license warning even on a failed login.<br />
* Fixed an issue where the wizard is shown again when you navigate to a new but saved object offline.<br />
* Fixed an issue where duplicate notifications are shown when you scan an NFC tag for a supervisor task and no fitting supervisor is found.<br />
<br />
<br />
== Known issues ==<br />
* When changing the device orientation during attaching a photo on iOS, the app gets stuck. This is an issue Microsoft confirmed in .NET9 and will fix in .NET10.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Currently, the Samsung keyboard doesn't show {{key press|,}} at all, regardless of the current language/locale setting of the device. Please use a different virtual keyboard (e.g. Gboard from Google) instead if {{key press|.}} is unacceptable.<br />
* The periodic execution of background pushes is not guaranteed on iOS.<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* It is currently not possible to select which camera to use for AR views (e.g. scan page) on Windows.<br />
* SfPullToRefresh was removed due to [[Mobile_XAML#Issues_with_SfPullToRefresh_in_Mobile_client|existing issues]], and replaced with a Refresh option in the Context menu.<br />
<br/><br />
<br />
<br />
<br />
<br />
<br />
= ⚠️ XAML Notes =<br />
Due to the change of the underlying XAML technology, the existing XAMLs for the old mobile clients (pre 5.0) are no longer compatible. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.<br />
<br />
<headertabs /><br />
<br />
[[Category:Client|Version 5.0 (Mobile)]]<br />
[[Category:Mobile|Version 5.0 (Mobile)]]<br />
[[Category:Version 5.0|Version 5.0 (Mobile)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.0_(WinX)&diff=29259Version 5.0 (WinX)2026-01-14T12:54:19Z<p>LGE: </p>
<hr />
<div>{{Attention|This version requires [https://en.wikipedia.org/wiki/Windows_10_version_history#Version_1809_(October_2018_Update) Windows 10 build 17763] or higher}}<br />
<br />
== Availability ==<br />
{{key press|Store}}: Publicly available in Microsoft Store.<br />
<br />
{{key press|Store Beta}} / {{key press|Store Preview}}: Publicly available in Microsoft Store as beta or preview versions to those whose account email is participating in our beta or preview test. To join, please send an email to testing@augmensys.com and provide an email address to add to the list as well as the information which test you want to join. Alternatively you can contact the Augmensys staff and submit your chosen email address.<br />
<br />
Example: Please add my email account example@example.com to the '''Beta''' test group for the '''WinX''' client.<br />
<br />
<br/><br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
<br />
=== 5.0.41 on 2026-01-14 {{key press|Store}} ===<br />
* Fixed an issue where [[MRO_Objects_(Client)#Work_Progress|MRO progress]] is rounded up too aggressively and inconsistent with the mobile clients.<br />
<br />
<br />
=== 5.0.40 on 2025-12-18 {{key press|Store}} ===<br />
* Fixed an issue where the deletion of some objects was not reflected in the UI until refresh.<br />
<br />
<br />
=== 5.0.36 on 2025-10-02 {{key press|Store}} ===<br />
* Fixed an issue where task direct editing doesn't work the first time.<br />
<br />
<br />
=== 5.0.35 on 2025-09-29 {{key press|Store}} ===<br />
* Updated some translations.<br />
* Updated the default Demo profile.<br />
* Updated the notification message about branch download to avoid misunderstanding. When a branch download is in progress, you can work with the offline data which is already available at the time of the download, but any communication with the content server will be scheduled after the branch download is finished.<br />
* Fixed issue that rendered authentication when editing a geo property impossible.<br />
* Fixed an issue that triggered a license warning even on a failed login.<br />
* Fixed an issue where the wizard is shown again when you navigate to a new but saved object offline.<br />
* Fixed an issue where duplicate notifications are shown when you scan an NFC tag for a supervisor task and no fitting supervisor is found.<br />
<br />
<br />
== Known issues ==<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Free Text Annotations that where created in former sessions cannot be selected and therefore cannot be edited any more.<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* Known issues regarding the [[Documents_(Client)#Remember_Document_Settings|Remember Document Settings]] feature:<br />
** Saving the Zoom value via touch gestures is not supported.<br />
** Due to a third-party framework issue it can't be guaranteed that saving the Zoom level is always working properly. We reported this issue and will update our solution as soon as it is resolved on their side.<br />
<br />
<br/><br />
<br />
= ⚠️ XAML Notes =<br />
<br />
<br />
<br />
<headertabs /><br />
<br />
<br />
{{Category/Version2|{{PAGENAME}}}}<br />
<br />
[[Category:Client|Version 5.0 (WinX)]]<br />
[[Category:Version 5.0|Version 5.0 (WinX)]]<br />
[[Category:WinX|Version 5.0 (WinX)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.0_(WinX)&diff=29249Version 5.0 (WinX)2026-01-13T14:29:03Z<p>LGE: </p>
<hr />
<div>{{Attention|This version requires [https://en.wikipedia.org/wiki/Windows_10_version_history#Version_1809_(October_2018_Update) Windows 10 build 17763] or higher}}<br />
<br />
== Availability ==<br />
{{key press|Store}}: Publicly available in Microsoft Store.<br />
<br />
{{key press|Store Beta}} / {{key press|Store Preview}}: Publicly available in Microsoft Store as beta or preview versions to those whose account email is participating in our beta or preview test. To join, please send an email to testing@augmensys.com and provide an email address to add to the list as well as the information which test you want to join. Alternatively you can contact the Augmensys staff and submit your chosen email address.<br />
<br />
Example: Please add my email account example@example.com to the '''Beta''' test group for the '''WinX''' client.<br />
<br />
<br/><br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
<br />
=== 5.0.41 on 2026-01-?? {{key press|Store}} ===<br />
* Fixed an issue where [[MRO_Objects_(Client)#Work_Progress|MRO progress]] is rounded up too aggressively and inconsistent with the mobile clients.<br />
<br />
<br />
=== 5.0.40 on 2025-12-18 {{key press|Store}} ===<br />
* Fixed an issue where the deletion of some objects was not reflected in the UI until refresh.<br />
<br />
<br />
=== 5.0.36 on 2025-10-02 {{key press|Store}} ===<br />
* Fixed an issue where task direct editing doesn't work the first time.<br />
<br />
<br />
=== 5.0.35 on 2025-09-29 {{key press|Store}} ===<br />
* Updated some translations.<br />
* Updated the default Demo profile.<br />
* Updated the notification message about branch download to avoid misunderstanding. When a branch download is in progress, you can work with the offline data which is already available at the time of the download, but any communication with the content server will be scheduled after the branch download is finished.<br />
* Fixed issue that rendered authentication when editing a geo property impossible.<br />
* Fixed an issue that triggered a license warning even on a failed login.<br />
* Fixed an issue where the wizard is shown again when you navigate to a new but saved object offline.<br />
* Fixed an issue where duplicate notifications are shown when you scan an NFC tag for a supervisor task and no fitting supervisor is found.<br />
<br />
<br />
== Known issues ==<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Free Text Annotations that where created in former sessions cannot be selected and therefore cannot be edited any more.<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* Known issues regarding the [[Documents_(Client)#Remember_Document_Settings|Remember Document Settings]] feature:<br />
** Saving the Zoom value via touch gestures is not supported.<br />
** Due to a third-party framework issue it can't be guaranteed that saving the Zoom level is always working properly. We reported this issue and will update our solution as soon as it is resolved on their side.<br />
<br />
<br/><br />
<br />
= ⚠️ XAML Notes =<br />
<br />
<br />
<br />
<headertabs /><br />
<br />
<br />
{{Category/Version2|{{PAGENAME}}}}<br />
<br />
[[Category:Client|Version 5.0 (WinX)]]<br />
[[Category:Version 5.0|Version 5.0 (WinX)]]<br />
[[Category:WinX|Version 5.0 (WinX)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=MRO_Objects_(Client)&diff=29245MRO Objects (Client)2026-01-13T12:14:55Z<p>LGE: /* Work Progress */</p>
<hr />
<div>[[File:UI_WinX_MRO_ChildList.png|thumb|alt=MRO Child List UI (WinX)|MRO UI (WinX)]]<br />
[[File:Android_mro_ui.jpg|thumb|alt=MRO Child List UI (Android)|MRO UI (Android)]]<br />
The WinX client UI displays MRO configured objects like any other root- or child-object enriched by some additional logic and features.<br />
<br />
== Basic User Interface ==<br />
The representation of MRO features comprises some indicators and interactive controls. In the {{UBIK}} child list, the main object displays cumulated technical and organisational status as well as the overall work progress based on the underlying data branch. Objects classified as MRO objects in general provide indicators for the MRO status. This means the status is shown next to the main icon of a child-/details-/documents-page as well as next to the icons of the child list items:<br />
<br />
=== Technical Status ===<br />
The technical status indicator is shown on all objects that represent a technical state or receive the technical status from subsequent objects in the underlying data branch. If e.g. a inventory object is reported as damaged, its parent objects will all display the exclamation mark symbol to indicate that a problem was reported in the child items.<br />
<br />
<gallery><br />
File:UI_WinX_MRO_TechnicalStatusIndicator.png|thumb|Technical Status Indicator (WinX)<br />
File:Android_tech_status.PNG|thumb|Technical Status Indicator (Android)<br />
</gallery><br />
<br />
=== Organisational Status ===<br />
The organisational status indicator is shown on all objects that represent an organisational state or receive the organisational status from subsequent objects in the underlying data branch. This indicator shows the amount of confirmed work done in the data branch. It can as well display a work package to be already confirmed or show tasks that are already locked by their owning workpackage.<br />
<gallery><br />
File:UI_WinX_MRO_OrganisationalStatusIndicator.png|Organisational Status Indicator (WinX)<br />
File:UI_WinX_MRO_WPConfirmedIndicator.png|MRO Workpackage Confirmed (Flag) Indicator (WinX)<br />
File:Android_orga_status.PNG|Organisational Status Indicator (Android)<br />
File:Android_orga_status_finished.PNG|MRO Workpackage Confirmed Indicator (Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
=== Work Progress ===<br />
The work progress is shown on all objects that represent the current work progress or receive the work progress cumulated from subsequent objects in the underlying data branch. This indicator shows the amount of work done in the data branch.<br />
<br />
{{Version/WinXSince|5.0}} {{Version/MobileSince|5.0}} By default, the progress is displayed with maximum one decimal place. For example, 99.75% is displayed as 99.8%. The format string used to achieve this is <code>{0:0.#}%</code>.<br />
<br />
If other numeric formats are preferred in your usecases, you can refer to [https://learn.microsoft.com/en-us/dotnet/standard/base-types/custom-numeric-format-strings custom numeric format strings] for more information. The template to customize for this is the UBIKMROProgressBadge within UBIKThemes.<br />
<br />
{{Clear}}<br />
<br />
[[Category:Android|MRO Objects (UBIK WinX)]]<br />
[[Category:Client|MRO Objects (Client)]]<br />
[[Category:Mobile|MRO Objects (Client)]]<br />
[[Category:Pages with broken file links|MRO Objects (Client)]]<br />
[[Category:WinX|MRO Objects (UBIK WinX)]]<br />
<br />
== MRO Objects ==<br />
A set of specific objects can be used to provide the required structure for MRO:<br />
<br />
=== Task Owner ===<br />
A [[MROCLS_MRO_TASKOWNER|Task Owner]] is an object having a substructure of jobs to be done. It can have a tree of other task owners or work packages underneath that will update the status of the task owner. This status consists of technical, organisational and progress information. With a task owner a user can get an overview of all the work to be done in the underlying job structure.<br />
<br />
=== Work Package===<br />
A [[MROCLS_MRO_WORKPACKAGE|Work Package]] is a collection of objects to collect and summarize other task owning objects, workpackages, or tasks. A simple workpackage has a certain amount of tasks that have to be finished in order to confirm the workpackage as done. More complex workpackages can also own other underlying workpackages that have to be confirmed. Confirming a workpackage itself requires a progress of 100% of all related tasks, as well as 100% confirmed sub work packages.<br />
<br />
<gallery><br />
File:UI_WinX_MRO_WPConfirmButton.png|MRO Workpackage confirm button (WinX)<br />
File:UI_WinX_MRO_WPRevokeConfirmButton.png|MRO Workpackage revoke confirmation button (WinX)<br />
File:Android_finish_workpackage.PNG|MRO Workpackage confirm button (Android)<br />
File:Android reopen workpackage.PNG|MRO Workpackage revoke confirmation button (Android)<br />
</gallery><br />
<br />
=== Task ===<br />
A [[MROCLS_MRO_TASK|Task]] is an object reporting a certain progress to the owning workpackage. There are several specialized types of task objects. All kinds of tasks have a property called '''VALUE''' in common. It is very important, that this property is able to be validated. Therefore, a MetaAttribute (providing a validation timestamp by default) has to be attached on the used MetaProperty.<br />
<br />
On both clients, a Task can be reverted by clicking twice on the Not Applicable button.<br />
<br />
<br />
<br />
{{Attention|The MetaProperty ''VALUE'' has to use [[Attributes]] in order to be validated. Otherwise, the calculation of work progress will not be possible.}}<br />
<br />
==== Measurement Task ====<br />
<br />
A [[MROCLS_MRO_MEASUREMENT_TASK|Measurement Task]] inherits from [[MROCLS_MRO_TASK|Task]] and documents a measured value (e.g. read from a pressure gauge). Therefore, clicking the value on the shown task opens an editor to enter the desired value. If no value was entered before, an empty line will be shown. Once a value has been entered, the task is finished. Alternatively, the task can also be closed by the option ''Not Applicable'' to document the situation of not being able to fullfill the measurement (e.g. the pressure gauge is broken). An additional small value indicator below the main value can report e.g. the previously entered value. The behaviour of this previous value indicator has to be specified separately in the customizing.<br />
{{Clear}}<br />
<br />
<gallery widths=497px heights=69px><br />
File:Measurment Task Empty UWP.png|Measurement Task without a reported value (WinX)<br />
File:Measurment Task Not Empty UWP.png|Measurement Task with a reported value (WinX)<br />
File:Measurment Task Empty Android.jpg|Measurement Task without a reported value (Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
==== Progress Task ====<br />
<br />
[[MROCLS_MRO_PROGRESS_TASK| Progress Task]] inherits from [[MROCLS_MRO_MEASUREMENT_TASK|Task]] and reports a certain progress while fullfilling a task. The progress will influence the overall progress of the owning workpackage. If the task cannot be fullfilled, it can also be finished with the option ''Not Applicable''.<br />
<br />
There is also an [[MRO_PROGRESS_TASK_EDITOR|alternative editor]] available for progress tasks.{{Version/WinXSince|2.5.4}}<br />
{{Clear}}<br />
<br />
<gallery widths=497px heights=69px><br />
File:Progress Task UWP.png|Progress Task with a reported work progress (WinX)<br />
File:Progress Task Android.jpg|Progress Task with a reported work progress and a previous progress(Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
==== Check Task ====<br />
<br />
A [[MROCLS_MRO_CHECK_TASK|Check Task]] inherits from [[MROCLS_MRO_TASK|Task]] and is finished by reporting ''Done'' or ''Not Applicable''. This is intended for a simple To-Do task that is either done or not.<br />
{{Clear}}<br />
<br />
<gallery widths=497px heights=69px><br />
File:Check Task finished UWP.png|Unfinished MRO CheckTask (WinX)<br />
File:Check Task android.jpg|Not Applicable MRO CheckTask (Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
==== Inspection Task ====<br />
<br />
[[MROCLS_MRO_INSPECTION_TASK|Inspection Task]] inherits from [[MROCLS_MRO_TASK|Task]] and is finished, when the user reports with a positive or negative answer or ''Not Applicable'' (e.g. reporting a yes/no answer for existing equipment).<br />
{{Clear}}<br />
<br />
<gallery widths=497px heights=69px><br />
File:Finished Inspection Task UWP.png|Finished MRO InspectionTask (WinX)<br />
File:Inspection task android.jpg|Finished MRO InspectionTask (Android)<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
==== Sequential Task ====<br />
The [[MROCLS_SEQUENTIALTASK|sequential task classification]] allows you to pre-define a sequence in which tasks are to be resolved by users. This means that it is required for one or multiple tasks to be finished in order for other tasks to become "unlocked" and editable. A task can have any number of "predecessors". Predecessors are the tasks that are required to be finished first.<br />
<br />
A task can have predecessors that live anywhere else in the object hierarchy. It is not necessary for a task and its predecessors to be part of the same work package, even though this is likely the most common use case.<br />
<br />
The state of a sequential task is evaluated both offline and online to get the best possible user experience. The user will see dependent tasks update immediately if their successors were finished, if those tasks are currently visible in the UI. There is 1 case in which the server-side state will override the client-side (offline) evaluation, discussed below.<br />
The state of each sequential task is evaluated the following way:<br />
<br />
# If the server-side state says the task is open, we consider this as the truthful state and don't do any other evaluation.<br />
# Check if the task has any predecessors.<br />
# Try to load each predecessor task.<br />
#* If loading of any predecessor fails (the object is not available offline), the task will be locked.<br />
# If all predecessor tasks are finished, the task is open and can be edited. Otherwise, the task is locked.<br />
<br />
The customizer setting up the task dependency relations needs to ensure that the dependencies are not cyclical. In this case, it would be impossible for any tasks in the "cycle" to be finished.<br />
<br />
'''Example'''<br />
<br />
As a demonstration of this feature, see [[Media:Sequential_tasks_winx.mp4|this video]]. The relations between tasks are defined as in [[Media:Task_relations.png|this image]], starting at A1 and A2, which are not dependent on any other tasks. The lines (from left to right) indicate dependencies. This means that B2 has tasks A1 and A2 as its predecessors, for example.<br />
<br />
<br />
==== Grouped Task {{Version/WinXSince|4.2}}{{Version/XamarinSince|4.2}} ====<br />
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 [[MROCLS_GROUPEDTASK|grouped tasks]].<br />
<br />
The idea is, a group of tasks can be defined as siblings to each other and they also share the same server configured threshold. When the number of finished tasks among that group exceeds the threshold, the entire group is considered as no longer necessary. When reflected in the overall status of the task owner(s), these tasks would appear as if they are finished.<br />
<br />
{{Hint|Technically speaking, the finished status is completely independent from the not necessary status on a task. A grouped task which is no longer necessary can be both finished or not yet finished. In other words, users don't have to finish a not necessary grouped task, but they still can.}}<br />
<br />
{{Hint|The precise status calculation for grouped tasks and their task owners requires the knowledge of all siblings tasks. Imagine 2 out of 3 tasks must be finished but the client only knows 1 in total and the others are only available at the server at that time. This makes it impossible to draw conclusions whether the task(s) should be necessary or not. Under such circumstances, the local status calculation is done as if these are just regular tasks.}}<br />
<br />
{{Hint|Like with the other MRO objects, the client always chooses the best available statuses for grouped tasks to present to the users. More specifically, it uses the statuses calculated by the server when the client is not offline and there are no uncommitted local changes on the involved objects. Otherwise, it uses the statuses calculated locally to the best of its knowledge.}}<br />
<br />
A task can also be a grouped and a sequential one at the same time. In such a case, the grouped nature of the sibling tasks will affect the way the task sequence completes.<br />
<br />
For example, task A1, A2 and A3 are 3 grouped sibling tasks and only 1 of them needs to be finished. At the same time, they are all predecessors of task B. Normally, all predecessors must be finished (and locked) before task B becomes the next one in the sequence and therefore unlocked. In this case, however, as soon as one of the predecessors is finished, all three become unnecessary (and locked) and task B unlocks as a result of that.<br />
<br />
<br />
==== Supervisor Task {{Version/XamarinSince|4.8}} ====<br />
As the name suggests, supervisor tasks are those that must be finished under supervision. When users want to finish a [[MROCLS_MRO_SUPERVISOR_TASK|supervisor task]], they must hand over their work devices to a supervisor. The latter checks the work status and scans an NFC tag if the work is approved. If the [[MROCLS_MRO_SUPERVISOR|supervisor]] has sufficient permissions for the task and the correct supervisor PIN is given, the task gets unlocked and the users can proceed to finish it.<br />
<br />
<gallery widths=300px heights=300px><br />
File:UI_Xamarin_Supervisor_Task_Before_Verification.jpg|Supervisor Task Before Verification/Unlocking (Mobile)<br />
File:UI_Xamarin_Supervisor_Task_Enter_PIN.jpg|Supervisor Task Enter PIN (Mobile)<br />
File:UI_Xamarin_Supervisor_Task_After_Verification.jpg|Supervisor Task After Verification/Unlocking (Mobile)<br />
</gallery><br />
<br />
A thing to note is that while the need to verify a supervisor task can be seen as a type of locking, it's certainly not the only reason for a [[Locked_Objects|locked object]]. This means a supervisor task can remain locked (although for different reasons) even after a supervisor has successfully verified it. This can often be the case if you use it in combination with other features such as [[MRO_Objects_(Client)#Sequential_Task|sequential tasks]], [[User_Rights|user rights]].<br />
<br />
{{Hint|For security reasons, the verification process is cancelled if the supervisor enters the wrong PIN for three times. Scanning the tag again is required in that case.}}<br />
{{Hint|A setting controls [[RFID_tags#Choose_which_information_to_use_from_a_tag|which information in a scanned tag is used]] during this process.}}<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
=== MRO objects with project information (WinX only) {{Version/WinXSince|2.5.4}} ===<br />
[[File:UI_WinX_MRO_ProjectInfo.png|thumb|MRO Object with Project Info (WinX)]]<br />
An MRO object (except tasks) might also bring along [[MROCLS_PROJECTINFORMATION|project information]]. In this case, the project information together with the MRO progress are displayed in a bar chart. The start & end dates of the MRO object are displayed on the progress bar. The length and the position of the progress bar, together with the current date mark indicate the timeline.<br />
{{Clear}}<br />
<br />
<br />
== Locking ==<br />
When an (MRO) object is locked, editing it becomes impossible. More details about [[Locked_Objects|locked objects]].<br />
<br />
<br />
<br />
<br />
== See also ==<br />
* [[MRO (Plugin)]]<br />
* [[MROCLS_PROJECT]]<br />
* [[MROCLS_PROJECTINFORMATION]]<br />
* [[MROCLS_SEQUENTIALTASK]]<br />
* [[MROCLS_GROUPEDTASK]]<br />
* [[MROCLS_MRO_CHECK_TASK]]<br />
* [[MROCLS_MRO_INSPECTION_TASK]]<br />
* [[MROCLS_MRO_MEASUREMENT_TASK]]<br />
* [[MROCLS_MRO_PROGRESS_TASK]]<br />
* [[MROCLS_MRO_TASK]]<br />
* [[MROCLS_MRO_TASKOWNER]]<br />
* [[MROCLS_MRO_WORKPACKAGE]]<br />
* [[MROCLS_PROCEDURE#Procedure Workpackage]] (Classification)<br />
* [[MROCLS_SWITCH_TASK#Switch Task]] (Classification)<br />
* [[MROCLS_SWITCH_END_TASK#Switch End Task]] (Classification)<br />
* [[MROCLS_CALCULATION_TASK#Calculation Task]] (Classification)<br />
<br />
[[Category:Android|MRO Objects (UBIK WinX)]]<br />
[[Category:Client|MRO Objects (Client)]]<br />
[[Category:Mobile|MRO Objects (Client)]]<br />
[[Category:Pages with broken file links|MRO Objects (Client)]]<br />
[[Category:WinX|MRO Objects (UBIK WinX)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=XAML_Tips&diff=29244XAML Tips2026-01-12T15:06:43Z<p>LGE: /* FlipView */</p>
<hr />
<div>== Attachable behaviors ==<br />
It's quite often that you need to attach behaviors to certain XAML elements. For example, on a Grid, you want to attach a behavior which executes a command upon a Tapped event, or you want to execute a command when a certain property on a UBIK object changes.<br />
<br />
Notice that in the following examples, "Interactivity" and "Core" are both namespaces and you have to make sure that they are defined at the root of your XAMLs:<br />
<br />
<source lang = "xml"><br />
<DataTemplate<br />
...<br />
xmlns:Core="using:Microsoft.Xaml.Interactions.Core"<br />
xmlns:Interactivity="using:Microsoft.Xaml.Interactivity"><br />
...<br />
</DataTemplate><br />
</source><br />
<br><br />
<br />
=== Event Triggered ===<br />
With an EventTriggerBehavior, you can react on changes/events of UI Elements:<br />
<br />
<source lang = "xml"><br />
<Grid><br />
<Interactivity:Interaction.Behaviors><br />
<Core:EventTriggerBehavior EventName="Tapped"><br />
<Core:InvokeCommandAction Command="{Binding NavigateToChildrenCommand}" /><br />
</Core:EventTriggerBehavior><br />
</Interactivity:Interaction.Behaviors><br />
</Grid><br />
</source><br />
<br><br />
<br />
=== Data Triggered ===<br />
If you want to react on changes of the underlying data (ViewModel), you can use DataTriggerBehavior instead. The following example, when used in the ''UBIKSplashArea'' template, automatically navigates to the root objects once the login process is finished and the user was successfully authenticated:<br />
<br />
<source lang = "xml"><br />
<Grid><br />
<Interactivity:Interaction.Behaviors><br />
<Core:DataTriggerBehavior Binding="{Binding IsLoggedIn}" Value="True"><br />
<Core:InvokeCommandAction Command="{Binding NavigateToRootPageCommand}" /><br />
</Core:DataTriggerBehavior><br />
</Interactivity:Interaction.Behaviors><br />
</Grid><br />
</source><br />
<br><br />
<br><br />
<br />
== Content creation ==<br />
=== Child item creation ===<br />
{{Version/WinXSince|3.5.5}}<br />
To directly create an object on a child of the current object, you can define a Button as follows. The method "Item.IsTypeCreationAllowed" used in the expression gets the uid of the type that should be created below a child, if a child does not allow the creation of that type underneath it, the child will be hidden in the selection dialog. To actually create the object, the "CreateChildItemCommand" needs to be passed a KeyValueList with two parameters: The Parent-key is the UID or the ContentViewModel of the child underneath the object should be created, the Type-key is the type of object which should be created--this should match the uid passed to the "Item.IsTypeCreationAllowed" method.<br />
<br />
<source lang = "xml"><br />
xmlns:uc="using:UBIK.WinX.Controls"<br />
xmlns:cv="using:UBIK.WinX.UI.CollectionView"<br />
</source><br />
<br />
<source lang = "xml"><br />
<x:String x:Key="PlantMap">Item.IsTypeCreationAllowed(&quot;21fc990a-d064-4bee-8d48-3293351f827a&quot;)</x:String><br />
<cv:ListCollectionView x:Key="PlantMapView" Expression="{StaticResource PlantMap}" ItemsSource="{Binding Children.Items}" /><br />
<br />
<AppBarButton><br />
<AppBarButton.Flyout><br />
<Flyout Placement="Full"><br />
<ListView ItemsSource="{Binding Source={StaticResource PlantMapView}}"><br />
<ListView.ItemTemplate><br />
<DataTemplate><br />
<Button Content="{Binding Header}" Command="{Binding CreateChildItemCommand}" x:Name="CreateButton" Tag="{Binding}"><br />
<Button.CommandParameter><br />
<uc:KeyValueList><br />
<uc:KeyValueParameter Key="Parent" Value="6D733909-1742-4110-8619-237849BFE453"/><br />
<uc:KeyValueParameter Key="Type" Value="21fc990a-d064-4bee-8d48-3293351f827a"/><br />
</uc:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</DataTemplate><br />
</ListView.ItemTemplate><br />
</ListView><br />
</Flyout><br />
</AppBarButton.Flyout><br />
</AppBarButton><br />
</source><br />
<br />
<source lang = "xml"><br />
<x:String x:Key="PlantMap">Item.IsTypeCreationAllowed(&quot;21fc990a-d064-4bee-8d48-3293351f827a&quot;)</x:String><br />
<cv:ListCollectionView x:Key="PlantMapView" Expression="{StaticResource PlantMap}" ItemsSource="{Binding Children.Items}" /><br />
<br />
<AppBarButton><br />
<AppBarButton.Flyout><br />
<Flyout Placement="Full"><br />
<ListView ItemsSource="{Binding Source={StaticResource PlantMapView}}"><br />
<ListView.ItemTemplate><br />
<DataTemplate><br />
<Button Content="{Binding Header}" Command="{Binding CreateChildItemCommand}" x:Name="CreateButton" Tag="{Binding}"><br />
<Button.CommandParameter><br />
<uc:KeyValueList><br />
<uc:KeyValueParameter Key="Parent" Value="{Binding Tag, ElementName=CreateButton}"/><br />
<uc:KeyValueParameter Key="Type" Value="21fc990a-d064-4bee-8d48-3293351f827a"/><br />
</uc:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</DataTemplate><br />
</ListView.ItemTemplate><br />
</ListView><br />
</Flyout><br />
</AppBarButton.Flyout><br />
</AppBarButton><br />
</source><br />
<br />
<br/><br />
Additionally, the following optional parameters can be added as well.<br />
* CreateOnly (optional, defaults to false): When set to true, the client will not automatically navigate to the created content, rather automatically save and commit it. If set to true, this overrides the following parameters;<br />
* AutoNavigate (optional, defaults to true): When set to false, the client will not automatically navigate to the created content;<br />
* AutoCommit (optional, defaults to false): When set to true, the change(s) will be saved to the local cache and the database, and then committed to the server.<br />
<br><br />
<br />
=== Creating multiple documents ===<br />
To upload multiple documents at once, the CreateChildItemsCommand can be used. The list of supported command parameters are similar to those of the CreateChildItemCommand (single item). Except that anything other than AutoNavigate=false and AutoCommit=true do not make sense in multi-creation scenario. Therefore, those parameters are fixed and any received from XAML will be ignored.<br />
<br />
<!-- <tabs><br />
<br />
<tab name="UWP">--><br />
<source lang = "xml"><br />
<Button ...<br />
xmlns:uc="using:UBIK.WinX.Controls"<br />
Command="{Binding CreateChildItemsCommand}"<br />
Content="Create multiple documents"><br />
<Button.CommandParameter><br />
<uc:KeyValueList><br />
<uc:KeyValueParameter Key="Type" Value="6170a068-2314-4444-ad62-0da99769a048" /><br />
</uc:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
<!--</tab><br />
<br />
<tab name="Mobile(Xamarin)"><br />
<source lang = "xml"><br />
<Button ...<br />
xmlns:classes="clr-namespace:UBIK.CPL.Classes;assembly=UBIK.CPL"<br />
Command="{Binding CreateChildItemsCommand}"<br />
Content="Create multiple documents"><br />
<Button.CommandParameter><br />
<classes:KeyValueList><br />
<classes:KeyValueParameter Key="Type" Value="6170a068-2314-4444-ad62-0da99769a048" /><br />
</classes:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
</tab><br />
<br />
</tabs>--><br />
<br><br />
<br><br />
<br />
=== Disable FilloutCriteria ===<br />
{{Version/WinXSince|3.5}}<br />
To enable/disable the automatic filtering of a query based on the ParentObject, there is the possibility to specify EnableFillOutCriteria--if it is not set, it defaults to false. Additionaly "SkipDialog" can be set to true, to not display a dialog.<br />
<br />
<source lang="xml"><br />
<Grid x:Name="selectionGrid" Tag="{Binding MetaUID}"><br />
<Interactivity:Interaction.Behaviors><br />
<Core:EventTriggerBehavior EventName="Tapped"><br />
<Core:InvokeCommandAction Command="{Binding ElementName=ChildAreaGrid, Path=DataContext.AddTemplatableDataCommand}" ><br />
<Core:InvokeCommandAction.CommandParameter><br />
<uc:KeyValueList><br />
<uc:KeyValueParameter Key="Uid" Value="{Binding Tag,ElementName=selectionGrid}"/><br />
<uc:KeyValueParameter Key="EnableFillOutCriteria" Value="false"/><br />
<uc:KeyValueParameter Key="SkipDialog" Value="false"/><br />
</uc:KeyValueList><br />
</Core:InvokeCommandAction.CommandParameter><br />
</Core:InvokeCommandAction><br />
</Core:EventTriggerBehavior><br />
</Interactivity:Interaction.Behaviors><br />
</Grid><br />
</source><br />
<br><br />
<br><br />
<br />
== Hotspotting ==<br />
{{Attention|To use a binding in the KeyValueParameter, it has to be applied like in the example provided here: [[KeyValueList]]}}<br />
The hotspotting command is used for hotspotting as well as for annotating, to configure the button for hotspotting, the commandparameter "Mode" should be set to "HotSpotting", for annotating the "Mode" should be "Annotate". The parameter commit is optional, if set to true, the changes get automatically persisted when leaving the editing mode.<br />
<br />
<source lang = "xml"><br />
<AppBarToggleButton<br />
IsChecked="{Binding EditingAnnotation, Mode=TwoWay}"<br />
IsEnabled="{Binding IsAnnotatable}"<br />
Command="{Binding HotSpottingCommand}"><br />
<AppBarToggleButton.CommandParameter><br />
<uc:KeyValueList><br />
<uc:KeyValueParameter Key="Mode" Value="Annotate"/><br />
<uc:KeyValueParameter Key="Commit" Value="true"/><br />
</uc:KeyValueList><br />
</AppBarToggleButton.CommandParameter><br />
</AppBarToggleButton><br />
</source><br />
<br><br />
<br><br />
<br />
== Remember scroll positions of list views ==<br />
<br />
=== Version 3.7 & later {{Version/WinXSince|3.7}} ===<br />
Starting from this version,<br />
* The precision of scroll position remembering is improved(by pixel offsets instead of by items);<br />
* It also works for other scrollable lists (instead of just for content object lists).<br />
<br /><br />
To enable this feature, you should make sure the following.<br />
* The SelectionBoundListView is used instead of the standard ListView. Its {{UBIK}} namespace is <code>UBIK.WinX.Controls</code>;<br />
* The SelectionBoundListView's <code>RememberScrollPosition</code> property is not set to "false"; (It's "true" by default.)<br />
* The SelectionBoundListView's <code>x:Name</code> property value is unique.<br />
<br><br />
<br />
=== Version 3.6 {{Version/WinXSince|3.6}} ===<br />
The UBIK-Client does include a function to remember the position in a list (ListView) when navigating away from it. This function is only available when the list (ListView) has a unique name as a property (x:Name). When browsing back to the previously visited list UBIK scrolls back to the last position. The function does not save scroll positions over different sessions.<br />
Implementing the function to remember the scroll position in a ListView one has to consider that the list elements (Children) could depend on a other UI-element. If the list elements do depend on a other UI-elemente, this element has to be created above the ListView in the XAML.<br />
<br />
<source lang = "xml"><br />
<DataTemplate xmlns:behaviors="using:UBIK.WinX.Behaviors" xmlns:uc="using:UBIK.WinX.Controls"><br />
...<br />
<uc:SelectionBoundListView x:Name="ChildListView"><br />
<Interactivity:Interaction.Behaviors><br />
<behaviors:FirstVisibleItemPersistenceBehavior FirstVisibleItems="{Binding ScrollItems}" /><br />
</Interactivity:Interaction.Behaviors><br />
</uc:SelectionBoundListView><br />
</DataTemplate><br />
</source><br />
<br><br />
<br><br />
<br />
<br />
== MultiBinding {{Version/WinXSince|3.6}} ==<br />
Very often we want to display some UI elements (e.g. a Grid) depending on whether multiple criteria are met. It's much easier to achieve this by using a MultiBindingBehavior like the following.<br />
<source lang = "xml"><br />
<DataTemplate<br />
xmlns:Interactivity="using:Microsoft.Xaml.Interactivity"<br />
xmlns:behaviors="using:UBIK.WinX.Behaviors"><br />
...<br />
<Grid><br />
<Interactivity:Interaction.Behaviors><br />
<behaviors:MultiBindingBehavior Converter="{StaticResource VisLogicAndConverter}" PropertyName="Visibility"><br />
<behaviors:MultiBindingItem Value="{Binding MassEditViewModel, Converter={StaticResource NullToVisConverter}}" /><br />
<behaviors:MultiBindingItem Value="{Binding Documents.Items.Count, Converter={StaticResource ItemCountToVisConverter}}" /><br />
</behaviors:MultiBindingBehavior><br />
</Interactivity:Interaction.Behaviors><br />
</Grid><br />
</DataTemplate><br />
</source><br />
The behavior makes sure the container Grid is set to Visibile only if the mass editing mode is not turned on (MassEditViewModel is null) and the context object has child document(s) (Documents.Items.Count is greater than 0. You can combine any number of binding results (MultiBindingItem) using the VisLogicAndConverter (the name should be self explanatory).<br />
<br><br />
<br><br />
<br />
== Other Commands ==<br />
=== InvokeOnItemsCommand {{Version/WinXSince|3.6}} ===<br />
Available on all ListViewModels, this command allows executing a specified command on a collection of list items. It can be used in combination with features such as [[Mass_Edit_(UBIK_WinX)|mass editing]] and [[XAML_Changes_in_UBIK_WinX_3.5#After_3.5|expression based collection filtering]]. Examples for both combinations are provided below.<br />
<br />
{{Attention|The command specified through the "Command" parameter is executed on list items and, therefore, must be available in the list item contexts (view models). If in doubt, the [[Developer_Mode|developer mode]] can be used to inspect if a command is available in a certain context.}}<br />
<br />
{{Hint|Parameter "Command" and "SelectedItemsOnly" are specific to the InvokeOnItemsCommand. What other parameters to define or whether to define them at all depends on the type of command to be executed on the items.}}<br />
<br><br />
<br />
==== Invoke on selected items ====<br />
{{Attention|To use a binding in the KeyValueParameter, it has to be applied like in the example provided here: [[KeyValueList]]}}<br />
This example demonstrates how you can use the mass editing feature to select certain objects from the child list and then execute the SetPropertyValueCommand for those selected.<br />
* The example code assumes that the child objects have an editable property called "VALUE" and tries to set 50 as their value;<br />
* You should insert the following code snippet into the default UBIKChildArea template;<br />
* If the parameter "SelectedItemsOnly" is missed or set to "False", the command will be executed on all child items;<br />
* To enable selection, click on the "Mass Edit" button below the property list.<br />
<br /><br />
<br />
<tabs><br />
<tab name="UWP"><br />
<source lang = "xml"><br />
<Button<br />
xmlns:example="using:UBIK.WinX.Controls"<br />
Command="{Binding Children.InvokeOnItemsCommand}"<br />
Content="Set to 50%"><br />
<Button.CommandParameter><br />
<example:KeyValueList><br />
<example:KeyValueParameter Key="Command" Value="SetPropertyValueCommand" /><br />
<example:KeyValueParameter Key="SelectedItemsOnly" Value="False" /><br />
<example:KeyValueParameter Key="PropertyName" Value="VALUE" /><br />
<example:KeyValueParameter Key="PropertyValue"><br />
<example:KeyValueParameter.Value><br />
<x:Double>50</x:Double><br />
</example:KeyValueParameter.Value><br />
</example:KeyValueParameter><br />
</example:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
</tab><br />
<br />
<tab name="Mobile(Xamarin)"><br />
<source lang = "xml"><br />
<Button<br />
xmlns:example="clr-namespace:UBIK.CPL.Classes;assembly=UBIK.CPL"<br />
Command="{Binding Children.InvokeOnItemsCommand}"<br />
Text="Set to 50%"><br />
<Button.CommandParameter><br />
<example:KeyValueList><br />
<example:KeyValueParameter Key="Command" Value="SetPropertyValueCommand" /><br />
<example:KeyValueParameter Key="SelectedItemsOnly" Value="False" /><br />
<example:KeyValueParameter Key="PropertyName" Value="VALUE" /><br />
<example:KeyValueParameter Key="PropertyValue"><br />
<example:KeyValueParameter.Value><br />
<x:Double>50</x:Double><br />
</example:KeyValueParameter.Value><br />
</example:KeyValueParameter><br />
</example:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
</tab><br />
</tabs><br />
<br><br />
<br><br />
<br />
==== Invoke on filtered results ====<br />
{{Attention|To use a binding in the KeyValueParameter, it has to be applied like in the example provided here: [[KeyValueList]]}}<br />
<br />
* First, you need to setup a filtered list<br />
**UWP: Setup a ListCollectionView in the Resources section of a UI element (e.g. Grid). This list is only available/visible within that UI element (the Grid in this case).<br />
**Mobile: Setup a String with a filtering expression & a SfDataSourceExt in the ResourceDictionary of the ContentView. For the Expression property of the SfDataSourceExt refer to the created expression String.<br />
<br />
* The ItemsSource uses Children.Items. Use the [[Developer_Mode|developer mode]] if necessary to find out if this is available where you intend to define the list;<br />
* The example expression filters for any items that don't contain the text "EXAMPLE" in their Title texts. You can filter differently by altering the expression.<br />
<br /><br />
<br />
<tabs><br />
<tab name="UWP"><br />
<source lang = "xml"><br />
<Grid xmlns:CV="using:UBIK.WinX.UI.CollectionView"><br />
<Grid.Resources><br />
<CV:ListCollectionView<br />
x:Key="Filtered"<br />
Expression="!Item.Title.Contains(&quot;EXAMPLE&quot;)"<br />
ItemsSource="{Binding Children.Items}" /><br />
</Grid.Resources><br />
...<br />
</Grid><br />
</source><br />
</tab><br />
<br />
<tab name="Mobile(Xamarin)"><br />
<source lang = "xml"><br />
<ContentView<br />
xmlns:controls="clr-namespace:UBIK.CPL.Controls;assembly=UBIK.CPL"<br />
...><br />
<ContentView.Resources><br />
<ResourceDictionary><br />
<x:String x:Key="Expresssion">!Item.Title.Contains(&quot;EXAMLPLE&quot;)</x:String><br />
<controls:SfDataSourceExt x:Key="Filtered" Expression="{StaticResource Expresssion}" ItemsSource="{Binding Children.Items}" /><br />
</ResourceDictionary><br />
</ContentView.Resources><br />
</ContentView><br />
</source><br />
</tab><br />
</tabs><br />
<br />
<br /><br />
With the filtered list configured, you can then insert the following code snippet to execute the SetPropertyValueCommand for the filtered result items.<br />
* The example code assumes that the child objects have an editable property called "VALUE" and tries to set 50 as their value;<br />
* The "Filtered" refers to the ListCollectionView (UWP) or SfDataSourceExt (Mobile) configured above.<br />
<br /><br />
<br />
<tabs><br />
<tab name="UWP"><br />
<source lang = "xml"><br />
<AppBarButton<br />
xmlns:example="using:UBIK.WinX.Controls"<br />
Command="{Binding Source={StaticResource Filtered}, Path=ListViewModel.InvokeOnItemsCommand}"<br />
Icon="AllApps"<br />
Label="Set to 50"<br />
Style="{ThemeResource UBIKActionAppBarButton}"><br />
<AppBarButton.CommandParameter><br />
<example:KeyValueList><br />
<example:KeyValueParameter Key="Command" Value="SetPropertyValueCommand" /><br />
<example:KeyValueParameter Key="PropertyName" Value="VALUE" /><br />
<example:KeyValueParameter Key="PropertyValue" Value="50" /><br />
</example:KeyValueList><br />
</AppBarButton.CommandParameter><br />
</AppBarButton><br />
</source><br />
</tab><br />
<br />
<tab name="Mobile(Xamarin)"><br />
<source lang = "xml"><br />
<Button<br />
xmlns:example="clr-namespace:UBIK.CPL.Classes;assembly=UBIK.CPL"<br />
Command="{Binding Source={StaticResource Filtered}, Path=ListViewModel.InvokeOnItemsCommand}"<br />
Text="Set to 50"><br />
<Button.CommandParameter><br />
<example:KeyValueList><br />
<example:KeyValueParameter Key="Command" Value="SetPropertyValueCommand" /><br />
<example:KeyValueParameter Key="PropertyName" Value="VALUE" /><br />
<example:KeyValueParameter Key="PropertyValue" Value="50" /><br />
</example:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
</tab><br />
</tabs><br />
<br />
{{Attention|The binding <code>ListViewModel.InvokeOnItemsCommand</code> should be updated to <code>BulkOperation.InvokeOnItemsCommand</code> starting from version 4.3.}}<br />
<br><br />
<br />
==== Support for old styled commands ====<br />
Some old commands might not support KeyValueLists as parameters. In that case, just define the parameter value under the "CommandParameter" key, e.g.<br />
<br /><br />
<source lang = "xml"><example:KeyValueParameter Key="CommandParameter" Value="some string value for example" /></source>.<br />
This single value is then passed as the command parameter instead of the entire KeyValueList.<br />
<br><br />
<br><br />
<br />
=== SetPropertyValueCommand {{Version/WinXSince|3.6}} ===<br />
{{Attention|To use a binding in the KeyValueParameter, it has to be applied like in the example provided here: [[KeyValueList]]}}<br />
<br />
This command existed before but was implemented differently. In the newer version(s), it is improved to provide customizers more control over the things that happen during/after the property value changes.<br />
The available command parameters are:<br />
* PropertyName: the name of the property to set a new value to;<br />
* PropertyValue: the value to be set to the above mentioned property;<br />
* OnlyForUnvalidated (optional, defaults to false): When set to true, the value will only be set if the property is not yet validated;<br />
* AutoSave (optional, defaults to false): When set to true, the change(s) will be saved to the local cache and database;<br />
* AutoCommit (optional, defaults to false): When set to true, the change(s) will be committed to the server.<br />
<br />
{{Hint|There's no way to commit changes without saving them locally first. Therefore, the "AutoSave" parameter will be ignored when "AutoCommit" is set to true.}}<br />
<br />
<br />
Here's an example of the command usage. It tries to set the property called "VALUE" to a double value 50 regardless of its current state and then automatically save and commit the change.<br />
<br /><br />
<source lang = "xml"><br />
xmlns:example="using:UBIK.WinX.Controls"<br />
...<br />
<Button<br />
Command="{Binding SetPropertyValueCommand}"<br />
Style="{StaticResource UBIKButtonStyle}"<br />
Content="Set Property"><br />
<Button.CommandParameter><br />
<controls:KeyValueList><br />
<controls:KeyValueParameter Key="PropertyName" Value="MP_PROPERTY" /><br />
<controls:KeyValueParameter Key="PropertyValue" Value="My Value" /><br />
<controls:KeyValueParameter Key="OnlyForUnvalidated" Value="false" /><br />
<controls:KeyValueParameter Key="AutoSave" Value="true" /><br />
<controls:KeyValueParameter Key="AutoCommit" Value="true" /><br />
</controls:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
<br />
{{Hint|For simple types, you can try writing them in the text format like <nowiki><controls:KeyValueParameter Key="PropertyValue" Value="50"/></nowiki> and {{UBIK}} will try to find the right type. For advanced property types, it is advised to provide typed values like <nowiki><x:Boolean>true</x:Boolean></nowiki>.}}<br />
<br><br />
<br />
==== Set a Binding as PropertyValue ====<br />
There is a known issue in XAML where Behaviors and KeyValueLists do not inherit the binding context of the control they are attached to. Simply put, trying to use a binding directly in the PropertyValue part of the command; '''<nowiki><controls:KeyValueParameter Key="PropertyValue" Value="{Binding BindingPath}" /></nowiki>''', would lead to the client setting the value of MP_PROPERTY to null.<br />
<br />
Luckily, there is a simple way to link this Binding to a context. Using the above example as a foundation, adapt the button as shown below:<br />
<tabs><br />
<tab name="UWP"><br />
<source lang = "xml"><br />
<Button<br />
x:Name="SetDynamicPropertyButton"<br />
Tag="{Binding}"<br />
... ><br />
<Button.CommandParameter><br />
<controls:KeyValueList><br />
...<br />
<controls:KeyValueParameter Key="PropertyValue" Value="{Binding Tag.BindingPath, ElementName=SetDynamicPropertyButton}" /><br />
...<br />
</controls:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
</tab><br />
<br />
<tab name="Mobile"><br />
<source lang = "xml"><br />
<Button<br />
x:Name="SetDynamicPropertyButton"<br />
... ><br />
<Button.CommandParameter><br />
<classes:KeyValueList><br />
...<br />
<classes:KeyValueParameter Key="PropertyValue" Value="{Binding BindingContext.BindingPath, Source={x:Reference SetDynamicPropertyButton}}" /><br />
...<br />
</classes:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
</tab><br />
<br />
{{Hint|Replace ''BindingPath'' in the above snippets with your required binding path, for example, ''AppStatus.CurrentUser.RawDetails[...]''. }}<br />
</tabs><br />
<br />
The above code uses the x:Name of the button to specify the viewmodel from which we wish to begin our binding path.<br><br />
You do not need to follow this exact syntax, all that is necessary is to provide a connection to the BindingContext of an observable control.<br />
<br><br />
<br><br />
<br />
<br />
<br />
<br />
<br />
<br />
==== Set Current DateTime ====<br />
The current DateTime stamp can be retrieved from '''AppStatus.LiveDateTime'''.<br><br />
Since the known issue described in the section above prevents direct binding to this, below are examples for how to implement it.<br />
<br />
<tabs><br />
<tab name="UWP"><br />
<source lang = "xml"><br />
xmlns:example="using:UBIK.WinX.Controls"<br />
...<br />
<Button<br />
x:Name="SetCurrentDateTimeButton"<br />
Tag="{Binding}"<br />
Command="{Binding SetPropertyValueCommand}"<br />
Style="{StaticResource UBIKButtonStyle}"<br />
Content="Set Property"><br />
<Button.CommandParameter><br />
<controls:KeyValueList><br />
<controls:KeyValueParameter Key="PropertyName" Value="MP_PROPERTY" /><br />
<controls:KeyValueParameter Key="PropertyValue" Value="{Binding Tag.AppStatus.LiveDateTime, ElementName=SetCurrentDateTimeButton}" /><br />
<controls:KeyValueParameter Key="OnlyForUnvalidated" Value="false" /><br />
<controls:KeyValueParameter Key="AutoSave" Value="true" /><br />
<controls:KeyValueParameter Key="AutoCommit" Value="true" /><br />
</controls:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
{{Hint|The DateTime can be set to the desired format by adding a StringFormatConverter to the LiveDateTime binding:<br><nowiki>"{Binding Tag.AppStatus.LiveDateTime, ElementName=SetCurrentDateTimeButton, </nowiki>'''<nowiki>Converter={StaticResource StringFormatConverter}, ConverterParameter={0:yyyy-MM-dd HH:mm}</nowiki>'''<nowiki>}" </nowiki>.}}<br />
</tab><br />
<br />
<tab name="Mobile"><br />
<source lang="xml"><br />
<Button<br />
x:Name="SetCurrentDateTimeButton"<br />
Command="{Binding SetPropertyValueCommand}"<br />
Text="Set Property"><br />
<Button.CommandParameter><br />
<classes:KeyValueList><br />
<classes:KeyValueParameter Key="PropertyName" Value="MP_PROPERTY" /><br />
<classes:KeyValueParameter Key="PropertyValue" Value="{Binding BindingContext.AppStatus.LiveDateTime, Source={x:Reference SetCurrentDateTimeButton}}" /><br />
<classes:KeyValueParameter Key="OnlyForUnvalidated" Value="false" /><br />
<classes:KeyValueParameter Key="AutoSave" Value="true" /><br />
<classes:KeyValueParameter Key="AutoCommit" Value="true" /><br />
</classes:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
</tab><br />
</tabs><br />
<br />
<br><br />
<br />
<br />
<br />
<br />
<br />
<br />
=== SaveAndCommitCommand ===<br />
With the ''SaveAndCommitCommand'' it is possible to save and commit unsaved changes on a ContentViewModel.<br />
<br />
* ForceCommit CommandParameter (optional, defaults to false): Normally when the App is in Online mode, changes are automatically committed when saved. This is not the case when the App is in Manual mode. Setting the ''ForceCommit'' parameter to true makes it possible to commit the changes when saved in Manual mode.<br />
* {{Version/WinXSince|4.7}} {{Version/XamarinSince|4.7}} PropertyNameToSave CommandParameter (optional, defaults to null): Delivers the Property Name as String of a specific Property that should be saved. E.g. when called via PropertyViewModel.ResetCommand or PropertyViewModel.DeleteCommand, the ''PropertyNameToSave'' parameter is used to only apply the SaveAndCommitCommand on the related PropertyViewModel called from, and not on other unsaved changes on this ContentViewModel.<br />
<br/><br />
<tabs><br />
<tab name="UWP"><br />
<source lang = "xml"><br />
<Button<br />
xmlns:example="using:UBIK.WinX.Controls"<br />
Command="{Binding SaveAndCommitCommand}"><br />
<Button.CommandParameter><br />
<example:KeyValueList><br />
<example:KeyValueParameter Key="ForceCommit" Value="True" /><br />
</example:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
</tab><br />
<tab name="Mobile(Xamarin)"><br />
<source lang = "xml"><br />
<Button<br />
xmlns:example="using:clr-namespace:UBIK.CPL.Classes;assembly=UBIK.CPL"<br />
Command="{Binding SaveAndCommitCommand}"><br />
<Button.CommandParameter><br />
<example:KeyValueList><br />
<example:KeyValueParameter Key="ForceCommit" Value="True" /><br />
</example:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
</tab><br />
</tabs><br />
<br><br />
<br />
=== DisplayViewCommand ===<br />
This command can be used to [[Custom_View_(Client)|display cutom views]].<br />
<br><br />
<br />
=== TeachInCommand ===<br />
With the '''TeachInCommand''' you're allowed to set your device's current location ("teach-in", "TeachIn") as the value of the context object's [[SYSCLS_GEO|geo property]].<br />
This command is available in both '''ContentViewModel''' and '''PropertyViewModel'''.<br />
* ContentViewModel.TeachInCommand: If possible, sets the current location of the device as the value of the context object's [[SYSCLS_GEO|geo property]]. Saves and commits the change;<br />
* PropertyViewModel.TeachInCommand: If possible, sets the current location of the device as the value of the current property if it's a geo property (not necessarily the [[SYSCLS_GEO|geo property]]). Addtionally supports a boolean command parameter:<br />
** False (default): The change is not automatically saved. <br />
** True: The change is saved.<br />
<br/> {{hint| Make sure you use the correct binding path for your command depending on your current context view model. E.g., if the context view model is already the ContentViewModel then your binding path should simply be TeachInCommand. You can use the [[Developer_Mode|developer mode]] to find out the current view model in a view.}}<br />
<br><br />
<br />
===UpdateArbitraryObjectCommand {{Version/WinXSince|4.7}}===<br />
The "UpdateArbitraryObjectCommand" is responsible for updating an arbitrary object based on a set of provided parameters. The command is accessible in the AppStatusViewModel (as '''ViewModel.AppStatus'''). <br />
<br /><br />
The available command parameters are:<br />
* Uid (Mandatory): UID of the object to be updated;<br />
* UpdateChildDepth (Optional): Child depth/level to update (defaults to 1);<br />
* UpdateParentDepth (Optional): Parent depth/level to update (defaults to 0);<br />
* UpdateIgnoreExpiry (Optional): Ignore update expiry (defaults to false); <br />
<br />
{{Hint|Note that if you set the UpdateChildDepth property to "-1" you are also able to update a whole branch with this command.}}<br />
<br />
Here is an example of the command usage: <br />
<br /><br />
<tabs><br />
<tab name="UWP"><br />
<source lang = "xml"><br />
<Button ...<br />
xmlns:uc="using:UBIK.WinX.Controls"<br />
Command="{Binding UpdateArbitraryObjectCommand}"<br />
Content="Update Arbitrary Object"><br />
<Button.CommandParameter><br />
<uc:KeyValueList><br />
<uc:KeyValueParameter Key="Uid" Value="...valid UID..." /><br />
<uc:KeyValueParameter Key="UpdateChildDepth" Value="2" /><br />
<uc:KeyValueParameter Key="UpdateParentDepth" Value="0" /><br />
<uc:KeyValueParameter Key="UpdateIgnoreExpiry" Value="true" /><br />
</uc:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
</tab><br />
<br />
<tab name="Mobile(Xamarin)"><br />
<source lang = "xml"><br />
<Button ...<br />
xmlns:uc="using:clr-namespace:UBIK.CPL.Classes;assembly=UBIK.CPL"<br />
Command="{Binding UpdateArbitraryObjectCommand}"<br />
Content="Update Arbitrary Object"><br />
<Button.CommandParameter><br />
<uc:KeyValueList><br />
<uc:KeyValueParameter Key="Uid" Value="...valid UID..." /><br />
<uc:KeyValueParameter Key="UpdateChildDepth" Value="2" /><br />
<uc:KeyValueParameter Key="UpdateParentDepth" Value="0" /><br />
<uc:KeyValueParameter Key="UpdateIgnoreExpiry" Value="true" /><br />
</uc:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
</tab><br />
</tabs><br />
<br><br />
<br />
=== Access to an arbitrary object {{Version/WinXSince|4.6}} {{Version/XamarinSince|4.6}} ===<br />
With the ObjectByUID feature it is possible to access any local arbitrary object by its UID and, for example, display a value of it.<br />
It can be accessed from ContentViewModel, AuthenticationViewModel, and RootPageViewModel levels.<br />
<br />
To display a string of e.g. a property of an arbitrary object from ContentViewModel, AuthenticationViewModel & RootPageViewModel, the following syntax can be used in related XAMLs:<br />
<tabs><br />
<tab name="UWP"><br />
<source lang = "xml"><br />
<TextBlock Text="{Binding ObjectByUID[paste-your-uid].Properties.VisibleItems[add-your-property-name].DisplayValue}" /><br />
</source><br />
</tab><br />
<br />
<tab name="Mobile(Xamarin)"><br />
<source lang = "xml"><br />
<Label Text="{Binding ObjectByUID[paste-your-uid].Properties.VisibleItems[add-your-property-name].DisplayValue}" /><br />
</source><br />
</tab><br />
</tabs><br />
<br />
For Property Dialogs the CallingViewModel prefix is needed to access an arbitrary object:<br />
<tabs><br />
<tab name="UWP"><br />
<source lang = "xml"><br />
<TextBlock Text="{Binding CallingViewModel.ObjectByUID[paste-your-uid].Properties.VisibleItems[add-your-property-name].DisplayValue}" /><br />
</source><br />
</tab><br />
<br />
<tab name="Mobile(Xamarin)"><br />
<source lang = "xml"><br />
<Label Text="{Binding CallingViewModel.ObjectByUID[paste-your-uid].Properties.VisibleItems[add-your-property-name].DisplayValue}" /><br />
</source><br />
</tab><br />
</tabs><br />
<br><br />
<br><br />
<br />
==== Localizing UI Texts ====<br />
The most efficient practice is to use pre-localized texts from the standard client, however, this is not always possible, especially in custom UIs. The ObjectByUID indexer was therefore initially developed as a technique to allow localization of custom UI label texts. <br />
<br />
The concept is to create an infrastructure object that carries metaproperties for localized texts, then bind to this infrastructure object using ObjectByUID, and bind to a specific metaproperty to receive it's localized Description text as follows:<br />
<source lang = "xml"><br />
"{Binding ObjectByUID[paste-your-uid].Properties.VisibleItems[add-your-property-name].Description}"<br />
</source><br />
<br />
From here there are two approaches; the database-leaning one is to add one metaproperty per UI label, and simply bind to the Description of it. However, this shifts maintenance effort to the UBIK Studio after the initial adding of the label in XAML. Another approach would be to use the metaproperty to provide a "tag" that the xaml customizer can then use to differentiate between hardcoded labels.<br />
<br />
A third approach would be to create one infrastructure object per label, however, this can lead to many objects being loaded upon startup.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Approach !! Implementation !! Maintenance Effort !! Recommendation<br />
|-<br />
| One metaproperty per UI Label || Bind the label text to the metaproperty Description || Database / UBIK Studio || Recommended for UWP, customizings with fewer UI texts, finalized customizings.<br />
|-<br />
| One metaproperty delivering a localization "tag" (such as: "EN" / "DE") || Use something like DataTrigger (Mobile) to hardcode a different localized text per tag (such as: "eg." / "zb.") || XAML || Recommended for Mobile, highly customized UIs with many texts, customizings that tend to change often.<br />
|}<br />
<br><br />
<br><br />
<br />
<br />
<br />
<br />
<br />
<br />
== Showing Images and Icons ==<br />
In UBIK, there are two types of image;<br />
* The thumbnail image assigned to a UBIK object, delivered using the <nowiki>{Binding Icon...}</nowiki> binding, in combination with a ByteToImageConverter. Examples can commonly be found on UBIKChildItem templates.<br />
* Custom image shown with a specific purpose, such as a company logo or icon on a button/UI element.<br />
<br><br />
<br />
==== Paths as string resources ====<br />
When using custom images in your UI, it is a good idea not to hardcode path data into your Image control but instead to create a string resource in UBIKThemes that holds the image path, and use this string resource in your Image control. The benefit of the indirect connection between image file and usage is that the "file is in use" issue (sometimes experienced when either manual, or auto-deployment of xamls, tries to change image files when UBIK is running) is avoided this way.<br />
<br />
Sample:<br />
<tabs><br />
<tab name="UWP"><br />
'''UBIKThemes:'''<br />
<source lang = "xml"><x:String x:Key="MainLogo">ms-appdata:///local/xaml/Images/MainLogo.png</x:String><br />
</source><br />
<br><br />
'''Usage:'''<br />
<source lang = "xml"><br />
<Image<br />
x:Name="LogoImage"<br />
Height="32"<br />
Stretch="Uniform"<br />
Source="{Binding Source={StaticResource MainLogo}, Converter={StaticResource PathToImageConverter}}" /><br />
</source><br />
</tab><br />
<br />
<tab name="Mobile(Xamarin)"> <br />
'''UBIKThemes:'''<br />
<source lang = "xml"><br />
<x:String x:Key="Logo_Image">IMG_Logo.png</x:String><br />
</source><br />
<br><br />
'''Usage:'''<br />
<source lang = "xml"><br />
xmlns:customimage="clr-namespace:UBIK.CPL.Controls;assembly=UBIK.CPL"<br />
...<br />
<customimage:FileImage<br />
HeightRequest="140"<br />
Aspect="AspectFit"<br />
FileName="{StaticResource BorealisLogo_Image}" <br />
FolderName="xaml" /><br />
</source><br />
</tab><br />
</tabs><br />
<br><br />
<br />
=== Icons ===<br />
UBIK comes equipped with a collection of icons that can be easily used in your customizing. [[Icon_Font|Here is an indepth explanation on usage]].<br />
<br />
In the case that you require an icon that is not included in our icon font file, there is the possibility to use SVG path data to render your required icon in the UI.<br />
<br><br />
<br />
==== Custom Icons ====<br />
Here referring to icons which are not included as standard icons un UBIK.<br />
<br />
'''Path data''' is a collection of points, which combined together form a vector image. Vector images, compared to raster images like a PNG or JPG, are scalable, because they are always rendered from path data, and not from a bitmap, which has to be stretched or squished to fit your defined size. Described below two approaches. <br />
<br />
===== Using (SVG) Files =====<br />
<br><br />
The '''UWP approach''' involves adding an SVG icon file to your xaml project and render it using an Image control. <br />
<source lang = "xml"> <br />
<Image Width="14" Height="14" Margin="0,0,0,1"><br />
<Image.Source ><br />
<SvgImageSource UriSource="{StaticResource PP_Issued}" /><br />
</Image.Source><br />
</Image><br />
</source><br />
<br><br><br />
<br />
===== Using Path Data =====<br />
<br><br />
The '''Mobile(Xamarin) approach''' shows how to use svg data directly using a Path control.<br />
<br />
The first step is to generate path data for your icon. The easiest way is to download the [https://apps.microsoft.com/detail/9wzdncrdxf41?hl=en-US&gl=US| Character Map] tool from Microsoft. This can be used to browse all installed icon files for your icon of choice. Once selected, use Tools > Xaml / Xamarin Forms to show various useful aspects of the icon. With an icon selected, the Path Geometry section can be used to generate a path data that can be pasted directly in your xaml as follows:<br />
<br />
<source lang = "xml"><br />
<Path Fill="{StaticResource UBIKAccentColor}" Data="F1 M 8.75 1.25 L 18.75 1.25 L 18.75 18.75 L 1.25 18.75 L 1.25 8.75 L 5 8.75 L 5 6.25 L 1.25 6.25 L 1.25 1.25 L 6.25 1.25 L 6.25 5 L 8.75 5 Z M 10 2.5 L 10 5 L 12.5 5 L 12.5 2.5 Z M 2.5 5 L 5 5 L 5 2.5 L 2.5 2.5 Z M 6.25 6.25 L 6.25 8.75 L 8.75 8.75 L 8.75 6.25 Z M 2.5 10 L 2.5 12.5 L 5 12.5 L 5 10 Z M 17.5 17.5 L 17.5 2.5 L 13.75 2.5 L 13.75 6.25 L 10 6.25 L 10 10 L 6.25 10 L 6.25 13.75 L 2.5 13.75 L 2.5 17.5 Z " /> <br />
</source><br />
<br />
Once you have your Path control, you can customize it as [https://learn.microsoft.com/en-us/previous-versions/xamarin/xamarin-forms/user-interface/shapes/path| documented by Microsoft] (Maui documentation: [https://learn.microsoft.com/en-us/dotnet/maui/user-interface/controls/shapes/path?view=net-maui-9.0| see here]). Path data generated using the above method will most likely need a Fill attribute, for example <nowiki>Fill="{StaticResource UBIKAccentColor}"</nowiki>.<br />
<br />
{{Hint|More complicated icons will have longer and more complicated paths.}}<br />
<br />
<br><br />
<br><br />
<br />
[[Category:Client|XAML Tips]]<br />
[[Category:Mobile|XAML Tips]]<br />
[[Category:WinX|XAML Tips]]<br />
[[Category:XAML|XAML Tips]]<br />
<br />
== TabView ==<br />
<br />
=== UI virtualization ===<br />
When using the TabView control in your XAML code, UI virtualization can greatly improve initial loading performance, based on the scenario.Here's how to enable it:<br />
<br />
<tabs><br />
<tab name="Mobile(Xamarin)"><br />
<source lang = "xml"><br />
<tabView:SfTabView EnableVirtualization="true"><br />
...<br />
</tabView:SfTabView><br />
</source><br />
</tab><br />
</tabs><br />
<br />
=== Default Tab Selection ===<br />
The tab selection in UBIKContentView defaults to the first tab, which is Children objects. However, for cases where it makes more sense to display Properties or Documents by default, it is possible to change the tab selection using the following classifications:<br />
* [[SYSCLS_SHOWDOCUMENTS]]<br />
* [[SYSCLS_SHOWPROPERTIES]]<br />
<br />
<tabs><br />
<tab name="UWP"><br />
Adding the classification to a metaclass is enough for UWP.<br />
</tab><br />
<tab name="Mobile(Xamarin)"><br />
Xamarin currently requires additional customizing to make use of the TabSelector property. One approach is to add a DataTrigger to the SfTabView found in UBIKContentArea that is triggered by the value of the TabSelector property, as shown below;<br />
<source lang = "xml"><br />
<tabView:SfTabView VisibleHeaderCount="3" ><br />
<!-- tabView:SfTabItems ... --><br />
<tabView:SfTabView.Triggers><br />
<DataTrigger TargetType="tabView:SfTabView" Binding="{Binding TabSelector}" Value="PropertiesTab"><br />
<Setter Property="SelectedIndex" Value="1"/><br />
</DataTrigger><br />
<DataTrigger TargetType="tabView:SfTabView" Binding="{Binding TabSelector}" Value="DocumentsTab"><br />
<Setter Property="SelectedIndex" Value="2"/><br />
</DataTrigger><br />
</tabView:SfTabView.Triggers><br />
</tabView:SfTabView><br />
</source><br />
</tab><br />
</tabs><br />
<br><br />
<br><br />
<br />
<br />
<br />
<br />
<br />
<br />
== FlipView ==<br />
<br />
=== UI virtualization ===<br />
When using the FlipView control in your XAML code, it's better to enable [https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/optimize-gridview-and-listview#ui-virtualization UI virtualization]. The difference in performance gets more obvious as the number of items in the FlipView increases. Here's how to enable it.<br />
<br />
<source lang = "xml"><br />
<FlipView<br />
...<br />
VirtualizingStackPanel.VirtualizationMode="Standard"><br />
<Flipview.ItemsPanel><br />
<ItemsPanelTemplate><br />
<VirtualizingStackPanel Orientation="Horizontal" /><br />
</ItemsPanelTemplate><br />
</Flipview.ItemsPanel><br />
</FlipView><br />
</source><br />
<br />
VirtualizingStackPanel.VirtualizationMode offers two possibilities: Standard & Recycling. In case you are interested, here are their [https://docs.microsoft.com/en-us/dotnet/api/system.windows.controls.virtualizationmode?view=netframework-4.7.2 differences].<br />
<br />
=== Delayed loading {{Version/WinXSince|4.7}} ===<br />
By default the FlipView control (UWP only) doesn't have a delayed loading mechanism.<br />
Imagine if you flip through a large list of documents quickly, the control would actually end up loading every single one of them even if you just want to look at the content of the last one. This has a very negative effect that the app wastes a lot of resources loading documents for nothing, while struggling to display the content you care about. In some extreme case, this can even lead to an app hang/crash.<br />
<br />
We added such a delayed loading mechanism to this control. With it, the item content only starts to load when you stay on it for a while (1 second). If you are using the content of UBIKDocumentFlipView.xaml from an older version (before 4.7) and therefore experience such a performance/stability issue, please check the FlipView related section in the newer default templates of it.<br />
<br />
=== Auto saving {{Version/WinXSince|4.6}} ===<br />
Unsaved changes on the document (e.g. Annotations) are gonna be saved and committed automatically when flipping the page in the FlipView.<br />
<br />
{{Attention|Changes are lost when leaving the page without flipping the document first.}}<br />
<br />
{{Version/WinXSince|4.7}} {{Version/XamarinSince|4.7}} If you want to keep the changes when leaving the page by e.g. navigating away without flipping the document first, there is a boolean property called ''AutoSaveDocumentsOnPageClose'' (default value: false) which enables this behavior. It can be activated by adding the property to (or editing it in) the custom UBIKThemes as follows:<br />
<tabs><br />
<tab name="UWP"><br />
<source lang = "xml"><br />
<x:String x:Key="AutoSaveDocumentsOnPageClose">true</x:String><br />
</source><br />
</tab><br />
<br />
<tab name="Mobile(Xamarin)"><br />
<source lang = "xml"><br />
<x:String x:Key="AutoSaveDocumentsOnPageClose">true</x:String><br />
</source><br />
</tab><br />
</tabs><br />
<br />
[[Category:Client|XAML Tips]]<br />
[[Category:Mobile|XAML Tips]]<br />
[[Category:WinX|XAML Tips]]<br />
[[Category:XAML|XAML Tips]]<br />
<br />
== Platform and Device-specific UI with OnPlatform and OnIdiom {{Version/MobileSince|5.0}} ==<br />
<br />
'''OnPlatform''' can be used to define different property values based on the platform. Valid Platform names are:<br />
* iOS<br />
* Android<br />
* WinUI (for Mobile Windows)<br />
* further ones see [https://learn.microsoft.com/en-us/dotnet/maui/platform-integration/customize-ui-appearance?view=net-maui-9.0#customize-ui-appearance-with-a-markup-extension-based-on-the-platform here]<br />
<br><br />
'''OnIdom''' can be used to define different property values based on the device type (e.g. Phone, Tablet, Desktop).<br />
<br />
When it comes to the proper syntax, we should stick with the approaches mentioned in the [https://learn.microsoft.com/en-us/dotnet/maui/platform-integration/customize-ui-appearance?view=net-maui-9.0 official documentation].<br />
Means, we should '''avoid''' using the single-tag syntax like ''<OnPlatform Android="..." iOS="..." />'' or ''<OnIdiom Phone="..." Desktop="..." />'' like it was usual in Xamarin.<br />
<br />
Instead, we should either use the '''multi-tag syntax''' or the '''inline syntax''' for OnPlatform / OnIdiom.<br />
<br />
==== Multi-tag syntax ====<br />
Here it is mandatory to add '''x:TypeArguments="TheType"''' with the proper type to OnPlatfrom/OnIdiom. ''Default="..."'' is optional and can be added like in the following example if a default value needs to be defined.<br />
<tabs><br />
<tab name="OnPlatform"><br />
<source lang = "XML"><br />
<OnPlatform x:TypeArguments="Thickness" Default="20"><br />
<On Platform="iOS, WinUI" Value="0,20,0,0" /><br />
<On Platform="Android" Value="10,20,20,10" /><br />
</OnPlatform><br />
</source><br />
</tab><br />
<tab name="OnIdiom"><br />
<source lang = "XML"><br />
<OnIdiom x:TypeArguments="Thickness" Default="20"><br />
<OnIdiom.Desktop>0,60,0,0</OnIdiom.Desktop><br />
</OnIdiom><br />
</source><br />
</tab><br />
</tabs><br />
<br />
If OnPlatform Values contain multiple subtags, the following syntax can be used:<br />
<source lang = "XML"><br />
<ControlTemplate x:Key="ExampleControlTemplate"><br />
<Grid><br />
<OnPlatform x:TypeArguments="View"><br />
<On Platform="Android"><br />
<Button<br />
...<br />
Text="Button A" /><br />
...<br />
</On><br />
<On Platform="iOS"><br />
<Button<br />
...<br />
Text="Button B" /><br />
...<br />
</On><br />
<On Platform="WinUI"><br />
<Grid><br />
<Button<br />
...<br />
Text="Button C" /><br />
<Label Text="Example" /><br />
...<br />
</Grid><br />
</On><br />
</OnPlatform><br />
</Grid><br />
</ControlTemplate><br />
</source><br />
<br />
{{Attention|When using ''GridLength'' as a type in OnPlatform/OnIdiom, it should only be used in combination with the inline syntax.}}<br />
<br />
==== Inline syntax ====<br />
When using the inline syntax, the type should not be specified. ''Default='' is optional.<br />
<tabs><br />
<tab name="OnPlatform"><br />
<source lang = "XML"><br />
<BoxView Color="{OnPlatform Default=Yellow, iOS=Red, Android=Green}" /><br />
</source><br />
</tab><br />
<tab name="OnIdiom"><br />
<source lang = "XML"><br />
<BoxView Color="{OnIdiom Default=Yellow, Phone=Red, Tablet=Green}" /><br />
</source><br />
</tab><br />
</tabs><br />
<br />
If the value contains any special characters like <code>"</code> or <code>,</code> or a '''string''' when using the OnIdiom or OnPlatform inline variant, it needs to be wrapped between <code>' '</code>. But be careful with using apostrophes - when using them around curly brackets {} it can lead to an error.<br />
<tabs><br />
<tab name="Don't"><br />
<source lang = "XML"><br />
Margin="{OnIdiom 10,2, Phone=2,0}"<br />
</source><br />
</tab><br />
<tab name="Instead do"><br />
<source lang = "XML"><br />
Margin="{OnIdiom '10,2', Phone='2,0'}"<br />
</source><br />
</tab><br />
</tabs><br />
<br />
=== Complex values ===<br />
If the OnPlatform/OnIdiom value contains a '''Binding''', '''StaticResource''' or any other complex value in curly brackets, it is recommended to use the '''inline syntax'''. Although it's not confirmed in any official documentation, it seems to work according to our experience. However, the multi-tag syntax doesn't always seem to work for such cases. DynamicResource values seem to be not supported at all in OnIdiom / OnPlatform.<br />
<br />
<tabs><br />
<tab name="Don't"><br />
<source lang = "XML"><br />
<OnIdiom x:TypeArguments="..." Default="{Binding ...}"><br />
<OnIdiom.Phone>{Binding ...}</OnIdiom.Phone><br />
</OnIdiom><br />
</source><br />
</tab><br />
<tab name="Instead do"><br />
<source lang = "XML"><br />
Header="{OnIdiom Default={Binding ...}, Phone={Binding ...}}"<br />
</source><br />
</tab><br />
</tabs><br />
<br />
{{Attention|Unreliable Support: Behavior may vary when using bindings or complex resources. Although it seems to work with the inline syntax according to our experiences, it is recommended to test these edge cases thoroughly.}}<br />
<br />
[[Category:Client|XAML Tips]]<br />
[[Category:Mobile|XAML Tips]]<br />
[[Category:WinX|XAML Tips]]<br />
[[Category:XAML|XAML Tips]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Mobile_XAML&diff=29227Mobile XAML2025-12-11T10:16:06Z<p>LGE: /* Performance */</p>
<hr />
<div>The User Interface of the Mobile Clients (Android, iOS, Windows) can be fundamentally customized using custom XAML definitions. This customization process is heavily influenced by the [[XAML|XAML Customization Process on the WinX Client]].<br />
<br />
= Basics =<br />
There are predefined XAML templates available that can be customized. If no customizing is found, the default templates will be used.<br />
<br />
== Default XAMLs ==<br />
All default XAML templates that can be customized are available through the Mobile Windows client. You need to go to the app settings and click the "Unpack default XAMLs" button.<br />
<br />
== Differences to WinX/UWP ==<br />
* Since it's based on the Mobile XAML dialect, you CANNOT use any existing XAML customizings for the WinX/UWP app;<br />
* Namespace definitions must include the corresponding assembly names;<br />
* XAML template files have the extension name of '''xamlx''' instead of '''xaml''';<br />
* You can deploy only those resources that you want to customize. (This is also the case for newer versions of WinX/UWP. {{Version/WinXSince|3.6}})<br />
<br />
<br />
<br />
= Overriding default XAMLs=<br />
On Windows (WinX/UWP), the <code>[App Package Folder]/LocalState/xaml/</code> folder can be accessed by the user and the customized XAML files directly added. An alternative to this on all platforms (including Android, iOS, etc.) is to use the ''Import Customizing'' button in the app settings to import the templates, styles, images, etc. (file by file, or all files within a zip package). The changes should be reflected in the UI (except the current page) without restarting the app. After directly editing the customizings (Mobile Windows), you can also use the "Reload customizing" button without restarting the app.<br />
<br />
In the following, we're going to override the default light theme color of the app:<br />
* Unpack the default XAMLs;<br />
* Pick and deploy the default UBIKThemes.xamlx to the '''xaml''' folder inside the ''LocalState'' folder;<br />
* Open it with the text editor of your choice and remove everything within the '''ResouceDictionary''' except <code><Color x:Key="UBIKLightThemeColor">blue</Color></code>;<br />
* Save the changes and reload. You should see changes successfully implemented.<br />
<br />
{{Attention| For maintainability reasons, it's HIGHLY recommended to deploy only those XAML resources you want to override. For example, if you only want to customize the UBIKChildArea, don't deploy others like the UBIKMenuArea. If you only want to customize the UBIKChildItem, that's the only content you should include in the UBIKThemes.}}<br />
<br><br />
<br />
== Custom Templates ==<br />
Custom templates can be added, just like on the WinX/UWP client. Make sure to include all '''namespace definitions''' (as attributes of the '''ContentView''' tag), otherwise the custom template will not load.<br />
<br />
Similar to the ''UBIKThemes.xamlx'' file, custom or overridden templates start with a <code><ContentView></code> tag containing all '''namespaces'''. <code><ContentView.Resources></code> takes a '''ResourceDictionary''' and contains resources like references to converters. Finally, <code><ContentView.Content></code> contains the actual layout content (it's best to start with a '''Grid'''). Again, don't forget to add namespaces that you need!<br />
<br />
Templates can also be defined in ''UBIKThemes.xamlx''. In this case, they need to be added into the <code><ResourceDictionary></code> inside the <code><ContentView.Resources></code> template as a <code><DataTemplate></code>. Similarly, if you want to split up the templates into seperate files, you need to make sure to follow the steps mentioned above and get the content of the <code><DataTemplate></code> into the <code><ContentView.Content></code> tag.<br />
<br />
{{Attention|Templates defined in separate files will override templates defined in the ''UBIKThemes.xamlx''!}}<br />
<br />
=== Bindings in resources ===<br />
When using bindings such as [[Xamarin_XAML#Content_filtering|this]] in a resource located in a custom template, it is necessary to place the template in a UBIKContentView.<br />
<br />
{{Hint|Technically speaking, this is because bindable objects in the ResourceDictionary of a ContentView (the custom template) don't automatically inherit the BindingContext from the container/parent view. UBIKContentView is created to additionally do that.}}<br />
<br />
<source lang = "xml"><br />
Mobile(Xamarin):<br />
<br />
<!-- UBIKCustomView.xamlx --><br />
<ContentView...<br />
xmlns:controls="clr-namespace:UBIK.CPL.Controls;assembly=UBIK.CPL"><br />
<ContentView.Resources><br />
<ResourceDictionary><br />
<controls:SfDataSourceExt... ItemsSource="{Binding Children.Items}" /><br />
</ResourceDictionary><br />
</ContentView.Resources><br />
...<br />
</ContentView><br />
<br />
<!-- Container where UBIKCustomView is placed, e.g. UBIKChildArea.xamlx --><br />
<ContentView...<br />
xmlns:controls="clr-namespace:UBIK.CPL.Controls;assembly=UBIK.CPL"><br />
...<br />
<controls:UBIKContentView Content="{Binding [UBIKCustomView], Source={x:Static services:TemplateService.Instance}}" /><br />
</ContentView><br />
</source><br />
<br />
<br />
<br />
<br />
<br />
<br />
== Adding Images ==<br />
Images can't be loaded with the default '''Image''' tag, as the image is on different paths on each operating system.<br />
<br />
Therefore, there's a custom '''FileImage''' that internally overrides the default ''Image'' with two custom parameters:<br />
* '''FolderName''' ...The name of the '''folder''' in the '''local folder'''. Only the first level inside the ''LocalState'' folder seems to work.<br />
* '''FileName''' ...The name of the '''file''' in the said folder. <br />
<br />
Make sure to implement the proper namespace as well by adding<br />
<code>xmlns:fimage="clr-namespace:UBIK.CPL.Controls;assembly=UBIK.CPL"</code> into the root item's attributes.<br />
<br />
Then, the image can be loaded using:<br/><br />
<code><fimage:FileImage FileName="image.png" FolderName="xaml"/></code><br />
<br />
This snipped loads the image called '''image.png''' located in the '''xaml''' folder inside the ''LocalState''.<br />
<br />
Furthermore, the ''FileImage'' tag doesn't seem to support most attributes. Therefore place it inside a '''Grid''' to achieve a perfect layout.<br />
<br><br />
<br />
== Custom Icons ==<br />
Moved to article [[XAML_Tips#Custom_Icons]].<br />
<br><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Converters==<br />
:''Main Page: [[Converters_In_Mobile]]''<br />
<br />
They are used to convert specific data into some desired output, using custom logic. <br />
<br />
Consider the following example:<br/><br />
A label saying ''There are no children items available!'' should only be visible if the number of children-items is 0.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
= Advanced =<br />
<br />
== Feature related ==<br />
<br />
=== Customizing Menu Button {{Version/XamarinSince|4.6.0}} === <br />
<br />
For the Mobile Client, it is possible to show/hide the '''Menu button''' of the client.<br><br />
To customize the visibility of the '''Menu button''' you have to edit the default XAML '''Themes''' file.<br />
<br />
* Search for "'''ShowMenuToolBar'''" in the Themes file.<br />
<br><br />
If there isn't any "'''ShowMenuToolBar'''" in your XAML Themes file, you just have to create one, like this:<br />
<br />
<source lang = "xml"><br />
<x:Boolean x:Key="ShowMenuToolBar">true</x:Boolean><br />
</source><br />
<br />
* Set the value to "true" to show the '''Menu button''' (default value).<br />
* Set the value to "false" to hide the '''Menu button'''.<br />
<br />
<gallery widths="300" heights="500"><br />
File:menu_button_show.png|Menu Button shown<br />
File:menu_button_hiddenV3.png|Menu Button hidden<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
=== Content filtering ===<br />
For the Mobile clients, an "SfDataSourceExt" type is available for filtering list of items using defined expressions.<br /><br />
The following example demonstrates how to filter for child items having certain property values. The filtered list and its count can be displayed in the UI.<br /><br />
<syntaxhighlight lang="xml"><br />
Mobile(Xamarin):<br />
<br />
<ContentView<br />
xmlns:controls="clr-namespace:UBIK.CPL.Controls;assembly=UBIK.CPL"<br />
...><br />
<ContentView.Resources><br />
<ResourceDictionary><br />
<x:String x:Key="Expresssion">Item.Values[&quot;MP_YEAR&quot;].Contains(&quot;2019&quot;)</x:String><br />
<controls:SfDataSourceExt x:Key="FilteredList" Expression="{StaticResource Expresssion}" ItemsSource="{Binding Children.Items}" Unloaded="{Binding SkipFiltering}" /><br />
</ResourceDictionary><br />
</ContentView.Resources><br />
<StackLayout Orientation="Vertical"><br />
<Label Text="{Binding DisplayItemsCount, Source={StaticResource FilteredList}}" /><br />
<controls:SfListViewExt ItemsSource="{Binding DisplayItems, Source={StaticResource FilteredList}}" /><br />
</StackLayout><br />
</ContentView><br />
</syntaxhighlight><br />
<br />
==== Notes on using bindings in ResourceDictionary ====<br />
In the example shown above, you can see <code>{Binding Children.Items}</code> is used. For this to work, the SfDataSourceExt control inside the ResourceDictionary must inherit the binding data context properly.<br />
* In this case, that data context comes from where this template (UBIKChildArea.xamlx) is used, namely the UBIKContentArea.xamlx;<br />
* When referencing this template in a ContentView control, the binding data context is '''NOT''' automatically inherited by the controls inside the ResourceDictioinary;<br />
* That's why we use a UBIKContentView control instead. You can find its example usage in the default UBIKContentArea.xamlx template.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
=== Search ===<br />
In the default UBIKMenuArea.xamlx (where the search UI is hosted), there are two commands associated with two events. See below.<br />
<syntaxhighlight lang="xml"><br />
Mobile(Xamarin):<br />
<br />
<SearchBar ...><br />
<SearchBar.Behaviors><br />
<behaviors:EventToCommandBehavior<br />
Command="{Binding FreeTextSearchCommand}"<br />
CommandParameter="{Binding Path=Text, Source={x:Reference SearchField}}"<br />
EventName="SearchButtonPressed" /><br />
<behaviors:EventToCommandBehavior Command="{Binding DelayedFreeTextSearchCommand}" EventName="TextChanged" /><br />
</SearchBar.Behaviors><br />
</SearchBar><br />
</syntaxhighlight><br />
<br /><br />
The one for <code>SearchButtonPressed</code> is responsible for executing searches after the user confirms the input (e.g. pressing {{{keypress|Enter}}} or the search button).<br />
<br /><br />
The one for <code>TextChanged</code> is responsible for the "search as you type" behavior. Namely it triggers an automatic search shortly (half second) after the user stops changing the text in the search bar. It can be turned off by simply removing that particular behavior.<br />
<br />
=== DisplayViewCommand ===<br />
This command can be used to [[Custom_View_(Client)|display custom views]].<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Performance ==<br />
To get a good performance in the app UI when using your Xaml customizings, it is recommended to try the following.<br />
* Always keep your UI structure simple. Choose the most efficient layouts for the scenarios and avoid unnecessary UI elements. Please refer to [https://docs.microsoft.com/en-us/xamarin/xamarin-forms/deploy-test/performance#choose-the-correct-layout "choose the correct layout"] and [https://docs.microsoft.com/en-us/xamarin/xamarin-forms/deploy-test/performance#reduce-the-visual-tree-size "reduce the visual tree size"];<br />
* Turn on [https://docs.microsoft.com/en-us/xamarin/xamarin-forms/user-interface/layouts/layout-compression layout compression] on wrapping elements that don't have any visual parameters set (reasons stated in the linked documentation).<br />
{{Hint|There is a default "HeadlessLayout" style available in the app you can use on elements such as Grids, StackLayouts, ContentViews, etc. It turns on [[Xamarin_XAML#Layout_compression_examples|layout compression]] on the applied elements in Xamarin.Android (since we find it not worth the effort in Xamarin.iOS).}}<br />
{{Attention|If possible, one should always favor designing the UI with less wrapping elements over turning on layout compression on unnecessary ones.}}<br />
<br />
=== General performance tips ===<br />
* Reduce number of views per page<br />
* Don’t bind things if they could be set static easily<br />
* If you do not change the default, don’t set it explicit. For example, [https://docs.microsoft.com/en-us/dotnet/api/Xamarin.Forms.StackLayout.Orientation?view=xamarin-forms Orientation of StackLayout] is “Vertical” by default. No need to set it manually if you don’t want to change it.<br />
* Transparency is expensive.<br />
* Use async/await to avoid blocking user interface.<br />
* Do not put ListViews into ScrollViews.<br />
* To stack elements, create a grid and add them to the same cell one after another. It’s cheaper than RelativeLayout.<br />
* Use Margins instead of Paddings.<br />
<br />
=== Layouts ===<br />
* Choose correct Layout, e.g. no need to add a StackLayout if it only has 1 child.<br />
* [https://docs.microsoft.com/en-us/xamarin/xamarin-forms/user-interface/layouts/layout-options LayoutOptions].Fill or .FillAndExpand are best choice in most cases. And they are already default, so no need to set.<br />
* Autosize of rows and columns in grids should used as few as possible.<br />
* RelativeLayout is very expensive. Try to avoid.<br />
* In StackLayout, make sure there is only 1 LayoutOptions Expand.<br />
<br />
=== Labels ===<br />
* Use [https://docs.microsoft.com/en-us/xamarin/xamarin-forms/user-interface/text/label#formatted-text FormattedText] instead of multiple labels.<br />
* Use [https://docs.microsoft.com/en-us/dotnet/api/xamarin.forms.linebreakmode?view=xamarin-forms Linebreakmode] NoWrap (which is already the default).<br />
* Avoid [https://docs.microsoft.com/en-us/dotnet/api/Xamarin.Forms.Label.VerticalTextAlignment?view=xamarin-forms VerticalTextAlignment]. Anyway, if needed, use VerticalTextAligment instead of <br />
VerticalOptions.<br />
* Use the "TextTransform" attribute to convert the value of the "Text" attribute to either uppercase or lowercase.<br />
<syntaxhighlight lang="xml"><br />
<Label<br />
TextTransform="Uppercase"<br />
Text="{Binding Properties.AllItems[DESCR].DisplayValue}" /><br />
</syntaxhighlight ><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
=== Images ===<br />
* Provide images in optimized width and size. Provide multiple resolutions for different usage.<br />
* Set [https://docs.microsoft.com/en-us/dotnet/api/Xamarin.Forms.Image.IsOpaque?view=xamarin-forms IsOpaque] to true if image is opaque.<br />
<br />
=== Layout compression examples ===<br />
<syntaxhighlight lang="xml"><br />
<ContentView ControlTemplate="{DynamicResource ChangedSymbol}" Style="{DynamicResource HeadlessLayout}" /><br />
</syntaxhighlight><br />
The code above removes one wrapping element added automatically by the ContentView and demonstrates a good reason to use layout compression because it can not be avoided otherwise.<br />
<syntaxhighlight lang="xml"><br />
<Grid Margin="2" Style="{DynamicResource HeadlessLayout}"><br />
<Label Margin="5" Text="{Binding Title}" /><br />
</Grid><br />
</syntaxhighlight><br />
This example, on the other hand, demonstrates a bad usage of layout compression because it can be easily achieved by better designs such as using only the Label with a merged margin.<br />
<br />
Sometimes the content inside a compressed layout appears on a wrong z-index level. For eample:<br />
<syntaxhighlight lang="xml"><br />
<BoxView CornerRadius="14" HeightRequest="28" WidthRequest="28" Color="Red" /><br />
<ContentView ControlTemplate="{DynamicResource Badge}" Style="{DynamicResource HeadlessLayout}"><br />
<Label Text="{Binding Title}" /><br />
</ContentView ><br />
</syntaxhighlight><br />
According to the order of the BoxView and the Label, the latter should appear on top of the former (later ones have higher z-index levels). However, this can be disturbed by layout compression, causing the exact opposite.<br />
In this case, you can add a <code>xmlns:android="clr-namespace:Xamarin.Forms.PlatformConfiguration.AndroidSpecific;assembly=Xamarin.Forms.Core"</code> namespace to your Xaml file and manually elevate the Label by specifying <code>android:VisualElement.Elevation="X"</code> on it accordingly (X is the delta of the z-index level you want).<br />
<br />
=== SfListViewExt ===<br />
For performance reasons, we created an extended version of the Syncfusion SfListView control and it should be used for all lists in customizings. You need to add a namespace like <code>xmlns:controls="clr-namespace:UBIK.CPL.Controls;assembly=UBIK.CPL"</code> to your Xaml file and use it like <code><controls:SfListViewExt ... /></code>.<br />
{{Hint|Technically speaking, SfListViewExt informs item view models when their corresponding item views appear on / disappear from the screen. This way, view models can skip a lot of unnecessary work (on the UI) when their views are not visible. '''If SfListView is used instead, the item views will not reflect content changes until the page is reloaded/refreshed.'''}}<br />
<br />
It is possible to configure the ListView, that the ScrollPosition is remembered when navigating away from the page, to do so, the property RembemberScrollPosition needs to be set to true. If unset, the value defaults to false and the scroll positions are not remembered.<br />
<br />
<syntaxhighlight lang="xml"><br />
<controls:SfListViewExt RememberScrollPosition="True"/><br />
</syntaxhighlight><br />
<br />
When using multiple Lists on one page (e.g. in a TabbedView), it is necessary to set the AutomationId property uniquely for each list on the page, to support the remembering of the ScrollPosition.<br />
<br />
=== Delay in UBIKContentView and ContentControl {{Version/MobileSince|5.1}} ===<br />
More complex UIs create a delay in rendering which leads to a feeling of "unresponsiveness" when navigating through the client. This is because the app loads and displays everything at once, leading to a larger delay between triggering navigation and completion of page loading.<br />
<br />
While the complexity of the UI directly affects the time taken to render it, the experience of responsiveness can be somewhat improved by actually adding a delay between the loading of the content page, and actual data content (properties, children, etc). By not loading both at once, resources are freed up in the app, leading to a quicker loading of the basic page. The content then loads in at its normal speed.<br />
<br />
<br />
Starting from version 5.1, a small delay was introduced in the content heavy pages (child page, document page and query page). However, additional delays can also be applied to the custom UI at will, using a new property added to two existing controls used to insert UI templates: UBIKContentView and ContentControl. You can specify a delay (in milliseconds) on both controls so that the content of them is loaded after that amount of time. Examples are shown below.<br />
<syntaxhighlight lang="xml"><br />
<controls:UBIKContentView Delay="50" Converter="{StaticResource ChildAreaTemplateConverter}" /><br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<controls:ContentControl Delay="50" ContentTemplate="{Binding [UBIKNavigationBar], Source={x:Static services:TemplateService.Instance}}" /><br />
</syntaxhighlight><br />
<br />
<br />
Please note: The delay won't have any effect if you specify the Content of the UBIKContentView control instead of its Converter, because the Content is immediately laid out by the XAML framework that way. If you don't need a converter to determine the actual template name dynamically, you can still use the TemplateConverter and specify the template name like the following so that the delay applies.<br />
<tabs><br />
<tab name="Delay applies ✅"><br />
<syntaxhighlight lang="xml"><br />
<controls:UBIKContentView Delay="50" Converter="{StaticResource TemplateConverter}" ConverterParameter="UBIKChildArea" /><br />
</syntaxhighlight><br />
</tab><br />
<tab name="Delay doesn't apply ❌"><br />
<syntaxhighlight lang="xml"><br />
<controls:UBIKContentView Delay="50" Content="{Binding [UBIKChildArea], Source={x:Static services:TemplateService.Instance}}" /><br />
</syntaxhighlight><br />
</tab><br />
</tabs><br />
<br />
[[Category:Client|Xamarin XAML]]<br />
[[Category:Mobile|Mobile XAML]]<br />
[[Category:Pages with broken file links|Xamarin XAML]]<br />
[[Category:Styling|Xamarin XAML]]<br />
[[Category:XAML|Xamarin XAML]]<br />
<br />
= Known issues =<br />
<br />
=== Headlesslayout style in custom UBIKThemes causing problems ===<br />
<br />
In our default '''UBIKThemes''', we are currently using this style for a headless layout:<br />
<br />
<syntaxhighlight lang="xml"><br />
Mobile(Xamarin):<br />
<br />
<Style x:Key="HeadlessLayout" TargetType="Layout"><br />
<Setter Property="CompressedLayout.IsHeadless"><br />
<Setter.Value><br />
<OnPlatform<br />
x:TypeArguments="x:Boolean"<br />
Android="True"<br />
WinPhone="False"<br />
iOS="False" /><br />
</Setter.Value><br />
</Setter><br />
</Style><br />
</syntaxhighlight><br />
<br />
<br/><br />
This style is used for better UI performance on Android.<br />
Using this style in a '''custom UBIKThemes''' could cause an exception & an app crash, or some objects to disappear.<br />
The best case would be to '''not''' include it in the custom themes file, as it's unnecessary if you don't want to make any changes here.<br />
<br />
'''This issue is only known on Android tablet devices.'''<br />
<br><br />
<br><br />
<br />
[[Category:Client|Xamarin XAML]]<br />
[[Category:Mobile|Mobile XAML]]<br />
[[Category:Pages with broken file links|Xamarin XAML]]<br />
[[Category:Styling|Xamarin XAML]]<br />
[[Category:XAML|Xamarin XAML]]<br />
<br />
=== DataTrigger Issues ===<br />
==== Conflicting Triggers ====<br />
DataTriggers in Mobile function better than the equivalent DataTriggerBehavior in UWP as they automatically handle the opposite case when a Boolean attribute value is set. This means that if a boolean DataTrigger is set, such as IsVisible=True, the False visibility will automatically be set if the Binding/Value condition is not met.<br />
<br />
However, this means that stacking multiple DataTriggers on the same attribute can lead to unexpected results. For this reason, it is recommended to use as few DataTriggers as possible. <br />
* Avoid setting the same attribute more than once; do not set the same value as a default attribute and in the DataTrigger (ControlTemplate in the below example).<br />
* Ideally, use only DataTriggers without a default ControlTemplate. This ensures that content is created only after the trigger evaluation is complete. If a default ControlTemplate is set, it is always loaded immediately, even if another template is applied right after.<br />
* It is acceptable, but not recommended, to combine a single DataTrigger with an opposite default value, but only if the default value is different from all values set in triggers.<br />
<br />
<tabs><br />
<tab name="Don't Do"><br />
<source lang = "xml"><br />
<ContentView x:Name="editorValueContainer" ControlTemplate="{StaticResource SelListTemplate}"><br />
<ContentView.Triggers><br />
<DataTrigger Binding="{Binding Source={x:Reference editorValueContainer}, Path=BindingContext.PropertyViewModel.ShowComboBox}" TargetType="ContentView" Value="true"><br />
<Setter Property="ControlTemplate" Value="{StaticResource SelListTemplate}" /><br />
</DataTrigger><br />
<DataTrigger Binding="{Binding Source={x:Reference editorValueContainer}, Path=BindingContext.PropertyViewModel.ShowComboBox}" TargetType="ContentView" Value="false"><br />
<Setter Property="ControlTemplate" Value="{StaticResource TextTemplate}" /><br />
</DataTrigger><br />
</ContentView.Triggers><br />
</ContentView><br />
</source><br />
<br><br />
</tab><br />
<br />
<tab name="Instead Do"><br />
<source lang = "xml"><br />
<ContentView x:Name="editorValueContainer"><br />
<ContentView.Triggers><br />
<DataTrigger Binding="{Binding Source={x:Reference editorValueContainer}, Path=BindingContext.PropertyViewModel.ShowComboBox}" TargetType="ContentView" Value="true"><br />
<Setter Property="ControlTemplate" Value="{StaticResource SelListTemplate}" /><br />
</DataTrigger><br />
<DataTrigger Binding="{Binding Source={x:Reference editorValueContainer}, Path=BindingContext.PropertyViewModel.ShowComboBox}" TargetType="ContentView" Value="false"><br />
<Setter Property="ControlTemplate" Value="{StaticResource TextTemplate}" /><br />
</DataTrigger><br />
</ContentView.Triggers><br />
</ContentView><br />
</source><br />
</tab><br />
<br />
<tab name="Acceptable, but not recommended"><br />
<source lang = "xml"><br />
<ContentView x:Name="editorValueContainer" ControlTemplate="{StaticResource SelListTemplate}"><br />
<ContentView.Triggers><br />
<DataTrigger Binding="{Binding Source={x:Reference editorValueContainer}, Path=BindingContext.PropertyViewModel.ShowComboBox}" TargetType="ContentView" Value="false"><br />
<Setter Property="ControlTemplate" Value="{StaticResource TextTemplate}" /><br />
</DataTrigger><br />
</ContentView.Triggers><br />
</ContentView><br />
</source><br />
</tab><br />
</tabs><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
==== DataTrigger to set Footer Properties in a ListView ====<br />
<br />
When using a DataTrigger to set the properties of a footer for a ListView, the sequence of the properties inside the DataTrigger might matter in some cases.<br />
It seems to occur since Version 4.4 due to a Syncfusion update and could lead to the page not being rendered properly and appearing empty.<br />
<br />
If you encounter such an issue, please workaround by adding the IsStickyFooter Property Setter on top inside the DataTrigger.<br />
Also, new customizings should consider this workaround as a preventive action.<br />
<br />
<syntaxhighlight lang="xml"><br />
<!-- THIS DOESN'T WORK IN CERTAIN CASES --><br />
<controls:SfListViewExt ...><br />
<controls:SfListViewExt.Triggers><br />
<DataTrigger TargetType="controls:SfListViewExt" Binding="{Binding Title}" Value="Administration"><br />
<Setter Property="FooterTemplate" Value="{DynamicResource AddLoginFooter}" /><br />
<Setter Property="FooterSize" Value="64" /><br />
<Setter Property="IsStickyFooter" Value="True" /><br />
</DataTrigger><br />
</controls:SfListViewExt.Triggers><br />
</controls:SfListViewExt><br />
</syntaxhighlight><br />
<br />
<br/><br />
<syntaxhighlight lang="xml"><br />
<!-- THIS WORKS --><br />
<controls:SfListViewExt ...><br />
<controls:SfListViewExt.Triggers><br />
<DataTrigger TargetType="controls:SfListViewExt" Binding="{Binding Title}" Value="Administration"><br />
<Setter Property="IsStickyFooter" Value="True" /><br />
<Setter Property="FooterTemplate" Value="{DynamicResource AddLoginFooter}" /><br />
<Setter Property="FooterSize" Value="64" /><br />
</DataTrigger><br />
</controls:SfListViewExt.Triggers><br />
</controls:SfListViewExt><br />
</syntaxhighlight><br />
<br><br />
<br><br />
=== Incorrect glyphs may be shown on buttons ===<br />
<br />
When using glyphs on buttons in Mobile, sometimes a different glyph than the expected one will show up when viewing the app on Android.<br />
They only seem to appear incorrectly when used as the Text property of the button (with FontFamily set to UBIKSymbols, such as the UBIKIconButton style.)<br />
<br />
If you encounter this issue please workaround by supplying the icon through the FontImageSource property of the button.<br />
<br />
<syntaxhighlight lang="xml"><br />
<Button Command="{Binding BulkOperation.InvokeOnItemsCommand}"><br />
<Button.ImageSource><br />
<FontImageSource <br />
FontFamily="{DynamicResource UBIKSymbols}"<br />
Glyph="{x:Static resources:UBIKIcons.MobileDelete}"<br />
Color="{DynamicResource UBIKDarkThemeColor}"<br />
Size="22"/><br />
</Button.ImageSource><br />
<Button.CommandParameter><br />
<classes:KeyValueList><br />
<classes:KeyValueParameter Key="Command" Value="DiscardContentCommand" /><br />
</classes:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</syntaxhighlight><br />
<br><br />
<br><br />
=== Buttons and gesture recognizers ===<br />
In Mobile XAML, you can use gesture recognizers on many UI elements such as a Grid to enable the latter to interact with user inputs.<br />
<br />
However, we've already made quite a lot of experience that gesture recognizers do not always work on Android and iOS when used on a Button control.<br />
For example, the following Button won't properly invoke the command on said platforms.<br />
<br />
<syntaxhighlight lang="xml"><br />
<!-- THIS DOESN'T WORK!!! --><br />
<Button ...><br />
<Button.GestureRecognizers><br />
<TapGestureRecognizer Command="{Binding ReplicateAsDataCommand}" /><br />
</Button.GestureRecognizers><br />
</Button><br />
</syntaxhighlight><br />
<br />
<br/><br />
Therefore, you should always seek alternatives for Buttons.<br />
'''If only one command is needed''', use the standard Command property on the Button, e.g.<br />
<br />
<syntaxhighlight lang="xml"><br />
<!-- THIS WORKS --><br />
<Button Command="{Binding ReplicateAsDataCommand}" .../><br />
</syntaxhighlight><br />
<br />
<br/><br />
Or if multiple commands are needed, use Behaviors '''instead''', e.g.<br />
<br />
<syntaxhighlight lang="xml"><br />
<!-- THIS ALSO WORKS --><br />
<Button xmlns:behaviors="clr-namespace:UBIK.CPL.Behaviors;assembly=UBIK.CPL" ...><br />
<Button.Behaviors><br />
<behaviors:EventToCommandBehavior Command="{Binding ReplicateAsDataCommand}" EventName="Clicked" /><br />
<behaviors:EventToCommandBehavior Command="{Binding NavigateBackCommand}" EventName="Clicked" /><br />
</Button.Behaviors><br />
</Button><br />
</syntaxhighlight><br />
<br><br />
<br><br />
=== No dynamic reloading of Document Viewer ===<br />
[[File:PDFViewerFixWiki.JPG]]<br />
<br />
In a customizing that combines a single-selection list of documents with some kind of viewer (especially UBIKDocumentContentArea), it is generally the case that switching the document causes the document viewer to then appear blank. The technical reason is that the PDFViewer used in the UBIKDocumentContentArea is not reloaded once the document content is reloaded. <br />
<br />
An easy fix is to apply a DataTrigger that unloads the ContentView when the document content is null, as the ContentView is forced to rerender itself when the trigger condition is no longer met.<br />
<br />
<syntaxhighlight lang="xml"><br />
<!-- Document Viewer --><br />
<controls:UBIKContentView <br />
x:Name="DoucmentViewer" <br />
BindingContext="{Binding SelectedItem, Source={x:Reference DocumentList}}"<br />
Content="{Binding [UBIKDocumentContentArea], Source={x:Static services:TemplateService.Instance}}"><br />
<br />
<controls:UBIKContentView.Triggers><br />
<DataTrigger TargetType="controls:UBIKContentView" Binding="{Binding SelectedItem.DocumentViewModel.DocumentContent, Source={x:Reference DocumentList}, Converter={StaticResource NullToBool}}" Value="True"><br />
<Setter Property="Content" Value="{x:Null}" /><br />
</DataTrigger><br />
</controls:UBIKContentView.Triggers><br />
</controls:UBIKContentView><br />
</syntaxhighlight><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
=== Issues with SfPullToRefresh in Mobile client {{Version/MobileSince|5.0}} ===<br />
Due to a third-party issue, problems may occur on Mobile Android when using the SfPullToRefresh control in combination with the SfListViewExt. This can result in e.g. navigation or task interaction sometimes requiring multiple clicks.<br />
In general, and due to more issues, it's not recommended to use the SfPullToRefresh control.<br />
In our Mobile standard client, the PullToRefresh control has been replaced by a Refresh button in the Context Menu.<br />
If you still decide to use SfPullToRefresh, there are a few points to consider:<br />
<br />
==== Avoid multiple SfPullToRefresh controls ====<br />
To prevent an issue that causes the app to freeze, avoid placing more than one SfPullToRefresh controls as siblings in a xaml hierarchy. If switching between contents in a SfPullToRefresh control is necessary use separate DataTemplates for the contents and use e.g. a DataTrigger to set one of them as the ControlTemplate of a ContentControl inside the SfPullToRefresh control. For an example, refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui#Avoid_multiple_SfPullToRefresh_controls|this link]].<br />
<br />
==== Avoid using SyncFusion ListViews directly in SfPullToRefresh controls ====<br />
To prevent an issue on some Android devices that can cause some items in a SfListViewExt to be rendered incorrectly or not at all after triggering a PullToRefresh, avoid placing a SfListViewExt directly in a SfPullToRefresh control. Instead, wrap the ListView in a DataTemplate and use it in a ContentControl as a child of the SfPullToRefresh control. For an example, refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui#Avoid_using_SyncFusion_ListViews_directly_in_SfPullToRefresh_controls|this link]].<br />
<br />
[[Category:Client|Xamarin XAML]]<br />
[[Category:Mobile|Mobile XAML]]<br />
[[Category:Pages with broken file links|Xamarin XAML]]<br />
[[Category:Styling|Xamarin XAML]]<br />
[[Category:XAML|Xamarin XAML]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Mobile_XAML&diff=29226Mobile XAML2025-12-10T15:07:01Z<p>LGE: /* Performance */</p>
<hr />
<div>The User Interface of the Mobile Clients (Android, iOS, Windows) can be fundamentally customized using custom XAML definitions. This customization process is heavily influenced by the [[XAML|XAML Customization Process on the WinX Client]].<br />
<br />
= Basics =<br />
There are predefined XAML templates available that can be customized. If no customizing is found, the default templates will be used.<br />
<br />
== Default XAMLs ==<br />
All default XAML templates that can be customized are available through the Mobile Windows client. You need to go to the app settings and click the "Unpack default XAMLs" button.<br />
<br />
== Differences to WinX/UWP ==<br />
* Since it's based on the Mobile XAML dialect, you CANNOT use any existing XAML customizings for the WinX/UWP app;<br />
* Namespace definitions must include the corresponding assembly names;<br />
* XAML template files have the extension name of '''xamlx''' instead of '''xaml''';<br />
* You can deploy only those resources that you want to customize. (This is also the case for newer versions of WinX/UWP. {{Version/WinXSince|3.6}})<br />
<br />
<br />
<br />
= Overriding default XAMLs=<br />
On Windows (WinX/UWP), the <code>[App Package Folder]/LocalState/xaml/</code> folder can be accessed by the user and the customized XAML files directly added. An alternative to this on all platforms (including Android, iOS, etc.) is to use the ''Import Customizing'' button in the app settings to import the templates, styles, images, etc. (file by file, or all files within a zip package). The changes should be reflected in the UI (except the current page) without restarting the app. After directly editing the customizings (Mobile Windows), you can also use the "Reload customizing" button without restarting the app.<br />
<br />
In the following, we're going to override the default light theme color of the app:<br />
* Unpack the default XAMLs;<br />
* Pick and deploy the default UBIKThemes.xamlx to the '''xaml''' folder inside the ''LocalState'' folder;<br />
* Open it with the text editor of your choice and remove everything within the '''ResouceDictionary''' except <code><Color x:Key="UBIKLightThemeColor">blue</Color></code>;<br />
* Save the changes and reload. You should see changes successfully implemented.<br />
<br />
{{Attention| For maintainability reasons, it's HIGHLY recommended to deploy only those XAML resources you want to override. For example, if you only want to customize the UBIKChildArea, don't deploy others like the UBIKMenuArea. If you only want to customize the UBIKChildItem, that's the only content you should include in the UBIKThemes.}}<br />
<br><br />
<br />
== Custom Templates ==<br />
Custom templates can be added, just like on the WinX/UWP client. Make sure to include all '''namespace definitions''' (as attributes of the '''ContentView''' tag), otherwise the custom template will not load.<br />
<br />
Similar to the ''UBIKThemes.xamlx'' file, custom or overridden templates start with a <code><ContentView></code> tag containing all '''namespaces'''. <code><ContentView.Resources></code> takes a '''ResourceDictionary''' and contains resources like references to converters. Finally, <code><ContentView.Content></code> contains the actual layout content (it's best to start with a '''Grid'''). Again, don't forget to add namespaces that you need!<br />
<br />
Templates can also be defined in ''UBIKThemes.xamlx''. In this case, they need to be added into the <code><ResourceDictionary></code> inside the <code><ContentView.Resources></code> template as a <code><DataTemplate></code>. Similarly, if you want to split up the templates into seperate files, you need to make sure to follow the steps mentioned above and get the content of the <code><DataTemplate></code> into the <code><ContentView.Content></code> tag.<br />
<br />
{{Attention|Templates defined in separate files will override templates defined in the ''UBIKThemes.xamlx''!}}<br />
<br />
=== Bindings in resources ===<br />
When using bindings such as [[Xamarin_XAML#Content_filtering|this]] in a resource located in a custom template, it is necessary to place the template in a UBIKContentView.<br />
<br />
{{Hint|Technically speaking, this is because bindable objects in the ResourceDictionary of a ContentView (the custom template) don't automatically inherit the BindingContext from the container/parent view. UBIKContentView is created to additionally do that.}}<br />
<br />
<source lang = "xml"><br />
Mobile(Xamarin):<br />
<br />
<!-- UBIKCustomView.xamlx --><br />
<ContentView...<br />
xmlns:controls="clr-namespace:UBIK.CPL.Controls;assembly=UBIK.CPL"><br />
<ContentView.Resources><br />
<ResourceDictionary><br />
<controls:SfDataSourceExt... ItemsSource="{Binding Children.Items}" /><br />
</ResourceDictionary><br />
</ContentView.Resources><br />
...<br />
</ContentView><br />
<br />
<!-- Container where UBIKCustomView is placed, e.g. UBIKChildArea.xamlx --><br />
<ContentView...<br />
xmlns:controls="clr-namespace:UBIK.CPL.Controls;assembly=UBIK.CPL"><br />
...<br />
<controls:UBIKContentView Content="{Binding [UBIKCustomView], Source={x:Static services:TemplateService.Instance}}" /><br />
</ContentView><br />
</source><br />
<br />
<br />
<br />
<br />
<br />
<br />
== Adding Images ==<br />
Images can't be loaded with the default '''Image''' tag, as the image is on different paths on each operating system.<br />
<br />
Therefore, there's a custom '''FileImage''' that internally overrides the default ''Image'' with two custom parameters:<br />
* '''FolderName''' ...The name of the '''folder''' in the '''local folder'''. Only the first level inside the ''LocalState'' folder seems to work.<br />
* '''FileName''' ...The name of the '''file''' in the said folder. <br />
<br />
Make sure to implement the proper namespace as well by adding<br />
<code>xmlns:fimage="clr-namespace:UBIK.CPL.Controls;assembly=UBIK.CPL"</code> into the root item's attributes.<br />
<br />
Then, the image can be loaded using:<br/><br />
<code><fimage:FileImage FileName="image.png" FolderName="xaml"/></code><br />
<br />
This snipped loads the image called '''image.png''' located in the '''xaml''' folder inside the ''LocalState''.<br />
<br />
Furthermore, the ''FileImage'' tag doesn't seem to support most attributes. Therefore place it inside a '''Grid''' to achieve a perfect layout.<br />
<br><br />
<br />
== Custom Icons ==<br />
Moved to article [[XAML_Tips#Custom_Icons]].<br />
<br><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Converters==<br />
:''Main Page: [[Converters_In_Mobile]]''<br />
<br />
They are used to convert specific data into some desired output, using custom logic. <br />
<br />
Consider the following example:<br/><br />
A label saying ''There are no children items available!'' should only be visible if the number of children-items is 0.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
= Advanced =<br />
<br />
== Feature related ==<br />
<br />
=== Customizing Menu Button {{Version/XamarinSince|4.6.0}} === <br />
<br />
For the Mobile Client, it is possible to show/hide the '''Menu button''' of the client.<br><br />
To customize the visibility of the '''Menu button''' you have to edit the default XAML '''Themes''' file.<br />
<br />
* Search for "'''ShowMenuToolBar'''" in the Themes file.<br />
<br><br />
If there isn't any "'''ShowMenuToolBar'''" in your XAML Themes file, you just have to create one, like this:<br />
<br />
<source lang = "xml"><br />
<x:Boolean x:Key="ShowMenuToolBar">true</x:Boolean><br />
</source><br />
<br />
* Set the value to "true" to show the '''Menu button''' (default value).<br />
* Set the value to "false" to hide the '''Menu button'''.<br />
<br />
<gallery widths="300" heights="500"><br />
File:menu_button_show.png|Menu Button shown<br />
File:menu_button_hiddenV3.png|Menu Button hidden<br />
</gallery><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
=== Content filtering ===<br />
For the Mobile clients, an "SfDataSourceExt" type is available for filtering list of items using defined expressions.<br /><br />
The following example demonstrates how to filter for child items having certain property values. The filtered list and its count can be displayed in the UI.<br /><br />
<syntaxhighlight lang="xml"><br />
Mobile(Xamarin):<br />
<br />
<ContentView<br />
xmlns:controls="clr-namespace:UBIK.CPL.Controls;assembly=UBIK.CPL"<br />
...><br />
<ContentView.Resources><br />
<ResourceDictionary><br />
<x:String x:Key="Expresssion">Item.Values[&quot;MP_YEAR&quot;].Contains(&quot;2019&quot;)</x:String><br />
<controls:SfDataSourceExt x:Key="FilteredList" Expression="{StaticResource Expresssion}" ItemsSource="{Binding Children.Items}" Unloaded="{Binding SkipFiltering}" /><br />
</ResourceDictionary><br />
</ContentView.Resources><br />
<StackLayout Orientation="Vertical"><br />
<Label Text="{Binding DisplayItemsCount, Source={StaticResource FilteredList}}" /><br />
<controls:SfListViewExt ItemsSource="{Binding DisplayItems, Source={StaticResource FilteredList}}" /><br />
</StackLayout><br />
</ContentView><br />
</syntaxhighlight><br />
<br />
==== Notes on using bindings in ResourceDictionary ====<br />
In the example shown above, you can see <code>{Binding Children.Items}</code> is used. For this to work, the SfDataSourceExt control inside the ResourceDictionary must inherit the binding data context properly.<br />
* In this case, that data context comes from where this template (UBIKChildArea.xamlx) is used, namely the UBIKContentArea.xamlx;<br />
* When referencing this template in a ContentView control, the binding data context is '''NOT''' automatically inherited by the controls inside the ResourceDictioinary;<br />
* That's why we use a UBIKContentView control instead. You can find its example usage in the default UBIKContentArea.xamlx template.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
=== Search ===<br />
In the default UBIKMenuArea.xamlx (where the search UI is hosted), there are two commands associated with two events. See below.<br />
<syntaxhighlight lang="xml"><br />
Mobile(Xamarin):<br />
<br />
<SearchBar ...><br />
<SearchBar.Behaviors><br />
<behaviors:EventToCommandBehavior<br />
Command="{Binding FreeTextSearchCommand}"<br />
CommandParameter="{Binding Path=Text, Source={x:Reference SearchField}}"<br />
EventName="SearchButtonPressed" /><br />
<behaviors:EventToCommandBehavior Command="{Binding DelayedFreeTextSearchCommand}" EventName="TextChanged" /><br />
</SearchBar.Behaviors><br />
</SearchBar><br />
</syntaxhighlight><br />
<br /><br />
The one for <code>SearchButtonPressed</code> is responsible for executing searches after the user confirms the input (e.g. pressing {{{keypress|Enter}}} or the search button).<br />
<br /><br />
The one for <code>TextChanged</code> is responsible for the "search as you type" behavior. Namely it triggers an automatic search shortly (half second) after the user stops changing the text in the search bar. It can be turned off by simply removing that particular behavior.<br />
<br />
=== DisplayViewCommand ===<br />
This command can be used to [[Custom_View_(Client)|display custom views]].<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Performance ==<br />
To get a good performance in the app UI when using your Xaml customizings, it is recommended to try the following.<br />
* Always keep your UI structure simple. Choose the most efficient layouts for the scenarios and avoid unnecessary UI elements. Please refer to [https://docs.microsoft.com/en-us/xamarin/xamarin-forms/deploy-test/performance#choose-the-correct-layout "choose the correct layout"] and [https://docs.microsoft.com/en-us/xamarin/xamarin-forms/deploy-test/performance#reduce-the-visual-tree-size "reduce the visual tree size"];<br />
* Turn on [https://docs.microsoft.com/en-us/xamarin/xamarin-forms/user-interface/layouts/layout-compression layout compression] on wrapping elements that don't have any visual parameters set (reasons stated in the linked documentation).<br />
{{Hint|There is a default "HeadlessLayout" style available in the app you can use on elements such as Grids, StackLayouts, ContentViews, etc. It turns on [[Xamarin_XAML#Layout_compression_examples|layout compression]] on the applied elements in Xamarin.Android (since we find it not worth the effort in Xamarin.iOS).}}<br />
{{Attention|If possible, one should always favor designing the UI with less wrapping elements over turning on layout compression on unnecessary ones.}}<br />
<br />
=== General performance tips ===<br />
* Reduce number of views per page<br />
* Don’t bind things if they could be set static easily<br />
* If you do not change the default, don’t set it explicit. For example, [https://docs.microsoft.com/en-us/dotnet/api/Xamarin.Forms.StackLayout.Orientation?view=xamarin-forms Orientation of StackLayout] is “Vertical” by default. No need to set it manually if you don’t want to change it.<br />
* Transparency is expensive.<br />
* Use async/await to avoid blocking user interface.<br />
* Do not put ListViews into ScrollViews.<br />
* To stack elements, create a grid and add them to the same cell one after another. It’s cheaper than RelativeLayout.<br />
* Use Margins instead of Paddings.<br />
<br />
=== Layouts ===<br />
* Choose correct Layout, e.g. no need to add a StackLayout if it only has 1 child.<br />
* [https://docs.microsoft.com/en-us/xamarin/xamarin-forms/user-interface/layouts/layout-options LayoutOptions].Fill or .FillAndExpand are best choice in most cases. And they are already default, so no need to set.<br />
* Autosize of rows and columns in grids should used as few as possible.<br />
* RelativeLayout is very expensive. Try to avoid.<br />
* In StackLayout, make sure there is only 1 LayoutOptions Expand.<br />
<br />
=== Labels ===<br />
* Use [https://docs.microsoft.com/en-us/xamarin/xamarin-forms/user-interface/text/label#formatted-text FormattedText] instead of multiple labels.<br />
* Use [https://docs.microsoft.com/en-us/dotnet/api/xamarin.forms.linebreakmode?view=xamarin-forms Linebreakmode] NoWrap (which is already the default).<br />
* Avoid [https://docs.microsoft.com/en-us/dotnet/api/Xamarin.Forms.Label.VerticalTextAlignment?view=xamarin-forms VerticalTextAlignment]. Anyway, if needed, use VerticalTextAligment instead of <br />
VerticalOptions.<br />
* Use the "TextTransform" attribute to convert the value of the "Text" attribute to either uppercase or lowercase.<br />
<syntaxhighlight lang="xml"><br />
<Label<br />
TextTransform="Uppercase"<br />
Text="{Binding Properties.AllItems[DESCR].DisplayValue}" /><br />
</syntaxhighlight ><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
=== Images ===<br />
* Provide images in optimized width and size. Provide multiple resolutions for different usage.<br />
* Set [https://docs.microsoft.com/en-us/dotnet/api/Xamarin.Forms.Image.IsOpaque?view=xamarin-forms IsOpaque] to true if image is opaque.<br />
<br />
=== Layout compression examples ===<br />
<syntaxhighlight lang="xml"><br />
<ContentView ControlTemplate="{DynamicResource ChangedSymbol}" Style="{DynamicResource HeadlessLayout}" /><br />
</syntaxhighlight><br />
The code above removes one wrapping element added automatically by the ContentView and demonstrates a good reason to use layout compression because it can not be avoided otherwise.<br />
<syntaxhighlight lang="xml"><br />
<Grid Margin="2" Style="{DynamicResource HeadlessLayout}"><br />
<Label Margin="5" Text="{Binding Title}" /><br />
</Grid><br />
</syntaxhighlight><br />
This example, on the other hand, demonstrates a bad usage of layout compression because it can be easily achieved by better designs such as using only the Label with a merged margin.<br />
<br />
Sometimes the content inside a compressed layout appears on a wrong z-index level. For eample:<br />
<syntaxhighlight lang="xml"><br />
<BoxView CornerRadius="14" HeightRequest="28" WidthRequest="28" Color="Red" /><br />
<ContentView ControlTemplate="{DynamicResource Badge}" Style="{DynamicResource HeadlessLayout}"><br />
<Label Text="{Binding Title}" /><br />
</ContentView ><br />
</syntaxhighlight><br />
According to the order of the BoxView and the Label, the latter should appear on top of the former (later ones have higher z-index levels). However, this can be disturbed by layout compression, causing the exact opposite.<br />
In this case, you can add a <code>xmlns:android="clr-namespace:Xamarin.Forms.PlatformConfiguration.AndroidSpecific;assembly=Xamarin.Forms.Core"</code> namespace to your Xaml file and manually elevate the Label by specifying <code>android:VisualElement.Elevation="X"</code> on it accordingly (X is the delta of the z-index level you want).<br />
<br />
=== SfListViewExt ===<br />
For performance reasons, we created an extended version of the Syncfusion SfListView control and it should be used for all lists in customizings. You need to add a namespace like <code>xmlns:controls="clr-namespace:UBIK.CPL.Controls;assembly=UBIK.CPL"</code> to your Xaml file and use it like <code><controls:SfListViewExt ... /></code>.<br />
{{Hint|Technically speaking, SfListViewExt informs item view models when their corresponding item views appear on / disappear from the screen. This way, view models can skip a lot of unnecessary work (on the UI) when their views are not visible. '''If SfListView is used instead, the item views will not reflect content changes until the page is reloaded/refreshed.'''}}<br />
<br />
It is possible to configure the ListView, that the ScrollPosition is remembered when navigating away from the page, to do so, the property RembemberScrollPosition needs to be set to true. If unset, the value defaults to false and the scroll positions are not remembered.<br />
<br />
<syntaxhighlight lang="xml"><br />
<controls:SfListViewExt RememberScrollPosition="True"/><br />
</syntaxhighlight><br />
<br />
When using multiple Lists on one page (e.g. in a TabbedView), it is necessary to set the AutomationId property uniquely for each list on the page, to support the remembering of the ScrollPosition.<br />
<br />
=== Delay in UBIKContentView and ContentControl {{Version/MobileSince|5.1}} ===<br />
Sometimes the UI of the app can be quite complex (especially in certain customizings) and it may take a while for it to get displayed. In such cases, the app might feel more responsive if the basic page is first displayed and the content of it gets displayed with a short delay. So starting from version 5.1, we introduced a small delay in the content heavy pages (child page, document page and query page).<br />
<br />
And if necessary, this can be applied to other/smaller parts of the UI as well. For this, we introduced a new property on two existing controls which you could already use to insert UI templates: UBIKContentView and ContentControl. You can specify a delay (in milliseconds) on both controls so that the content of them is loaded after that amount of time. Examples are shown below.<br />
<syntaxhighlight lang="xml"><br />
<controls:UBIKContentView Delay="50" Converter="{StaticResource ChildAreaTemplateConverter}" /><br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<controls:ContentControl Delay="50" ContentTemplate="{Binding [UBIKNavigationBar], Source={x:Static services:TemplateService.Instance}}" /><br />
</syntaxhighlight><br />
<br />
<br />
Please note: The delay won't have any effect if you specify the Content of the UBIKContentView control instead of its Converter, because the Content is immediately laid out by the XAML framework that way. If you don't need a converter to determine the actual template name dynamically, you can still use the TemplateConverter and specify the template name like the following so that the delay applies.<br />
<tabs><br />
<tab name="Delay applies"><br />
<syntaxhighlight lang="xml"><br />
<controls:UBIKContentView Delay="50" Converter="{StaticResource TemplateConverter}" ConverterParameter="UBIKChildArea" /><br />
</syntaxhighlight><br />
</tab><br />
<tab name="Delay doesn't apply"><br />
<syntaxhighlight lang="xml"><br />
<controls:UBIKContentView Delay="50" Content="{Binding [UBIKChildArea], Source={x:Static services:TemplateService.Instance}}" /><br />
</syntaxhighlight><br />
</tab><br />
</tabs><br />
<br />
[[Category:Client|Xamarin XAML]]<br />
[[Category:Mobile|Mobile XAML]]<br />
[[Category:Pages with broken file links|Xamarin XAML]]<br />
[[Category:Styling|Xamarin XAML]]<br />
[[Category:XAML|Xamarin XAML]]<br />
<br />
= Known issues =<br />
<br />
=== Headlesslayout style in custom UBIKThemes causing problems ===<br />
<br />
In our default '''UBIKThemes''', we are currently using this style for a headless layout:<br />
<br />
<syntaxhighlight lang="xml"><br />
Mobile(Xamarin):<br />
<br />
<Style x:Key="HeadlessLayout" TargetType="Layout"><br />
<Setter Property="CompressedLayout.IsHeadless"><br />
<Setter.Value><br />
<OnPlatform<br />
x:TypeArguments="x:Boolean"<br />
Android="True"<br />
WinPhone="False"<br />
iOS="False" /><br />
</Setter.Value><br />
</Setter><br />
</Style><br />
</syntaxhighlight><br />
<br />
<br/><br />
This style is used for better UI performance on Android.<br />
Using this style in a '''custom UBIKThemes''' could cause an exception & an app crash, or some objects to disappear.<br />
The best case would be to '''not''' include it in the custom themes file, as it's unnecessary if you don't want to make any changes here.<br />
<br />
'''This issue is only known on Android tablet devices.'''<br />
<br><br />
<br><br />
<br />
[[Category:Client|Xamarin XAML]]<br />
[[Category:Mobile|Mobile XAML]]<br />
[[Category:Pages with broken file links|Xamarin XAML]]<br />
[[Category:Styling|Xamarin XAML]]<br />
[[Category:XAML|Xamarin XAML]]<br />
<br />
=== DataTrigger Issues ===<br />
==== Conflicting Triggers ====<br />
DataTriggers in Mobile function better than the equivalent DataTriggerBehavior in UWP as they automatically handle the opposite case when a Boolean attribute value is set. This means that if a boolean DataTrigger is set, such as IsVisible=True, the False visibility will automatically be set if the Binding/Value condition is not met.<br />
<br />
However, this means that stacking multiple DataTriggers on the same attribute can lead to unexpected results. For this reason, it is recommended to use as few DataTriggers as possible. <br />
* Avoid setting the same attribute more than once; do not set the same value as a default attribute and in the DataTrigger (ControlTemplate in the below example).<br />
* Ideally, use only DataTriggers without a default ControlTemplate. This ensures that content is created only after the trigger evaluation is complete. If a default ControlTemplate is set, it is always loaded immediately, even if another template is applied right after.<br />
* It is acceptable, but not recommended, to combine a single DataTrigger with an opposite default value, but only if the default value is different from all values set in triggers.<br />
<br />
<tabs><br />
<tab name="Don't Do"><br />
<source lang = "xml"><br />
<ContentView x:Name="editorValueContainer" ControlTemplate="{StaticResource SelListTemplate}"><br />
<ContentView.Triggers><br />
<DataTrigger Binding="{Binding Source={x:Reference editorValueContainer}, Path=BindingContext.PropertyViewModel.ShowComboBox}" TargetType="ContentView" Value="true"><br />
<Setter Property="ControlTemplate" Value="{StaticResource SelListTemplate}" /><br />
</DataTrigger><br />
<DataTrigger Binding="{Binding Source={x:Reference editorValueContainer}, Path=BindingContext.PropertyViewModel.ShowComboBox}" TargetType="ContentView" Value="false"><br />
<Setter Property="ControlTemplate" Value="{StaticResource TextTemplate}" /><br />
</DataTrigger><br />
</ContentView.Triggers><br />
</ContentView><br />
</source><br />
<br><br />
</tab><br />
<br />
<tab name="Instead Do"><br />
<source lang = "xml"><br />
<ContentView x:Name="editorValueContainer"><br />
<ContentView.Triggers><br />
<DataTrigger Binding="{Binding Source={x:Reference editorValueContainer}, Path=BindingContext.PropertyViewModel.ShowComboBox}" TargetType="ContentView" Value="true"><br />
<Setter Property="ControlTemplate" Value="{StaticResource SelListTemplate}" /><br />
</DataTrigger><br />
<DataTrigger Binding="{Binding Source={x:Reference editorValueContainer}, Path=BindingContext.PropertyViewModel.ShowComboBox}" TargetType="ContentView" Value="false"><br />
<Setter Property="ControlTemplate" Value="{StaticResource TextTemplate}" /><br />
</DataTrigger><br />
</ContentView.Triggers><br />
</ContentView><br />
</source><br />
</tab><br />
<br />
<tab name="Acceptable, but not recommended"><br />
<source lang = "xml"><br />
<ContentView x:Name="editorValueContainer" ControlTemplate="{StaticResource SelListTemplate}"><br />
<ContentView.Triggers><br />
<DataTrigger Binding="{Binding Source={x:Reference editorValueContainer}, Path=BindingContext.PropertyViewModel.ShowComboBox}" TargetType="ContentView" Value="false"><br />
<Setter Property="ControlTemplate" Value="{StaticResource TextTemplate}" /><br />
</DataTrigger><br />
</ContentView.Triggers><br />
</ContentView><br />
</source><br />
</tab><br />
</tabs><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
==== DataTrigger to set Footer Properties in a ListView ====<br />
<br />
When using a DataTrigger to set the properties of a footer for a ListView, the sequence of the properties inside the DataTrigger might matter in some cases.<br />
It seems to occur since Version 4.4 due to a Syncfusion update and could lead to the page not being rendered properly and appearing empty.<br />
<br />
If you encounter such an issue, please workaround by adding the IsStickyFooter Property Setter on top inside the DataTrigger.<br />
Also, new customizings should consider this workaround as a preventive action.<br />
<br />
<syntaxhighlight lang="xml"><br />
<!-- THIS DOESN'T WORK IN CERTAIN CASES --><br />
<controls:SfListViewExt ...><br />
<controls:SfListViewExt.Triggers><br />
<DataTrigger TargetType="controls:SfListViewExt" Binding="{Binding Title}" Value="Administration"><br />
<Setter Property="FooterTemplate" Value="{DynamicResource AddLoginFooter}" /><br />
<Setter Property="FooterSize" Value="64" /><br />
<Setter Property="IsStickyFooter" Value="True" /><br />
</DataTrigger><br />
</controls:SfListViewExt.Triggers><br />
</controls:SfListViewExt><br />
</syntaxhighlight><br />
<br />
<br/><br />
<syntaxhighlight lang="xml"><br />
<!-- THIS WORKS --><br />
<controls:SfListViewExt ...><br />
<controls:SfListViewExt.Triggers><br />
<DataTrigger TargetType="controls:SfListViewExt" Binding="{Binding Title}" Value="Administration"><br />
<Setter Property="IsStickyFooter" Value="True" /><br />
<Setter Property="FooterTemplate" Value="{DynamicResource AddLoginFooter}" /><br />
<Setter Property="FooterSize" Value="64" /><br />
</DataTrigger><br />
</controls:SfListViewExt.Triggers><br />
</controls:SfListViewExt><br />
</syntaxhighlight><br />
<br><br />
<br><br />
=== Incorrect glyphs may be shown on buttons ===<br />
<br />
When using glyphs on buttons in Mobile, sometimes a different glyph than the expected one will show up when viewing the app on Android.<br />
They only seem to appear incorrectly when used as the Text property of the button (with FontFamily set to UBIKSymbols, such as the UBIKIconButton style.)<br />
<br />
If you encounter this issue please workaround by supplying the icon through the FontImageSource property of the button.<br />
<br />
<syntaxhighlight lang="xml"><br />
<Button Command="{Binding BulkOperation.InvokeOnItemsCommand}"><br />
<Button.ImageSource><br />
<FontImageSource <br />
FontFamily="{DynamicResource UBIKSymbols}"<br />
Glyph="{x:Static resources:UBIKIcons.MobileDelete}"<br />
Color="{DynamicResource UBIKDarkThemeColor}"<br />
Size="22"/><br />
</Button.ImageSource><br />
<Button.CommandParameter><br />
<classes:KeyValueList><br />
<classes:KeyValueParameter Key="Command" Value="DiscardContentCommand" /><br />
</classes:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</syntaxhighlight><br />
<br><br />
<br><br />
=== Buttons and gesture recognizers ===<br />
In Mobile XAML, you can use gesture recognizers on many UI elements such as a Grid to enable the latter to interact with user inputs.<br />
<br />
However, we've already made quite a lot of experience that gesture recognizers do not always work on Android and iOS when used on a Button control.<br />
For example, the following Button won't properly invoke the command on said platforms.<br />
<br />
<syntaxhighlight lang="xml"><br />
<!-- THIS DOESN'T WORK!!! --><br />
<Button ...><br />
<Button.GestureRecognizers><br />
<TapGestureRecognizer Command="{Binding ReplicateAsDataCommand}" /><br />
</Button.GestureRecognizers><br />
</Button><br />
</syntaxhighlight><br />
<br />
<br/><br />
Therefore, you should always seek alternatives for Buttons.<br />
'''If only one command is needed''', use the standard Command property on the Button, e.g.<br />
<br />
<syntaxhighlight lang="xml"><br />
<!-- THIS WORKS --><br />
<Button Command="{Binding ReplicateAsDataCommand}" .../><br />
</syntaxhighlight><br />
<br />
<br/><br />
Or if multiple commands are needed, use Behaviors '''instead''', e.g.<br />
<br />
<syntaxhighlight lang="xml"><br />
<!-- THIS ALSO WORKS --><br />
<Button xmlns:behaviors="clr-namespace:UBIK.CPL.Behaviors;assembly=UBIK.CPL" ...><br />
<Button.Behaviors><br />
<behaviors:EventToCommandBehavior Command="{Binding ReplicateAsDataCommand}" EventName="Clicked" /><br />
<behaviors:EventToCommandBehavior Command="{Binding NavigateBackCommand}" EventName="Clicked" /><br />
</Button.Behaviors><br />
</Button><br />
</syntaxhighlight><br />
<br><br />
<br><br />
=== No dynamic reloading of Document Viewer ===<br />
[[File:PDFViewerFixWiki.JPG]]<br />
<br />
In a customizing that combines a single-selection list of documents with some kind of viewer (especially UBIKDocumentContentArea), it is generally the case that switching the document causes the document viewer to then appear blank. The technical reason is that the PDFViewer used in the UBIKDocumentContentArea is not reloaded once the document content is reloaded. <br />
<br />
An easy fix is to apply a DataTrigger that unloads the ContentView when the document content is null, as the ContentView is forced to rerender itself when the trigger condition is no longer met.<br />
<br />
<syntaxhighlight lang="xml"><br />
<!-- Document Viewer --><br />
<controls:UBIKContentView <br />
x:Name="DoucmentViewer" <br />
BindingContext="{Binding SelectedItem, Source={x:Reference DocumentList}}"<br />
Content="{Binding [UBIKDocumentContentArea], Source={x:Static services:TemplateService.Instance}}"><br />
<br />
<controls:UBIKContentView.Triggers><br />
<DataTrigger TargetType="controls:UBIKContentView" Binding="{Binding SelectedItem.DocumentViewModel.DocumentContent, Source={x:Reference DocumentList}, Converter={StaticResource NullToBool}}" Value="True"><br />
<Setter Property="Content" Value="{x:Null}" /><br />
</DataTrigger><br />
</controls:UBIKContentView.Triggers><br />
</controls:UBIKContentView><br />
</syntaxhighlight><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
=== Issues with SfPullToRefresh in Mobile client {{Version/MobileSince|5.0}} ===<br />
Due to a third-party issue, problems may occur on Mobile Android when using the SfPullToRefresh control in combination with the SfListViewExt. This can result in e.g. navigation or task interaction sometimes requiring multiple clicks.<br />
In general, and due to more issues, it's not recommended to use the SfPullToRefresh control.<br />
In our Mobile standard client, the PullToRefresh control has been replaced by a Refresh button in the Context Menu.<br />
If you still decide to use SfPullToRefresh, there are a few points to consider:<br />
<br />
==== Avoid multiple SfPullToRefresh controls ====<br />
To prevent an issue that causes the app to freeze, avoid placing more than one SfPullToRefresh controls as siblings in a xaml hierarchy. If switching between contents in a SfPullToRefresh control is necessary use separate DataTemplates for the contents and use e.g. a DataTrigger to set one of them as the ControlTemplate of a ContentControl inside the SfPullToRefresh control. For an example, refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui#Avoid_multiple_SfPullToRefresh_controls|this link]].<br />
<br />
==== Avoid using SyncFusion ListViews directly in SfPullToRefresh controls ====<br />
To prevent an issue on some Android devices that can cause some items in a SfListViewExt to be rendered incorrectly or not at all after triggering a PullToRefresh, avoid placing a SfListViewExt directly in a SfPullToRefresh control. Instead, wrap the ListView in a DataTemplate and use it in a ContentControl as a child of the SfPullToRefresh control. For an example, refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui#Avoid_using_SyncFusion_ListViews_directly_in_SfPullToRefresh_controls|this link]].<br />
<br />
[[Category:Client|Xamarin XAML]]<br />
[[Category:Mobile|Mobile XAML]]<br />
[[Category:Pages with broken file links|Xamarin XAML]]<br />
[[Category:Styling|Xamarin XAML]]<br />
[[Category:XAML|Xamarin XAML]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.0_(Mobile)&diff=29154Version 5.0 (Mobile)2025-11-14T13:49:47Z<p>LGE: </p>
<hr />
<div>{{Attention|Existing pre 5.0 XAMLs are not compatible with UBIK Mobile client 5.0. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.}}<br />
<br />
{{Attention|UBIK 5 clients can only connect to {{UBIK}} Servers of [[Version 3.6(Server)|version 3.6]] and higher!}}<br />
<br />
{{Attention|The minimum supported OS versions are:<br />
* Android 9;<br />
* iOS 12.}}<br />
<br />
== Availability ==<br />
{{key press|Android: Store}}{{key press|iOS: Store}}: Publicly available in Google Play Store / Apple App Store.<br />
<br />
{{key press|Android: Store Beta}}: Publicly available in Google Play Store as beta versions. You can opt in or out of the beta at any time in the store.<br />
<br />
{{key press|Android: Store Preview}}: Available through Google Play Store's [https://play.google.com/store/apps/details?id=com.augmensys.ubik.go invitation link].<br />
<br />
{{key press|iOS: Store Beta}}: Available through Apple App Store's [https://testflight.apple.com/join/Kmb1HG9E invitation link].<br />
<br />
{{key press|iOS: Store Preview}}: Available through Apple App Store's [https://testflight.apple.com/join/yHRnbYbt invitation link].<br />
<br />
{{key press|Windows: Store Preview}}: The mobile Windows client is not an official product and is only distributed as test versions upon request and/or in our [https://release.augmensys.com/download/modules/client/mobile/ release portal].<br />
<br/><br />
<br />
<br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with a ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
<br />
=== 5.0.223 on 2025-11-?? {{key press|iOS: Store}} ===<br />
* (iOS) Fixed an issue where [[EvalExpression]] doesn't produce expected results for expressions containing "Condition ? A : B".<br />
<br />
<br />
=== 5.0.221 on 2025-11-05 {{key press|Android: Store}} ===<br />
* (Android) Fixed an issue where creating new objects when there are already a lot of existing ones leads to an app freeze or even crash.<br />
<br />
<br />
=== 5.0.218 on 2025-10-10 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Added logging of the authentication headers in UBIKWebserviceDebug.log for better diagnostics.<br />
* A third party issue was fixed where some text Annotations in the ImageEditor weren't visible on iOS.<br />
* A third party issue was fixed where stream bytes increased exponentially when saving Annotations in the ImageEditor.<br />
<br />
<br />
=== 5.0.212 on 2025-10-03 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Fixed an issue where task direct editing doesn't work the first time.<br />
* Updated the notification message about branch download to avoid misunderstanding. When a branch download is in progress, you can work with the offline data which is already available at the time of the download, but any communication with the content server will be scheduled after the branch download is finished.<br />
<br />
<br />
=== 5.0.209 on 2025-09-27 {{key press|Android: Store}} 5.0.207 on 2025-09-25 {{key press|iOS: Store}} ===<br />
* UBIK GO is the cutting-edge evolution of Augmensys' trusted mobile client — rebuilt from the ground up with a modern architecture that unlocks unprecedented flexibility.<br />
* Improved the branch download performance especially when there are duplicate objects in multiple branches.<br />
* Updated some translations.<br />
* Updated the default Demo profile.<br />
* Fixed an issue that triggered a license warning even on a failed login.<br />
* Fixed an issue where the wizard is shown again when you navigate to a new but saved object offline.<br />
* Fixed an issue where duplicate notifications are shown when you scan an NFC tag for a supervisor task and no fitting supervisor is found.<br />
<br />
<br />
== Known issues ==<br />
* When changing the device orientation during attaching a photo on iOS, the app gets stuck. This is an issue Microsoft confirmed in .NET9 and will fix in .NET10.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Currently, the Samsung keyboard doesn't show {{key press|,}} at all, regardless of the current language/locale setting of the device. Please use a different virtual keyboard (e.g. Gboard from Google) instead if {{key press|.}} is unacceptable.<br />
* The periodic execution of background pushes is not guaranteed on iOS.<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* It is currently not possible to select which camera to use for AR views (e.g. scan page) on Windows.<br />
* SfPullToRefresh was removed due to [[Mobile_XAML#Issues_with_SfPullToRefresh_in_Mobile_client|existing issues]], and replaced with a Refresh option in the Context menu.<br />
<br/><br />
<br />
<br />
<br />
<br />
<br />
= ⚠️ XAML Notes =<br />
Due to the change of the underlying XAML technology, the existing XAMLs for the old mobile clients (pre 5.0) are no longer compatible. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.<br />
<br />
<headertabs /><br />
<br />
[[Category:Client|Version 5.0 (Mobile)]]<br />
[[Category:Mobile|Version 5.0 (Mobile)]]<br />
[[Category:Version 5.0|Version 5.0 (Mobile)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Help:Editing&diff=29136Help:Editing2025-11-12T08:42:19Z<p>LGE: </p>
<hr />
<div>=Introduction=<br />
<br />
== Introduction ==<br />
*For the basics about MediaWiki please read ''[http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]''<br />
*In the beginning, the [http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet Cheatsheat] is very useful<br />
<br />
== Most frequently asked ==<br />
* [[Help:List_of_Templates|Available templates]]<br />
* [[Help:Editing#Lists|Editing lists]]<br />
* [[Help:Editing#tab=Categorizing|Categories]]<br />
<br />
== Acceptance criteria ==<br />
Any article should meet the following general acceptance criteria<br />
* Is the article structured logically and coherently?<br />
* Can the reader be directed to any other article (eg See also...)? <br />
* Is the article categorized into at least one category?<br />
* Is the version information added wherever necessary?<br />
* If the article links to other articles, check whether or not they exist?<br />
* Check the article for integrity and correctness in regards of technical descriptions. Test the described procedure and verify possible dependencies on versions.<br />
* Check the article for linguistic correctness in regards to grammar and style.<br />
* Images are prepared as described [[Help:Editing#Images|here]]<br />
* Templates are used if appropriate, find a list of templates [[Help:List_of_Templates|here]]<br />
* Meet all (additional) requirements defined in this guideline<br />
<br />
=Formatting=<br />
== Reference articles ==<br />
Please have a look at the following reference articles<br />
* [[Entity_Data_Model]], [[Class Browser]]<br />
* [[:Category:Metaclasses]]: [[METACLASSSCOPE]], [[QUERYSCOPE]]<br />
* [[:Category:Classifications]]: [[SYSCLS_TASK]], [[SYSCLS_THUMBNAILEDFILE]] (with properties)<br />
* How-To: [[HowTo:Create a new MetaClass]]<br />
<br />
{{Hint|It is common to use the expression: ''Save the changes with {{key press|Ctrl|S}} or the save command''}}<br />
{{Hint|Do also use screenshots in How-To‘s, so that the reader is guided visually.}}<br />
<br />
== Texts ==<br />
<br />
===Descriptive text===<br />
Descriptive text should be left aligned and in the standard font, without any additional formatting. <br />
<br />
===Emphasizing===<br />
If you want to emphasize something, use '''bold''' style.<br />
<br />
===Colors===<br />
Colors should be used very sparingly and only if they really contribute to the better understanding of a text.<br />
<br />
===UI===<br />
If you want to refer to the exact name of something in the UI of {{UBIK}}, use ''italic'' style.<br />
<br />
===Headlines===<br />
Use the general headline formatting, type in regular case.<br />
<br />
== Version history ==<br />
Information related to previous versions should be documented using tool tips. An example of an image tool tip can be seen on the page for the POI dialog:<br /><br />
* [[POI_View#Billboard|Billboard]]<br />
* [[POI_View#LLA_only_mode_button|LLA only mode button]]<br />
<br />
Technically it is also possible to place an {{#tip-text: inline tool tip | inline tool tip text}}.<br />
<br />
==Infoboxes==<br />
Infoboxes should be used as an introduction for articles that have a useful common denominator. They will appear at the top right ans summarize the article in Keywords and/or pictures. Currently there is a template for a [[Template:ControlInfoBox|Control Infobox]] implemented that should be used for all articles about {{UBIK}} controls.<br />
<br />
==Lists==<br />
There are two types of lists that can be used:<br />
<br />
===Bullets===<br />
Use a bullets if you want to list several (short) statements of the same area, which are not chronologically connected. Do not use punctuation for bulleted items.<br />
* Statement<br />
* Another Statement<br />
<br />
In addition, if you want to list certain tasks that do not follow a particular order you can use right arrows:<br />
<br />
&rarr; Task a<br />
<br />
&rarr; Task b<br />
<br />
===Numbered list===<br />
Use numbered list if the items are chronologically connected and have to be executed one after the other. Do not use punctuation for bulleted items.<br />
# Do this first<br />
# then do this<br />
# end finally, do this<br />
<br />
If you want to add special formatted content, like ''<nowiki><syntaxhighlight></nowiki>'' tags within the numbered items, use one of the following workarounds to preserve continuous numbering:<br />
<pre><br />
# Item 1<br />
# Item 2 <!--<br />
--><syntaxhighlight lang="xml"><br />
<Node1>Value1</Node1><br />
</syntaxhighlight><br />
# Item 3<br />
# Item 4 <br /><syntaxhighlight lang="xml"><br />
<Node1>Value1</Node1><br />
</syntaxhighlight><br />
# Item 5<br />
</pre><br />
<br />
Using a HTML comment <nowiki><!-- --></nowiki> '''OR''' <nowiki><br/></nowiki> for the line break prevents that the numbered list is broken and numbering starts over:<br />
# Item 1<br />
# Item 2 <!--<br />
--><syntaxhighlight lang="xml"><br />
<Node1>Value1</Node1><br />
</syntaxhighlight><br />
# Item 3<br />
# Item 4 <br /><syntaxhighlight lang="xml"><br />
<Node1>Value1</Node1><br />
</syntaxhighlight><br />
# Item 5<br />
<br />
Obeying this syntax it is also possible to use the <nowiki>{{Hint}}</nowiki> and <nowiki>{{Attention}}</nowiki> templates:<br />
<pre><br />
# Item 1<br />
# Item 2 <!--<br />
-->{{Hint|asdfasdf}}<br />
# Item 3<br />
# Item 4 <!--<br />
-->{{Attention|asdfasdf}}<br />
# Item 5<br />
</pre><br />
<br />
# Item 1<br />
# Item 2<!--<br />
-->{{Hint|asdfasdf}}<br />
# Item 3<br />
# Item 4 <!--<br />
-->{{Attention|asdfasdf}}<br />
# Item 5<br />
<br />
==Tables==<br />
<br />
Use the WikiTable like in the following example:<br />
<br />
<code>{| class="wikitable sortable" | width = "50%"<br />
<br />
|-<br />
! Columns 1!! Column 2<br />
<br />
|-<br />
| Row 1.1|| Row 1.2<br />
<br />
|-<br />
| Row 2.1|| Row 2.2<br />
<br />
|-<br />
| Row 3.1|| Row 3.2<br />
<br />
|-<br />
|}</code><br />
<br />
will result in<br />
<br />
{| class="wikitable sortable" | width = "50%"<br />
|-<br />
! Columns 1!! Column 2<br />
|-<br />
| Row 1.1|| Row 1.2<br />
|-<br />
| Row 2.1|| Row 2.2<br />
|-<br />
| Row 3.1|| Row 3.2<br />
|-<br />
|}<br />
<br />
For larger data, the sortable table might be more useful:<br />
<br />
<code>{| class="wikitable sortable" | width = "50%"<br />
<br />
|-<br />
! Columns 1!! Column 2<br />
<br />
|-<br />
| Row 1.1|| Row 1.2<br />
<br />
|-<br />
| Row 2.1|| Row 2.2<br />
<br />
|-<br />
| Row 3.1|| Row 3.2<br />
<br />
|-<br />
|}</code><br />
<br />
will result in<br />
<br />
{| class="wikitable sortable" | width = "50%"<br />
|-<br />
! Columns 1!! Column 2<br />
|-<br />
| Row 1.1|| Row 1.2<br />
|-<br />
| Row 2.1|| Row 2.2<br />
|-<br />
| Row 3.1|| Row 3.2<br />
|-<br />
|}<br />
<br />
==Code==<br />
Use either a leading blank to format text as source code, or the <code><code>-Tag</code> for regular code highlighting.<br />
<br />
For highlighting a syntax of a specific programming language, use the syntaxhighlight-Tag (values for '''lang''' are for example: csharp, xml, ...).<br />
<br />
<pre><nowiki><br />
<syntaxhighlight lang="csharp"><br />
// Hello World in Microsoft C#.<br />
<br />
using System;<br />
<br />
class HelloWorld<br />
{<br />
public static int Main(String[] args)<br />
{<br />
Console.WriteLine("Hello, World!");<br />
return 0;<br />
}<br />
}<br />
</syntaxhighlight><br />
</nowiki></pre><br />
<br />
which will result in<br />
<br />
<syntaxhighlight lang="csharp"><br />
// Hello World in Microsoft C#.<br />
<br />
using System;<br />
<br />
class HelloWorld<br />
{<br />
public static int Main(String[] args)<br />
{<br />
Console.WriteLine("Hello, World!");<br />
return 0;<br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
=Images=<br />
==Wiki specific templates==<br />
Check the [[Help:List of Images|list of images]] for this Wiki.<br />
<br />
==Naming conventions==<br />
To obtain some kind of categorization the name of new images must start with one a prefix. Choose the most appropriate one from the below list:<br />
{| class="wikitable sortable" | width = "50%"<br />
|-<br />
! Prefix !! Description !! Examples<br />
|-<br />
| UI_|| screenshots of {{UBIK}} Studio, {{UBIK}} Client, Windows (IIS, SQL, Excel, ...) || [[Help:List_of_Images|UBIK UI]]<br />
|-<br />
| IL_|| Illustrations (diagrams, fractions of slides, ...) || -<br />
|-<br />
| SY_|| {{UBIK}} symbols (e.g. images for MetaClass, BASECLASS, relations, ...) || -<br />
|-<br />
| IC_|| small graphics (icons, arrows, ...) || [[Help:List_of_Images#Icons|UBIK Icons]]<br />
|-<br />
|}<br />
<br />
==Formats==<br />
<br />
=== Supporting images ===<br />
[[File:Example.jpg|220px|thumb|border|alt=Example Supporting images|Example Supporting images]]<br />
Supporting images must be formatted as <code>thumb</code> to make them appear on the right side, with the following dimensions:<br />
* Images in portrait format with 170 pixels width<br />
* Images in landscape format with 220 pixels width<br />
<br />
Example: <code><nowiki>[[File:Example.jpg|220px|thumb|border|alt=Example|Example]]</nowiki></code><br />
{{Clear}}<br />
<br />
=== Descriptive images ===<br />
Images as part of the descriptive article text can be placed inline, like for emphasizing a certain manual visually, with the following dimensions:<br />
* Images in landscape should not exceed 700 pixels width<br />
* Images in portrait should not exceed 700 pixels height<br />
<br />
Example: <code><nowiki>[[File:Example.jpg|700px|border|alt=Example|Example]]</nowiki></code><br />
<br />
=== Borders ===<br />
Use the '''border''' parameter in the tag for the embedded image, for example <code><nowiki>[[File:Example.jpg|border]]</nowiki></code> results in<br/>[[File:Example.jpg|border]]<br />
<br />
=== Image captions ===<br />
Use image captions if appropriate to describe the image and to create a relation to the text.<br />
<br />
== Gallery style ==<br />
If there is the need to place a series of images within the text use the gallery tag with an appropriate width and height<br />
<br />
<code><nowiki><gallery widths="200" heights="200"></nowiki></code><br/><br />
<code><nowiki>File:Example.jpg|1 - Example</nowiki></code><br/><br />
<code><nowiki>File:Example.jpg|2 - Example</nowiki></code><br/><br />
<code><nowiki>File:Example.jpg|3 - Example</nowiki></code><br/><br />
<code><nowiki></gallery></nowiki></code><br />
<br />
which results in<br />
<br />
<gallery widths="200" heights="200"><br />
File:Example.jpg|1 - Example<br />
File:Example.jpg|2 - Example<br />
File:Example.jpg|3 - Example<br />
</gallery><br />
<br />
== <nowiki>{{Clear}}</nowiki> Template ==<br />
If one or more images should be located next to the descriptive text but which is organized in several sections, use the <nowiki>{{Clear}}</nowiki> template. Have a look at the below section example:<br />
<br />
{{Attention|Use this command very rarely - try to place the images in a gallery style!}}<br />
<br />
=== Section 1 starts here ===<br />
[[File:Example.jpg|220px|thumb|border|alt=Example|Example]]<br />
Some text 1<br />
<br />
Watch that section 2 starts after some spacing.<br />
{{Clear}}<br />
<br />
=== Section 2 starts here ===<br />
[[File:Example.jpg|220px|thumb|border|alt=Example|Example]]<br />
Some text 2<br />
{{Clear}}<br />
<br />
=Categorizing=<br />
Each article must be assigned to '''at least one category''' and a maximum of 3 categories. <br />
* If you feel an article fits into more than 3 categories, consider splitting it into multiple articles<br />
* If you feel an article fits into no category, consider merging it into another article OR use at least the category UBIK<br />
* Do not create new categories every time - check if an existing fits to your needs.<br />
<br />
== Sub Categories ==<br />
A new sub category can be created by pasting a category within the source of another category page.<br />
<br />
== Sort Key ==<br />
Use sort keys for articles and subcategories, e.g. objects of category [[:Category:Classifications]], so that the article is sorted by a propery sort key instead of S always.<br />
Example: <code><nowiki>[[Category:System Classifications|T]]</nowiki></code><br />
<br />
== Category Tree ==<br />
The articles and categories are evaluated by the [http://www.mediawiki.org/wiki/Extension:CategoryTree Category Tree extension] and used on the [[SiteMap]] page.<br />
* [http://www.mediawiki.org/wiki/Extension:CategoryTree Extension:Category Tree]<br />
* [http://ddowiki.com/page/Help:Extension:CategoryTree Help:Extension:CategoryTree]<br />
<br />
=Namespaces=<br />
Certain types of articles should be assigned to a namespace, which is simply done by adding a namespace-prefix in front of the article name like ''<nowiki>HowTo:Assign_a_Namespace</nowiki>''<br />
<br />
Find a list of namespaces and how its realted to a main category below.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Main category !! Namespace !! Example<br />
|-<br />
| How-To || HowTo || HowTo:Assign_a_Namespace<br />
|-<br />
| FAQ || FAQ || FAQ:UBIK_Studio<br />
|-<br />
| Activity || Activity || Activity:DebugMessage<br />
|}<br />
<br />
=Linking=<br />
Internal linking is a good thing, but it must not be used too extensively. Link to the articles that make sense in context of the manual, especially when they are about fundamental principles of {{UBIK}}, like for example the [[MetaClass]] article. Link to each keyword only once in an article, at first appearance of the keyword.<br />
<br />
External links only make sense if the target article supports in comprehending an article, for example a certain standard or norm that is used by or in {{UBIK}}, i.e. [http://en.wikipedia.org/wiki/ISO_15926 ISO15926].<br />
<br />
=== Linking to category pages ===<br />
Unlike links to other pages, <code><nowiki>[[Category:CategoryName]]</nowiki></code> will not work as a link. For that, you need to add ":" at the beginning like <code><nowiki>[[:Category:CategoryName]]</nowiki></code>.<br />
<br />
=== Download links ===<br />
* Use the <nowiki>{{FileLink|1|2}}</nowiki> template to create download links within wiki articles, like {{FileLink|Start_Screen_Configuration.zip|Start_Screen_Configuration.zip}}<br />
* All downloads should be prepared as .zip files.<br />
<br />
==== Naming ====<br />
* <version>: Version number as stated on Release portal<br />
* <date>: Creation date of file / download resources<br />
* <description>: Short description of .zip package content<br />
{| class="wikitable" | width = "50%"<br />
|- <br />
! Type !! Comment !! File name<br />
|- <br />
| .xaml || XAML files for the WinX client || xaml_<version>_<date>_<description>.zip<br />
|- <br />
| .uwf || UBIK workflow files || uwf_<version>_<date>_<description>.zip<br />
|- <br />
| .xyz / ABC || Arbitrary files / folders || <date>_<description>.zip<br />
|}<br />
<br />
= Client articles =<br />
There are four types of pages related to client documentation,<br />
* Features (technical documentation, etc.)<br />
* How-Tos<br />
* FAQ<br />
* Version pages<br />
<br />
Documentation related to the different platforms (Android, Windows and Web) should be placed as within those pages as described below.<br />
<br />
== Page types ==<br />
<br />
=== Features ===<br />
Features and behavior of the clients sometimes have a rather big overlap, especially how it is documented. On the other side, due to different platforms we have varying UI elements in both, form and handling.<br />
Nevertheless, documentation should be kept to a minimum and hence, the features described in the most generic way possible. The parts which differ in between the platforms (UI, handling, etc.) should be described in different sections and by using according screenshots. Add a suffix to the section's name or figure's title, which is<br />
<br />
* (Android) ... for Android client<br />
* (Windows) ... for Windows client<br />
* (Web) ... for the Web client<br />
<br />
''&rarr; See [[Map View]] or [[Live Values]] for examples.''<br />
<br />
=== How-Tos ===<br />
Platform / component specific documentation is to be placed onto distinctive tabs. Hence, the information is placed onto the following tabs <br />
* '''Studio''': describing actions to be performed with UBIK Studio<br />
* '''Android''': describing actions performed in the Android client<br />
* '''Windows''': describing actions performed in the Windows client<br />
* '''Web''': describing actions performed in the Web client<br />
<br />
&rarr; ''See [[HowTo:Install_UBIK_Client_Certificate]] for an example''<br />
<br />
=== FAQ ===<br />
An additional tab '''Windows''' is added to the FAQ page for the clients. FAQs related to the Windows client is to be placed here.<br />
<br />
&rarr; ''See [[FAQ:Client]] for an example''<br />
<br />
=== Version pages ===<br />
Separate version pages are created for the Windows client, rather similar to the version pages for Android or the Server.<br />
<br />
== Categories ==<br />
Assign the platform related category ''Android'', ''Windows'', ''Web'' to pages, respectively.<br />
<br />
=Special articles=<br />
== HowTos ==<br />
Create a [[:Category:How-To|How-To]] to describe '''HOW''' to solve a certain issue. The given instructions should be clear and easy to follow, therefore use screenshots (server and client side) to document your explanations. Use a descriptive name for the How-To article, such that already describes the content.<br />
{{Hint|Consider the KISS principle - '''K'''eep '''I'''t '''S'''hort and '''S'''imple}}<br />
{{Hint|Place images within the items of the numbered list (its width should remain 220 pixels width in landscape or 170 pixels height in portrait orientation).}}<br />
<br />
== FAQ ==<br />
Create or edit a [[:Category:FAQ]] page to provide answers to questions or issues the reader would ask using '''WHY''', '''WHO''', '''WHEN''', etc. Provide a short answer, which probably also includes a few instructions.<br />
<br />
If the issue requires more detailed explanations refer to an existing wiki article or create a new one.<br />
<br />
=Templates=<br />
<br />
==Wiki specific templates==<br />
{{Hint|Check the [[Help:List_of_Templates|list of templates]] for a comprehensive list of available templates in this Wiki.}}<br />
<br />
== Download links ==<br />
Use the <nowiki>{{FileLink|1|2}}</nowiki> template to create download links within wiki articles, like {{FileLink|Start_Screen_Configuration.zip|Start_Screen_Configuration.zip}}.<br />
<br />
==Attention==<br />
Use the [[Template:Attention|Attention]] template to draw attention to a certain sentence:<br />
<pre><nowiki>{{Attention|Please don't miss this sentence!}}</nowiki></pre><br />
<br />
will result in <br />
<br />
{{Attention|Please don't miss this sentence!}}<br />
<br />
==Hints==<br />
Use the [[Template:Hint|Hint]] template to outline useful tips and hints:<br />
<pre><nowiki>{{Hint|You should read this, it will simplify your work!}}</nowiki></pre><br />
<br />
will result in<br />
<br />
{{Hint|You should read this, it will simplify your work!}}<br />
<br />
=== HintEvents ===<br />
Use [[Template:HintEvents|HintEvents]] to outline that the type has specific events.<br />
<pre><nowiki>{{HintEvents}}</nowiki></pre><br />
<br />
will result in<br />
<br />
{{HintEvents}}<br />
<br />
=== HintMethods ===<br />
Use [[Template:HintMethods|HintMethods]] to outline that the type has specific events.<br />
<pre><nowiki>{{HintMethods}}</nowiki></pre><br />
<br />
will result in<br />
<br />
{{HintMethods}}<br />
<br />
== Infoboxes ==<br />
See also the list of available [[Help:List_of_Templates#Infoboxes|Infoboxes templates]].<br />
<br />
==Other useful templates==<br />
<br />
* The [[Template:key press|KeyPress]] template allows you to display keyboard commands, so <code><nowiki>{{key press|Ctrl|W}}</nowiki></code> will result in {{key press|Ctrl|W}}<br />
* Use the [[Template:UMM|UBIK MetaModel]] template to refer to the data model:<br />
{{UMM|A descriptive model, where objects provide information about the aspects of the data, is also called “Metamodel”.}}<br />
<br />
== Template list ==<br />
A list of available templates can be found here [[Help:List_of_Templates]]<br />
<br />
= Wizards =<br />
The '''[[Help:Editing_Wizard|Editing Wizard]]''' offers a convenient way to create articles having a pre-defined structure and purpose.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Category !! Preload template !! Example<br />
|-<br />
| How-To || Template:HowTo/Preload || [[Template:HowTo/Preload]]<br />
|-<br />
| Activity || Template:Activity/Preload || [[Template:Activity/Preload]]<br />
|}<br />
<br />
<headertabs /><br />
<br />
[[Category:Help]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.0_(Mobile)&diff=29132Version 5.0 (Mobile)2025-11-04T10:59:52Z<p>LGE: </p>
<hr />
<div>{{Attention|Existing pre 5.0 XAMLs are not compatible with UBIK Mobile client 5.0. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.}}<br />
<br />
{{Attention|UBIK 5 clients can only connect to {{UBIK}} Servers of [[Version 3.6(Server)|version 3.6]] and higher!}}<br />
<br />
{{Attention|The minimum supported OS versions are:<br />
* Android 9;<br />
* iOS 12.}}<br />
<br />
== Availability ==<br />
{{key press|Android: Store}}{{key press|iOS: Store}}: Publicly available in Google Play Store / Apple App Store.<br />
<br />
{{key press|Android: Store Beta}}: Publicly available in Google Play Store as beta versions. You can opt in or out of the beta at any time in the store.<br />
<br />
{{key press|Android: Store Preview}}: Available through Google Play Store's [https://play.google.com/store/apps/details?id=com.augmensys.ubik.go invitation link].<br />
<br />
{{key press|iOS: Store Beta}}: Available through Apple App Store's [https://testflight.apple.com/join/Kmb1HG9E invitation link].<br />
<br />
{{key press|iOS: Store Preview}}: Available through Apple App Store's [https://testflight.apple.com/join/yHRnbYbt invitation link].<br />
<br />
{{key press|Windows: Store Preview}}: The mobile Windows client is not an official product and is only distributed as test versions upon request and/or in our [https://release.augmensys.com/download/modules/client/mobile/ release portal].<br />
<br/><br />
<br />
<br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with a ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
<br />
=== 5.0.221 on 2025-11-05 {{key press|Android: Store}} ===<br />
* (Android) Fixed an issue where creating new objects when there are already a lot of existing ones leads to an app freeze or even crash.<br />
<br />
<br />
=== 5.0.218 on 2025-10-10 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Added logging of the authentication headers in UBIKWebserviceDebug.log for better diagnostics.<br />
* A third party issue was fixed where some text Annotations in the ImageEditor weren't visible on iOS.<br />
* A third party issue was fixed where stream bytes increased exponentially when saving Annotations in the ImageEditor.<br />
<br />
<br />
=== 5.0.212 on 2025-10-03 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Fixed an issue where task direct editing doesn't work the first time.<br />
* Updated the notification message about branch download to avoid misunderstanding. When a branch download is in progress, you can work with the offline data which is already available at the time of the download, but any communication with the content server will be scheduled after the branch download is finished.<br />
<br />
<br />
=== 5.0.209 on 2025-09-27 {{key press|Android: Store}} 5.0.207 on 2025-09-25 {{key press|iOS: Store}} ===<br />
* UBIK GO is the cutting-edge evolution of Augmensys' trusted mobile client — rebuilt from the ground up with a modern architecture that unlocks unprecedented flexibility.<br />
* Improved the branch download performance especially when there are duplicate objects in multiple branches.<br />
* Updated some translations.<br />
* Updated the default Demo profile.<br />
* Fixed an issue that triggered a license warning even on a failed login.<br />
* Fixed an issue where the wizard is shown again when you navigate to a new but saved object offline.<br />
* Fixed an issue where duplicate notifications are shown when you scan an NFC tag for a supervisor task and no fitting supervisor is found.<br />
<br />
<br />
== Known issues ==<br />
* When changing the device orientation during attaching a photo on iOS, the app gets stuck. This is an issue Microsoft confirmed in .NET9 and will fix in .NET10.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Currently, the Samsung keyboard doesn't show {{key press|,}} at all, regardless of the current language/locale setting of the device. Please use a different virtual keyboard (e.g. Gboard from Google) instead if {{key press|.}} is unacceptable.<br />
* The periodic execution of background pushes is not guaranteed on iOS.<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* It is currently not possible to select which camera to use for AR views (e.g. scan page) on Windows.<br />
* SfPullToRefresh was removed due to [[Mobile_XAML#Issues_with_SfPullToRefresh_in_Mobile_client|existing issues]], and replaced with a Refresh option in the Context menu.<br />
<br/><br />
<br />
<br />
<br />
<br />
<br />
= ⚠️ XAML Notes =<br />
Due to the change of the underlying XAML technology, the existing XAMLs for the old mobile clients (pre 5.0) are no longer compatible. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.<br />
<br />
<headertabs /><br />
<br />
[[Category:Client|Version 5.0 (Mobile)]]<br />
[[Category:Mobile|Version 5.0 (Mobile)]]<br />
[[Category:Version 5.0|Version 5.0 (Mobile)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5.0_(Mobile)&diff=29031Version 5.0 (Mobile)2025-10-13T08:20:30Z<p>LGE: </p>
<hr />
<div>{{Attention|Existing pre 5.0 XAMLs are not compatible with UBIK Mobile client 5.0. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.}}<br />
<br />
{{Attention|UBIK 5 clients can only connect to {{UBIK}} Servers of [[Version 3.6(Server)|version 3.6]] and higher!}}<br />
<br />
{{Attention|The minimum supported OS versions are:<br />
* Android 9;<br />
* iOS 12.}}<br />
<br />
== Availability ==<br />
{{key press|Android: Store}}{{key press|iOS: Store}}: Publicly available in Google Play Store / Apple App Store.<br />
<br />
{{key press|Android: Store Beta}}: Publicly available in Google Play Store as beta versions. You can opt in or out of the beta at any time in the store.<br />
<br />
{{key press|Android: Store Preview}}: Available through Google Play Store's [https://play.google.com/store/apps/details?id=com.augmensys.ubik.go invitation link].<br />
<br />
{{key press|iOS: Store Beta}}: Available through Apple App Store's [https://testflight.apple.com/join/Kmb1HG9E invitation link].<br />
<br />
{{key press|iOS: Store Preview}}: Available through Apple App Store's [https://testflight.apple.com/join/yHRnbYbt invitation link].<br />
<br />
{{key press|Windows: Store Preview}}: The mobile Windows client is not an official product and is only distributed as test versions upon request and/or in our [https://release.augmensys.com/download/modules/client/mobile/ release portal].<br />
<br/><br />
<br />
<br />
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with a ⚠️}}<br />
<br />
<br />
= Release Notes =<br />
<br />
== Release ==<br />
<br />
=== 5.0.218 on 2025-10-10 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Added logging of the authentication headers in UBIKWebserviceDebug.log for better diagnostics.<br />
* A third party issue was fixed where some text Annotations in the ImageEditor weren't visible on iOS.<br />
* A third party issue was fixed where stream bytes increased exponentially when saving Annotations in the ImageEditor.<br />
<br />
<br />
=== 5.0.212 on 2025-10-03 {{key press|Android: Store}}{{key press|iOS: Store}} ===<br />
* Fixed an issue where task direct editing doesn't work the first time.<br />
* Updated the notification message about branch download to avoid misunderstanding. When a branch download is in progress, you can work with the offline data which is already available at the time of the download, but any communication with the content server will be scheduled after the branch download is finished.<br />
<br />
<br />
=== 5.0.209 on 2025-09-27 {{key press|Android: Store}} 5.0.207 on 2025-09-25 {{key press|iOS: Store}} ===<br />
* UBIK GO is the cutting-edge evolution of Augmensys' trusted mobile client — rebuilt from the ground up with a modern architecture that unlocks unprecedented flexibility.<br />
* Improved the branch download performance especially when there are duplicate objects in multiple branches.<br />
* Updated some translations.<br />
* Updated the default Demo profile.<br />
* Fixed an issue that triggered a license warning even on a failed login.<br />
* Fixed an issue where the wizard is shown again when you navigate to a new but saved object offline.<br />
* Fixed an issue where duplicate notifications are shown when you scan an NFC tag for a supervisor task and no fitting supervisor is found.<br />
<br />
<br />
== Known issues ==<br />
* When changing the device orientation during attaching a photo on iOS, the app gets stuck. This is an issue Microsoft confirmed in .NET9 and will fix in .NET10.<br />
* When editing Guid Link properties, you can no longer further edit the filtering if there are predefined filter parameters (such as the [[Dynamic_Selective_List_(Client)#Dependency_property_values|dependency property values in dynamic selective lists]]). This is because those parameters are to be enforced by design and should not be changed by users. In the future, we might consider a finer level of control over which parameters can be edited in such cases.<br />
* Currently, the Samsung keyboard doesn't show {{key press|,}} at all, regardless of the current language/locale setting of the device. Please use a different virtual keyboard (e.g. Gboard from Google) instead if {{key press|.}} is unacceptable.<br />
* The periodic execution of background pushes is not guaranteed on iOS.<br />
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].<br />
* It is currently not possible to select which camera to use for AR views (e.g. scan page) on Windows.<br />
* SfPullToRefresh was removed due to [[Mobile_XAML#Issues_with_SfPullToRefresh_in_Mobile_client|existing issues]], and replaced with a Refresh option in the Context menu.<br />
<br/><br />
<br />
<br />
<br />
<br />
<br />
= ⚠️ XAML Notes =<br />
Due to the change of the underlying XAML technology, the existing XAMLs for the old mobile clients (pre 5.0) are no longer compatible. Please refer to [[HowTo:Convert_Xamarin_XAMLs_to_Maui]] for migrating them to the new client.<br />
<br />
<headertabs /><br />
<br />
[[Category:Client|Version 5.0 (Mobile)]]<br />
[[Category:Mobile|Version 5.0 (Mobile)]]<br />
[[Category:Version 5.0|Version 5.0 (Mobile)]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5&diff=28992Version 52025-10-09T14:16:20Z<p>LGE: </p>
<hr />
<div><noinclude>{{RoadmapDetailHeader}}</noinclude><br />
<br />
{{RoadmapDetailItem <br />
| version=5.1<br />
| date= December 2025<br />
| status={{RoadmapChip-Announced|Future}} <br />
| content=<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Studio}} | feature=Extended Plugin C# solution generation| descr=Possibility to design MetaClasses, MetaProperties and Custom Code for a UBIK plugin and generate a C# solution for it. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Mobile}} | feature=Map view in mobile MAUI client | descr= }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Mobile}} | feature=Charts in mobile MAUI client | descr= }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Mobile}} | feature=Native push in mobile MAUI client | descr= }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Mobile}} | feature=POI view in mobile MAUI client | descr= }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Mobile}} | feature=Location service in mobile MAUI client | descr= }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Client}} | feature=Better control over file upload size | descr= }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Client}} | feature=Harder-to-miss branch download summary | descr= }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Client}} | feature=Improved save button design | descr= }}<br />
}}<br />
<br />
{{RoadmapDetailItem <br />
| version=5.0<br />
| date= September 2025<br />
| status={{RoadmapChip-Announced|Future}} <br />
| content=<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Studio}} | feature=Basic Plugin C# solution generation| descr=Possibility to configure plugins in UBIK.Studio, and to generate a C# solution from this configuration. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Server}} | feature=Server MRO Procedures | descr=Introduces server-side support for managing and executing MRO (Maintenance, Repair, Overhaul) procedures. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Mobile}} | feature=Mobile UBIK .NET MAUI Client | descr=Modernized UBIK mobile application built with .NET MAUI for cross-platform compatibility and improved performance. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Client}} | feature=Improved branch download performance | descr=Improved the branch download performance especially when there are duplicate objects in multiple branches. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Studio}} | feature=Studio Iterative Instance Data Transfer in SmartStudio | descr=Enables transferring instance data between environments or projects using iterative and controlled processes. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Studio}} | feature=Studio Text-Markup Annotations support opacity now | descr=Annotations in SmartStudio now support opacity settings for better visual clarity and flexibility. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Server}} | feature=Server UBIK supports the Exclusive Checkout Query now | descr=Enhances UBIK's versioning control with support for exclusive checkouts via query. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Server}} | feature=Server Extended Archon License Information | descr=Archon licenses now include more detailed metadata and management information on the server. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-CUI}} | feature=Log CUI Web Request V2 | descr=Improved logging of CUI web requests for better traceability and debugging. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Server}} | feature=Server UBIK Traits | descr=New support for defining and using Traits in the UBIK Server model - "Lightweight Properties" }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-MaTaP}} | feature=MaTaP Blind List Management | descr=Adds functionality for blind list handling in MaTaP, improving confidentiality and targeting. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Studio}} | feature=Bulk Editor UID Column | descr=A UID column can now be shown in UBIK.Studio's BulkEditor. }}<br />
}}<br />
<br />
[[Category:Client|Version 5]]<br />
[[Category:Release notes|Version 5]]<br />
[[Category:Roadmap|Version 5]]<br />
[[Category:Server|Version 5]]</div>LGEhttps://wiki.augmensys.com/index.php?title=RoadmapOverview&diff=28991RoadmapOverview2025-10-09T14:15:35Z<p>LGE: </p>
<hr />
<div>{{RoadmapOverview<br />
| versionReleases=[[Version_4|View All v4 Releases]]<br />
| content=<br />
<!-- Begin Content (Items) --><br />
<br />
| last= <br />
{{RoadmapOverviewItem <br />
| version=4.6 <br />
| date={{RoadmapChip-Released|February 2024}} <br />
| content=<br />
* Prefilter Objects with the same QR code.<br />
* Access To An Arbitrary Object in UI.<br />
* Indicator for Uncommitted Changes. <br />
* {{RoadmapChip-Xamarin}} Customizable Visibility of appbar Menu Button.<br />
* SSO: Automatic JWKS renewal for OIDC.<br />
* {{RoadmapChip-WinX}} SSO Login.<br />
* {{RoadmapChip-WinX}} Various improvements to PDF Annotations.<br />
* Better UI Performance when Accessing Single Properties.<br />
* Productization of MaTaP Features.<br />
* Improvements in CUI Orchestration.<br />
* Hide unconfigured Live Value Properties.<br />
* DB concurrency stabilized, deadlock prevention.<br />
* DB performance improvement, adding indexes.<br />
* Improvements in the Comos MetaData SmartImport.<br />
* {{RoadmapChip-Server}} The {{UBIK}} reporting module for creating HTML or PDF reports from custom code is available again.<br />
}}<br />
<br />
<br />
| {{RoadmapOverviewItem | version=4.7 | date={{RoadmapChip-Released| May 2024}} | content=<br />
* {{RoadmapChip-MaTaP}} Productization of MaTaP Features.<br />
* {{RoadmapChip-WinX}} Support Bing Maps Road for UWP.<br />
* {{RoadmapChip-Mobile}} Online Results for OCR Scan.<br />
* {{RoadmapChip-Mobile}} Command to Update An Arbitrary Object.<br />
* {{RoadmapChip-CUI}} Comos Min / Max values available in UBIK Clients.<br />
* {{RoadmapChip-Studio}} UI for the Automatic View Adaptation to Model Changes (Views)<br />
* {{RoadmapChip-CUI}} Improve Import Export Orchestration<br />
* {{RoadmapChip-CUI}} Prevent JIT Exports when processing imports<br />
* {{RoadmapChip-CUI}} Configurable object amount for processing notifications.<br />
* SmartModels know their MetaClass now<br />
* {{RoadmapChip-Server}} Enterprise Server: Enable json task configuration to contain multiple task definitions<br />
* {{RoadmapChip-Server}} Attributes on MRO classification MetaProperties<br />
* {{RoadmapChip-CUI}}CUI: Enable the possibility to configure the amount of Exported Proxies<br />
<br />
}}<br />
<br />
| last= {{RoadmapOverviewItem | version=4.8 | date={{RoadmapChip-Released| September 2024}} | content=<br />
* {{RoadmapChip-MaTaP}} Productization of MaTaP Features (Server / Desktop Client).<br />
* {{RoadmapChip-iOS}} OIDC for iOS <br />
* {{RoadmapChip-CUI}} Improvements of the CUI Interface<br />
* {{RoadmapChip-Studio}}Automatic ReferenceViewItem creation<br />
* {{RoadmapChip-Xamarin}} Improved customizability of the Document Page<br />
* {{RoadmapChip-Xamarin}} Customizable Charts.<br />
* Recycle of App Pool.<br />
* UBIK license control<br />
<br />
}}<br />
<br />
| last= {{RoadmapOverviewItem | version=4.8.1 | date={{RoadmapChip-Released| October 2024}} | content=<br />
* Native Push Service<br />
* {{RoadmapChip-iOS}} Managed App configuration for iOS<br />
* NFC 4-eyes acceptance feature<br />
* Improved Upload Document Handling <br />
}}<br />
<br />
| last= {{RoadmapOverviewItem | version=4.9 | date={{RoadmapChip-Released| January 2025}} | content=<br />
* {{RoadmapChip-Server}} Optimized RAM consumption: Prevent caching for specific objects<br />
* {{RoadmapChip-Studio}} Local DB Views: Human readable DB views on the UBIK DB<br />
* {{RoadmapChip-MaTaP}} MaTaP provides the feature of the Commissioning Wallpaper.<br />
* {{RoadmapChip-MaTaP}} MaTaP Admin Tool is now available.<br />
* {{RoadmapChip-MaTaP}} The communication feature is now available in MaTaP.<br />
* {{RoadmapChip-Studio}} Plugins are now initialized in the correct order of their dependency<br />
* {{RoadmapChip-WinX}} Context filtering for template queries and Clientside Replication<br />
* {{RoadmapChip-Studio}} MetaProxy Properties are now modelled more consistently in SmartStudio<br />
* {{RoadmapChip-Studio}} Custom code for MetaProxies can now be edited and transported using SmartStudio<br />
* {{RoadmapChip-Mobile}} It is now possible to customize the freetext search<br />
* {{RoadmapChip-Mobile}} It is possible to preserve the settings from the PDFViewer<br />
* {{RoadmapChip-CUI}} Auto - reset proxies for "undeleted" Comos Objects <br />
* {{RoadmapChip-CUI}} It is now possible to configure the Reset of Property Values During Import<br />
* {{RoadmapChip-Studio}} The Auto-Create Scope drag & drop action was enhanced greatly<br />
}}<br />
<br />
<br />
<br />
| current= {{RoadmapOverviewItem | version=5.0 | date={{RoadmapChip-Announced| September 2025}} | content=<br />
* {{RoadmapChip-Server}} MRO Procedures<br />
* {{RoadmapChip-Mobile}} Mobile UBIK .NET MAUI Client<br />
* {{RoadmapChip-Client}} Improved branch download performance<br />
* {{RoadmapChip-Studio}} Iterative Instance Data Transfer in SmartStudio.<br />
* {{RoadmapChip-Studio}} Text-Markup Annotations support opacity now.<br />
* {{RoadmapChip-Server}} UBIK supports the Exclusive Checkout Query now.<br />
* {{RoadmapChip-Server}} Extended Archon License Information<br />
* {{RoadmapChip-Server}} Plugin Configuration and Code Generation.<br />
* {{RoadmapChip-CUI}} Log CUI Web Request V2<br />
* {{RoadmapChip-Server}} UBIK Traits<br />
* {{RoadmapChip-MaTaP}} Blind List Management<br />
* Other Features in Planning <br />
}}<br />
<br />
| next= {{RoadmapOverviewItem | version=5.1 | date={{RoadmapChip-Announced| December 2025}} | content=<br />
* {{RoadmapChip-Mobile}} Map view in mobile MAUI client<br />
* {{RoadmapChip-Mobile}} Charts in mobile MAUI client<br />
* {{RoadmapChip-Mobile}} Native push in mobile MAUI client<br />
* {{RoadmapChip-Mobile}} POI view in mobile MAUI client<br />
* {{RoadmapChip-Mobile}} Location service in mobile MAUI client<br />
* {{RoadmapChip-Client}} Better control over file upload size<br />
* {{RoadmapChip-Client}} Harder-to-miss branch download summary<br />
* {{RoadmapChip-Client}} Improved save button design<br />
}}<br />
<br />
<!-- end Content --><br />
}}<br />
<br />
[[Category:Roadmap|RoadmapOverview]]</div>LGEhttps://wiki.augmensys.com/index.php?title=Version_5&diff=28990Version 52025-10-09T14:09:36Z<p>LGE: </p>
<hr />
<div><noinclude>{{RoadmapDetailHeader}}</noinclude><br />
<br />
{{RoadmapDetailItem <br />
| version=5.1<br />
| date= Late 2025<br />
| status={{RoadmapChip-Announced|Future}} <br />
| content=<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Studio}} | feature=Extended Plugin C# solution generation| descr=Possibility to design MetaClasses, MetaProperties and Custom Code for a UBIK plugin and generate a C# solution for it. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Mobile}} | feature=Map view in mobile MAUI client | descr= }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Mobile}} | feature=Charts in mobile MAUI client | descr= }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Mobile}} | feature=Native push in mobile MAUI client | descr= }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Mobile}} | feature=POI view in mobile MAUI client | descr= }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Mobile}} | feature=Location service in mobile MAUI client | descr= }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Client}} | feature=Better control over file upload size | descr= }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Client}} | feature=Harder-to-miss branch download summary | descr= }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Client}} | feature=Improved save button design | descr= }}<br />
}}<br />
<br />
{{RoadmapDetailItem <br />
| version=5.0<br />
| date= Late Summer 2025<br />
| status={{RoadmapChip-Announced|Future}} <br />
| content=<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Studio}} | feature=Basic Plugin C# solution generation| descr=Possibility to configure plugins in UBIK.Studio, and to generate a C# solution from this configuration. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Server}} | feature=Server MRO Procedures | descr=Introduces server-side support for managing and executing MRO (Maintenance, Repair, Overhaul) procedures. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Mobile}} | feature=Mobile UBIK .NET MAUI Client | descr=Modernized UBIK mobile application built with .NET MAUI for cross-platform compatibility and improved performance. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Client}} | feature=Improved branch download performance | descr=Improved the branch download performance especially when there are duplicate objects in multiple branches. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Studio}} | feature=Studio Iterative Instance Data Transfer in SmartStudio | descr=Enables transferring instance data between environments or projects using iterative and controlled processes. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Studio}} | feature=Studio Text-Markup Annotations support opacity now | descr=Annotations in SmartStudio now support opacity settings for better visual clarity and flexibility. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Server}} | feature=Server UBIK supports the Exclusive Checkout Query now | descr=Enhances UBIK's versioning control with support for exclusive checkouts via query. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Server}} | feature=Server Extended Archon License Information | descr=Archon licenses now include more detailed metadata and management information on the server. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-CUI}} | feature=Log CUI Web Request V2 | descr=Improved logging of CUI web requests for better traceability and debugging. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Server}} | feature=Server UBIK Traits | descr=New support for defining and using Traits in the UBIK Server model - "Lightweight Properties" }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-MaTaP}} | feature=MaTaP Blind List Management | descr=Adds functionality for blind list handling in MaTaP, improving confidentiality and targeting. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Studio}} | feature=Bulk Editor UID Column | descr=A UID column can now be shown in UBIK.Studio's BulkEditor. }}<br />
}}<br />
<br />
[[Category:Client|Version 5]]<br />
[[Category:Release notes|Version 5]]<br />
[[Category:Roadmap|Version 5]]<br />
[[Category:Server|Version 5]]</div>LGEhttps://wiki.augmensys.com/index.php?title=RoadmapOverview&diff=28989RoadmapOverview2025-10-09T13:54:19Z<p>LGE: </p>
<hr />
<div>{{RoadmapOverview<br />
| versionReleases=[[Version_4|View All v4 Releases]]<br />
| content=<br />
<!-- Begin Content (Items) --><br />
<br />
| last= <br />
{{RoadmapOverviewItem <br />
| version=4.6 <br />
| date={{RoadmapChip-Released|February 2024}} <br />
| content=<br />
* Prefilter Objects with the same QR code.<br />
* Access To An Arbitrary Object in UI.<br />
* Indicator for Uncommitted Changes. <br />
* {{RoadmapChip-Xamarin}} Customizable Visibility of appbar Menu Button.<br />
* SSO: Automatic JWKS renewal for OIDC.<br />
* {{RoadmapChip-WinX}} SSO Login.<br />
* {{RoadmapChip-WinX}} Various improvements to PDF Annotations.<br />
* Better UI Performance when Accessing Single Properties.<br />
* Productization of MaTaP Features.<br />
* Improvements in CUI Orchestration.<br />
* Hide unconfigured Live Value Properties.<br />
* DB concurrency stabilized, deadlock prevention.<br />
* DB performance improvement, adding indexes.<br />
* Improvements in the Comos MetaData SmartImport.<br />
* {{RoadmapChip-Server}} The {{UBIK}} reporting module for creating HTML or PDF reports from custom code is available again.<br />
}}<br />
<br />
<br />
| {{RoadmapOverviewItem | version=4.7 | date={{RoadmapChip-Released| May 2024}} | content=<br />
* {{RoadmapChip-MaTaP}} Productization of MaTaP Features.<br />
* {{RoadmapChip-WinX}} Support Bing Maps Road for UWP.<br />
* {{RoadmapChip-Mobile}} Online Results for OCR Scan.<br />
* {{RoadmapChip-Mobile}} Command to Update An Arbitrary Object.<br />
* {{RoadmapChip-CUI}} Comos Min / Max values available in UBIK Clients.<br />
* {{RoadmapChip-Studio}} UI for the Automatic View Adaptation to Model Changes (Views)<br />
* {{RoadmapChip-CUI}} Improve Import Export Orchestration<br />
* {{RoadmapChip-CUI}} Prevent JIT Exports when processing imports<br />
* {{RoadmapChip-CUI}} Configurable object amount for processing notifications.<br />
* SmartModels know their MetaClass now<br />
* {{RoadmapChip-Server}} Enterprise Server: Enable json task configuration to contain multiple task definitions<br />
* {{RoadmapChip-Server}} Attributes on MRO classification MetaProperties<br />
* {{RoadmapChip-CUI}}CUI: Enable the possibility to configure the amount of Exported Proxies<br />
<br />
}}<br />
<br />
| last= {{RoadmapOverviewItem | version=4.8 | date={{RoadmapChip-Released| September 2024}} | content=<br />
* {{RoadmapChip-MaTaP}} Productization of MaTaP Features (Server / Desktop Client).<br />
* {{RoadmapChip-iOS}} OIDC for iOS <br />
* {{RoadmapChip-CUI}} Improvements of the CUI Interface<br />
* {{RoadmapChip-Studio}}Automatic ReferenceViewItem creation<br />
* {{RoadmapChip-Xamarin}} Improved customizability of the Document Page<br />
* {{RoadmapChip-Xamarin}} Customizable Charts.<br />
* Recycle of App Pool.<br />
* UBIK license control<br />
<br />
}}<br />
<br />
| last= {{RoadmapOverviewItem | version=4.8.1 | date={{RoadmapChip-Released| October 2024}} | content=<br />
* Native Push Service<br />
* {{RoadmapChip-iOS}} Managed App configuration for iOS<br />
* NFC 4-eyes acceptance feature<br />
* Improved Upload Document Handling <br />
}}<br />
<br />
| last= {{RoadmapOverviewItem | version=4.9 | date={{RoadmapChip-Released| January 2025}} | content=<br />
* {{RoadmapChip-Server}} Optimized RAM consumption: Prevent caching for specific objects<br />
* {{RoadmapChip-Studio}} Local DB Views: Human readable DB views on the UBIK DB<br />
* {{RoadmapChip-MaTaP}} MaTaP provides the feature of the Commissioning Wallpaper.<br />
* {{RoadmapChip-MaTaP}} MaTaP Admin Tool is now available.<br />
* {{RoadmapChip-MaTaP}} The communication feature is now available in MaTaP.<br />
* {{RoadmapChip-Studio}} Plugins are now initialized in the correct order of their dependency<br />
* {{RoadmapChip-WinX}} Context filtering for template queries and Clientside Replication<br />
* {{RoadmapChip-Studio}} MetaProxy Properties are now modelled more consistently in SmartStudio<br />
* {{RoadmapChip-Studio}} Custom code for MetaProxies can now be edited and transported using SmartStudio<br />
* {{RoadmapChip-Mobile}} It is now possible to customize the freetext search<br />
* {{RoadmapChip-Mobile}} It is possible to preserve the settings from the PDFViewer<br />
* {{RoadmapChip-CUI}} Auto - reset proxies for "undeleted" Comos Objects <br />
* {{RoadmapChip-CUI}} It is now possible to configure the Reset of Property Values During Import<br />
* {{RoadmapChip-Studio}} The Auto-Create Scope drag & drop action was enhanced greatly<br />
}}<br />
<br />
<br />
<br />
| current= {{RoadmapOverviewItem | version=5.0 | date={{RoadmapChip-Announced| September 2025}} | content=<br />
* {{RoadmapChip-Server}} MRO Procedures<br />
* {{RoadmapChip-Mobile}} UBIK .NET MAUI Client<br />
* {{RoadmapChip-Studio}} Iterative Instance Data Transfer in SmartStudio.<br />
* {{RoadmapChip-Studio}} Text-Markup Annotations support opacity now.<br />
* {{RoadmapChip-Server}} UBIK supports the Exclusive Checkout Query now.<br />
* {{RoadmapChip-Server}} Extended Archon License Information<br />
* {{RoadmapChip-Server}} Plugin Configuration and Code Generation.<br />
* {{RoadmapChip-CUI}} Log CUI Web Request V2<br />
* {{RoadmapChip-Server}} UBIK Traits<br />
* {{RoadmapChip-MaTaP}} Blind List Management<br />
* Other Features in Planning <br />
}}<br />
<br />
| next= {{RoadmapOverviewItem | version=5.1 | date={{RoadmapChip-Announced| December 2025}} | content=<br />
* Features in Planning<br />
}}<br />
<br />
<!-- end Content --><br />
}}<br />
<br />
[[Category:Roadmap|RoadmapOverview]]</div>LGE