Version 5.1 (Mobile)

2026-01-29T09:15:56Z

LKR: /* 5.1.??? on 202?-??-?? */

{{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.}}

{{Attention|UBIK 5 clients can only connect to {{UBIK}} Servers of [[Version 3.6(Server)|version 3.6]] and higher!}}

{{Attention|The minimum supported OS versions are:
* Android 9;
* iOS 12.}}

== Availability ==
{{key press|Android: Store}}{{key press|iOS: Store}}: Publicly available in Google Play Store / Apple App Store.

{{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.

{{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].

{{key press|iOS: Store Beta}}: Available through Apple App Store's [https://testflight.apple.com/join/Kmb1HG9E invitation link].

{{key press|iOS: Store Preview}}: Available through Apple App Store's [https://testflight.apple.com/join/yHRnbYbt invitation link].

{{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/>

{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with a ⚠️}}

= Release Notes =

== Preview ==

=== 5.1.??? on 202?-??-?? ===
* Fixed an issue where the Chart Thresholds didn't update.
* Added support for configurable file-upload size restrictions, preventing oversized files from being uploaded and providing users with feedback when limits are exceeded.
* (Android) Fixed an issue in the WebView where some links could not be opened.
* Added support for conditionally showing the ImageEditor Save button only when edits have been made, enabled when MergeAnnotationsOnSave is set to true.
* Fixed an issue where the deletion of some objects was not reflected in the UI until refresh.
* Fixed an issue that caused content to not be rendered sometimes.

[[Category:Client|Version 5.1 (Mobile)]]
[[Category:Mobile|Version 5.1 (Mobile)]]
[[Category:Version 5.1|Version 5.1 (Mobile)]]

== Known issues ==
* 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/>

= ⚠️ XAML Notes =
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.

<headertabs />

[[Category:Client|Version 5.1 (Mobile)]]
[[Category:Mobile|Version 5.1 (Mobile)]]
[[Category:Version 5.1|Version 5.1 (Mobile)]]

Version 5.0 (WinX)

2026-01-13T13:53:31Z

LKR: /* 5.0.40 on 2025-12-?? {{key press|Store}} */

HowTo:Convert Xamarin XAMLs to Maui

2025-08-05T12:49:01Z

LKR: /* Mandatory */

== Information ==
=== Frame to Border ===
'''Use Border instead of Frame.'''
Frame is deprecated in MAUI. Use Border with `Stroke` instead of `BorderColor`.

{| class="wikitable"
! Xamarin
! MAUI
|-
| <Frame ... />
| <Border ... />
|}

=== LayoutOptions with "...AndExpand" ===
'''Replace "...AndExpand" with Grid layout.'''
Horizontal/VerticalOptions ending in "...AndExpand" are deprecated. Use Grid with `ColumnDefinition Width="*"` for expansion.

=== GlyphLabel and Styles ===
'''Use Label with new styles.'''
Custom controls like `GlyphLabel` are no longer needed. Use `Label` with styles like `UBIKSymbolText`.

{| class="wikitable"
! Xamarin
! MAUI
|-
| controls:GlyphLabel
| Label with UBIKSymbolText style
|}

=== SfTabView Virtualization ===
'''Enable virtualization.'''
Add `EnableVirtualization="True"` to all SfTabView instances or styles.

=== Swipe Menu Icons on Android ===
'''Refactor swipe templates and label styles.'''
Icons in swipe menus were truncated on Android. Fixed via refactoring.

=== Color Style Changes ===
'''Dark theme adjustments.'''
Changes to color styles may affect appearance. Review usage of `UBIKDarkThemeColor`, `UBIKDarkTextColor`, etc.

=== Strikethrough Converter ===
'''Use `TextDecorations="Strikethrough"` instead of converter.'''

{| class="wikitable"
! Xamarin
! MAUI
|-
| Text="{Binding ..., Converter={StaticResource StrikethroughConverter}}"
| Text="{Binding ...}" TextDecorations="Strikethrough"
|}

=== Button Disabled Trigger ===
'''Add trigger for disabled buttons.'''
Maui buttons don’t visually change when disabled. Add trigger to style.

=== TapGestureRecognizer Replacement ===
'''Use TappedBehavior instead.'''
TapGestureRecognizer now intercepts taps. Use `TappedBehavior` to avoid conflicts.

{| class="wikitable"
! Xamarin
! MAUI
|-
| <... .GestureRecognizers><TapGestureRecognizer Command="{Binding ...}" /></... .GestureRecognizers>
| <... .Behaviors><behaviors:TappedBehavior><behaviors:InvokeCommandAction Command="{Binding ...}" /></behaviors:TappedBehavior></... .Behaviors>
|}

=== TapGestureRecognizer and Swipe Conflict ===
'''Remove TapGestureRecognizer from root Grid.'''
TapGestureRecognizer blocks swipe behavior. Remove it and adapt parent list to trigger navigation.

=== Navigation in UBIKChildItem ===
'''Use EventHandlerBehavior for navigation.'''

{| class="wikitable"
! Xamarin
! MAUI
|-
| [none]
| <controls:SfListViewExt.Behaviors><behaviors:EventHandlerBehavior EventName="ItemTapped"><behaviors:InvokeCommandAction Command="{Binding AppStatus.RootList.Items[0].NavigateToChildrenCommand}" /></behaviors:EventHandlerBehavior></controls:SfListViewExt.Behaviors>
|}
== Recommended ==
=== Extract DataTemplates from UBIKThemes ===
'''Create separate .xamlx files for the following DataTemplates.'''
It's not so easy about the namespaces:
* In our default templates, it's enough to add the following ones to every new separate .xamlx files at the beginning;
* xmlns:ctrls="clr-namespace:UBIK.MAUI.Controls;assembly=UBIK.MAUI";
* xmlns:platform="clr-namespace:UBIK.MAUI.Platform.Renderers;assembly=UBIK.MAUI";
* xmlns:resources="clr-namespace:UBIK.MAUI.Resources;assembly=UBIK.MAUI";
* xmlns:services="clr-namespace:UBIK.MAUI.Services;assembly=UBIK.MAUI";
* xmlns:uiservices="clr-namespace:UBIK.UI.Services;assembly=UBIK.UI".
* But we don't know if other namespaces might be used in the custom templates. So it might be necessary to really analyze the namespaces used and find/copy them from the UBIKThemes file.
{| class="wikitable"
!   !! Templates !!  
|-
| UBIKMainItem || UBIKChildItem || UBIKTaskItem
|-
| UBIKTaskProperty || UBIKTaskPropertyString || UBIKTaskPropertyDouble
|-
| UBIKTaskPropertyInt || UBIKTaskPropertyNumeric || UBIKTaskPropertyDateTime
|-
| UBIKTaskPropertyGeoData || UBIKTaskPropertyBool || UBIKTaskPropertyPopup
|-
| UBIKTaskPropertyList || UBIKTaskPropertyGuid || UBIKPropertyItem
|-
| UBIKPropertyTextLengthHint || UBIKPropertyDirectEditButtons || UBIKTaskPropertyEditButtons
|-
| UBIKPropertyDirectItemString || UBIKPropertyDirectItemDouble || UBIKPropertyDirectItemInt
|-
| UBIKPropertyDirectItemMinMax || UBIKPropertyDirectItemNumeric || UBIKPropertyDirectItemDateTime
|-
| UBIKPropertyDirectItemGeoData || UBIKPropertyDirectItemBool || UBIKPropertyDirectItemPopup
|-
| UBIKPropertyDirectItemList || UBIKPropertyDirectItemGuid || UBIKDocumentItem
|-
| UBIKSearchResultItem || UBIKDefaultHotSpot || UBIKAngularLinkHotSpot
|-
| UBIKRoundLinkHotSpot || UBIKInputHotSpot || UBIKSignatureHotSpot
|-
| UBIKObjectHotSpot || UBIKMediaHotSpot ||
|}
=== VideoPlayer Adjustments ===
'''This property is repsonsible for the video player regarding how or if it should get scaled up depending on the value of the
Aspect property'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">VideoPlayer...</syntaxhighlight>
| <syntaxhighlight lang="xml">VideoPlayer Aspect="AspectFit"</syntaxhighlight>
|}

'''The UriToVideoSourceConverter is no longer needed because the conversion of the
VideoSource gets done by the MediaElement itself. It is marked as obsolete and should therefore no longer be used.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml"><controls:VideoPlayer... Source="{Binding DocumentViewModel.LocalURI, Converter={StaticResource UriToVideoSource}}"/></syntaxhighlight>
| <syntaxhighlight lang="xml"><controls:VideoPlayer... Source="{Binding DocumentViewModel.LocalURI}"/></syntaxhighlight>
|}

'''The StopTimer property is obsolete and no longer needed because the MediaElement behind does the Stop of the VideoPlayer
by itself.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml"><controls:VideoPlayer... StopTimer="{Binding Unloaded}" /></syntaxhighlight>
| <syntaxhighlight lang="xml"><controls:VideoPlayer... /></syntaxhighlight>
|}
=== SearchBar Style Fix on iOS ===
'''On iOS, defining a transparent background for the SearchBar control results in a black text on black background appearance.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">[issue on iOS only] UBIKThemes: SearchBar style: <Setter Property="BackgroundColor" Value="Transparent" /></syntaxhighlight>
| <syntaxhighlight lang="xml">Delete this setter</syntaxhighlight>
|}
=== Avoid Redundant ControlTemplate in DataTriggers ===
'''This is about finding ControlTemplates that are set in DataTriggers in customized Xamls. When the same template is already set as a ContentView default ControlTemplate, it is recommended to remove the default ControlTemplate on the ContentView. For a detailed description please refer to sheet "Mandatory" in cell 27A-27C.
Behavior that might occur if it remains unchanged: Property editor might not open on Android.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml"><ContentView x:Name="containerName" ControlTemplate="{StaticResource YourTemplate1}">
<ContentView.Triggers>
<DataTrigger
Binding="{Binding Source={x:Reference containerName}, Path=...}"
TargetType="ContentView"
Value="true">
<Setter Property="ControlTemplate"
Value="{StaticResource YourTemplate1}" />
</DataTrigger>
...
</ContentView.Triggers>
</ContentView></syntaxhighlight>
| <syntaxhighlight lang="xml"><ContentView x:Name="containerName">
<ContentView.Triggers>
<DataTrigger
Binding="{Binding Source={x:Reference containerName}, Path=...}"
TargetType="ContentView"
Value="true">
<Setter Property="ControlTemplate"
Value="{StaticResource YourTemplate1}" />
</DataTrigger>
...
</ContentView.Triggers>
</ContentView></syntaxhighlight>
|}
=== Replace TemplateBinding with Binding and Source ===
'''This is about finding SfListViewExt controls in customizings, and if there are TemplateBindings used, it's recommended to replace them with Binding, and the Source reference should be added. For a detailed description please refer to sheet "Mandatory" in cell 26A-26C.
Behavior that might occur if it remains unchanged: Pre-selected item might appear unselected.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml"><ContentView
...
x:Name="YourContentViewName">

<ContentView.Resources>
<ResourceDictionary>
...
<ControlTemplate x:Key="YourTemplateKey">
<ctrls:SfListViewExt
ItemsSource="{TemplateBinding BindingContext.YourBinding,
...}"
SelectedItem="{TemplateBinding BindingContext.YourBinding,
...}"
... />
</ControlTemplate>
...
</ResourceDictionary>
</ContentView.Resources>

...
</ContentView></syntaxhighlight>
| <syntaxhighlight lang="xml"><ContentView
...
x:Name="YourContentViewName">

<ContentView.Resources>
<ResourceDictionary>
...
<ControlTemplate x:Key="YourTemplateKey">
<ctrls:SfListViewExt
ItemsSource="{Binding BindingContext.YourBinding,
Source={x:Reference YourContentViewName},
...}"
SelectedItem="{Binding BindingContext.YourBinding,
Source={x:Reference YourContentViewName},
...}"
... />
</ControlTemplate>
...
</ResourceDictionary>
</ContentView.Resources>

...
</ContentView></syntaxhighlight>
|}
=== Remove TapGestureRecognizer from Main Item ===
'''Swiping on the Main items was broken by Maui (Documented in Information). The workaround is to remove the TapGestureRecognizer from UBIKMainItem, and add ListView-based navigation similar to that found in UBIKChildArea (with an extended binding path for technical reasons).'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">(In UBIKMainItem)
<Grid.GestureRecognizers>
<TapGestureRecognizer Command="{Binding NavigateToChildrenCommand}" />
</Grid.GestureRecognizers></syntaxhighlight>
| <syntaxhighlight lang="xml">[nothing]</syntaxhighlight>
|}
=== Add Navigation Behavior in Child Area ===
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">(In UBIKChildArea)
[nothing]</syntaxhighlight>
| <syntaxhighlight lang="xml"><controls:SfListViewExt.Behaviors>
<behaviors:EventHandlerBehavior EventName="ItemTapped">
<behaviors:InvokeCommandAction Command="{Binding AppStatus.RootList.Items[0].NavigateToChildrenCommand}" />
</behaviors:EventHandlerBehavior>
</controls:SfListViewExt.Behaviors></syntaxhighlight>
|}
== Highly Recommended ==
=== CircularImage to AvatarView ===
'''Use AvatarView instead of CircularImage.'''
CircularImage and its wrapping Frame are no longer needed. Use AvatarView from the MAUI Community Toolkit. Add the namespace:
<syntaxhighlight lang="xml">
xmlns:toolkit="http://schemas.microsoft.com/dotnet/2022/maui/toolkit"
</syntaxhighlight>

{| class="wikitable"
! Xamarin
! MAUI
|-
| <Frame><CircularImage Source="..." /></Frame>
| <toolkit:AvatarView ImageSource="..." BorderWidth="..." BackgroundColor="..." />
|}

=== GlyphSize to FontSize and Alignment ===
'''Use FontSize and alignment properties instead of GlyphSize.'''
The GlyphSize property is obsolete. Use FontSize and add alignment properties for better layout.

{| class="wikitable"
! Xamarin
! MAUI
|-
| <Setter Property="GlyphSize" Value="13.0" />
| <Setter Property="FontSize" Value="16" /><br/><Setter Property="VerticalOptions" Value="Center" /><br/><Setter Property="HorizontalOptions" Value="Center" /><br/><Setter Property="VerticalTextAlignment" Value="Center" /><br/><Setter Property="HorizontalTextAlignment" Value="Center" />
|}

=== StaticResource to DynamicResource ===
'''Use DynamicResource and BaseResourceKey.'''
For dynamic theming, use DynamicResource instead of StaticResource. When inheriting styles, use BaseResourceKey.

{| class="wikitable"
! Xamarin
! MAUI
|-
| BasedOn="{StaticResource SomeStyle}"<br/>Style="{StaticResource SomeStyle}"
| BaseResourceKey="SomeStyle"<br/>Style="{DynamicResource SomeStyle}"
|}
== Mandatory ==

=== Namespace conversion ===
'''Update all namespaces to MAUI equivalents.'''
All `xmlns` and `clr-namespace` declarations must be updated to their MAUI counterparts.

{| class="wikitable"
! Xamarin
! MAUI
|-
| xmlns="http://xamarin.com/schemas/2014/forms"
| xmlns="http://schemas.microsoft.com/dotnet/2021/maui"
|-
| clr-namespace:Xamarin.Forms.PlatformConfiguration.AndroidSpecific;assembly=Xamarin.Forms.Core
| clr-namespace:Microsoft.Maui.Controls.PlatformConfiguration.AndroidSpecific;assembly=Microsoft.Maui.Controls
|-
| clr-namespace:UBIK.CPL.Behaviors;assembly=UBIK.CPL
| clr-namespace:UBIK.MAUI.Behaviors;assembly=UBIK.MAUI
|-
| clr-namespace:UBIK.CPL.Classes;assembly=UBIK.CPL
| clr-namespace:UBIK.MAUI.Classes;assembly=UBIK.MAUI
|-
| clr-namespace:UBIK.CPL.Controls;assembly=UBIK.CPL
| clr-namespace:UBIK.MAUI.Controls;assembly=UBIK.MAUI
|-
| clr-namespace:UBIK.CPL.Converters;assembly=UBIK.CPL
| clr-namespace:UBIK.MAUI.Converters;assembly=UBIK.MAUI
|-
| clr-namespace:UBIK.CPL.Platform.Renderers;assembly=UBIK.CPL
| clr-namespace:UBIK.MAUI.Platform.Controls;assembly=UBIK.MAUI
|-
| clr-namespace:UBIK.CPL.Services;assembly=UBIK.CPL
| clr-namespace:UBIK.MAUI.Services;assembly=UBIK.MAUI
|-
| clr-namespace:UBIK.CPL.Resources;assembly=UBIK.CPL
| clr-namespace:UBIK.MAUI.Resources;assembly=UBIK.MAUI
|-
| clr-namespace:UBIK.Scanning.Forms;assembly=UBIK.Scanning.Forms
| clr-namespace:UBIK.MAUI.Controls.ZXingScanner;assembly=UBIK.MAUI
|-
| clr-namespace:Syncfusion.SfPullToRefresh.XForms;assembly=Syncfusion.SfPullToRefresh.XForms
| clr-namespace:Syncfusion.Maui.Toolkit.PullToRefresh;assembly=Syncfusion.Maui.Toolkit
|-
| clr-namespace:Syncfusion.XForms.TabView;assembly=Syncfusion.SfTabView.Xforms
| clr-namespace:Syncfusion.Maui.Toolkit.TabView;assembly=Syncfusion.Maui.Toolkit
|-
| clr-namespace:Syncfusion.ListView.XForms;assembly=Syncfusion.SfListView.XForms
| clr-namespace:Syncfusion.Maui.ListView;assembly=Syncfusion.Maui.ListView
|-
| clr-namespace:Syncfusion.XForms.TreeView;assembly=Syncfusion.SfTreeView.XForms
| clr-namespace:Syncfusion.Maui.TreeView;assembly=Syncfusion.Maui.TreeView
|-
| clr-namespace:Syncfusion.XForms.TextInputLayout;assembly=Syncfusion.Core.XForms
| clr-namespace:Syncfusion.Maui.Core;assembly=Syncfusion.Maui.Core
|}

For classes referenced in the XAML code, please don't forget to also replace "CPL" with "MAUI" in the class namespace.

=== Syncfusion control updates ===
'''There are some other properties that have changed their names on SfListView/SfListViewExt. We don't use them in our standard XAMLs. But if you use them in customizings, please refer to https://help.syncfusion.com/maui/listview/migration for the complete list.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
SfListViewExt:
* ItemHolding
</syntaxhighlight>
| ItemLongPress
|}

=== Syncfusion control updates ===
{| class="wikitable"
! Xamarin
! MAUI
|-
| * LeftSwipeTemplate, RightSwipeTemplate
| StartSwipeTemplate, EndSwipeTemplate
|}

=== Layout name change ===
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
* <sync:SfListView.LayoutManager>
</syntaxhighlight>
| <syntaxhighlight lang="xml">
<sync:SfListView.ItemsLayout>
</syntaxhighlight>
|}

=== TemplateService binding for extracted templates ===
'''1. We need to add the following namespace where the changes are applied:
xmlns:services="clr-namespace:UBIK.MAUI.Services;assembly=UBIK.MAUI";
2. We need to search for both "StaticResource" and "DynamicResource";
3. We only listed some examples here. But the same rule applies to all those templates exacted from UBIKThemes (see the first "Recommended" point).'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| {StaticResource UBIKChildItem}
| {Binding [UBIKChildItem], Source={x:Static services:TemplateService.Instance}}
|-
| {StaticResource UBIKDocumentItem}
| {Binding [UBIKDocumentItem], Source={x:Static services:TemplateService.Instance}}
|-
| {StaticResource UBIKMainItem}
| {Binding [UBIKMainItem], Source={x:Static services:TemplateService.Instance}}
|}

=== OnPlatform and OnIdiom syntax changes ===
'''All code containing the OnPlatform and OnIdiom functionalities needs to be refactored as the syntax changed. It is recommended to use the inline syntax (see example) as a default wherever possible, but there are also other approaches.
When using Bindings, Resources or other complex values in OnIdiom or OnPlatform values, it should only be used with the inline syntax.
Please rely to the wiki for more details and possibilities (e.g. if the value contains multiple elements): https://wiki.augmensys.com/index.php?title=XAML_Tips#Platform_and_Device-specific_UI_with_OnPlatform_and_OnIdiom'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| OnPlatform
| <syntaxhighlight lang="xml">
<TheControl
...
TheProperty="{OnPlatform Android=False, iOS=True}" />

<TheControl
...
TheProperty="{OnPlatform Android={Binding ...}, iOS={Binding ...}}" />
</syntaxhighlight>

|-
| OnIdiom
| <syntaxhighlight lang="xml">
<TheControl
...
TheProperty="{OnIdiom Phone=False, Desktop=True}" />

<TheControl
...
TheProperty="{OnIdiom Desktop={Binding ...}, Phone={Binding ...}}" />
</syntaxhighlight>
|-
| WinPhone
| WinUI
|-
| <syntaxhighlight lang="xml">
e.g.
<ColumnDefinition.Width>
<OnIdiom
...
Desktop="Auto"
Phone="*" />
</ColumnDefinition.Width>
or
<RowDefinition.Height>
<OnPlatform
...
Android="Auto"
iOS="*" />
</RowDefinition.Height>
</syntaxhighlight>
| <syntaxhighlight lang="xml">
<ColumnDefinition Width="{OnIdiom Desktop='Auto', Phone='*'}" />

<RowDefinition Height="{OnPlatform Android='Auto', iOS='*'}" />
</syntaxhighlight>
|}

=== Syncfusion control updates ===
'''It is necessary to use the default Binding with the Source reference to the parent control instead of TemplateBinding when using a SfListViewExt ControlTemplate with selectable items in the ResourceDictionary to be set in the ContentView DataTrigger. Otherwise, the pre-selected items might not appear selected anymore according to our experience.

Affected standard Xamls are:
- UBIKEditDouble
- UBIKEditInt
- UBIKEditString
- UBIKEditMinMax
(For the exact syntax please refer to our latest standard Xamls.)

If the above explained is also used in any custom Xamls, please consider changing it there, too.

However, the problem only seems to occur if there is TemplateBinding in the ItemsSource & SelectedItem property. But, for example, if the TemplateBinding is only in the BindingContext property of the SfListViewExt (like it is the case in the UBIKPropertyDirectEditListPopup), there seems to be no such problem and therefore no change is necessary.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
<ContentView
...
x:Name="YourContentViewName">

<ContentView.Resources>
<ResourceDictionary>
...
<ControlTemplate x:Key="YourTemplateKey">
<ctrls:SfListViewExt
ItemsSource="{TemplateBinding BindingContext.YourBinding,
...}"
SelectedItem="{TemplateBinding BindingContext.YourBinding,
...}"
... />
</ControlTemplate>
...
</ResourceDictionary>
</ContentView.Resources>

...
</ContentView>
</syntaxhighlight>
| <syntaxhighlight lang="xml">
<ContentView
...
x:Name="YourContentViewName">

<ContentView.Resources>
<ResourceDictionary>
...
<ControlTemplate x:Key="YourTemplateKey">
<ctrls:SfListViewExt
ItemsSource="{Binding BindingContext.YourBinding,
Source={x:Reference YourContentViewName},
...}"
SelectedItem="{Binding BindingContext.YourBinding,
Source={x:Reference YourContentViewName},
...}"
... />
</ControlTemplate>
...
</ResourceDictionary>
</ContentView.Resources>

...
</ContentView>
</syntaxhighlight>
|}

=== Remove default ControlTemplate in DataTriggers ===
'''To prevent an issue on Android where the direct edit Link to Object editor does not open, there is a change necessary in the UBIKPropertyDirectEditListPopup Xaml:
The default ControlTemplate needs to be removed from the ContentView that contains the DataTriggers.

According to our experience, this issue only occurs to our UBIKPropertyDirectEditListPopup standard Xaml, but we can't guarantee that there is no such issue in customized Xamls.
So please, if you encounter an issue on Android where a Property Editor doesn't open, report it the mobile development team, and/or try removing the default ControlTemplate from the affected control.

In our standard Xamls, we removed the default ControlTemplate in every ContentView that contains DataTriggers with ControlTemplates where the same template is already set in a DataTrigger. So please, also remove the default ControlTemplates it in the following Xamls if you use customized ones:
- UBIKEditDouble
- UBIKEditInt
- UBIKEditString
- UBIKEditMinMax
(For the exact syntax please refer to our latest standard Xamls.)

If the above explained is also used in any of your other custom Xamls, please consider changing it there, too. Otherwise, some property editor might not open.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
<ContentView x:Name="containerName" ControlTemplate="{StaticResource YourTemplate}">
<ContentView.Triggers>
<DataTrigger
Binding="{Binding Source={x:Reference containerName}, Path=...}"
TargetType="ContentView"
Value="true">
<Setter Property="ControlTemplate"
Value="{StaticResource YourTemplate}" />
</DataTrigger>
...
</ContentView.Triggers>
</ContentView>
</syntaxhighlight>
| <syntaxhighlight lang="xml">
<ContentView x:Name="containerName">
<ContentView.Triggers>
<DataTrigger
Binding="{Binding Source={x:Reference containerName}, Path=...}"
TargetType="ContentView"
Value="true">
<Setter Property="ControlTemplate"
Value="{StaticResource YourTemplate}" />
</DataTrigger>
...
</ContentView.Triggers>
</ContentView>
</syntaxhighlight>
|}

=== Remove HeadlessLayout style ===
'''This Style has no longer any effect in MAUI and even degrades app performance. We are keeping it in our standard UBIKThemes under the Obsolete section to maintain backward compatibility.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
<Style x:Key="HeadlessLayout" TargetType="Layout">
<Setter Property="CompressedLayout.IsHeadless" Value="{OnPlatform False, Android=True}" />
</Style>
</syntaxhighlight>
| Delete it from your custom UBIKThemes file
|}

=== Additional mandatory rule ===
'''In the customizings, however, it can and should be removed entirely, as it negatively affects performance, as mentioned before. To remove the style, you can simply use VS Code or any other editor with a search function and look through all custom .xaml files for usages of {StaticResource HeadlessLayout} or {DynamicResource HeadlessLayout}. These references should be removed from the respective elements or controls.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
<ContentView
Grid.Column="2"
ControlTemplate="{DynamicResource ChildCountBadge}"
HorizontalOptions="Start"
Style="{DynamicResource HeadlessLayout}"
VerticalOptions="Start" />
</syntaxhighlight>
| <syntaxhighlight lang="xml">
<ContentView
Grid.Column="2"
ControlTemplate="{DynamicResource ChildCountBadge}"
HorizontalOptions="Start"
VerticalOptions="Start" />
</syntaxhighlight>
|}

=== Avoid multiple SfPullToRefresh controls ===
'''To prevent an issue that causes the app to freeze, avoid placing more then 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 a e.g. a DataTrigger to set one of them as the ControlTemplate of a ContentControl inside the SfPullToRefresh control

{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
<pullToRefresh:SfPullToRefresh IsVisible = {Binding ShowContentB, Converter={StaticResource BoolToNotBool}}>
<pullToRefresh:SfPullToRefresh.PullableContent>
<Grid x:Name="ContentA"/>
</pullToRefresh:SfPullToRefresh.PullableContent>
</pullToRefresh:SfPullToRefresh>

<pullToRefresh:SfPullToRefresh IsVisible = {Binding ShowContentB}>
<pullToRefresh:SfPullToRefresh.PullableContent>
<Grid x:Name="ContentB"/>
</pullToRefresh:SfPullToRefresh.PullableContent>
</pullToRefresh:SfPullToRefresh>
</syntaxhighlight>
| <syntaxhighlight lang="xml">
<Grid>
<Grid.Resources>
<ResourceDictionary>
<DataTemplate x:Key="TemplateA">
<Grid x:Name="ContentA"/>
</DataTemplate>
<DataTemplate x:Key="TemplateB">
<Grid x:Name="ContentB"/>
</DataTemplate>
</ResourceDictionary>
</Grid.Resources>
<pullToRefresh:SfPullToRefresh>
<pullToRefresh:SfPullToRefresh.PullableContent>
<controls:ContentControl ContentTemplate="{DynamicResource TemplateA}">
<controls:ContentControl.Triggers>
<DataTrigger
Binding="{Binding ShowContentB}}"
TargetType="controls:ContentControl"
Value="true">
<Setter Property="ContentTemplate" Value="{DynamicResource TemplateB}" />
</DataTrigger>
</controls:ContentControl.Triggers>
</controls:ContentControl>
</pullToRefresh:SfPullToRefresh.PullableContent>
</pullToRefresh:SfPullToRefresh>
</Grid>
</syntaxhighlight>
|}

=== Rename SfPullToRefresh properties ===
'''Renamed in Maui, however, currently these properties cause an issue and should not be included in customizings.'''
SfPullToRefresh:
{| class="wikitable"
! Xamarin
! MAUI
|-
| RefreshContentHeight, RefreshContentWidth
| RefreshViewHeight, RefreshViewWidth
|}

=== Rename progress colors ===
'''Renamed in Maui.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| ProgressBackgroundColor, ProgressStrokeColor
| ProgressBackground, ProgressColor
|}

[[Category:How-To|Convert Xamarin XAMLs to Maui]]
[[Category:MAUI|Convert Xamarin XAMLs to Maui]]
[[Category:XAML|Convert Xamarin XAMLs to Maui]]

== SfTabView ==

=== Namespace Update ===
'''Update Syncfusion TabView namespace.'''
Replace the Xamarin namespace with the MAUI equivalent.

{| class="wikitable"
! Xamarin
! MAUI
|-
| clr-namespace:Syncfusion.XForms.TabView;assembly=Syncfusion.SfTabView.XForms
| clr-namespace:Syncfusion.Maui.Toolkit.TabView;assembly=Syncfusion.Maui.Toolkit
|}

=== Remove Obsolete Converters ===
'''Remove ItemCountToBoolConverter from Resources.'''
This converter is no longer usable in TabView headers.

{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml"><converters:ItemCountToBoolConverter x:Key="ItemCountToBool" /></syntaxhighlight>
| [remove]
|}

=== Add StringFormatConverter ===
'''Use StringFormatConverter for combined header strings.'''
Syncfusion MAUI TabView uses a single `Header` property instead of templates.
For all tab headers, formatters should be specified to assemble the text. As a best practice, even for simple header strings.

{| class="wikitable"
! Xamarin
! MAUI
|-
| [template-based header]
| <syntaxhighlight lang="xml"><converters:StringFormatConverter x:Key="ChildrenTabFormatter" Parameter1="{resources:Translate ChildrenTitle}" /></syntaxhighlight>
|}

In the above example, a previously defined formatter (that must be also added to the resource dictionary) is used to fill in the header attribute value.
⚠️ Avoid using bindings in `Parameter1` and `Parameter2` — use static strings only. For complex cases, use `EvalExpression`.

[[Category:How-To|Convert Xamarin XAMLs to Maui]]
[[Category:MAUI|Convert Xamarin XAMLs to Maui]]
[[Category:XAML|Convert Xamarin XAMLs to Maui]]

=== FontImageSource Styling ===
'''Add local style for FontImageSource.'''
Global styles are not supported.

{| class="wikitable"
! Xamarin
! MAUI
|-
| [global FontImageSource style]
| <syntaxhighlight lang="xml">
<Style TargetType="FontImageSource">
<Setter Property="FontFamily" Value="{DynamicResource UBIKSymbols}" />
<Setter Property="Color" Value="{DynamicResource UBIKLightThemeColor}" />
</Style>
</syntaxhighlight>
|}

=== TabView Structure ===
'''Use Grid to wrap TabView.'''
MAUI TabView requires a different structure and property set.

{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
<tabView:SfTabView VisibleHeaderCount="3">
...
</tabView:SfTabView>
</syntaxhighlight>
| <syntaxhighlight lang="xml">
<Grid>
<tabView:SfTabView>
<tabView:SfTabItem Header="string example header">
<tabView:SfTabItem.ImageSource>
<FontImageSource Glyph="{x:Static resources:UBIKIcons.XXX}" />
</tabView:SfTabItem.ImageSource>
<tabView:SfTabItem.Content>
<controls:UBIKContentView x:Name="ChildContainer" Converter="{StaticResource ChildAreaTemplateConverter}" />
</tabView:SfTabItem.Content>
</tabView:SfTabItem>
</tabView:SfTabView>
</Grid>
</syntaxhighlight>
|}

=== Property Changes ===
'''Update renamed or removed properties.'''

{| class="wikitable"
! Xamarin
! MAUI
|-
| VisibleHeaderCount
| [not available yet]
|-
| UBIKCenterButtonSettings
| CenterButtonSettings
|-
| SelectionIndicatorSettings
| IndicatorPlacement, IndicatorStrokeThickness, IndicatorBackground
|-
| SelectionColor
| Use VisualStateManager instead
|}

⚠️ Refer to [https://help.syncfusion.com/maui/tabview/migration Syncfusion migration guide] for full property list.

== OnPlatform + OnIdiom backup ==

=== Syntax Changes ===
'''Use inline or multi-tag syntax.'''
Single-tag syntax is outdated and may not build.

{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml"><OnPlatform Android="False" iOS="True" /></syntaxhighlight>
| <syntaxhighlight lang="xml"><TheControl TheProperty="{OnPlatform Android=False, iOS=True}" /></syntaxhighlight>
|}

{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
<OnPlatform x:TypeArguments="TheType">
<On Platform="Android" Value="False" />
<On Platform="iOS" Value="True" />
</OnPlatform>
</syntaxhighlight>
| Required for multi-tag syntax
|}

=== WinPhone to WinUI ===
'''Replace WinPhone with WinUI.'''

{| class="wikitable"
! Xamarin
! MAUI
|-
| WinPhone
| WinUI
|}

=== GridLength and TypeArguments ===
'''Avoid x:TypeArguments with GridLength.'''

{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
<ColumnDefinition.Width>
<OnIdiom x:TypeArguments="GridLength" Desktop="Auto" Phone="*" />
</ColumnDefinition.Width>
</syntaxhighlight>
| <syntaxhighlight lang="xml"><ColumnDefinition Width="{OnIdiom Desktop='Auto', Phone='*'}" /></syntaxhighlight>
|}

⚠️ Inline syntax is more reliable when using bindings or resources.

=== Special Characters ===
'''Wrap values in quotes if they contain commas or strings.'''

{| class="wikitable"
! Xamarin
! MAUI
|-
| Margin={OnIdiom 10,2, Phone=2,0}
| Margin={OnIdiom '10,2', Phone='2,0'}
|}

=== UWP to WinUI ===
'''Replace UWP with WinUI in all OnPlatform scopes.'''

{| class="wikitable"
! Xamarin
! MAUI
|-
| UWP
| WinUI
|}

⚠️ For more details, refer to the [https://wiki.augmensys.com/index.php?title=XAML_Tips#Device_and_Platform_Responsiveness Wiki documentation].

[[Category:How-To|Convert Xamarin XAMLs to Maui]]
[[Category:MAUI|Convert Xamarin XAMLs to Maui]]
[[Category:XAML|Convert Xamarin XAMLs to Maui]]

HowTo:Convert Xamarin XAMLs to Maui

2025-08-05T12:48:18Z

LKR: /* Avoid multiple SfPullToRefresh controls */

== Information ==
=== Frame to Border ===
'''Use Border instead of Frame.'''
Frame is deprecated in MAUI. Use Border with `Stroke` instead of `BorderColor`.

{| class="wikitable"
! Xamarin
! MAUI
|-
| <Frame ... />
| <Border ... />
|}

=== LayoutOptions with "...AndExpand" ===
'''Replace "...AndExpand" with Grid layout.'''
Horizontal/VerticalOptions ending in "...AndExpand" are deprecated. Use Grid with `ColumnDefinition Width="*"` for expansion.

=== GlyphLabel and Styles ===
'''Use Label with new styles.'''
Custom controls like `GlyphLabel` are no longer needed. Use `Label` with styles like `UBIKSymbolText`.

{| class="wikitable"
! Xamarin
! MAUI
|-
| controls:GlyphLabel
| Label with UBIKSymbolText style
|}

=== SfTabView Virtualization ===
'''Enable virtualization.'''
Add `EnableVirtualization="True"` to all SfTabView instances or styles.

=== Swipe Menu Icons on Android ===
'''Refactor swipe templates and label styles.'''
Icons in swipe menus were truncated on Android. Fixed via refactoring.

=== Color Style Changes ===
'''Dark theme adjustments.'''
Changes to color styles may affect appearance. Review usage of `UBIKDarkThemeColor`, `UBIKDarkTextColor`, etc.

=== Strikethrough Converter ===
'''Use `TextDecorations="Strikethrough"` instead of converter.'''

{| class="wikitable"
! Xamarin
! MAUI
|-
| Text="{Binding ..., Converter={StaticResource StrikethroughConverter}}"
| Text="{Binding ...}" TextDecorations="Strikethrough"
|}

=== Button Disabled Trigger ===
'''Add trigger for disabled buttons.'''
Maui buttons don’t visually change when disabled. Add trigger to style.

=== TapGestureRecognizer Replacement ===
'''Use TappedBehavior instead.'''
TapGestureRecognizer now intercepts taps. Use `TappedBehavior` to avoid conflicts.

{| class="wikitable"
! Xamarin
! MAUI
|-
| <... .GestureRecognizers><TapGestureRecognizer Command="{Binding ...}" /></... .GestureRecognizers>
| <... .Behaviors><behaviors:TappedBehavior><behaviors:InvokeCommandAction Command="{Binding ...}" /></behaviors:TappedBehavior></... .Behaviors>
|}

=== TapGestureRecognizer and Swipe Conflict ===
'''Remove TapGestureRecognizer from root Grid.'''
TapGestureRecognizer blocks swipe behavior. Remove it and adapt parent list to trigger navigation.

=== Navigation in UBIKChildItem ===
'''Use EventHandlerBehavior for navigation.'''

{| class="wikitable"
! Xamarin
! MAUI
|-
| [none]
| <controls:SfListViewExt.Behaviors><behaviors:EventHandlerBehavior EventName="ItemTapped"><behaviors:InvokeCommandAction Command="{Binding AppStatus.RootList.Items[0].NavigateToChildrenCommand}" /></behaviors:EventHandlerBehavior></controls:SfListViewExt.Behaviors>
|}
== Recommended ==
=== Extract DataTemplates from UBIKThemes ===
'''Create separate .xamlx files for the following DataTemplates.'''
It's not so easy about the namespaces:
* In our default templates, it's enough to add the following ones to every new separate .xamlx files at the beginning;
* xmlns:ctrls="clr-namespace:UBIK.MAUI.Controls;assembly=UBIK.MAUI";
* xmlns:platform="clr-namespace:UBIK.MAUI.Platform.Renderers;assembly=UBIK.MAUI";
* xmlns:resources="clr-namespace:UBIK.MAUI.Resources;assembly=UBIK.MAUI";
* xmlns:services="clr-namespace:UBIK.MAUI.Services;assembly=UBIK.MAUI";
* xmlns:uiservices="clr-namespace:UBIK.UI.Services;assembly=UBIK.UI".
* But we don't know if other namespaces might be used in the custom templates. So it might be necessary to really analyze the namespaces used and find/copy them from the UBIKThemes file.
{| class="wikitable"
!   !! Templates !!  
|-
| UBIKMainItem || UBIKChildItem || UBIKTaskItem
|-
| UBIKTaskProperty || UBIKTaskPropertyString || UBIKTaskPropertyDouble
|-
| UBIKTaskPropertyInt || UBIKTaskPropertyNumeric || UBIKTaskPropertyDateTime
|-
| UBIKTaskPropertyGeoData || UBIKTaskPropertyBool || UBIKTaskPropertyPopup
|-
| UBIKTaskPropertyList || UBIKTaskPropertyGuid || UBIKPropertyItem
|-
| UBIKPropertyTextLengthHint || UBIKPropertyDirectEditButtons || UBIKTaskPropertyEditButtons
|-
| UBIKPropertyDirectItemString || UBIKPropertyDirectItemDouble || UBIKPropertyDirectItemInt
|-
| UBIKPropertyDirectItemMinMax || UBIKPropertyDirectItemNumeric || UBIKPropertyDirectItemDateTime
|-
| UBIKPropertyDirectItemGeoData || UBIKPropertyDirectItemBool || UBIKPropertyDirectItemPopup
|-
| UBIKPropertyDirectItemList || UBIKPropertyDirectItemGuid || UBIKDocumentItem
|-
| UBIKSearchResultItem || UBIKDefaultHotSpot || UBIKAngularLinkHotSpot
|-
| UBIKRoundLinkHotSpot || UBIKInputHotSpot || UBIKSignatureHotSpot
|-
| UBIKObjectHotSpot || UBIKMediaHotSpot ||
|}
=== VideoPlayer Adjustments ===
'''This property is repsonsible for the video player regarding how or if it should get scaled up depending on the value of the
Aspect property'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">VideoPlayer...</syntaxhighlight>
| <syntaxhighlight lang="xml">VideoPlayer Aspect="AspectFit"</syntaxhighlight>
|}

'''The UriToVideoSourceConverter is no longer needed because the conversion of the
VideoSource gets done by the MediaElement itself. It is marked as obsolete and should therefore no longer be used.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml"><controls:VideoPlayer... Source="{Binding DocumentViewModel.LocalURI, Converter={StaticResource UriToVideoSource}}"/></syntaxhighlight>
| <syntaxhighlight lang="xml"><controls:VideoPlayer... Source="{Binding DocumentViewModel.LocalURI}"/></syntaxhighlight>
|}

'''The StopTimer property is obsolete and no longer needed because the MediaElement behind does the Stop of the VideoPlayer
by itself.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml"><controls:VideoPlayer... StopTimer="{Binding Unloaded}" /></syntaxhighlight>
| <syntaxhighlight lang="xml"><controls:VideoPlayer... /></syntaxhighlight>
|}
=== SearchBar Style Fix on iOS ===
'''On iOS, defining a transparent background for the SearchBar control results in a black text on black background appearance.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">[issue on iOS only] UBIKThemes: SearchBar style: <Setter Property="BackgroundColor" Value="Transparent" /></syntaxhighlight>
| <syntaxhighlight lang="xml">Delete this setter</syntaxhighlight>
|}
=== Avoid Redundant ControlTemplate in DataTriggers ===
'''This is about finding ControlTemplates that are set in DataTriggers in customized Xamls. When the same template is already set as a ContentView default ControlTemplate, it is recommended to remove the default ControlTemplate on the ContentView. For a detailed description please refer to sheet "Mandatory" in cell 27A-27C.
Behavior that might occur if it remains unchanged: Property editor might not open on Android.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml"><ContentView x:Name="containerName" ControlTemplate="{StaticResource YourTemplate1}">
<ContentView.Triggers>
<DataTrigger
Binding="{Binding Source={x:Reference containerName}, Path=...}"
TargetType="ContentView"
Value="true">
<Setter Property="ControlTemplate"
Value="{StaticResource YourTemplate1}" />
</DataTrigger>
...
</ContentView.Triggers>
</ContentView></syntaxhighlight>
| <syntaxhighlight lang="xml"><ContentView x:Name="containerName">
<ContentView.Triggers>
<DataTrigger
Binding="{Binding Source={x:Reference containerName}, Path=...}"
TargetType="ContentView"
Value="true">
<Setter Property="ControlTemplate"
Value="{StaticResource YourTemplate1}" />
</DataTrigger>
...
</ContentView.Triggers>
</ContentView></syntaxhighlight>
|}
=== Replace TemplateBinding with Binding and Source ===
'''This is about finding SfListViewExt controls in customizings, and if there are TemplateBindings used, it's recommended to replace them with Binding, and the Source reference should be added. For a detailed description please refer to sheet "Mandatory" in cell 26A-26C.
Behavior that might occur if it remains unchanged: Pre-selected item might appear unselected.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml"><ContentView
...
x:Name="YourContentViewName">

<ContentView.Resources>
<ResourceDictionary>
...
<ControlTemplate x:Key="YourTemplateKey">
<ctrls:SfListViewExt
ItemsSource="{TemplateBinding BindingContext.YourBinding,
...}"
SelectedItem="{TemplateBinding BindingContext.YourBinding,
...}"
... />
</ControlTemplate>
...
</ResourceDictionary>
</ContentView.Resources>

...
</ContentView></syntaxhighlight>
| <syntaxhighlight lang="xml"><ContentView
...
x:Name="YourContentViewName">

<ContentView.Resources>
<ResourceDictionary>
...
<ControlTemplate x:Key="YourTemplateKey">
<ctrls:SfListViewExt
ItemsSource="{Binding BindingContext.YourBinding,
Source={x:Reference YourContentViewName},
...}"
SelectedItem="{Binding BindingContext.YourBinding,
Source={x:Reference YourContentViewName},
...}"
... />
</ControlTemplate>
...
</ResourceDictionary>
</ContentView.Resources>

...
</ContentView></syntaxhighlight>
|}
=== Remove TapGestureRecognizer from Main Item ===
'''Swiping on the Main items was broken by Maui (Documented in Information). The workaround is to remove the TapGestureRecognizer from UBIKMainItem, and add ListView-based navigation similar to that found in UBIKChildArea (with an extended binding path for technical reasons).'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">(In UBIKMainItem)
<Grid.GestureRecognizers>
<TapGestureRecognizer Command="{Binding NavigateToChildrenCommand}" />
</Grid.GestureRecognizers></syntaxhighlight>
| <syntaxhighlight lang="xml">[nothing]</syntaxhighlight>
|}
=== Add Navigation Behavior in Child Area ===
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">(In UBIKChildArea)
[nothing]</syntaxhighlight>
| <syntaxhighlight lang="xml"><controls:SfListViewExt.Behaviors>
<behaviors:EventHandlerBehavior EventName="ItemTapped">
<behaviors:InvokeCommandAction Command="{Binding AppStatus.RootList.Items[0].NavigateToChildrenCommand}" />
</behaviors:EventHandlerBehavior>
</controls:SfListViewExt.Behaviors></syntaxhighlight>
|}
== Highly Recommended ==
=== CircularImage to AvatarView ===
'''Use AvatarView instead of CircularImage.'''
CircularImage and its wrapping Frame are no longer needed. Use AvatarView from the MAUI Community Toolkit. Add the namespace:
<syntaxhighlight lang="xml">
xmlns:toolkit="http://schemas.microsoft.com/dotnet/2022/maui/toolkit"
</syntaxhighlight>

{| class="wikitable"
! Xamarin
! MAUI
|-
| <Frame><CircularImage Source="..." /></Frame>
| <toolkit:AvatarView ImageSource="..." BorderWidth="..." BackgroundColor="..." />
|}

=== GlyphSize to FontSize and Alignment ===
'''Use FontSize and alignment properties instead of GlyphSize.'''
The GlyphSize property is obsolete. Use FontSize and add alignment properties for better layout.

{| class="wikitable"
! Xamarin
! MAUI
|-
| <Setter Property="GlyphSize" Value="13.0" />
| <Setter Property="FontSize" Value="16" /><br/><Setter Property="VerticalOptions" Value="Center" /><br/><Setter Property="HorizontalOptions" Value="Center" /><br/><Setter Property="VerticalTextAlignment" Value="Center" /><br/><Setter Property="HorizontalTextAlignment" Value="Center" />
|}

=== StaticResource to DynamicResource ===
'''Use DynamicResource and BaseResourceKey.'''
For dynamic theming, use DynamicResource instead of StaticResource. When inheriting styles, use BaseResourceKey.

{| class="wikitable"
! Xamarin
! MAUI
|-
| BasedOn="{StaticResource SomeStyle}"<br/>Style="{StaticResource SomeStyle}"
| BaseResourceKey="SomeStyle"<br/>Style="{DynamicResource SomeStyle}"
|}
== Mandatory ==

=== Namespace conversion ===
'''Update all namespaces to MAUI equivalents.'''
All `xmlns` and `clr-namespace` declarations must be updated to their MAUI counterparts.

{| class="wikitable"
! Xamarin
! MAUI
|-
| xmlns="http://xamarin.com/schemas/2014/forms"
| xmlns="http://schemas.microsoft.com/dotnet/2021/maui"
|-
| clr-namespace:Xamarin.Forms.PlatformConfiguration.AndroidSpecific;assembly=Xamarin.Forms.Core
| clr-namespace:Microsoft.Maui.Controls.PlatformConfiguration.AndroidSpecific;assembly=Microsoft.Maui.Controls
|-
| clr-namespace:UBIK.CPL.Behaviors;assembly=UBIK.CPL
| clr-namespace:UBIK.MAUI.Behaviors;assembly=UBIK.MAUI
|-
| clr-namespace:UBIK.CPL.Classes;assembly=UBIK.CPL
| clr-namespace:UBIK.MAUI.Classes;assembly=UBIK.MAUI
|-
| clr-namespace:UBIK.CPL.Controls;assembly=UBIK.CPL
| clr-namespace:UBIK.MAUI.Controls;assembly=UBIK.MAUI
|-
| clr-namespace:UBIK.CPL.Converters;assembly=UBIK.CPL
| clr-namespace:UBIK.MAUI.Converters;assembly=UBIK.MAUI
|-
| clr-namespace:UBIK.CPL.Platform.Renderers;assembly=UBIK.CPL
| clr-namespace:UBIK.MAUI.Platform.Controls;assembly=UBIK.MAUI
|-
| clr-namespace:UBIK.CPL.Services;assembly=UBIK.CPL
| clr-namespace:UBIK.MAUI.Services;assembly=UBIK.MAUI
|-
| clr-namespace:UBIK.CPL.Resources;assembly=UBIK.CPL
| clr-namespace:UBIK.MAUI.Resources;assembly=UBIK.MAUI
|-
| clr-namespace:UBIK.Scanning.Forms;assembly=UBIK.Scanning.Forms
| clr-namespace:UBIK.MAUI.Controls.ZXingScanner;assembly=UBIK.MAUI
|-
| clr-namespace:Syncfusion.SfPullToRefresh.XForms;assembly=Syncfusion.SfPullToRefresh.XForms
| clr-namespace:Syncfusion.Maui.Toolkit.PullToRefresh;assembly=Syncfusion.Maui.Toolkit
|-
| clr-namespace:Syncfusion.XForms.TabView;assembly=Syncfusion.SfTabView.Xforms
| clr-namespace:Syncfusion.Maui.Toolkit.TabView;assembly=Syncfusion.Maui.Toolkit
|-
| clr-namespace:Syncfusion.ListView.XForms;assembly=Syncfusion.SfListView.XForms
| clr-namespace:Syncfusion.Maui.ListView;assembly=Syncfusion.Maui.ListView
|-
| clr-namespace:Syncfusion.XForms.TreeView;assembly=Syncfusion.SfTreeView.XForms
| clr-namespace:Syncfusion.Maui.TreeView;assembly=Syncfusion.Maui.TreeView
|-
| clr-namespace:Syncfusion.XForms.TextInputLayout;assembly=Syncfusion.Core.XForms
| clr-namespace:Syncfusion.Maui.Core;assembly=Syncfusion.Maui.Core
|}

For classes referenced in the XAML code, please don't forget to also replace "CPL" with "MAUI" in the class namespace.

=== Syncfusion control updates ===
'''There are some other properties that have changed their names on SfListView/SfListViewExt. We don't use them in our standard XAMLs. But if you use them in customizings, please refer to https://help.syncfusion.com/maui/listview/migration for the complete list.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
SfListViewExt:
* ItemHolding
</syntaxhighlight>
| ItemLongPress
|}

=== Syncfusion control updates ===
{| class="wikitable"
! Xamarin
! MAUI
|-
| * LeftSwipeTemplate, RightSwipeTemplate
| StartSwipeTemplate, EndSwipeTemplate
|}

=== Layout name change ===
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
* <sync:SfListView.LayoutManager>
</syntaxhighlight>
| <syntaxhighlight lang="xml">
<sync:SfListView.ItemsLayout>
</syntaxhighlight>
|}

=== TemplateService binding for extracted templates ===
'''1. We need to add the following namespace where the changes are applied:
xmlns:services="clr-namespace:UBIK.MAUI.Services;assembly=UBIK.MAUI";
2. We need to search for both "StaticResource" and "DynamicResource";
3. We only listed some examples here. But the same rule applies to all those templates exacted from UBIKThemes (see the first "Recommended" point).'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| {StaticResource UBIKChildItem}
| {Binding [UBIKChildItem], Source={x:Static services:TemplateService.Instance}}
|-
| {StaticResource UBIKDocumentItem}
| {Binding [UBIKDocumentItem], Source={x:Static services:TemplateService.Instance}}
|-
| {StaticResource UBIKMainItem}
| {Binding [UBIKMainItem], Source={x:Static services:TemplateService.Instance}}
|}

=== OnPlatform and OnIdiom syntax changes ===
'''All code containing the OnPlatform and OnIdiom functionalities needs to be refactored as the syntax changed. It is recommended to use the inline syntax (see example) as a default wherever possible, but there are also other approaches.
When using Bindings, Resources or other complex values in OnIdiom or OnPlatform values, it should only be used with the inline syntax.
Please rely to the wiki for more details and possibilities (e.g. if the value contains multiple elements): https://wiki.augmensys.com/index.php?title=XAML_Tips#Platform_and_Device-specific_UI_with_OnPlatform_and_OnIdiom'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| OnPlatform
| <syntaxhighlight lang="xml">
<TheControl
...
TheProperty="{OnPlatform Android=False, iOS=True}" />

<TheControl
...
TheProperty="{OnPlatform Android={Binding ...}, iOS={Binding ...}}" />
</syntaxhighlight>

|-
| OnIdiom
| <syntaxhighlight lang="xml">
<TheControl
...
TheProperty="{OnIdiom Phone=False, Desktop=True}" />

<TheControl
...
TheProperty="{OnIdiom Desktop={Binding ...}, Phone={Binding ...}}" />
</syntaxhighlight>
|-
| WinPhone
| WinUI
|-
| <syntaxhighlight lang="xml">
e.g.
<ColumnDefinition.Width>
<OnIdiom
...
Desktop="Auto"
Phone="*" />
</ColumnDefinition.Width>
or
<RowDefinition.Height>
<OnPlatform
...
Android="Auto"
iOS="*" />
</RowDefinition.Height>
</syntaxhighlight>
| <syntaxhighlight lang="xml">
<ColumnDefinition Width="{OnIdiom Desktop='Auto', Phone='*'}" />

<RowDefinition Height="{OnPlatform Android='Auto', iOS='*'}" />
</syntaxhighlight>
|}

=== Syncfusion control updates ===
'''It is necessary to use the default Binding with the Source reference to the parent control instead of TemplateBinding when using a SfListViewExt ControlTemplate with selectable items in the ResourceDictionary to be set in the ContentView DataTrigger. Otherwise, the pre-selected items might not appear selected anymore according to our experience.

Affected standard Xamls are:
- UBIKEditDouble
- UBIKEditInt
- UBIKEditString
- UBIKEditMinMax
(For the exact syntax please refer to our latest standard Xamls.)

If the above explained is also used in any custom Xamls, please consider changing it there, too.

However, the problem only seems to occur if there is TemplateBinding in the ItemsSource & SelectedItem property. But, for example, if the TemplateBinding is only in the BindingContext property of the SfListViewExt (like it is the case in the UBIKPropertyDirectEditListPopup), there seems to be no such problem and therefore no change is necessary.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
<ContentView
...
x:Name="YourContentViewName">

<ContentView.Resources>
<ResourceDictionary>
...
<ControlTemplate x:Key="YourTemplateKey">
<ctrls:SfListViewExt
ItemsSource="{TemplateBinding BindingContext.YourBinding,
...}"
SelectedItem="{TemplateBinding BindingContext.YourBinding,
...}"
... />
</ControlTemplate>
...
</ResourceDictionary>
</ContentView.Resources>

...
</ContentView>
</syntaxhighlight>
| <syntaxhighlight lang="xml">
<ContentView
...
x:Name="YourContentViewName">

<ContentView.Resources>
<ResourceDictionary>
...
<ControlTemplate x:Key="YourTemplateKey">
<ctrls:SfListViewExt
ItemsSource="{Binding BindingContext.YourBinding,
Source={x:Reference YourContentViewName},
...}"
SelectedItem="{Binding BindingContext.YourBinding,
Source={x:Reference YourContentViewName},
...}"
... />
</ControlTemplate>
...
</ResourceDictionary>
</ContentView.Resources>

...
</ContentView>
</syntaxhighlight>
|}

=== Remove default ControlTemplate in DataTriggers ===
'''To prevent an issue on Android where the direct edit Link to Object editor does not open, there is a change necessary in the UBIKPropertyDirectEditListPopup Xaml:
The default ControlTemplate needs to be removed from the ContentView that contains the DataTriggers.

According to our experience, this issue only occurs to our UBIKPropertyDirectEditListPopup standard Xaml, but we can't guarantee that there is no such issue in customized Xamls.
So please, if you encounter an issue on Android where a Property Editor doesn't open, report it the mobile development team, and/or try removing the default ControlTemplate from the affected control.

In our standard Xamls, we removed the default ControlTemplate in every ContentView that contains DataTriggers with ControlTemplates where the same template is already set in a DataTrigger. So please, also remove the default ControlTemplates it in the following Xamls if you use customized ones:
- UBIKEditDouble
- UBIKEditInt
- UBIKEditString
- UBIKEditMinMax
(For the exact syntax please refer to our latest standard Xamls.)

If the above explained is also used in any of your other custom Xamls, please consider changing it there, too. Otherwise, some property editor might not open.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
<ContentView x:Name="containerName" ControlTemplate="{StaticResource YourTemplate}">
<ContentView.Triggers>
<DataTrigger
Binding="{Binding Source={x:Reference containerName}, Path=...}"
TargetType="ContentView"
Value="true">
<Setter Property="ControlTemplate"
Value="{StaticResource YourTemplate}" />
</DataTrigger>
...
</ContentView.Triggers>
</ContentView>
</syntaxhighlight>
| <syntaxhighlight lang="xml">
<ContentView x:Name="containerName">
<ContentView.Triggers>
<DataTrigger
Binding="{Binding Source={x:Reference containerName}, Path=...}"
TargetType="ContentView"
Value="true">
<Setter Property="ControlTemplate"
Value="{StaticResource YourTemplate}" />
</DataTrigger>
...
</ContentView.Triggers>
</ContentView>
</syntaxhighlight>
|}

=== Remove HeadlessLayout style ===
'''This Style has no longer any effect in MAUI and even degrades app performance. We are keeping it in our standard UBIKThemes under the Obsolete section to maintain backward compatibility.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
<Style x:Key="HeadlessLayout" TargetType="Layout">
<Setter Property="CompressedLayout.IsHeadless" Value="{OnPlatform False, Android=True}" />
</Style>
</syntaxhighlight>
| Delete it from your custom UBIKThemes file
|}

=== Additional mandatory rule ===
'''In the customizings, however, it can and should be removed entirely, as it negatively affects performance, as mentioned before. To remove the style, you can simply use VS Code or any other editor with a search function and look through all custom .xaml files for usages of {StaticResource HeadlessLayout} or {DynamicResource HeadlessLayout}. These references should be removed from the respective elements or controls.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
<ContentView
Grid.Column="2"
ControlTemplate="{DynamicResource ChildCountBadge}"
HorizontalOptions="Start"
Style="{DynamicResource HeadlessLayout}"
VerticalOptions="Start" />
</syntaxhighlight>
| <syntaxhighlight lang="xml">
<ContentView
Grid.Column="2"
ControlTemplate="{DynamicResource ChildCountBadge}"
HorizontalOptions="Start"
VerticalOptions="Start" />
</syntaxhighlight>
|}

{{UnderConstructionStart}}
=== Avoid multiple SfPullToRefresh controls ===
'''To prevent an issue that causes the app to freeze, avoid placing more then 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 a e.g. a DataTrigger to set one of them as the ControlTemplate of a ContentControl inside the SfPullToRefresh control

{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
<pullToRefresh:SfPullToRefresh IsVisible = {Binding ShowContentB, Converter={StaticResource BoolToNotBool}}>
<pullToRefresh:SfPullToRefresh.PullableContent>
<Grid x:Name="ContentA"/>
</pullToRefresh:SfPullToRefresh.PullableContent>
</pullToRefresh:SfPullToRefresh>

<pullToRefresh:SfPullToRefresh IsVisible = {Binding ShowContentB}>
<pullToRefresh:SfPullToRefresh.PullableContent>
<Grid x:Name="ContentB"/>
</pullToRefresh:SfPullToRefresh.PullableContent>
</pullToRefresh:SfPullToRefresh>
</syntaxhighlight>
| <syntaxhighlight lang="xml">
<Grid>
<Grid.Resources>
<ResourceDictionary>
<DataTemplate x:Key="TemplateA">
<Grid x:Name="ContentA"/>
</DataTemplate>
<DataTemplate x:Key="TemplateB">
<Grid x:Name="ContentB"/>
</DataTemplate>
</ResourceDictionary>
</Grid.Resources>
<pullToRefresh:SfPullToRefresh>
<pullToRefresh:SfPullToRefresh.PullableContent>
<controls:ContentControl ContentTemplate="{DynamicResource TemplateA}">
<controls:ContentControl.Triggers>
<DataTrigger
Binding="{Binding ShowContentB}}"
TargetType="controls:ContentControl"
Value="true">
<Setter Property="ContentTemplate" Value="{DynamicResource TemplateB}" />
</DataTrigger>
</controls:ContentControl.Triggers>
</controls:ContentControl>
</pullToRefresh:SfPullToRefresh.PullableContent>
</pullToRefresh:SfPullToRefresh>
</Grid>
</syntaxhighlight>
|}

[[Category:How-To|Convert Xamarin XAMLs to Maui]]
[[Category:MAUI|Convert Xamarin XAMLs to Maui]]
[[Category:XAML|Convert Xamarin XAMLs to Maui]]

=== Rename SfPullToRefresh properties ===
'''Renamed in Maui, however, currently these properties cause an issue and should not be included in customizings.'''
SfPullToRefresh:
{| class="wikitable"
! Xamarin
! MAUI
|-
| RefreshContentHeight, RefreshContentWidth
| RefreshViewHeight, RefreshViewWidth
|}

=== Rename progress colors ===
'''Renamed in Maui.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| ProgressBackgroundColor, ProgressStrokeColor
| ProgressBackground, ProgressColor
|}

[[Category:How-To|Convert Xamarin XAMLs to Maui]]
[[Category:MAUI|Convert Xamarin XAMLs to Maui]]
[[Category:XAML|Convert Xamarin XAMLs to Maui]]

== SfTabView ==

=== Namespace Update ===
'''Update Syncfusion TabView namespace.'''
Replace the Xamarin namespace with the MAUI equivalent.

{| class="wikitable"
! Xamarin
! MAUI
|-
| clr-namespace:Syncfusion.XForms.TabView;assembly=Syncfusion.SfTabView.XForms
| clr-namespace:Syncfusion.Maui.Toolkit.TabView;assembly=Syncfusion.Maui.Toolkit
|}

=== Remove Obsolete Converters ===
'''Remove ItemCountToBoolConverter from Resources.'''
This converter is no longer usable in TabView headers.

{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml"><converters:ItemCountToBoolConverter x:Key="ItemCountToBool" /></syntaxhighlight>
| [remove]
|}

=== Add StringFormatConverter ===
'''Use StringFormatConverter for combined header strings.'''
Syncfusion MAUI TabView uses a single `Header` property instead of templates.
For all tab headers, formatters should be specified to assemble the text. As a best practice, even for simple header strings.

{| class="wikitable"
! Xamarin
! MAUI
|-
| [template-based header]
| <syntaxhighlight lang="xml"><converters:StringFormatConverter x:Key="ChildrenTabFormatter" Parameter1="{resources:Translate ChildrenTitle}" /></syntaxhighlight>
|}

In the above example, a previously defined formatter (that must be also added to the resource dictionary) is used to fill in the header attribute value.
⚠️ Avoid using bindings in `Parameter1` and `Parameter2` — use static strings only. For complex cases, use `EvalExpression`.

[[Category:How-To|Convert Xamarin XAMLs to Maui]]
[[Category:MAUI|Convert Xamarin XAMLs to Maui]]
[[Category:XAML|Convert Xamarin XAMLs to Maui]]

=== FontImageSource Styling ===
'''Add local style for FontImageSource.'''
Global styles are not supported.

{| class="wikitable"
! Xamarin
! MAUI
|-
| [global FontImageSource style]
| <syntaxhighlight lang="xml">
<Style TargetType="FontImageSource">
<Setter Property="FontFamily" Value="{DynamicResource UBIKSymbols}" />
<Setter Property="Color" Value="{DynamicResource UBIKLightThemeColor}" />
</Style>
</syntaxhighlight>
|}

=== TabView Structure ===
'''Use Grid to wrap TabView.'''
MAUI TabView requires a different structure and property set.

{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
<tabView:SfTabView VisibleHeaderCount="3">
...
</tabView:SfTabView>
</syntaxhighlight>
| <syntaxhighlight lang="xml">
<Grid>
<tabView:SfTabView>
<tabView:SfTabItem Header="string example header">
<tabView:SfTabItem.ImageSource>
<FontImageSource Glyph="{x:Static resources:UBIKIcons.XXX}" />
</tabView:SfTabItem.ImageSource>
<tabView:SfTabItem.Content>
<controls:UBIKContentView x:Name="ChildContainer" Converter="{StaticResource ChildAreaTemplateConverter}" />
</tabView:SfTabItem.Content>
</tabView:SfTabItem>
</tabView:SfTabView>
</Grid>
</syntaxhighlight>
|}

=== Property Changes ===
'''Update renamed or removed properties.'''

{| class="wikitable"
! Xamarin
! MAUI
|-
| VisibleHeaderCount
| [not available yet]
|-
| UBIKCenterButtonSettings
| CenterButtonSettings
|-
| SelectionIndicatorSettings
| IndicatorPlacement, IndicatorStrokeThickness, IndicatorBackground
|-
| SelectionColor
| Use VisualStateManager instead
|}

⚠️ Refer to [https://help.syncfusion.com/maui/tabview/migration Syncfusion migration guide] for full property list.

== OnPlatform + OnIdiom backup ==

=== Syntax Changes ===
'''Use inline or multi-tag syntax.'''
Single-tag syntax is outdated and may not build.

{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml"><OnPlatform Android="False" iOS="True" /></syntaxhighlight>
| <syntaxhighlight lang="xml"><TheControl TheProperty="{OnPlatform Android=False, iOS=True}" /></syntaxhighlight>
|}

{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
<OnPlatform x:TypeArguments="TheType">
<On Platform="Android" Value="False" />
<On Platform="iOS" Value="True" />
</OnPlatform>
</syntaxhighlight>
| Required for multi-tag syntax
|}

=== WinPhone to WinUI ===
'''Replace WinPhone with WinUI.'''

{| class="wikitable"
! Xamarin
! MAUI
|-
| WinPhone
| WinUI
|}

=== GridLength and TypeArguments ===
'''Avoid x:TypeArguments with GridLength.'''

{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
<ColumnDefinition.Width>
<OnIdiom x:TypeArguments="GridLength" Desktop="Auto" Phone="*" />
</ColumnDefinition.Width>
</syntaxhighlight>
| <syntaxhighlight lang="xml"><ColumnDefinition Width="{OnIdiom Desktop='Auto', Phone='*'}" /></syntaxhighlight>
|}

⚠️ Inline syntax is more reliable when using bindings or resources.

=== Special Characters ===
'''Wrap values in quotes if they contain commas or strings.'''

{| class="wikitable"
! Xamarin
! MAUI
|-
| Margin={OnIdiom 10,2, Phone=2,0}
| Margin={OnIdiom '10,2', Phone='2,0'}
|}

=== UWP to WinUI ===
'''Replace UWP with WinUI in all OnPlatform scopes.'''

{| class="wikitable"
! Xamarin
! MAUI
|-
| UWP
| WinUI
|}

⚠️ For more details, refer to the [https://wiki.augmensys.com/index.php?title=XAML_Tips#Device_and_Platform_Responsiveness Wiki documentation].

[[Category:How-To|Convert Xamarin XAMLs to Maui]]
[[Category:MAUI|Convert Xamarin XAMLs to Maui]]
[[Category:XAML|Convert Xamarin XAMLs to Maui]]

HowTo:Convert Xamarin XAMLs to Maui

2025-08-04T12:20:22Z

LKR: /* Mandatory */

== Information ==
=== Frame to Border ===
'''Use Border instead of Frame.'''
Frame is deprecated in MAUI. Use Border with `Stroke` instead of `BorderColor`.

{| class="wikitable"
! Xamarin
! MAUI
|-
| <Frame ... />
| <Border ... />
|}

=== LayoutOptions with "...AndExpand" ===
'''Replace "...AndExpand" with Grid layout.'''
Horizontal/VerticalOptions ending in "...AndExpand" are deprecated. Use Grid with `ColumnDefinition Width="*"` for expansion.

=== GlyphLabel and Styles ===
'''Use Label with new styles.'''
Custom controls like `GlyphLabel` are no longer needed. Use `Label` with styles like `UBIKSymbolText`.

{| class="wikitable"
! Xamarin
! MAUI
|-
| controls:GlyphLabel
| Label with UBIKSymbolText style
|}

=== SfTabView Virtualization ===
'''Enable virtualization.'''
Add `EnableVirtualization="True"` to all SfTabView instances or styles.

=== Swipe Menu Icons on Android ===
'''Refactor swipe templates and label styles.'''
Icons in swipe menus were truncated on Android. Fixed via refactoring.

=== Color Style Changes ===
'''Dark theme adjustments.'''
Changes to color styles may affect appearance. Review usage of `UBIKDarkThemeColor`, `UBIKDarkTextColor`, etc.

=== Strikethrough Converter ===
'''Use `TextDecorations="Strikethrough"` instead of converter.'''

{| class="wikitable"
! Xamarin
! MAUI
|-
| Text="{Binding ..., Converter={StaticResource StrikethroughConverter}}"
| Text="{Binding ...}" TextDecorations="Strikethrough"
|}

=== Button Disabled Trigger ===
'''Add trigger for disabled buttons.'''
Maui buttons don’t visually change when disabled. Add trigger to style.

=== TapGestureRecognizer Replacement ===
'''Use TappedBehavior instead.'''
TapGestureRecognizer now intercepts taps. Use `TappedBehavior` to avoid conflicts.

{| class="wikitable"
! Xamarin
! MAUI
|-
| <... .GestureRecognizers><TapGestureRecognizer Command="{Binding ...}" /></... .GestureRecognizers>
| <... .Behaviors><behaviors:TappedBehavior><behaviors:InvokeCommandAction Command="{Binding ...}" /></behaviors:TappedBehavior></... .Behaviors>
|}

=== TapGestureRecognizer and Swipe Conflict ===
'''Remove TapGestureRecognizer from root Grid.'''
TapGestureRecognizer blocks swipe behavior. Remove it and adapt parent list to trigger navigation.

=== Navigation in UBIKChildItem ===
'''Use EventHandlerBehavior for navigation.'''

{| class="wikitable"
! Xamarin
! MAUI
|-
| [none]
| <controls:SfListViewExt.Behaviors><behaviors:EventHandlerBehavior EventName="ItemTapped"><behaviors:InvokeCommandAction Command="{Binding AppStatus.RootList.Items[0].NavigateToChildrenCommand}" /></behaviors:EventHandlerBehavior></controls:SfListViewExt.Behaviors>
|}
== Recommended ==
=== Extract DataTemplates from UBIKThemes ===
'''Create separate .xamlx files for the following DataTemplates.'''
It's not so easy about the namespaces:
* In our default templates, it's enough to add the following ones to every new separate .xamlx files at the beginning;
* xmlns:ctrls="clr-namespace:UBIK.MAUI.Controls;assembly=UBIK.MAUI";
* xmlns:platform="clr-namespace:UBIK.MAUI.Platform.Renderers;assembly=UBIK.MAUI";
* xmlns:resources="clr-namespace:UBIK.MAUI.Resources;assembly=UBIK.MAUI";
* xmlns:services="clr-namespace:UBIK.MAUI.Services;assembly=UBIK.MAUI";
* xmlns:uiservices="clr-namespace:UBIK.UI.Services;assembly=UBIK.UI".
* But we don't know if other namespaces might be used in the custom templates. So it might be necessary to really analyze the namespaces used and find/copy them from the UBIKThemes file.
{| class="wikitable"
!   !! Templates !!  
|-
| UBIKMainItem || UBIKChildItem || UBIKTaskItem
|-
| UBIKTaskProperty || UBIKTaskPropertyString || UBIKTaskPropertyDouble
|-
| UBIKTaskPropertyInt || UBIKTaskPropertyNumeric || UBIKTaskPropertyDateTime
|-
| UBIKTaskPropertyGeoData || UBIKTaskPropertyBool || UBIKTaskPropertyPopup
|-
| UBIKTaskPropertyList || UBIKTaskPropertyGuid || UBIKPropertyItem
|-
| UBIKPropertyTextLengthHint || UBIKPropertyDirectEditButtons || UBIKTaskPropertyEditButtons
|-
| UBIKPropertyDirectItemString || UBIKPropertyDirectItemDouble || UBIKPropertyDirectItemInt
|-
| UBIKPropertyDirectItemMinMax || UBIKPropertyDirectItemNumeric || UBIKPropertyDirectItemDateTime
|-
| UBIKPropertyDirectItemGeoData || UBIKPropertyDirectItemBool || UBIKPropertyDirectItemPopup
|-
| UBIKPropertyDirectItemList || UBIKPropertyDirectItemGuid || UBIKDocumentItem
|-
| UBIKSearchResultItem || UBIKDefaultHotSpot || UBIKAngularLinkHotSpot
|-
| UBIKRoundLinkHotSpot || UBIKInputHotSpot || UBIKSignatureHotSpot
|-
| UBIKObjectHotSpot || UBIKMediaHotSpot ||
|}
=== VideoPlayer Adjustments ===
'''This property is repsonsible for the video player regarding how or if it should get scaled up depending on the value of the
Aspect property'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">VideoPlayer...</syntaxhighlight>
| <syntaxhighlight lang="xml">VideoPlayer Aspect="AspectFit"</syntaxhighlight>
|}

'''The UriToVideoSourceConverter is no longer needed because the conversion of the
VideoSource gets done by the MediaElement itself. It is marked as obsolete and should therefore no longer be used.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml"><controls:VideoPlayer... Source="{Binding DocumentViewModel.LocalURI, Converter={StaticResource UriToVideoSource}}"/></syntaxhighlight>
| <syntaxhighlight lang="xml"><controls:VideoPlayer... Source="{Binding DocumentViewModel.LocalURI}"/></syntaxhighlight>
|}

'''The StopTimer property is obsolete and no longer needed because the MediaElement behind does the Stop of the VideoPlayer
by itself.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml"><controls:VideoPlayer... StopTimer="{Binding Unloaded}" /></syntaxhighlight>
| <syntaxhighlight lang="xml"><controls:VideoPlayer... /></syntaxhighlight>
|}
=== SearchBar Style Fix on iOS ===
'''On iOS, defining a transparent background for the SearchBar control results in a black text on black background appearance.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">[issue on iOS only] UBIKThemes: SearchBar style: <Setter Property="BackgroundColor" Value="Transparent" /></syntaxhighlight>
| <syntaxhighlight lang="xml">Delete this setter</syntaxhighlight>
|}
=== Avoid Redundant ControlTemplate in DataTriggers ===
'''This is about finding ControlTemplates that are set in DataTriggers in customized Xamls. When the same template is already set as a ContentView default ControlTemplate, it is recommended to remove the default ControlTemplate on the ContentView. For a detailed description please refer to sheet "Mandatory" in cell 27A-27C.
Behavior that might occur if it remains unchanged: Property editor might not open on Android.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml"><ContentView x:Name="containerName" ControlTemplate="{StaticResource YourTemplate1}">
<ContentView.Triggers>
<DataTrigger
Binding="{Binding Source={x:Reference containerName}, Path=...}"
TargetType="ContentView"
Value="true">
<Setter Property="ControlTemplate"
Value="{StaticResource YourTemplate1}" />
</DataTrigger>
...
</ContentView.Triggers>
</ContentView></syntaxhighlight>
| <syntaxhighlight lang="xml"><ContentView x:Name="containerName">
<ContentView.Triggers>
<DataTrigger
Binding="{Binding Source={x:Reference containerName}, Path=...}"
TargetType="ContentView"
Value="true">
<Setter Property="ControlTemplate"
Value="{StaticResource YourTemplate1}" />
</DataTrigger>
...
</ContentView.Triggers>
</ContentView></syntaxhighlight>
|}
=== Replace TemplateBinding with Binding and Source ===
'''This is about finding SfListViewExt controls in customizings, and if there are TemplateBindings used, it's recommended to replace them with Binding, and the Source reference should be added. For a detailed description please refer to sheet "Mandatory" in cell 26A-26C.
Behavior that might occur if it remains unchanged: Pre-selected item might appear unselected.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml"><ContentView
...
x:Name="YourContentViewName">

<ContentView.Resources>
<ResourceDictionary>
...
<ControlTemplate x:Key="YourTemplateKey">
<ctrls:SfListViewExt
ItemsSource="{TemplateBinding BindingContext.YourBinding,
...}"
SelectedItem="{TemplateBinding BindingContext.YourBinding,
...}"
... />
</ControlTemplate>
...
</ResourceDictionary>
</ContentView.Resources>

...
</ContentView></syntaxhighlight>
| <syntaxhighlight lang="xml"><ContentView
...
x:Name="YourContentViewName">

<ContentView.Resources>
<ResourceDictionary>
...
<ControlTemplate x:Key="YourTemplateKey">
<ctrls:SfListViewExt
ItemsSource="{Binding BindingContext.YourBinding,
Source={x:Reference YourContentViewName},
...}"
SelectedItem="{Binding BindingContext.YourBinding,
Source={x:Reference YourContentViewName},
...}"
... />
</ControlTemplate>
...
</ResourceDictionary>
</ContentView.Resources>

...
</ContentView></syntaxhighlight>
|}
=== Remove TapGestureRecognizer from Main Item ===
'''Swiping on the Main items was broken by Maui (Documented in Information). The workaround is to remove the TapGestureRecognizer from UBIKMainItem, and add ListView-based navigation similar to that found in UBIKChildArea (with an extended binding path for technical reasons).'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">(In UBIKMainItem)
<Grid.GestureRecognizers>
<TapGestureRecognizer Command="{Binding NavigateToChildrenCommand}" />
</Grid.GestureRecognizers></syntaxhighlight>
| <syntaxhighlight lang="xml">[nothing]</syntaxhighlight>
|}
=== Add Navigation Behavior in Child Area ===
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">(In UBIKChildArea)
[nothing]</syntaxhighlight>
| <syntaxhighlight lang="xml"><controls:SfListViewExt.Behaviors>
<behaviors:EventHandlerBehavior EventName="ItemTapped">
<behaviors:InvokeCommandAction Command="{Binding AppStatus.RootList.Items[0].NavigateToChildrenCommand}" />
</behaviors:EventHandlerBehavior>
</controls:SfListViewExt.Behaviors></syntaxhighlight>
|}
== Highly Recommended ==
=== CircularImage to AvatarView ===
'''Use AvatarView instead of CircularImage.'''
CircularImage and its wrapping Frame are no longer needed. Use AvatarView from the MAUI Community Toolkit. Add the namespace:
<syntaxhighlight lang="xml">
xmlns:toolkit="http://schemas.microsoft.com/dotnet/2022/maui/toolkit"
</syntaxhighlight>

{| class="wikitable"
! Xamarin
! MAUI
|-
| <Frame><CircularImage Source="..." /></Frame>
| <toolkit:AvatarView ImageSource="..." BorderWidth="..." BackgroundColor="..." />
|}

=== GlyphSize to FontSize and Alignment ===
'''Use FontSize and alignment properties instead of GlyphSize.'''
The GlyphSize property is obsolete. Use FontSize and add alignment properties for better layout.

{| class="wikitable"
! Xamarin
! MAUI
|-
| <Setter Property="GlyphSize" Value="13.0" />
| <Setter Property="FontSize" Value="16" /><br/><Setter Property="VerticalOptions" Value="Center" /><br/><Setter Property="HorizontalOptions" Value="Center" /><br/><Setter Property="VerticalTextAlignment" Value="Center" /><br/><Setter Property="HorizontalTextAlignment" Value="Center" />
|}

=== StaticResource to DynamicResource ===
'''Use DynamicResource and BaseResourceKey.'''
For dynamic theming, use DynamicResource instead of StaticResource. When inheriting styles, use BaseResourceKey.

{| class="wikitable"
! Xamarin
! MAUI
|-
| BasedOn="{StaticResource SomeStyle}"<br/>Style="{StaticResource SomeStyle}"
| BaseResourceKey="SomeStyle"<br/>Style="{DynamicResource SomeStyle}"
|}
== Mandatory ==

=== Namespace conversion ===
'''Update all namespaces to MAUI equivalents.'''
All `xmlns` and `clr-namespace` declarations must be updated to their MAUI counterparts.

{| class="wikitable"
! Xamarin
! MAUI
|-
| xmlns="http://xamarin.com/schemas/2014/forms"
| xmlns="http://schemas.microsoft.com/dotnet/2021/maui"
|-
| clr-namespace:Xamarin.Forms.PlatformConfiguration.AndroidSpecific;assembly=Xamarin.Forms.Core
| clr-namespace:Microsoft.Maui.Controls.PlatformConfiguration.AndroidSpecific;assembly=Microsoft.Maui.Controls
|-
| clr-namespace:UBIK.CPL.Behaviors;assembly=UBIK.CPL
| clr-namespace:UBIK.MAUI.Behaviors;assembly=UBIK.MAUI
|-
| clr-namespace:UBIK.CPL.Classes;assembly=UBIK.CPL
| clr-namespace:UBIK.MAUI.Classes;assembly=UBIK.MAUI
|-
| clr-namespace:UBIK.CPL.Controls;assembly=UBIK.CPL
| clr-namespace:UBIK.MAUI.Controls;assembly=UBIK.MAUI
|-
| clr-namespace:UBIK.CPL.Converters;assembly=UBIK.CPL
| clr-namespace:UBIK.MAUI.Converters;assembly=UBIK.MAUI
|-
| clr-namespace:UBIK.CPL.Platform.Renderers;assembly=UBIK.CPL
| clr-namespace:UBIK.MAUI.Platform.Controls;assembly=UBIK.MAUI
|-
| clr-namespace:UBIK.CPL.Services;assembly=UBIK.CPL
| clr-namespace:UBIK.MAUI.Services;assembly=UBIK.MAUI
|-
| clr-namespace:UBIK.CPL.Resources;assembly=UBIK.CPL
| clr-namespace:UBIK.MAUI.Resources;assembly=UBIK.MAUI
|-
| clr-namespace:UBIK.Scanning.Forms;assembly=UBIK.Scanning.Forms
| clr-namespace:UBIK.MAUI.Controls.ZXingScanner;assembly=UBIK.MAUI
|-
| clr-namespace:Syncfusion.SfPullToRefresh.XForms;assembly=Syncfusion.SfPullToRefresh.XForms
| clr-namespace:Syncfusion.Maui.Toolkit.PullToRefresh;assembly=Syncfusion.Maui.Toolkit
|-
| clr-namespace:Syncfusion.XForms.TabView;assembly=Syncfusion.SfTabView.Xforms
| clr-namespace:Syncfusion.Maui.Toolkit.TabView;assembly=Syncfusion.Maui.Toolkit
|-
| clr-namespace:Syncfusion.ListView.XForms;assembly=Syncfusion.SfListView.XForms
| clr-namespace:Syncfusion.Maui.ListView;assembly=Syncfusion.Maui.ListView
|-
| clr-namespace:Syncfusion.XForms.TreeView;assembly=Syncfusion.SfTreeView.XForms
| clr-namespace:Syncfusion.Maui.TreeView;assembly=Syncfusion.Maui.TreeView
|-
| clr-namespace:Syncfusion.XForms.TextInputLayout;assembly=Syncfusion.Core.XForms
| clr-namespace:Syncfusion.Maui.Core;assembly=Syncfusion.Maui.Core
|}

For classes referenced in the XAML code, please don't forget to also replace "CPL" with "MAUI" in the class namespace.

=== Syncfusion control updates ===
'''There are some other properties that have changed their names on SfListView/SfListViewExt. We don't use them in our standard XAMLs. But if you use them in customizings, please refer to https://help.syncfusion.com/maui/listview/migration for the complete list.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
SfListViewExt:
* ItemHolding
</syntaxhighlight>
| ItemLongPress
|}

=== Syncfusion control updates ===
{| class="wikitable"
! Xamarin
! MAUI
|-
| * LeftSwipeTemplate, RightSwipeTemplate
| StartSwipeTemplate, EndSwipeTemplate
|}

=== Layout name change ===
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
* <sync:SfListView.LayoutManager>
</syntaxhighlight>
| <syntaxhighlight lang="xml">
<sync:SfListView.ItemsLayout>
</syntaxhighlight>
|}

=== TemplateService binding for extracted templates ===
'''1. We need to add the following namespace where the changes are applied:
xmlns:services="clr-namespace:UBIK.MAUI.Services;assembly=UBIK.MAUI";
2. We need to search for both "StaticResource" and "DynamicResource";
3. We only listed some examples here. But the same rule applies to all those templates exacted from UBIKThemes (see the first "Recommended" point).'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| {StaticResource UBIKChildItem}
| {Binding [UBIKChildItem], Source={x:Static services:TemplateService.Instance}}
|-
| {StaticResource UBIKDocumentItem}
| {Binding [UBIKDocumentItem], Source={x:Static services:TemplateService.Instance}}
|-
| {StaticResource UBIKMainItem}
| {Binding [UBIKMainItem], Source={x:Static services:TemplateService.Instance}}
|}

=== OnPlatform and OnIdiom syntax changes ===
'''All code containing the OnPlatform and OnIdiom functionalities needs to be refactored as the syntax changed. It is recommended to use the inline syntax (see example) as a default wherever possible, but there are also other approaches.
When using Bindings, Resources or other complex values in OnIdiom or OnPlatform values, it should only be used with the inline syntax.
Please rely to the wiki for more details and possibilities (e.g. if the value contains multiple elements): https://wiki.augmensys.com/index.php?title=XAML_Tips#Platform_and_Device-specific_UI_with_OnPlatform_and_OnIdiom'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| OnPlatform
| <syntaxhighlight lang="xml">
<TheControl
...
TheProperty="{OnPlatform Android=False, iOS=True}" />

<TheControl
...
TheProperty="{OnPlatform Android={Binding ...}, iOS={Binding ...}}" />
</syntaxhighlight>

|-
| OnIdiom
| <syntaxhighlight lang="xml">
<TheControl
...
TheProperty="{OnIdiom Phone=False, Desktop=True}" />

<TheControl
...
TheProperty="{OnIdiom Desktop={Binding ...}, Phone={Binding ...}}" />
</syntaxhighlight>
|-
| WinPhone
| WinUI
|-
| <syntaxhighlight lang="xml">
e.g.
<ColumnDefinition.Width>
<OnIdiom
...
Desktop="Auto"
Phone="*" />
</ColumnDefinition.Width>
or
<RowDefinition.Height>
<OnPlatform
...
Android="Auto"
iOS="*" />
</RowDefinition.Height>
</syntaxhighlight>
| <syntaxhighlight lang="xml">
<ColumnDefinition Width="{OnIdiom Desktop='Auto', Phone='*'}" />

<RowDefinition Height="{OnPlatform Android='Auto', iOS='*'}" />
</syntaxhighlight>
|}

=== Syncfusion control updates ===
'''It is necessary to use the default Binding with the Source reference to the parent control instead of TemplateBinding when using a SfListViewExt ControlTemplate with selectable items in the ResourceDictionary to be set in the ContentView DataTrigger. Otherwise, the pre-selected items might not appear selected anymore according to our experience.

Affected standard Xamls are:
- UBIKEditDouble
- UBIKEditInt
- UBIKEditString
- UBIKEditMinMax
(For the exact syntax please refer to our latest standard Xamls.)

If the above explained is also used in any custom Xamls, please consider changing it there, too.

However, the problem only seems to occur if there is TemplateBinding in the ItemsSource & SelectedItem property. But, for example, if the TemplateBinding is only in the BindingContext property of the SfListViewExt (like it is the case in the UBIKPropertyDirectEditListPopup), there seems to be no such problem and therefore no change is necessary.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
<ContentView
...
x:Name="YourContentViewName">

<ContentView.Resources>
<ResourceDictionary>
...
<ControlTemplate x:Key="YourTemplateKey">
<ctrls:SfListViewExt
ItemsSource="{TemplateBinding BindingContext.YourBinding,
...}"
SelectedItem="{TemplateBinding BindingContext.YourBinding,
...}"
... />
</ControlTemplate>
...
</ResourceDictionary>
</ContentView.Resources>

...
</ContentView>
</syntaxhighlight>
| <syntaxhighlight lang="xml">
<ContentView
...
x:Name="YourContentViewName">

<ContentView.Resources>
<ResourceDictionary>
...
<ControlTemplate x:Key="YourTemplateKey">
<ctrls:SfListViewExt
ItemsSource="{Binding BindingContext.YourBinding,
Source={x:Reference YourContentViewName},
...}"
SelectedItem="{Binding BindingContext.YourBinding,
Source={x:Reference YourContentViewName},
...}"
... />
</ControlTemplate>
...
</ResourceDictionary>
</ContentView.Resources>

...
</ContentView>
</syntaxhighlight>
|}

=== Remove default ControlTemplate in DataTriggers ===
'''To prevent an issue on Android where the direct edit Link to Object editor does not open, there is a change necessary in the UBIKPropertyDirectEditListPopup Xaml:
The default ControlTemplate needs to be removed from the ContentView that contains the DataTriggers.

According to our experience, this issue only occurs to our UBIKPropertyDirectEditListPopup standard Xaml, but we can't guarantee that there is no such issue in customized Xamls.
So please, if you encounter an issue on Android where a Property Editor doesn't open, report it the mobile development team, and/or try removing the default ControlTemplate from the affected control.

In our standard Xamls, we removed the default ControlTemplate in every ContentView that contains DataTriggers with ControlTemplates where the same template is already set in a DataTrigger. So please, also remove the default ControlTemplates it in the following Xamls if you use customized ones:
- UBIKEditDouble
- UBIKEditInt
- UBIKEditString
- UBIKEditMinMax
(For the exact syntax please refer to our latest standard Xamls.)

If the above explained is also used in any of your other custom Xamls, please consider changing it there, too. Otherwise, some property editor might not open.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
<ContentView x:Name="containerName" ControlTemplate="{StaticResource YourTemplate}">
<ContentView.Triggers>
<DataTrigger
Binding="{Binding Source={x:Reference containerName}, Path=...}"
TargetType="ContentView"
Value="true">
<Setter Property="ControlTemplate"
Value="{StaticResource YourTemplate}" />
</DataTrigger>
...
</ContentView.Triggers>
</ContentView>
</syntaxhighlight>
| <syntaxhighlight lang="xml">
<ContentView x:Name="containerName">
<ContentView.Triggers>
<DataTrigger
Binding="{Binding Source={x:Reference containerName}, Path=...}"
TargetType="ContentView"
Value="true">
<Setter Property="ControlTemplate"
Value="{StaticResource YourTemplate}" />
</DataTrigger>
...
</ContentView.Triggers>
</ContentView>
</syntaxhighlight>
|}

=== Remove HeadlessLayout style ===
'''This Style has no longer any effect in MAUI and even degrades app performance. We are keeping it in our standard UBIKThemes under the Obsolete section to maintain backward compatibility.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
<Style x:Key="HeadlessLayout" TargetType="Layout">
<Setter Property="CompressedLayout.IsHeadless" Value="{OnPlatform False, Android=True}" />
</Style>
</syntaxhighlight>
| Delete it from your custom UBIKThemes file
|}

=== Additional mandatory rule ===
'''In the customizings, however, it can and should be removed entirely, as it negatively affects performance, as mentioned before. To remove the style, you can simply use VS Code or any other editor with a search function and look through all custom .xaml files for usages of {StaticResource HeadlessLayout} or {DynamicResource HeadlessLayout}. These references should be removed from the respective elements or controls.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
<ContentView
Grid.Column="2"
ControlTemplate="{DynamicResource ChildCountBadge}"
HorizontalOptions="Start"
Style="{DynamicResource HeadlessLayout}"
VerticalOptions="Start" />
</syntaxhighlight>
| <syntaxhighlight lang="xml">
<ContentView
Grid.Column="2"
ControlTemplate="{DynamicResource ChildCountBadge}"
HorizontalOptions="Start"
VerticalOptions="Start" />
</syntaxhighlight>
|}

{{UnderConstructionStart}}
=== Avoid multiple SfPullToRefresh controls ===
'''To prevent an issue that causes the app to freeze avoid placing more then 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 a e.g. a DataTrigger to set one of them as the ControlTemplate of a ContentControl inside the SfPullToRefresh control

{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
<pullToRefresh:SfPullToRefresh IsVisible = {Binding ShowContentB, Converter={StaticResource BoolToNotBool}}>
<pullToRefresh:SfPullToRefresh.PullableContent>
<Grid x:Name="ContentA"/>
</pullToRefresh:SfPullToRefresh.PullableContent>
</pullToRefresh:SfPullToRefresh>

<pullToRefresh:SfPullToRefresh IsVisible = {Binding ShowContentB}>
<pullToRefresh:SfPullToRefresh.PullableContent>
<Grid x:Name="ContentB"/>
</pullToRefresh:SfPullToRefresh.PullableContent>
</pullToRefresh:SfPullToRefresh>
</syntaxhighlight>
| <syntaxhighlight lang="xml">
<pullToRefresh:SfPullToRefresh>
<pullToRefresh:SfPullToRefresh.PullableContent>
<controls:ContentControl ContentTemplate="{DynamicResource TemplateA}">
<controls:ContentControl.Triggers>
<DataTrigger
Binding="{Binding UseTemplateB}}"
TargetType="controls:ContentControl"
Value="true">
<Setter Property="ContentTemplate" Value="{DynamicResource TemplateB}" />
</DataTrigger>
</controls:ContentControl.Triggers>
</controls:ContentControl>
</pullToRefresh:SfPullToRefresh.PullableContent>
</pullToRefresh:SfPullToRefresh>
</syntaxhighlight>
|}
{{UnderConstructionEnd}}

=== Rename SfPullToRefresh properties ===
'''Renamed in Maui, however, currently these properties cause an issue and should not be included in customizings.'''
SfPullToRefresh:
{| class="wikitable"
! Xamarin
! MAUI
|-
| RefreshContentHeight, RefreshContentWidth
| RefreshViewHeight, RefreshViewWidth
|}

=== Rename progress colors ===
'''Renamed in Maui.'''
{| class="wikitable"
! Xamarin
! MAUI
|-
| ProgressBackgroundColor, ProgressStrokeColor
| ProgressBackground, ProgressColor
|}

[[Category:How-To|Convert Xamarin XAMLs to Maui]]
[[Category:MAUI|Convert Xamarin XAMLs to Maui]]
[[Category:XAML|Convert Xamarin XAMLs to Maui]]

== SfTabView ==

=== Namespace Update ===
'''Update Syncfusion TabView namespace.'''
Replace the Xamarin namespace with the MAUI equivalent.

{| class="wikitable"
! Xamarin
! MAUI
|-
| clr-namespace:Syncfusion.XForms.TabView;assembly=Syncfusion.SfTabView.XForms
| clr-namespace:Syncfusion.Maui.Toolkit.TabView;assembly=Syncfusion.Maui.Toolkit
|}

=== Remove Obsolete Converters ===
'''Remove ItemCountToBoolConverter from Resources.'''
This converter is no longer usable in TabView headers.

{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml"><converters:ItemCountToBoolConverter x:Key="ItemCountToBool" /></syntaxhighlight>
| [remove]
|}

=== Add StringFormatConverter ===
'''Use StringFormatConverter for combined header strings.'''
Syncfusion MAUI TabView uses a single `Header` property instead of templates.
For all tab headers, formatters should be specified to assemble the text. As a best practice, even for simple header strings.

{| class="wikitable"
! Xamarin
! MAUI
|-
| [template-based header]
| <syntaxhighlight lang="xml"><converters:StringFormatConverter x:Key="ChildrenTabFormatter" Parameter1="{resources:Translate ChildrenTitle}" /></syntaxhighlight>
|}

In the above example, a previously defined formatter (that must be also added to the resource dictionary) is used to fill in the header attribute value.
⚠️ Avoid using bindings in `Parameter1` and `Parameter2` — use static strings only. For complex cases, use `EvalExpression`.

[[Category:How-To|Convert Xamarin XAMLs to Maui]]
[[Category:MAUI|Convert Xamarin XAMLs to Maui]]
[[Category:XAML|Convert Xamarin XAMLs to Maui]]

=== FontImageSource Styling ===
'''Add local style for FontImageSource.'''
Global styles are not supported.

{| class="wikitable"
! Xamarin
! MAUI
|-
| [global FontImageSource style]
| <syntaxhighlight lang="xml">
<Style TargetType="FontImageSource">
<Setter Property="FontFamily" Value="{DynamicResource UBIKSymbols}" />
<Setter Property="Color" Value="{DynamicResource UBIKLightThemeColor}" />
</Style>
</syntaxhighlight>
|}

=== TabView Structure ===
'''Use Grid to wrap TabView.'''
MAUI TabView requires a different structure and property set.

{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
<tabView:SfTabView VisibleHeaderCount="3">
...
</tabView:SfTabView>
</syntaxhighlight>
| <syntaxhighlight lang="xml">
<Grid>
<tabView:SfTabView>
<tabView:SfTabItem Header="string example header">
<tabView:SfTabItem.ImageSource>
<FontImageSource Glyph="{x:Static resources:UBIKIcons.XXX}" />
</tabView:SfTabItem.ImageSource>
<tabView:SfTabItem.Content>
<controls:UBIKContentView x:Name="ChildContainer" Converter="{StaticResource ChildAreaTemplateConverter}" />
</tabView:SfTabItem.Content>
</tabView:SfTabItem>
</tabView:SfTabView>
</Grid>
</syntaxhighlight>
|}

=== Property Changes ===
'''Update renamed or removed properties.'''

{| class="wikitable"
! Xamarin
! MAUI
|-
| VisibleHeaderCount
| [not available yet]
|-
| UBIKCenterButtonSettings
| CenterButtonSettings
|-
| SelectionIndicatorSettings
| IndicatorPlacement, IndicatorStrokeThickness, IndicatorBackground
|-
| SelectionColor
| Use VisualStateManager instead
|}

⚠️ Refer to [https://help.syncfusion.com/maui/tabview/migration Syncfusion migration guide] for full property list.

== OnPlatform + OnIdiom backup ==

=== Syntax Changes ===
'''Use inline or multi-tag syntax.'''
Single-tag syntax is outdated and may not build.

{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml"><OnPlatform Android="False" iOS="True" /></syntaxhighlight>
| <syntaxhighlight lang="xml"><TheControl TheProperty="{OnPlatform Android=False, iOS=True}" /></syntaxhighlight>
|}

{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
<OnPlatform x:TypeArguments="TheType">
<On Platform="Android" Value="False" />
<On Platform="iOS" Value="True" />
</OnPlatform>
</syntaxhighlight>
| Required for multi-tag syntax
|}

=== WinPhone to WinUI ===
'''Replace WinPhone with WinUI.'''

{| class="wikitable"
! Xamarin
! MAUI
|-
| WinPhone
| WinUI
|}

=== GridLength and TypeArguments ===
'''Avoid x:TypeArguments with GridLength.'''

{| class="wikitable"
! Xamarin
! MAUI
|-
| <syntaxhighlight lang="xml">
<ColumnDefinition.Width>
<OnIdiom x:TypeArguments="GridLength" Desktop="Auto" Phone="*" />
</ColumnDefinition.Width>
</syntaxhighlight>
| <syntaxhighlight lang="xml"><ColumnDefinition Width="{OnIdiom Desktop='Auto', Phone='*'}" /></syntaxhighlight>
|}

⚠️ Inline syntax is more reliable when using bindings or resources.

=== Special Characters ===
'''Wrap values in quotes if they contain commas or strings.'''

{| class="wikitable"
! Xamarin
! MAUI
|-
| Margin={OnIdiom 10,2, Phone=2,0}
| Margin={OnIdiom '10,2', Phone='2,0'}
|}

=== UWP to WinUI ===
'''Replace UWP with WinUI in all OnPlatform scopes.'''

{| class="wikitable"
! Xamarin
! MAUI
|-
| UWP
| WinUI
|}

⚠️ For more details, refer to the [https://wiki.augmensys.com/index.php?title=XAML_Tips#Device_and_Platform_Responsiveness Wiki documentation].

[[Category:How-To|Convert Xamarin XAMLs to Maui]]
[[Category:MAUI|Convert Xamarin XAMLs to Maui]]
[[Category:XAML|Convert Xamarin XAMLs to Maui]]

Version 5.0 (Mobile)

2025-07-31T12:29:24Z

LKR: /* Known issues */

{{Attention|UBIK 5 clients can only connect to {{UBIK}} Servers of [[Version 3.6(Server)|version 3.6]] and higher!}}

{{Attention|The minimum supported OS versions are:
* Android 9;
* iOS 12.}}

== Availability ==
{{key press|Android: Store}}{{key press|iOS: Store}}: Publicly available in Google Play Store / Apple App Store.

{{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.

{{key press|Android: Store Preview}}: To join the preview tests please send an email to testing@augmensys.com and provide an email address that is connected to a google play account as well as the information that you want to join the android preview test. Alternatively you can contact the Augmensys staff and submit your chosen email address. You can opt in or out of the test at any time in the store.

Example: Please add my email account example@example.com to the '''Preview''' test group for the '''Android''' client.

{{key press|iOS: Store Beta}}: Available through Apple App Store's [https://testflight.apple.com/join/ijGm4j2h invitation link].

{{key press|iOS: Store Preview}}: Available through Apple App Store's [https://testflight.apple.com/join/qDMZjTgg invitation link].

{{key press|UWP: Store Preview}}:Publicly available in Microsoft Store as preview versions to those whose account email is participating in our preview test. To join, please send an email 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.

Example: Please add my email account example@example.com to the '''Preview''' test group for the '''Xamarin UWP''' client.
<br/>

{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with a ⚠️}}

= Release Notes =

== Release ==

== Beta ==

== Preview ==
* Improved the branch download performance especially when there are duplicate objects in multiple branches.

== Known issues ==
* 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.
* 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.
* 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.
* The periodic execution of background pushes is not guaranteed on iOS.
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].
* It is currently not possible to select which camera to use on Windows.
<br/>

= ⚠️ XAML Notes =

<headertabs />

Version 4.9 (WinX)

2025-05-28T09:54:50Z

LKR: /* 4.9.7 on 2025-05-07 */

{{Attention|This version requires [https://en.wikipedia.org/wiki/Windows_10_version_history#Version_1809_(October_2018_Update) Windows 10 build 17763] or higher}}

== Availability ==
{{key press|Store}}: Publicly available in Microsoft Store.

{{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.

Example: Please add my email account example@example.com to the '''Beta''' test group for the '''WinX''' client.

<br/>
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with ⚠️}}

= Release Notes =

== Release ==

=== 4.9.? on 2025-06-?? ===
* Improved the quality/sharpness of PDF content when it's printed out using the embedded PDF control.
* Resolved an issue where annotations created with external tools were displayed incorrectly in PDFs.

[[Category:Version 4.9|Version 4.9 (WinX)]]

=== 4.9.7 on 2025-05-07 ===
* Improved the quality/sharpness of PDF content when it's printed out using the embedded PDF control.

=== 4.9.5 on 2025-02-19 ===
* [[Property_Based_Content_Filters#Troubleshooting|Property based filtering configs]] are now persisted per profile and per user.
* Fixed an issue where excessive license warnings are displayed sometimes (when you don't have enough licenses and push/live value updates are active).

=== 4.9.4 on 2025-02-05 ===
* Fixed an issue where the values of a geo task item content control had a bad readability.

== Beta ==

=== 4.9.2 on 2025-01-28 {{key press|Store Beta}} ===
* Fixed issue that wrongly enabled the Copy button in the multi select panel.
* Fixed an issue that affected multi selection of objects with multi owner properties.
* Added an indicator for invalid values to direct editing tasks.
* Fixed an issue where the guid property value did not display.
* Fixed an issue where the UBIK push service is not started when the profile used has starting/trailing spaces in their Project tag.
* Fixed an issue where navigating to a linked object when it's not yet available locally doesn't always work.
* Fixed an issue where the entered valid values do not get confirmed when the task direct editing UI loses focus.
* Fixed an issue where the UI of task items looked destroyed after pressing the NA button.

== Preview ==

=== 4.9.1 on 2024-12-20 {{key press|App Center}} ===
* The [[Data_Replication_(UBIK_Client)#Data_templates|data template replication]] feature is redesigned.
* The offline query feature is improved when there are [[Offline_Query_(UBIK_WinX)#Query_with_context_filter_values|automatically applied context values]].
** The UI displays context filter values and user entered filter values differently;
** It's now possible to reset/delete context filters values as well.
* A [[Custom_Query_Search|custom query based search]] is now available to be used in customizing.
* The [[Documents_(Client)#Remember_Document_Settings|Remember Document Settings]] feature enables the option to save PDF Viewer settings.
* Fixed some issues in the embedded PDF viewer.
** Fixed an issue where PDF free text annotations might change their colors (when you create many).
** Fixed some selection related issues for PDF annotations.
** Fixed an issue where underline & strike through text Annotations were not saved properly.
** There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].
* Fixed an issue where Guid/link properties do not always display their current selected values.
* Fixed an issue where dynamic selective list properties do not always display their current selected values.
* Fixed an issue where unconfirmed Guid property values couldn't get deleted.
* Fixed an issue where images with the same height & width got rotated 90 degrees after saving.
* Fixed an issue where document items do not get properly refilterd in a expression based filtering list.
* Fixed an issue where new annotations might be lost on PDF documents if you exit annotation mode too fast right after creation (e.g. by activating hotspotting mode).
* Fixed an issue where the thumbnails of hotspots are only updated once during creation, which results in potentially incorrect flattened results on the server.
* Fixed an issue where [[XAML_Tips#Access_to_an_arbitrary_object|ObjectByUID]] didn't update on Login.
* Fixed an issue that caused the validation time stamp of work packages to be null when confirming them.

== Known issues ==
* 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.
* Free Text Annotations that where created in former sessions cannot be selected and therefore cannot be edited any more.
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].
* Known issues regarding the [[Documents_(Client)#Remember_Document_Settings|Remember Document Settings]] feature:
** Saving the Zoom value via touch gestures is not supported.
** 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/>

= ⚠️ XAML Notes =

* UBIKTaskControlFullWidth in UBIKThemes is increased to 210 to fit the task editing fields in the task item templates. If you have this resource present in your custom UBIKThemes, you need to increase it accordingly. Otherwise, the task editing fields might be cut off. Likewise, you have to make sure any UI elements/templates (e.g. Grids) containing controls using this resource do not limit the width to less than this amount.

<headertabs />

{{Category/Version2|{{PAGENAME}}}}

[[Category:Version 4.9|Version 4.9 (WinX)]]

Version 4.9 (WinX)

2025-05-28T09:41:48Z

LKR: /* 4.9.? on 2025-06-?? */

{{Attention|This version requires [https://en.wikipedia.org/wiki/Windows_10_version_history#Version_1809_(October_2018_Update) Windows 10 build 17763] or higher}}

== Availability ==
{{key press|Store}}: Publicly available in Microsoft Store.

{{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.

Example: Please add my email account example@example.com to the '''Beta''' test group for the '''WinX''' client.

<br/>
{{Attention|Some customized XAMLs might need an update to work properly. These changes are marked with ⚠️}}

= Release Notes =

== Release ==

=== 4.9.7 on 2025-05-07 ===
* Improved the quality/sharpness of PDF content when it's printed out using the embedded PDF control.
* Resolved an issue where annotations created with external tools were displayed incorrectly in PDFs.

[[Category:Version 4.9|Version 4.9 (WinX)]]

=== 4.9.7 on 2025-05-07 ===
* Improved the quality/sharpness of PDF content when it's printed out using the embedded PDF control.

=== 4.9.5 on 2025-02-19 ===
* [[Property_Based_Content_Filters#Troubleshooting|Property based filtering configs]] are now persisted per profile and per user.
* Fixed an issue where excessive license warnings are displayed sometimes (when you don't have enough licenses and push/live value updates are active).

=== 4.9.4 on 2025-02-05 ===
* Fixed an issue where the values of a geo task item content control had a bad readability.

== Beta ==

=== 4.9.2 on 2025-01-28 {{key press|Store Beta}} ===
* Fixed issue that wrongly enabled the Copy button in the multi select panel.
* Fixed an issue that affected multi selection of objects with multi owner properties.
* Added an indicator for invalid values to direct editing tasks.
* Fixed an issue where the guid property value did not display.
* Fixed an issue where the UBIK push service is not started when the profile used has starting/trailing spaces in their Project tag.
* Fixed an issue where navigating to a linked object when it's not yet available locally doesn't always work.
* Fixed an issue where the entered valid values do not get confirmed when the task direct editing UI loses focus.
* Fixed an issue where the UI of task items looked destroyed after pressing the NA button.

== Preview ==

=== 4.9.1 on 2024-12-20 {{key press|App Center}} ===
* The [[Data_Replication_(UBIK_Client)#Data_templates|data template replication]] feature is redesigned.
* The offline query feature is improved when there are [[Offline_Query_(UBIK_WinX)#Query_with_context_filter_values|automatically applied context values]].
** The UI displays context filter values and user entered filter values differently;
** It's now possible to reset/delete context filters values as well.
* A [[Custom_Query_Search|custom query based search]] is now available to be used in customizing.
* The [[Documents_(Client)#Remember_Document_Settings|Remember Document Settings]] feature enables the option to save PDF Viewer settings.
* Fixed some issues in the embedded PDF viewer.
** Fixed an issue where PDF free text annotations might change their colors (when you create many).
** Fixed some selection related issues for PDF annotations.
** Fixed an issue where underline & strike through text Annotations were not saved properly.
** There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].
* Fixed an issue where Guid/link properties do not always display their current selected values.
* Fixed an issue where dynamic selective list properties do not always display their current selected values.
* Fixed an issue where unconfirmed Guid property values couldn't get deleted.
* Fixed an issue where images with the same height & width got rotated 90 degrees after saving.
* Fixed an issue where document items do not get properly refilterd in a expression based filtering list.
* Fixed an issue where new annotations might be lost on PDF documents if you exit annotation mode too fast right after creation (e.g. by activating hotspotting mode).
* Fixed an issue where the thumbnails of hotspots are only updated once during creation, which results in potentially incorrect flattened results on the server.
* Fixed an issue where [[XAML_Tips#Access_to_an_arbitrary_object|ObjectByUID]] didn't update on Login.
* Fixed an issue that caused the validation time stamp of work packages to be null when confirming them.

== Known issues ==
* 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.
* Free Text Annotations that where created in former sessions cannot be selected and therefore cannot be edited any more.
* There are still some [[Annotation_and_HotSpot#Known_issues|known issues with free text and text markup annotations]].
* Known issues regarding the [[Documents_(Client)#Remember_Document_Settings|Remember Document Settings]] feature:
** Saving the Zoom value via touch gestures is not supported.
** 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/>

= ⚠️ XAML Notes =

* UBIKTaskControlFullWidth in UBIKThemes is increased to 210 to fit the task editing fields in the task item templates. If you have this resource present in your custom UBIKThemes, you need to increase it accordingly. Otherwise, the task editing fields might be cut off. Likewise, you have to make sure any UI elements/templates (e.g. Grids) containing controls using this resource do not limit the width to less than this amount.

<headertabs />

{{Category/Version2|{{PAGENAME}}}}

[[Category:Version 4.9|Version 4.9 (WinX)]]

Version 4.9.0 (Server)

2025-05-19T13:11:33Z

LKR: /* Hot fixes */

= Kernel (initial release)=
== Features ==
* UBIK provides the possibility to customize an online text search. See [[SYSCLS_CUSTOMTEXTQUERY|Custom Text Search Classification]].
* Human-readable database views can be created in the same database instance where the data is stored.
* Custom code for MetaProxies can now be edited and transported using SmartStudio.
* UBIK.Studio provides the possibility to define the UID for a new derived MetaClass now.
* UBIK CUI Interface supports the (re)import of undeleted Comos objects now.
* UBIK StandardImport supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.
* A custom query-based search is now available to be used in customizing.
* UBIK OLEDB Plugin supports customizing the OLEDB provider string now.
* An improved configuration dialog for the auto-create MetaClassScope drag & drop action was created.

== Bug Fixes ==
* A bug in managing changelog/history items for properties with configured MetaAttributes was fixed.
* A problem in handling references to deleted objects was fixed: misleading exceptions are not thrown anymore.
* An issue where custom code couldn't be transported for system meta classes using SmartStudio was fixed.
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time in SmartStudio and AdminTool.
* New instances created in the AdminTool are now also saved if a refresh occurs beforehand.
* A problem in the new support to undelete CUI objects was fixed: the ID of the target object does not change when executing the undelete.
* System.Memory.dll is now provided in the release packages.
* OSIPI and ModuleReporting Plugins support the newest version of System.Memory now.
* A bug in the UBIK.NotificationEndPoint Service was fixed: it can handle subfolders in the Queue directory now.
* A bug when flattening Annotations and Hotspots into Document Revisions was fixed.
* Improved Exception Handling when saving objects and proxies during the interface execution, result in a higher stability as customizing related crashes do not stop the process any more.
* Fixed an issue in the AdminTool that permitted manipulation of locked properties.
* An issue where values for new languages weren't saved was fixed.
* A bug in the handling of History/Changelog items for MRO tasks was fixed: if the value is set directly to N.A., a changelog item gets created now.
* A Issue was fixed where the PunchPoint link was not visualized in the "Punchpoint Attachments" use case
* Issues in internal file handling (of queued notifications) were solved for the Event Notificatoin Endpoint.
* System.Numerics.Vectors, Microsoft.Bcl.TimeProvider, Microsoft.Bcl.AsyncInterfaces DLLs were added to the OIDC Processor plugin
<br/>

== Enhancements ==
* UBIK Standard-Import supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.
* A possibility to customize "real" property values for system design objects via Plugin was provided. Further, CUI system definitions can now be used without deriving.
* MetaProxy properties are now modeled more consistently in SmartStudio.
* A set of vulnerable 3rd party components were updated.
* For reduced RAM consumption, a system classification SYSCLS_PREVENT_CACHING was provided, and future measures were triggered.
* UBIK supports *.docx as standard filetype now
* The UBIK.EnterpriseService now processes queued tasks in an awaitable manner, with configurable pauses and idle-interruption when adding new tasks.

== MaTaP Improvements and fixes ==
* Fixed an issue where QRF and Check Operations were not included in Mile Stone Calculation of Workorder.
* Predefined views get saved and are available for Admin Tools now.
* The Project Usecase in the MATAP Admin Tool is standardized now: Job Descriptions + presented columns.
* MATAP supports encrypted passwords for imported MATAP users now.
* MATAP supports Quality Record Forms now.
* MATAP supports Check Tasks now.
* MATAP Wallpaper Client supports project-related Punchpoint columns now.
* The Project Status is now managed on the Project Instance itself.
* UBIK MATAP supports project-related data caching on the View Cache now.
* The communication feature is now available in MATAP.
* All operation imports support the import of a work property.
* MATAP supports reports now.
* Admin Tool shows the duration of a successful job run now instead of presenting start and end timestamps.
* MATAP supports the import and presentation of materials per operation now.
* In the Admin Tool, the (Turnaround) Project Usecase does not show SAP-specific columns anymore.
* In the Admin Tool, the Operation Usecases do not show SAP and Primavera-specific columns anymore.
* Identified an issue where activity codes were cut off when the project name was too long.
* Identified an issue where companies were cut off when the project name was too long.
* Deletion of default activity codes works now.
* Reimporting deleted objects is now possible.
* Wallpaper Client does not crash when opening a Scope Change anymore.
* A bug in evaluating the code was fixed. Configured grouped codes are no longer ignored.
* The Admin Tool is now able to download the customizing.
* Operations being set to Not Applicable show the right status color now (gray).
* Scheduling import works now for check and QRF operations too.
* Wallpaper does not crash anymore during progress reporting.
* Location assigning performance was improved.
* A misconfiguration that caused duplicated scope changes to also duplicate the progress was fixed.
* Fixed an issue where Punchpoint numbers were overwritten multiple times causing the number to unnecessarily increase.
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time.
* MATAP now provides the possibility to schedule nightly app pool restarts for all active projects.
* MATAP imports will not overwrite once edited string data with empty values anymore.
* The "Turnaround Project" use case was renamed to "Project".
* The description for the Currency Setting Property was wrong. It shows "Currency Settings" now.
* The currency on projects is now set to "€" by default.
* Key and unique filename have now been removed from the Plot Plans use case.
* Description has been replaced with Name in the Plot Plans use case (Admin Tool)
* The Plot Plan Name is now displayed in Plant Layouts (Client)
* Removed columns "Offline Sync Configuration" and "Branch Download" from Admin Tool "Functionality" use case.
* Removed columns "Unique Filename" and "Path to local file" from Admin Tool "Daily HSE" use case.
* Vertical and horizontal scroll bars now remain in their last set position after the saving process.
* The Zone column is now available in the Commissioning Package Usecase.
* Systems and subsystems are available in the Commissioning Tasks use case now.
* Documents below work orders are sorted by their type now.
* Names for systems and subsystems show in the expected order now.
* MATAP allows project names with a length of up to 100 characters now.
* New instances are now also saved if a refresh occurs beforehand.
* SC Desc., Operation No., and Estimated Costs are now displayed as saved after saving.
* Timesheets calculation issue for standard operations was solved.
* A sorting error for operations was fixed.
* When selecting import files, the file picker now remembers its last position.
* Template Usecases will now be replicated including their column configurations.
* Precom Activity Code cells show default operations information on the Turnaround Wallpaper now.
* An unused property (MATAP_PROJECT_ID) has been removed from the standard property pool.
* A new property (MATAP_ID) has been added to the standard property pool and integrated into the Activity Code Use Cases.
* The Admin Tool Turnaround Project Usecase now provides project creation status information.
* A problem in the Admin Tool which led to random warnings is solved now.
* MATAP Wallpaper Client now shows correct labels for Check/Operation detail tabs.
* Fixed recurring warnings in UBIK.Studio.
* Fixed recurring warnings in Admin Tool.
* The key column for MATAP users gets automatically filled if the object is created manually.
* Document system property will not be delivered to the client anymore.
* Fixed the issue where setting an operation status to N/A could cause the client to freeze or crash.
* The scope change workflow shows the user details again.
* A problem in the View Item Setup for the Communication Feature was fixed.
* Cells on the Commissioning Wallpaper only show the last change date if the task is considered to be finished.
* CODE_TYPE property doesn't get replicated when creating a Scope Change.
* A bug was fixed where empty Meta Classes were created after removing the MATAP plugin.
* Performance improvements and general bug fixes for Admin Tool.
* The Bulk Editor scroll bars now retain their positions after a refresh.
* Admin Tool shows the name of the referenced project when displaying use cases now.
* Punchpoints show a changelog for the 'Responsibility' property now.
* The Admin - Tool Scope Change Usecase shows scope changes only now.
* Import of EquipmentGroup and EquipmentType data is standardized now: the standard import supports import via the Equipment instance.
* The Admin - Tool Scope Change Attachment Usecase works now.
* Import of Equipments support a complex plant-system-subsystem structure as well as plant zone structure. it is not required any more that system and subsystem names are unique.
* Execution Documents show the Local Full Path in the AdminTool now.
* Punchpoints now show a changelog for the 'Responsibility' and 'Due Date' properties.
* A digit counter was added for Operation, Operation Description and ScopeChange Description in the Wallpaper Client.
* The current Project Status can now be seen in the project header of the start screen.
* In the Admin Tool, the Task - Progress is now displayed in the corresponding column.
* The filtering of instances in the Picker within the Admin Tool is now possible without reopening the popup.
* A Issue was fixed where the link to the PunchPoint was not visualized in the PunchpointAttachment usecase in the Admin Tool
* Users can change a project name only until the creation is finished.
* Wrong order of CTS and UTS columns at Commissioning Package and Commissioning Task Use Cases was fixed.
* Corrected the locked status for timesheet Use Case columns.
* Fixed an issue where users with Create only permissions could not edit Scopechange details.
* Added final document location to file path in Scope Change attachment use case.
* An issue was fixed where the information on the Commissioning Wallpaper did not update when grouped commissioning tasks were added/removed/finished.

= Hot fixes =

Version 4.9.0.10042 on 2025/05/16:
* An issue where attributes weren't reloaded for objects updated via change detection was fixed.
* A memory leak occurring for the UBIK Enterprise Service with Web Interface was fixed.
<br/>

Version 4.9.0.10040 on 2025/05/15:
* Importing of MATAP data containing empty strings does not result the Proxies having an import status of error any more.
* MATAP - AdminTool: An issue was fixed where new instances were added to the bottom of the list.
* CUI does not send empty update requests to the Comos RestAPI any more.
* An issue where MetaClasses with instances couldn't be deleted was fixed.
* The user group cache and rights evaluation mechanism was overhauled for better integrity and performance.
* Fixed an HotSpotting issue where the empty revision creation did not work.
* An issue where ComosMetaProxyProperties were created with the wrong meta class when importing from Comos XML was fixed.
* Fixed an issue where spare parts (materials) were not displayed on the client.
* Fixed an issue where system selective items' localizations were not provided via the web service.
* Fixed an issue that triggered a license warning even on a failed login.
<br/>

Version 4.9.0.10024 on 2025/04/17:
* An issue where proxy attributes were created unnecessarily was fixed.
* An issue where MetaClasses couldn't be loaded from a Plugin was fixed.
* A memory Leak in the Enterprise Service (Notification Controller - Usease) was fixed.
* A bug where certain database adaptations were skipped if no db-views were configured was fixed.
* A missleading (false) https status code was documented for failed http communication in the post log was fixed.
* CUI Document Proxies get saved immediately when exporting them to Comos. This will avoid duplicates in exports if further processing fails.
* An issue where database connections are not closed under certain erroneous circumstances was fixed.
* MATAP: Imports were improved. They do not overwrite data that were manually changed by using the Admin Tool any more.
* MATAP: An issue was fixed where template instances were not shown under the Template Use Case.
* MATAP:Fixed an issue where it was not possible to import new operations with a previously deleted Operation ID.

== Known Issues ==
* Exclusive Access is not fully supported (missing aspect: lock on database level)

Version 5.0 (WinX)

2025-05-19T12:56:48Z

LKR: /* 5.0.0 on 2025-??-?? {{key press|Store Preview}} */

2024-12-12T12:26:50Z

LKR: /* Application */

The custom query search uses a query provided via the customizing to define the context of the search. {{Version/WinXSince|4.9}}{{Version/XamarinSince|4.9}}

== Application ==
The custom query search is used when the [[Mobile_Free_Text_Search|free text search]] does not deliver the desired results and a customized online search based on the results of a query is desired. The custom query search does NOT include an offline search (in contrast to the [[Mobile_Free_Text_Search|free text search]]).

[[Category:Version 4.9|Custom Query Search]]

== Functionality ==
To use the custom query search it is necessary to customize the project as it is not part of the default UI. When the custom query search is added to the customizing it can be used to replace the standard UI's [[Mobile_Free_Text_Search|free text search]] field or added additionally.

When using the custom query search in the customizing of a project it is necessary to provide the UID of the query object that should be used to define the search context. When no UID is given the search will never provide results. How exactly the search term is interpreted and used to return a List of results is handled on the server side.

The custom query search utilizes the same result handling as the [[Mobile_Free_Text_Search|free text search]]. This means the results for both searches are represented in the same list, replacing each other.

=== Parameters ===
* SearchText: takes the string that should be used as search term for the search.
* QueryID: takes the UID of the query object that should be used as search context.
* (Optional) NavigateOnSingleResult: if this is set to true and a search returns only a single result the app will automatically navigate to the found object. By default its value is true.

[[Category:Version 4.9|Custom Query Search]]

== Example ==
<tabs>
<tab name="UWP">
<source lang = "xml">
<AutoSuggestBox x:Name="Search"
...
<interactivity:Interaction.Behaviors>
<behaviors:AutoSuggestBoxInputBehavior>
<core:InvokeCommandAction Command="{Binding CustomQuerySearchCommand}">
<core:InvokeCommandAction.CommandParameter>
<controls:KeyValueList>
<controls:KeyValueParameter Key="SearchText" Value="{Binding ElementName=Search, Path=Text}" />
<controls:KeyValueParameter Key="NavigateOnSingleResult" Value="true" />
<controls:KeyValueParameter Key="QueryID" Value="bab1c694-a5ad-421f-8c85-faa385891e4b" />
</controls:KeyValueList>
</core:InvokeCommandAction.CommandParameter>
</core:InvokeCommandAction>
</behaviors:AutoSuggestBoxInputBehavior>
</interactivity:Interaction.Behaviors>
</AutoSuggestBox>
</source>
</tab>

<tab name="Xamarin">
<source lang = "xml">
<SearchBar x:Name="SearchField"
...
<behaviors:EventHandlerBehavior EventName="SearchButtonPressed">
<behaviors:InvokeCommandAction Command="{Binding CustomQuerySearchCommand}">
<behaviors:InvokeCommandAction.CommandParameter>
<classes:KeyValueList>
<classes:KeyValueParameter Key="SearchText"
Value="{Binding Path=Text, Source={x:Reference SearchField}}" />
<classes:KeyValueParameter Key="NavigateOnSingleResult" Value="true" />
<classes:KeyValueParameter Key="QueryID" Value="bab1c694-a5ad-421f-8c85-faa385891e4b" />
</classes:KeyValueList>
</behaviors:InvokeCommandAction.CommandParameter>
</behaviors:InvokeCommandAction>
</behaviors:EventHandlerBehavior>
</SearchBar.Behaviors>
</SearchBar>
</source>
</tab>
</tabs>

== See also ==
* [[SYSCLS_CUSTOMQUERYSEARCH]]

[[Category:Version 4.9|Custom Query Search]]

Custom Query Search

2024-12-12T10:04:07Z

LKR: /* Parameters */

The custom query search uses a query provided via the customizing to define the context of the search. {{Version/WinXSince|4.9}}{{Version/XamarinSince|4.9}}

== Application ==
The custom query search is used when it is necessary to search within a defined subset of objects rather then the entire data structure. Additionally the custom query search does not include an offline search (in contrast to the [[Mobile_Free_Text_Search|free text search]]).

== Functionality ==
To use the custom query search it is necessary to customize the project as it is not part of the default UI. When the custom query search is added to the customizing it can be used to replace the standard UI's [[Mobile_Free_Text_Search|free text search]] field or added additionally.

When using the custom query search in the customizing of a project it is necessary to provide the UID of the query object that should be used to define the search context. When no UID is given the search will never provide results. How exactly the search term is interpreted and used to return a List of results is handled on the server side.

The custom query search utilizes the same result handling as the [[Mobile_Free_Text_Search|free text search]]. This means the results for both searches are represented in the same list, replacing each other.

=== Parameters ===
* SearchText: takes the string that should be used as search term for the search.
* QueryID: takes the UID of the query object that should be used as search context.
* (Optional) NavigateOnSingleResult: if this is set to true and a search returns only a single result the app will automatically navigate to the found object. By default its value is true.

[[Category:Version 4.9|Custom Query Search]]

== Example ==
<tabs>
<tab name="UWP">
<source lang = "xml">
<AutoSuggestBox x:Name="Search"
...
<interactivity:Interaction.Behaviors>
<behaviors:AutoSuggestBoxInputBehavior>
<core:InvokeCommandAction Command="{Binding CustomQuerySearchCommand}">
<core:InvokeCommandAction.CommandParameter>
<controls:KeyValueList>
<controls:KeyValueParameter Key="SearchText" Value="{Binding ElementName=Search, Path=Text}" />
<controls:KeyValueParameter Key="NavigateOnSingleResult" Value="true" />
<controls:KeyValueParameter Key="QueryID" Value="bab1c694-a5ad-421f-8c85-faa385891e4b" />
</controls:KeyValueList>
</core:InvokeCommandAction.CommandParameter>
</core:InvokeCommandAction>
</behaviors:AutoSuggestBoxInputBehavior>
</interactivity:Interaction.Behaviors>
</AutoSuggestBox>
</source>
</tab>

<tab name="Xamarin">
<source lang = "xml">
<SearchBar x:Name="SearchField"
...
<behaviors:EventHandlerBehavior EventName="SearchButtonPressed">
<behaviors:InvokeCommandAction Command="{Binding CustomQuerySearchCommand}">
<behaviors:InvokeCommandAction.CommandParameter>
<classes:KeyValueList>
<classes:KeyValueParameter Key="SearchText"
Value="{Binding Path=Text, Source={x:Reference SearchField}}" />
<classes:KeyValueParameter Key="NavigateOnSingleResult" Value="true" />
<classes:KeyValueParameter Key="QueryID" Value="bab1c694-a5ad-421f-8c85-faa385891e4b" />
</classes:KeyValueList>
</behaviors:InvokeCommandAction.CommandParameter>
</behaviors:InvokeCommandAction>
</behaviors:EventHandlerBehavior>
</SearchBar.Behaviors>
</SearchBar>
</source>
</tab>
</tabs>

== See also ==
* [[SYSCLS_CUSTOMQUERYSEARCH]]

[[Category:Version 4.9|Custom Query Search]]

Custom Query Search

2024-12-12T09:57:18Z

LKR:

The custom query search uses a query provided via the customizing to define the context of the search. {{Version/WinXSince|4.9}}{{Version/XamarinSince|4.9}}

== Application ==
The custom query search is used when it is necessary to search within a defined subset of objects rather then the entire data structure. Additionally the custom query search does not include an offline search (in contrast to the [[Mobile_Free_Text_Search|free text search]]).

== Functionality ==
To use the custom query search it is necessary to customize the project as it is not part of the default UI. When the custom query search is added to the customizing it can be used to replace the standard UI's [[Mobile_Free_Text_Search|free text search]] field or added additionally.

When using the custom query search in the customizing of a project it is necessary to provide the UID of the query object that should be used to define the search context. When no UID is given the search will never provide results. How exactly the search term is interpreted and used to return a List of results is handled on the server side.

The custom query search utilizes the same result handling as the [[Mobile_Free_Text_Search|free text search]]. This means the results for both searches are represented in the same list, replacing each other.

=== Parameters ===
* SearchText: takes the string that should be used as search term for the search.
* QueryID: takes the UID of the query object that should be used as search context.
* (Optional) NavigateOnSingleResult: if this is set to true and a search returns only a single result the app will automatically navigate to the found object. By default its value is false.

== Example ==
<tabs>
<tab name="UWP">
<source lang = "xml">
<AutoSuggestBox x:Name="Search"
...
<interactivity:Interaction.Behaviors>
<behaviors:AutoSuggestBoxInputBehavior>
<core:InvokeCommandAction Command="{Binding CustomQuerySearchCommand}">
<core:InvokeCommandAction.CommandParameter>
<controls:KeyValueList>
<controls:KeyValueParameter Key="SearchText" Value="{Binding ElementName=Search, Path=Text}" />
<controls:KeyValueParameter Key="NavigateOnSingleResult" Value="true" />
<controls:KeyValueParameter Key="QueryID" Value="bab1c694-a5ad-421f-8c85-faa385891e4b" />
</controls:KeyValueList>
</core:InvokeCommandAction.CommandParameter>
</core:InvokeCommandAction>
</behaviors:AutoSuggestBoxInputBehavior>
</interactivity:Interaction.Behaviors>
</AutoSuggestBox>
</source>
</tab>

<tab name="Xamarin">
<source lang = "xml">
<SearchBar x:Name="SearchField"
...
<behaviors:EventHandlerBehavior EventName="SearchButtonPressed">
<behaviors:InvokeCommandAction Command="{Binding CustomQuerySearchCommand}">
<behaviors:InvokeCommandAction.CommandParameter>
<classes:KeyValueList>
<classes:KeyValueParameter Key="SearchText"
Value="{Binding Path=Text, Source={x:Reference SearchField}}" />
<classes:KeyValueParameter Key="NavigateOnSingleResult" Value="true" />
<classes:KeyValueParameter Key="QueryID" Value="bab1c694-a5ad-421f-8c85-faa385891e4b" />
</classes:KeyValueList>
</behaviors:InvokeCommandAction.CommandParameter>
</behaviors:InvokeCommandAction>
</behaviors:EventHandlerBehavior>
</SearchBar.Behaviors>
</SearchBar>
</source>
</tab>
</tabs>

== See also ==
* [[SYSCLS_CUSTOMQUERYSEARCH]]

[[Category:Version 4.9|Custom Query Search]]

Custom Query Search

2024-12-10T06:58:11Z

LKR:

{{UnderConstructionStart}}

The custom query search uses a query provided via the customizing to define the context of the search. {{Version/WinXSince|4.9}}{{Version/XamarinSince|4.9}}

== Application ==
The custom query search is used when it is necessary to search within a defined subset of objects rather then the entire data structure. Additionally the custom query search does not include an offline search (in contrast to the [[Mobile_Free_Text_Search|free text search]]).

== Functionality ==
To use the custom query search it is necessary to customize the project as it is not part of the default UI. When the custom query search is added to the customizing it can be used to replace the standard UI's [[Mobile_Free_Text_Search|free text search]] field or added additionally.

When using the custom query search in the customizing of a project it is necessary to provide the UID of the query object that should be used to define the search context. When no UID is given the search will never provide results. How exactly the search term is interpreted and used to return a List of results is handled on the server side.

The custom query search utilizes the same result handling as the [[Mobile_Free_Text_Search|free text search]]. This means the results for both searches are represented in the same list, replacing each other.

=== Parameters ===
* SearchText: takes the string that should be used as search term for the search.
* QueryID: takes the UID of the query object that should be used as search context.
* NavigateOnSingleResult: if this is set to true and a search returns only a single result the app will automatically navigate to the found object.

== Example ==
<tabs>
<tab name="UWP">
<source lang = "xml">
<AutoSuggestBox
...
<interactivity:Interaction.Behaviors>
<behaviors:AutoSuggestBoxInputBehavior>
<core:InvokeCommandAction Command="{Binding CustomQuerySearchCommand}">
<core:InvokeCommandAction.CommandParameter>
<controls:KeyValueList>
<controls:KeyValueParameter Key="SearchText" Value="{Binding ElementName=Search, Path=Text}" />
<controls:KeyValueParameter Key="NavigateOnSingleResult" Value="true" />
<controls:KeyValueParameter Key="QueryID" Value="bab1c694-a5ad-421f-8c85-faa385891e4b" />
</controls:KeyValueList>
</core:InvokeCommandAction.CommandParameter>
</core:InvokeCommandAction>
</behaviors:AutoSuggestBoxInputBehavior>
</interactivity:Interaction.Behaviors>
</AutoSuggestBox>
</source>
</tab>

<tab name="Xamarin">
<source lang = "xml">
<SearchBar
...
<behaviors:EventHandlerBehavior EventName="SearchButtonPressed">
<behaviors:InvokeCommandAction Command="{Binding CustomQuerySearchCommand}">
<behaviors:InvokeCommandAction.CommandParameter>
<classes:KeyValueList>
<classes:KeyValueParameter Key="SearchText"
Value="{Binding Path=Text, Source={x:Reference SearchField}}" />
<classes:KeyValueParameter Key="NavigateOnSingleResult" Value="true" />
<classes:KeyValueParameter Key="QueryID" Value="bab1c694-a5ad-421f-8c85-faa385891e4b" />
</classes:KeyValueList>
</behaviors:InvokeCommandAction.CommandParameter>
</behaviors:InvokeCommandAction>
</behaviors:EventHandlerBehavior>
</SearchBar.Behaviors>
</SearchBar>
</source>
</tab>
</tabs>

== See also ==
* [[SYSCLS_CUSTOMQUERYSEARCH]]

[[Category:Version 4.9|Custom Query Search]]

Custom Query Search

2024-12-10T06:57:41Z

LKR:

SYSCLS CUSTOMQUERYSEARCH

2024-12-10T06:56:54Z

LKR:

{{ClassificationInfoBox
| title = Custom Query Search
| name = {{PAGENAME}}
| inheritance = [[SYSCLS_QUERY]]
| namespace = System.Classification.Query
| purpose = Online search for objects defined by query
| version = 4.9+
| id = {4b3a85f5-1c6b-4215-afc9-796ce140c584}
}}

An object classified by SYSCLS_CUSTOMQUERYSEARCH and implementing the [[MetaProperties]] marks a [[query]] object as query used for searching within a subset of objects based on a search term online. The value of the SEARCHTEXT property has to be set.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=30% | Data type !! Comment
|-
| SEARCHTEXT || {{Text}} || Contains the text to search for online
|}

== See also ==
* [[Custom_Query_Search]]

[[Category:Classifications|SYSCLS CUSTOMQUERYSEARCH]]
[[Category:Version 4.9|SYSCLS CUSTOMQUERYSEARCH]]

Category:Version 4.9

2024-12-10T06:56:50Z

LKR: Created page with "Category:Version"

[[Category:Version]]

SYSCLS CUSTOMQUERYSEARCH

2024-12-10T06:56:19Z

LKR:

Category:4.9

2024-12-10T06:55:53Z

LKR: Created page with "Category:Version"

[[Category:Version]]

SYSCLS CUSTOMQUERYSEARCH

2024-12-10T06:54:54Z

LKR: Created page with "{{ClassificationInfoBox | title = Custom Query Search | name = {{PAGENAME}} | inheritance = SYSCLS_QUERY | namespace = System.Classification.Query | purpose = Online searc..."

UBIK Client Basics

2024-12-05T05:32:56Z

LKR: /* Finding Objects */

{{UBIK}} Client is the mobile application for viewing and modifying data, showing documents, starting navigation, visualizing POIs and much more.

Client applications are available for Android and WinX, however the features available on each of the platform dependent applications might differ. An overview of the available features can be found in the [[Client_Feature_Table|feature comparison table]].

== Start Screen ==
The start screen (or start menu) is the first visible view. It contains the login button and several actions, most of them accessible only after login. The start screen's content is [[HowTo:Configure Start Screen Content|configurable]]. For any specific app, the start screen usually also has a (overwritable) default configuration compiled into the app.

== Login ==
Users need to login in order to access confidential data, this can be done in the [[Login Dialog]].

There is the possibility to define user credentials on a webservice. The user might get a different login UI then, for further information please take a look at [[Serverside Account Configuration]]. {{Version/AndroidSince|2.5.0}}

== Settings ==
Users can configure access and edit the settings controlling {{UBIK}} environment using the [[Settings|settings list]].

== Action Bar ==
On the top of every {{UBIK}} Android view, there is the action bar. It provides features like the [[Mobile_Free_Text_Search|free text search]] and buttons for receiving/sending changes from/to the server. Depending on the customization, other items like a ''Support button'' or a ''QR Code Scan button'' can be available. In some views, there are different actions than in others; e.g. in the map view there are map-specific actions.

The action bar also allows access to the navigation drawer. It also shows an icon of the currently viewed object or the app's logo if the view is not object-related.

{| class="wikitable" | width = "100%"
|-
! Icon !! Action item !! Purpose
|-
| [[File:Action_update.png|46 px|center]] || ''Update'' || Updates the currently viewed object and its children or (if no object is viewed) the meta definitions and infrastructure objects from the server.
|-
| [[File:Action_commit.png|46 px|center]] || ''Commit'' || Sends eventual changes of the currently viewed object (and its children) to the server, or opens the commit manager if no context object is viewed. {{Version/AndroidSince|2.5.2}}
|-
| [[File:Action_search.png|46 px|center]] || ''Search'' || Opens an input field that can be used for finding objects by free text search. {{Version/AndroidSince|2.4.5}}
|-
| [[File:Action_support.png|46 px|center]] || ''Support'' (Demo only) || Opens the configured support app, e.g. the Visocon Xing app. {{Version/AndroidSince|2.5.1}}
|-
|}

== Navigation Drawer ==
[[File:UI_Android_Navigation_Drawer.png|180 px|thumb|border|alt=Navigation Drawer|Navigation Drawer]]
The navigation drawer provides a convenient and familiar way of navigating the app. {{Version/AndroidSince|2.4.0}} There are two ways of opening/closing the drawer.
* Pressing the app logo in the top-left corner;
* Swiping from/to the left edge of the screen

{| class="wikitable" | width = "100%"
|-
! Drawer item !! Purpose
|-
| Start menu || Opens the start screen
|-
| Settings || Opens the [[Settings|settings]]
|-
| Information || Shows information about the software version and the device
|-
| Scanning|| Contains child items for scanning various codes and markers. {{Version/AndroidSince|2.4.3}}
|-
| AR || Contains child items for opening the Map or POI view. {{Version/AndroidSince|2.5.3}}
|-
| Support || Starts the communication application (e.g. Skype or Visocon) and is available in the UBIK.Android.Demo application only. It is used to directly get in touch with a support agent. <br/>The respective target Uri is configurable. {{Version/AndroidSince|2.5.2}}
|-
| Sync mode || Switches {{UBIK}} between different [[Sync Mode|sync modes]]
|-
|}

== Info Screen ==

[[File:UBIK_Android_UI_Info_Activity_Certificate_List.png|400 px|thumb|border|alt=Certificate List|Certificate List]]

Shows static information about the app, like the version code and the minimum required web service version.
It also contains additional buttons:
* {{key press|Install Certificate}}: Allows to [[HowTo:Install_UBIK_Client_Certificate|add a server certificate]] to the app.
* {{key press|Clear Cache}}: Deletes all local data for the current user. {{Version/AndroidSince|2.5.0}}
* {{key press|Show Certificates}}: Shows a list of installed certificates, with alias/subject and expiry date. {{Version/AndroidSince|2.5.1}}

== Content Browser ==
Allows to navigate through the entire data model in a hierarchical manner, as it is published by the server.

Initially, a list of objects ("root objects") is shown. Upon selecting an object, a new browser is opened for that object, showing details about it.
When an object is selected in the content browser, it is called the browser's context.
For such a contextual object, child objects, properties and child documents are shown. Also, there is a context menu providing actions related to the currently selected object.

As every {{UBIK}} Android activity, the content browser also contains an action bar on the very top. By default, it provides a search button and buttons for updating an object or sending changes to the server ("committing").

=== Context Menu ===
[[File:UBIK_Android_UI_Content_Browser_Context_actions.png|400px|border|thumb|alt=Context Menu|Context Menu]]
In the Content Browser a context sensitive menu is available where actions can be triggered that are relevant for the currently viewed object.
For example the creation of a child element or showing this object in another view.

{| class="wikitable" | width = "100%"
|-
! Icon !! style="width:150px" | Action item !! Purpose
|-
| [[File:Action_create_content.png|46px|center]] || ''Create Object'' || Opens a selection dialog for possible child MetaClasses, creating an object for the user's choice. The new object is opened in a view for editing.
|-
| [[File:Action_take_picture.png|46 px|center]] || ''Take Picture'' || Opens the camera activity and creates a new document object for the resulting picture. The new object is opened in a view for editing.
|-
| [[File:Action_ar_nav.png|46 px|center]] || ''AR Navigation'' || Opens the AR navigation activity in order to navigate to the current object using augmented reality.
|-
| [[File:Action_geo_group.png|46 px|center]] || ''Geo Actions'' || Opens a selection dialog for several geo-related actions.
* ''Edit Geo Data'':[[File:Action_edit_geo_data.png|46 px|right]]
: Opens an editor for the geo location of the current object. Allows to use the device's current location for teach-in.
* ''AR Navigation'':[[File:Action_ar_nav.png|46 px|right]]
: Opens the AR navigation activity in order to navigate to the current object using augmented reality. {{Tip/Version|Feature removed in 2.5.3}}
* ''Show in Map'':[[File:Action_show_in_map.png|46 px|right]]
: Opens the Map activity, showing the current object.
* ''Use Location'':[[File:Action_use_location.png|46 px|right]]
: Uses the current object's location for positioning; applies the position for the device's location management.
|-
| [[File:Action_download_branch.png|46 px|center]] || ''Download Branch'' || Downloads the current object and all children and switches to offline mode.
|-
| [[File:Action_object_deletion_group.png|46 px|center]] || ''Delete Actions'' <br/>{{Version/AndroidSince|2.5.0}} || Provides several actions for reverting or removing the current object:
* ''Discard Local Object'':[[File:Action_icon_discard.png|46 px|right]]
: Deletes the object locally.
* ''Delete Object on Server'':[[File:Action_icon_delete.png|46 px|right]]
: Marks the object for deletion on the server.
* ''Revert Changes'':[[File:Action_icon_revert.png|46 px|right]]
: Undoes all local changes for the current object, resetting it to the last known status from the server.
|-
| [[File:Action_object_teach_in_group_wiki.png|46 px|center]] || ''[[UBIK_Client_Basics#Teach-in_Actions|Teach-in Actions]]'' <br /> {{Version/AndroidSince|2.5.2}} || Provides several actions for teaching-in values of scannable properties:
* ''QR-Code teach-in'':[[File:Action_icon_teach_in_qr_wiki.png|46 px|right]]
: Sets the value of the QR-Code property by scanning a QR-Code.
* ''Barcode teach-in'':[[File:Action_icon_teach_in_barcode_wiki.png|46 px|right]]
: Sets the value of the Barcode property by scanning a Barcode.
* ''RFID teach-in'':[[File:Action_icon_teach_in_rfid_wiki.png|46 px|right]]
: Sets the value of the RFID property by scanning a RFID-Tag.
|-
|}

{{Hint|Some actions are united in groups, e.g. the ''Geo Actions'' or the ''Delete Actions''. Clicking on the respective icons opens a selection dialog for the detail actions. <br/>Depending on the current object, some actions might not be available. If a group consequently contains only one element, it is displayed directly instead of the group.}}

=== Objects ===

==== Root objects vs child objects ====

The first entry point in the ''Content Browser'' is the list of root objects.
Since no element is viewed initially, there is no ''Context Menu'' here.

If an object is opened in the ''Content Browser'', it serves as its current "context".
The list of its child objects is shown in the left tab of the content browser when viewing an object.

==== Task objects ====
[[Task Objects (UBIK Android)|Task objects]] are {{UBIK}} objects with properties the user has to fill in. They can be identified by the status check box that shows their status (open or finished).

==== Query objects ====
[[Query Objects (UBIK Android)|Query objects]] are used for finding objects on the server using criteria entered on the client.

==== Safety relevant objects ====
The [[Safety Instructions]] feature allows to make sure a user has to view special ''Safety Documents'' before an object can be opened in the ''Content Browser''. {{Version/AndroidSince|2.5.1}}

==== Commissioning objects ====
[[Commissioning Objects (UBIK Android)|Commissioning objects]] are task objects with extended functionality. They can be identified by the status ican which either shows a cross a check or a circle.

==== Locked objects ====
In some cases it might be useful to lock objects until the user varifies to be near to these objects. This can be done with the [[SYSCLS_UNLOCK_BY_SCAN]] {{Version/AndroidSince|2.5.2}} and [[SYSCLS_UNLOCK_GROUP_BY_SCAN]] {{Version/AndroidSince|3.1.0}} classifications. Instances of MetaClasses implementing this classification can only be edited after the object gets unlocked. The unlocking can currently happen by scanning any type of code (QR-Code, Barcode, ID-Marker, RFID, OCR) which is related to the according object. After a certain period of time (default 15min) the object gets locked again. In the case of Unlocking a group of objects, alternatively also more than one object can be unlocked at once by sharing a common unlock code.

Take care that objects classified by [[SYSCLS_UNLOCK_BY_SCAN]] also need the corresponding properties (e.g. QR-Code property) such that the user is allowed to unlock these objects. In the case of unlocking a group of objects, only one of the objects needs to be scannable in order to onlock all of them. If an object is locked, it is not possible to edit its properties. Furthermore, context actions like redlining or editing of documents, geo teach-in and deletion of the object on the server is not possible. Basically the locking is the same for all types of objects, except for work packages – unlocking them also means unlocking all underlying items (Tasks, Commissioning checks) as well.

[[Category:Client|UBIK Client Basics]]

=== Properties ===
In the Content Browser, properties are shown in the properties tab. Their appearance depends on the data type of their value, whether they are modifiable and whether they are currently modified.
Also, modifiable properties can be edited using the property editors described below.

==== Live value properties ====

If a user wants to know an up-to-date measurement value, for instance whether it is save to enter a room or shut down a pump, this property provides him this information with very frequently updated [[Live Values| live values]].

==== Direct editing of boolean properties ====
The user can switch {{Boolean}} properties by either clicking the checkbox in the property list view (without visible editor), or by clicking the property row to open the corresponding editor.

==== Selective List Properties ====
The user can select a value from a list of possible values for this property, by clicking on the saved property value on the property list view. The corresponding editor is displayed with the drop-down list already expanded. Once the user selects a value from the list, the value is immediately saved and editor closed. It is also possible to cancel the editing or delete the value.

==== Teach-in Actions ====
Properties of type QR-Code, Barcode or RFID can be taught-in using the corresponding teach-in action, which is located in the context sensitive action bar. {{Version/AndroidSince|2.5.2}} An object has to implement the [[SYSCLS_OBJECTWITHIDMARKER]] or [[SYSCLS_OBJECTWITHRFIDTAG]] classification and a respective editable property in order to use this feature. When clicking on a teach-in action the corresponding scanner appears and once the right marker/tag is scanned, the code directly appears as the new property value.

==== Default and Initial Values ====
Default values are used as long as a property has no value on its own. Initial values are used for new instances so they aren't completely empty after creation. Both can be configured on the server. See also: [http://wiki.augmensys.com/index.php?title=MetaProperty#Default_value MetaProperty Wiki Article]

==== Editors ====
{{UBIK}} has built-in editors for different property types, including String, Integer, Double, Boolean, DateTime, Geo data and Selective list.
Clicking on the input field of a property (or task) will open the respective editor.

===== Geo Editor & Teach In =====
[[File:UI_ContentBrowser_TeachIn2_Android.png|thumb|220px|Geo Editor]]
Editor used to set GEO locations for a specific content object. This is done by accessing the GEO property editor of the object.

The user can enter the location manually or, if available, can use the location provided by the positioning service. In case the positioning service doesn't deliver any location the user has only the possibility to enter the location manually.

[[Category:Client|UBIK Client Basics]]

=== Documents ===
UBIK supports and displays document objects and a bunch of actions related to them (editing, redlining, creation, thumbnails, ...).
See the [[Documents_(UBIK_Android)|Documents]] article for further information on documents.

=== MRO ===
UBIK provides the logic for Maintenance, Repair and Operations (MRO) features. This means, a user can report the status of work to be accomplished. Therefore specific MRO configuartions provide essential objects like workpackages and tasks to report accomplished tasks, results and confirmed workpackages. See the [[MRO_Objects_(UBIK_WinX)|MRO]] article for further information on MRO.

[[Category:Client|UBIK Client Basics]]

=== Dynamic Content Tabs ===
{{Version/AndroidSince|2.5.0}}

The content browser's tabs (children, properties and documents) are only shown if necessary (and if they are not empty). For some types of objects (e.g. tasks) specific tabs are always shown though, especially if a tab is considered the main view for that object.

It is possible to configure this feature in order to behave more precisely as desired. By default, the children tab is shown if no other view should be shown explicitely and if the client has no information whether there are children or not. This means that for objects where (by customizing) the properties tab or the documents tab should be shown when entering the browser, the children view is only shown if it is not empty.

However, if nothing is configured, the children tab will be shown by default, because there could be children on the server and it would be annoying for the user to not see the children tab at all until something is loaded.

This is the other way round for the properties tab, because properties are always known as soon as the object itself is available on the client.

Also, the documents tab is not shown by default because the documents most often are not the primary view. If they are, the customizing should take this into account.<br/>

==== Customizing Possibilities ====
There are basically two ways to configure the dynamic tabs feature:
* One can configure the [[SYSCLS_CHILDINFOOWNER|Children Information Classification]] (former: Document Owner Classification): this will lead to a precise behaviour of the dynamic tabs, because the client has more detailed knowledge about the children of respectively classified objects.
* Another possibility is the configuration of the [[SYSCLS_SHOWPROPERTIES]] or [[SYSCLS_SHOWDOCUMENTS]] classifications: this will lead to the displaying of the properties/documents tab as initial view, even if it is empty.

[[Category:Client|UBIK Client Basics]]

== UI Configurations ==
See [[UI_Configuration_(Mobile_Client)]].

== AR Features ==

=== POI View ===
Brings up the [[POI View|Augmented Reality view]] and displays Points of Interest (POI's) related to the current location of the mobile device.

=== AR Navigation ===
Allows the user to navigate to an object using the [[AR Navigation|Augmented Reality Navigation]] feature.
It is accessible via a {{UBIK}} object's context menu in the Content Browser.

=== Markerless ===
Opens the [[POI View|Augmented Reality view]] supporting [[HowTo:Configure_Dynamic_AR_Content#Markerless_Activity|Markerless Scanning]] based on Image Detection. If the scanned Object is a Geo-Object, it´s location can be used through [[UBIK Client Basics#Object Proximity Positioning|Object Proximity Positioning]]

=== ID Marker 3D ===
Opens the [[POI View|Augmented Reality view]] supporting [[HowTo:Configure_Dynamic_AR_Content#ID_Marker_Activity|ID Marker Scanning]] based on ID Markers. If the scanned Object is a Geo-Object, it´s location can be used through [[UBIK Client Basics#Object Proximity Positioning|Object Proximity Positioning]]

=== Map View ===
Opens the [[map View|Map view]] and displays Points of Interest (POI's) related to the current location of the mobile device.

== Positioning ==
{{UBIK}} clients use a [[Location_Manager|Location Manager]] in order to gain knowledge about their position, so it can help the user navigate to his/her target.

[[Category:Client|UBIK Client Basics]]

== Finding Objects ==
=== Free Text Search ===
A [[Mobile_Free_Text_Search|free text search feature]] is available in the Action Bar. The search action item opens a text input field when clicked. Use it to find objects by their Meta Class name, their Display Strings or properties. The search feature works online and offline. {{Version/AndroidSince|2.4.5}}

=== Custom Query Search ===
The [[Custom_Query_Search|custom query search feature]] provides the possibility to search in a subset of objects defined by a query. In contrast to the [[Mobile_Free_Text_Search|free text search feature]] it does not include a offline search.{{Version/XamarinSince|4.9}}{{Version/WinXSince|4.9}}

=== ID Marker ===
Provides a fast and convenient way for users to find objects that are identifiable through [[optical code|optical codes]], in this case ID Markers. If the scanned Object is a Geo-Object, it´s location can be used through [[UBIK Client Basics#Object Proximity Positioning|Object Proximity Positioning]]

=== QR Code ===
Provides a fast and convenient way for users to find objects that are identifiable through [[optical code|optical codes]], in this case QR Codes. When using Getac Z710 the integrated barcode/qr-code scanner can get used. If the scanned Object is a Geo-Object, it´s location can be used through [[UBIK Client Basics#Object Proximity Positioning|Object Proximity Positioning]]

=== Bar Code ===
Provides a fast and convenient way for users to find objects that are identifiable through [[optical code|optical codes]], in this case Bar Codes. When using Getac Z710 the integrated barcode/qr-code scanner can get used. If the scanned Object is a Geo-Object, it´s location can be used through [[UBIK Client Basics#Object Proximity Positioning|Object Proximity Positioning]]

=== RFID ===
Provides a fast and convenient way for users to find objects that are identifiable through [[RFID tags|RFID tags]]. If the scanned Object is a Geo-Object, it´s location can be used through [[UBIK Client Basics#Object Proximity Positioning|Object Proximity Positioning]]

=== OCR ===
Provides a fast and convenient way for users to find objects that are identifiable through [[OCR|OCR]]. If the scanned Object is a Geo-Object, it´s location can be used through [[UBIK Client Basics#Object Proximity Positioning|Object Proximity Positioning]]. {{Version/AndroidSince|2.5.0}}

[[Category:Client|UBIK Client Basics]]

== Synchronization ==
The {{UBIK}} client gets its data from the UBIK Content web service and is capable of synchronizing differences between this service and itself.
All data can be worked with offline.

=== Updating and Committing ===
Sending changed data from the mobile device to the {{UBIK}} server is called "committing". Fetching new data from the server is called "updating".<br/>
In {{UBIK}} Android's Action Bar, there are buttons for both actions. Their detail behaviour depends on the current view:
* In the Start Menu, the update button acquires basic data like the meta definitions or the infrastructure objects. The commit button opens the Commit Manager.
* In the Content Browser, the update button updates the currently viewed object and its children. Similarly, the commit button sends changes for the currently viewed object to the server. When committing an object in the Content Browser, all its changed child objects are also committed. {{Version/AndroidSince|2.5.2}}
* In the Commit Manager, one can select objects to commit or update from a list of all changed objects.

=== Synchronization Mode ===
Depending on the [[Sync Mode]] setting, the synchronization will behave differently - either taking care of everything automatically or giving the user full control over which changes are sent ("committed") to the server and which updates are fetched from it.<br/>
There are the following Sync Modes:
* Automatic: Handles updates and commits without requiring user input.
* Manual Commit: Updates automatically, lets the user decide when to commit changes.
* Offline: Doesn't update nor commit anything automatically; except for special situations like the first login in a new environment.

=== Error Handling ===
{{UBIK}} tries to solve problems automatically, for example by retrying failed web requests or updating missing content.
In case of an error that couldn't be resolved automatically, an Android Notification is shown to gently notify the user what has happened and eventually give hints on how to solve the problem.

=== Push ===
The {{UBIK}} [[Push Service (Client)|push service]] is a mechanism used to notify a client of updates, show messages to the user or trigger other events on the client.

== See also ==
* [[Client_Feature_Table]]

[[Category:Client|UBIK Client Basics]]

Custom Query Search

2024-12-05T05:25:22Z

LKR: Created page with "{{UnderConstructionStart}} The custom query search uses a query provided via the customizing to define the context of the search. {{Version/WinXSince|4.9}}{{Version/XamarinSi..."

SYSCLS EDITABLEDOCUMENT

2024-10-30T13:39:43Z

LKR: /* See also */

{{ClassificationInfoBox
| title = Editable file classification
| name = {{PAGENAMEE}}
| inheritance = [[SYSCLS_FILEDOCUMENT]]
| namespace = System.Classification.Document
| purpose = Classify documents to be editable
| version = 2+
| id = {c084a457-f100-40eb-88bd-843fd7f402d4}
}}

Classifies an object for being recognized as editable file document object by the client. The physical document of such an object can be actually modifized on the client (e.g. editied by an appropriate PDF reader) and is sent back to the server.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=30% | Data type !! Comment
|-
| EDIT_FILE_ALLOWED|| {{Boolean}} || Allow the docmument to be edited
|-
| ''FILETYPE'' || {{Text}} || Specifies the file type (inherited from [[SYSCLS_FILEDOCUMENT]])
|}

== See also ==
* [[SYSCLS_FILEDOCUMENT]]
* [[FILEDOCUMENT]]
* [[Documents_(Client)#Editing_Documents]]

[[Category:Classifications|E]]
[[Category:Document|E]]

Documents (Client)

2024-10-30T13:38:52Z

LKR: /* Editing Documents */

[[DOCUMENT|Documents]] are [[:Category:UBIK Object|{{UBIK}} objects]] referencing a file, e.g. a PDF document.
Like other {{UBIK}} objects, they can be synchronized to the {{UBIK Client}}.
The Android client provides various features related to documents.

== Document Types ==

* Managed Document - Documents with a locally managed file.
* Linked Document - Documents with a file linked by an URL, not locally managed by {{UBIK}}.

== Viewing Documents ==

=== Viewing the File ===
Documents can be viewed using the [[UBIK_Client_Basics#Content_Browser|Content Browser]].
For every object, three content tabs are shown: "Children", "Properties" and "Documents".
The latter contains a thumbnail grid view for all document-type children of the current object.

A click on such a thumbnail shows the document if it was already downloaded, otherwise the document will be downloaded from the server and a dialog for showing it will be shown on success.

3rd party applications are used to show documents. Therefore, if no viewer for a certain file type (e.g. PDF) is installed, an error message will be shown.

<gallery widths="200" heights="200">
File:UI_TechSpec_UBIKClient_Document_01.png|Content Browser
File:UI_TechSpec_UBIKClient_Document_02.png|Object List
File:UI_TechSpec_UBIKClient_Document_03.png|Thumbnail grid
File:UI_TechSpec_UBIKClient_Document_04.png|Download document
File:UI_TechSpec_UBIKClient_Document_05.png|Open document
</gallery>

=== Viewing the Object Data ===

Not only the file, but also the {{UBIK}} property values of a document object can be viewed.
To do so, the thumbnail has to be long-clicked.
Then, the property list view for the respective object will be opened, allowing the user to change values (if it was configured on the server).

== Creating Documents ==

Depending on the configuration of the {{UBIK}} data model and the [[ACM]], documents can be created as children for existing objects.
A context menu entry appears in the [[UBIK_Client_Basics#Content_Browser|Content Browser]] for creating objects if this is configured.

Find detailed information how to create a new document on the client [[HowTo:Create_a_new_Document_(UBIK_Android)|here]].

=== Taking a Picture ===

In certain cases, the camera can be used to take a picture and create a document for it - in this case, another "Take Picture" context menu entry is available.

=== Editing and Submitting the newly created Document ===

After either a document was chosen or a picture was taken, the newly created object is opened in a property view, allowing the user to abort the creation or to enter specific property values (e.g. for the description of the object) and finally save the object.

{{Version/WinXSince|3.6}} uploaded Document objects can potentially contain [[SYSCLS_FILEDETAILSCLASSIFICATION|detailed Information]] concerning the original file (e.g. file name, path)
{{Clear}}

=== Synchronization ===

Depending on the connectivity mode, the next synchronization run will bring the new content and file to the server.

== Modify Documents ==

For editing, [[HowTo:Make_a_Document_ready_for_Redlining|Redlining]] and actually changing [[ManagedDocuments]] (where changing is allowed) is possible.

=== Redlining ===

Redlining is the process of creating a new, adapted version of an existing document. This can be achieved on the {{UBIK}} Android client, if it has been configured correctly in the {{UBIK}} data model and ACM.
A respective context menu button will be available in the ''Content Browser'' for a document object in this case.

For redlining, a copy of the document will be created and opened for editing in any installed 3rd party application that can handle the "intent".
When the user accepts the change, the creation of a new document object classified as a redlined document will be triggered (as described in "Creating Documents in {{UBIK}} Android").

The previous redlining number indicators are replaced by the [[Child_Document_Indicator_(Android)|child document indicators]]. {{Version/AndroidSince|2.4.5}}
{{Clear}}

=== Editing Documents ===
In order to edit a document managed by {{UBIK}}, one has to access the Document object by long-clicking its thumbnail in the documents-tab of its parent object's ''Content Browser''.
Then, the ''Content Browser'' for the Document object provides an "Edit File" action item in the context aware action bar. {{Version/AndroidSince|2.4.5}}

<gallery widths="200" heights="200">
File:UI_TechSpec_UBIKClient_Document_01.png|Content Browser
File:UI_TechSpec_UBIKClient_Document_02.png|Object List
File:UI_TechSpec_UBIKClient_Document_03.png|Thumbnail grid
File:UI_TechSpec_UBIKClient_Document_Properties.png|Document in Content Browser
</gallery>

==== Editing an already downloaded file ====
[[File:UI_TechSpec_UBIKClient_ChooseAppForEditing.png|thumb|Choosing a 3rd party application for editing]]
If the file was already downloaded, the user is asked to choose any installed 3rd party application for editing the respective file.
In case no such app is installed, editing the document is not possible.

{{Attention|The 3rd party app used for editing the file must be able to return the resulting file (in contrast to store it on the file system without telling {{UBIK}})!
A recommended app fitting this requirement is the [[https://play.google.com/store/apps/details?id=com.aviary.android.feather Photo Editor by Aviary]].}}

When the editing was finished, the new file is marked as changed and will be committed automatically if Automatic Sync mode is active, else the user can commit manually.

==== Editing a not yet downloaded file ====
[[File:UI_TechSpec_UBIKClient_EditDownloadedFile.png|thumb|Notification for editing a downloaded file]]
When a file wasn't downloaded yet but editing was chosen nontheless, the {{UBIK}} Android client will automatically download the file.
After the download was finished, the user is asked if (s)he wants to edit the document now.
If so, the editing proceeds as described for an already downloaded file.

=== PDF Text Search ===
It is possible to search and highlight arbitrary texts in the UBIK PDF viewer. By clicking the magnifier button, an input field opens to search for specific text entries in the document. The results will be highlighted in the PDF file. By clicking the arrow buttons, it is possible to switch to the next and previous results. {{Version/XamarinSince|4.3.0}}
==== Automatic Text Search {{Version/XamarinSince|4.4.0}}{{Version/WinXSince|4.4.0}} ====
Using the [[SYSCLS_DOCUMENT_HIGHLIGHTING_CLASSIFICATION|Document Highlighting Classification]] A PDF document can search for a defined search term from its parents properties automatically as soon as it is being navigated to.

[[Category:Android|Documents (UBIK Android)]]
[[Category:Document|Documents (UBIK Android)]]

== See also ==
* [[HowTo:Create_a_new_Document_(UBIK_Android)]]
* [[HowTo:Make_a_Document_ready_for_Redlining]]
* [[SYSCLS_DOCUMENT]] (Classification)
* [[SYSCLS_FILEDOCUMENT]] (Classification)
* [[SYSCLS_EDITABLEDOCUMENT]] (Classification)
* [[SYSCLS_REDLINEDFILE]] (Classification)
* [[SYSCLS_DOCUMENT_HIGHLIGHTING_CLASSIFICATION]] (Classification)
* [[SYSCLS_URLDOCUMENT]] (Classification)
* [[SYSCLS_THUMBNAILEDDOCUMENT]] (Classification)
* [[SYSCLS_TEXTDOCUMENT]] (Classification)
* [[SYSCLS_OFFLINE_AVAILABLE_DOCUMENT]] (Classification)

[[Category:Android|Documents (UBIK Android)]]
[[Category:Document|Documents (UBIK Android)]]

SYSCLS REDLINEDFILE

2024-10-30T13:31:55Z

LKR: /* See also */

{{ClassificationInfoBox
| title = Redlined file classification
| name = {{PAGENAMEE}}
| inheritance = [[SYSCLS_FILEDOCUMENT]]
| namespace = System.Classification.Document
| purpose = Classify file documents to be redlined
| version = 2+
| id = {96402695-d892-4de7-9e13-62e29976925e}
}}

Classifies an object for being recognized as redline file document object by the client. A redline file document can be created as child object of another document and is sent back to the server.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=30% | Data type !! Comment
|-
| ''FILETYPE'' || {{Text}} || Specifies the file type (inherited from [[SYSCLS_FILEDOCUMENT]])
|}

== See also ==
* [[Documents_(Client)#Redlining]]

[[Category:Classifications|R]]
[[Category:Document|R]]

SYSCLS URLDOCUMENT

2024-10-30T13:16:40Z

LKR:

{{ClassificationInfoBox
| title = Url document classification
| name = {{PAGENAMEE}}
| inheritance = [[SYSCLS_DOCUMENT]]
| namespace = System.Classification
| purpose = Classify objects as URL documents
| version = 2.4.3
| id = {D9890FE0-5C34-11E3-949A-0800200C9A66}
}}

Classifies an object for being recognized as URL document object by the client. URL documents can be viewed by clicking a link when the client is online.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| URL|| String || Specifies the url link to the document
|}

{{Attention|To provide links to local documents located in the client's file storage, the placeholder %PUBLIC% can be used. It will be replaced by the local user's "Picture" directory, as this an accessible, public folder on Windows 10 clients. E.g. you can provide "%PUBLIC%MyDocument.PDF" as a local link on the client. (Version 3.0.0.23+)}}

== See also ==
* [[Documents_(Client)#Document_Types]]

[[Category:Classifications|U]]
[[Category:Document|U]]

SYSCLS URLDOCUMENT

2024-10-30T13:15:03Z

LKR: /* See also */

{{ClassificationInfoBox
| title = Url document classification
| name = {{PAGENAMEE}}
| inheritance = SYSCLS_DOCUMENT
| namespace = System.Classification
| purpose = Classify objects as URL documents
| version = 2.4.3
| id = {D9890FE0-5C34-11E3-949A-0800200C9A66}
}}

Classifies an object for being recognized as URL document object by the client. URL documents can be viewed by clicking a link when the client is online.

== MetaProperties ==
{| class="wikitable" width=50%
|-
! width=30% | Name !! width=20% | Data type !! Comment
|-
| URL|| String || Specifies the url link to the document
|}

{{Attention|To provide links to local documents located in the client's file storage, the placeholder %PUBLIC% can be used. It will be replaced by the local user's "Picture" directory, as this an accessible, public folder on Windows 10 clients. E.g. you can provide "%PUBLIC%MyDocument.PDF" as a local link on the client. (Version 3.0.0.23+)}}

== See also ==
* [[Documents_(Client)#Document_Types]]

[[Category:Classifications|U]]
[[Category:Document|U]]