UBIK Wiki Test / Augmensys - Recent changes [en]

Traits

KGR — Mon, 27 Apr 2026 09:07:51 GMT

‎Customizing / UI Integration (XAML Examples)

Category:ActiveList

CWI — Mon, 27 Apr 2026 07:52:10 GMT

Blanked the page

UBIK Active Lists

CWI — Mon, 27 Apr 2026 07:50:37 GMT

Traits

KGR — Fri, 24 Apr 2026 12:01:03 GMT

Traits

KGR — Fri, 24 Apr 2026 11:44:37 GMT

Created page with "= UBIK Traits (Client) = '''UBIK Traits''' provide the ability to define a dynamic list of lightweight properties for individual instances (objects). Unlike traditional UBIK..."

New page

= UBIK Traits (Client) =

'''UBIK Traits''' provide the ability to define a dynamic list of lightweight properties for individual instances (objects). Unlike traditional UBIK Properties, which are rigidly bound to a MetaClass, instances of the same entity can possess a different list of traits.

This feature is particularly useful for data that only becomes known at runtime or varies significantly from instance to instance.

{{Attention|This feature must be used wisely, too many traits could impact the performance. Traits do not replace properties.}}

== ViewModel Architecture & Data Access ==
To work with traits in the UI (XAML), the <code>ContentViewModel</code> provides several dedicated accessors and collections.

=== 1. ValueAccessors (Recommended for Read/Write) ===
The <code>ValueAccessors</code> acts as a combined dynamic value resolver. It is the '''preferred way''' to read or edit values in the UI because of its built-in fallback logic:
# '''Trait Lookup:''' First attempts to resolve the value via a trait with the specified name.
# '''Property Fallback:''' If no trait is found, it queries a regular UBIK Property with that name.
# '''Default:''' If neither exists, it returns <code>null</code>.

=== 2. TraitByName (Traits Only) ===
A dedicated collection (<code>ObservableTraitDictionary</code>) that exclusively loads and initializes traits. Unlike the <code>ValueAccessors</code>, this does not fall back to regular properties.
* '''Usage:''' When you explicitly want to query ''only'' traits (e.g., read-only display in the UI).

=== 3. Values (Raw Data) ===
This is a combined getter that returns the raw value directly from the dictionary, instead of providing a complex <code>TraitViewModel</code> or <code>PropertyViewModel</code>.
* '''Usage:''' For pure display purposes or evaluations

----

== Commands (Set & Create Values) ==

=== SetValueCommand ===
This command on the <code>ContentViewModel</code> orchestrates value assignments and handles the '''creation of new traits''' if necessary.
* '''If the trait exists:''' The value will be overwritten.
* '''If a property exists:''' The property's value will be overwritten (if it is not locked/read-only).
* '''If neither exists:''' A new <code>TraitViewModel</code> is created and added to the UBIKContent.

----

== Customizing / UI Integration (XAML Examples) ==

To display traits in custom XAML templates, make them editable, or create new ones, standard UBIK controls like <code>EvalExpression</code> or <code>SfListViewExt</code> are used. Here are real-world code examples to guide you:

=== 1. Pure Display of All Traits (List View) ===
If you simply want to display all traits of an object, you can bind directly to <code>Content.Traits</code>. Here, it is combined with the Syncfusion ListView (<code>SfListViewExt</code>):
{{Attention| With that you only bind on DataModel level (changes on viewmodel level are only visible after saving).}}
<syntaxhighlight lang="xml">
<controls:SfListViewExt ItemsSource="{Binding Content.Traits}">
<controls:SfListViewExt.ItemTemplate>
<DataTemplate>
<Border Padding="10,8" BackgroundColor="#FAFAFA" Stroke="#E0E0E0" StrokeShape="RoundRectangle 8">
<Grid ColumnDefinitions="0.4*, 0.6*">
<Label Grid.Column="0" FontAttributes="Bold" Text="{Binding Name}" VerticalTextAlignment="Center" />
<Label Grid.Column="1" Text="{Binding Value, TargetNullValue='Not found'}" TextColor="#555555" VerticalTextAlignment="Center" />
</Grid>
</Border>
</DataTemplate>
</controls:SfListViewExt.ItemTemplate>
</controls:SfListViewExt>
</syntaxhighlight>

=== 2. Edit a Single Trait or Property (via ValueAccessors) ===
To dynamically query and edit a specific trait, use the <code>EvalExpression</code> with the <code>ValueAccessors</code> context. The <code>TwoWay</code> binding ensures that changes are written directly back to the ViewModel.

<syntaxhighlight lang="xml">
<controls:EvalExpression x:Name="EvalS2" Context="{Binding ValueAccessors}" Expression="Context[P0]">
<controls:EvalExpressionParameter Name="P0" Value="{Binding Path=Text, Source={x:Reference S2NameInput}}" />
</controls:EvalExpression>

<Entry x:Name="S2NameInput" Placeholder="Enter name..." />

<Entry x:Name="S2ValueInput" Text="{Binding Result.Value, Source={x:Reference EvalS2}, Mode=TwoWay, FallbackValue='Not found'}" />
</syntaxhighlight>

=== 3. Delete a Trait ===
Deleting a trait does not require a dedicated command. Instead, it uses an event behavior to directly invoke the <code>Delete</code> method on the evaluator's result.

<syntaxhighlight lang="xml">
<Button Text="Delete" BackgroundColor="#D32F2F" TextColor="White">
<Button.Behaviors>
<behaviors:EventHandlerBehavior EventName="Clicked">
<behaviors:InvokeMethodAction TargetObject="{Binding Result, Source={x:Reference EvalS2}}" MethodName="Delete" />
</behaviors:EventHandlerBehavior>
</Button.Behaviors>
</Button>
</syntaxhighlight>

=== 4. Create or Overwrite a Trait (via SetValueCommand) ===
To create traits entirely from scratch (or explicitly overwrite an existing value), the <code>SetValueCommand</code> of the <code>ContentViewModel</code> is used. A <code>KeyValueList</code> must be passed to this command.

<syntaxhighlight lang="xml">
<Grid ColumnDefinitions="*, Auto" ColumnSpacing="10">
<Entry x:Name="S4NameInput" Placeholder="Name of the (new) trait..." />
<Entry x:Name="S4ValueInput" Grid.Column="0" Placeholder="Enter value to set..." />

<Button Grid.Column="1" Command="{Binding SetValueCommand}" Text="Set">
<Button.CommandParameter>
<classes:KeyValueList>
<classes:KeyValueParameter Key="PropertyName" Value="{Binding Text, Source={x:Reference S4NameInput}}" />
<classes:KeyValueParameter Key="PropertyValue" Value="{Binding Text, Source={x:Reference S4ValueInput}}" />
</classes:KeyValueList>
</Button.CommandParameter>
</Button>
</Grid>
</syntaxhighlight>

=== 5. Edit Specific Datatypes (e.g., DatePicker) ===
Traits store actual underlying datatypes (such as <code>DateTime</code>). This means you can bind regular UI controls like a <code>DatePicker</code> directly to the result of the <code>EvalExpression</code>.

<syntaxhighlight lang="xml">
<controls:EvalExpression x:Name="EvalDateTime" Context="{Binding}" Expression="Context.ValueAccessors[P0]">
<controls:EvalExpressionParameter Name="P0" Value="{Binding Path=Text, Source={x:Reference DateTraitNameInput}}" />
</controls:EvalExpression>

<Entry x:Name="DateTraitNameInput" Text="TRAIT_DATETIME" />

<DatePicker x:Name="DateTestPicker" Date="{Binding Result.Value, Source={x:Reference EvalDateTime}}" Format="dd.MM.yyyy" />

<Button Command="{Binding SetValueCommand}" Text="Set">
<Button.CommandParameter>
<classes:KeyValueList>
<classes:KeyValueParameter Key="PropertyName" Value="{Binding Text, Source={x:Reference DateTraitNameInput}}" />
<classes:KeyValueParameter Key="PropertyValue" Value="{Binding Date, Source={x:Reference DateTestPicker}}" />
</classes:KeyValueList>
</Button.CommandParameter>
</Button>
</syntaxhighlight>

----

Version 5.1.0 (Server)

NWE — Fri, 24 Apr 2026 09:14:30 GMT

Active List Client

CWI — Thu, 23 Apr 2026 13:49:29 GMT

‎XAML

MRO Objects (Client)

LKR — Thu, 23 Apr 2026 12:35:11 GMT

‎Task

UBIK WinX Client Basics

CWI — Thu, 23 Apr 2026 12:22:17 GMT

‎Selective List Properties

MROCLS PICK LIST TASK

ARU — Wed, 22 Apr 2026 09:36:08 GMT

Version 5.1 (WinX)

LGE — Tue, 21 Apr 2026 15:49:07 GMT

Active List Client

CWI — Tue, 21 Apr 2026 08:38:19 GMT

‎Introduction {{Version/WinXSince|5.1.0.0}} {{Version/MobileSince|5.1.0.0}}

UBIK WinX Client Basics

CWI — Mon, 20 Apr 2026 13:21:21 GMT

‎Selective List Properties

Converters In Mobile

CWI — Mon, 20 Apr 2026 13:19:26 GMT

‎List of Available Converters

UBIK WinX Client Basics

CWI — Mon, 20 Apr 2026 13:16:57 GMT

‎Selective List Properties

UBIK Active Lists

CWI — Mon, 20 Apr 2026 12:47:22 GMT

‎Further Notes

Active List Client

CWI — Mon, 20 Apr 2026 10:01:32 GMT

MRO Objects (Client)

CWI — Mon, 20 Apr 2026 09:54:49 GMT

‎See also

Category:Active List

CWI — Mon, 20 Apr 2026 09:52:53 GMT

Blanked the page

Active List Client

CWI — Mon, 20 Apr 2026 09:52:11 GMT

MRO Objects (Client)

CWI — Mon, 20 Apr 2026 09:32:15 GMT

‎Task

Converters In Mobile

ARU — Mon, 20 Apr 2026 09:27:52 GMT

‎List of Available Converters

UBIK Active Lists

ARU — Mon, 20 Apr 2026 09:25:38 GMT

Converters In Mobile

ARU — Mon, 20 Apr 2026 09:22:18 GMT

‎List of Available Converters

MROCLS PICK LIST TASK

CWI — Mon, 20 Apr 2026 09:04:12 GMT

Converters In Mobile

CWI — Mon, 20 Apr 2026 08:48:31 GMT

‎List of Available Converters

Active List Client

ARU — Mon, 20 Apr 2026 08:44:05 GMT

UBIK Active Lists

ARU — Mon, 20 Apr 2026 08:37:43 GMT

Active List Client

ARU — Mon, 20 Apr 2026 08:35:43 GMT

Version 3.7.1 (Server)

NWE — Mon, 20 Apr 2026 07:46:29 GMT

Active List Client

ARU — Mon, 20 Apr 2026 07:32:09 GMT

‎Introduction

← Older revision		Revision as of 07:52, 27 April 2026
Line 1:		Line 1:
−	~~[[Category:Server]]~~	+

@@ Line 10: / Line 10: @@
 If a MetaProperty has both a SelectiveList and an ActiveList, the ActiveList takes precedence when data is displayed on the client, and the SelectiveList is ignored.
-[[Category:ActiveList|UBIK Active Lists]]
-[[Category:Server|UBIK Active Lists]]
 = Client Behavior =
@@ Line 115: / Line 115: @@
 * When both an ActiveList and a SelectiveList are defined for the same MetaProperty, the ActiveList overrides the SelectiveList on the client.
 [[Category:Server|UBIK Active Lists]]

← Older revision		Revision as of 12:01, 24 April 2026
Line 126:		Line 126:

	----		----
		+
		+	[[Category:Client\|Traits]]
		+	[[Category:Mobile\|Traits]]
		+	[[Category:MAUI\|Traits]]

@@ Line 39: / Line 39: @@
 === Enhancements ===
 -->
 === Known Issues ===
 * Due to Configurable Unique Constraints not being implemented yet, Exclusive Access is not guaranteed on database level currently.
@@ Line 101: / Line 96: @@
 -->
 </div></div>
+<div class="toccolours mw-collapsible mw-collapsed" style="width:100%; overflow:auto;">
-[[Category:Release notes|Version 5.1.0 (Server)]]
+<div style="font-weight:bold;line-height:1.6;"><h2 style="text-decoration:none;border-style:none">Web Service</h2></div>
-[[Category:Server|Version 5.1.0 (Server)]]
+<div class="mw-collapsible-content">
-[[Category:Version 5.1|Version 5.1.0 (Server)]]
+<!--
 = 5.1.0.10003 - 2026-04-01 (Initial Release) =

@@ Line 12: / Line 12: @@
 === XAML ===
-A new SelectiveItems property was added to the PropertyViewModel to enable access to an ActiveList via XAML. No DataTriggers or additional checks are required, as the correct list selection is handled automatically.
+A new SelectiveItems property was added to the PropertyViewModel to enable access to an ActiveList via XAML. No DataTriggers or additional checks are required, as the correct list selection is handled automatically. As also mentioned [[UBIK_WinX_Client_Basics#Selective_List_Properties|here]], the following XAML changes are necessary:
 <tabs>
@@ Line 41: / Line 48: @@
      DisplayMemberPath="DisplayText"
      ItemsSource="{Binding PropertyViewModel.SelectiveItems}"
      PlaceholderText="{Binding PropertyEdit_PickerPlaceholder, Source={StaticResource AppResources}}"
      SelectedValue="{Binding PropertyValue, Mode=TwoWay}"

@@ Line 1: / Line 1: @@
-= UBIK Traits (Client) =
+= {{UBIK}} Traits (Client) =
-'''UBIK Traits''' provide the ability to define a dynamic list of lightweight properties for individual instances (objects). Unlike traditional UBIK Properties, which are rigidly bound to a MetaClass, instances of the same entity can possess a different list of traits.
+'''{{UBIK}} Traits''' provide the ability to define a dynamic list of lightweight properties for individual instances ({{UBIK}} objects). Unlike traditional {{UBIK}} Properties, which are rigidly bound to a MetaClass, instances of the same entity can contain a different list of traits.
 This feature is particularly useful for data that only becomes known at runtime or varies significantly from instance to instance.
@@ Line 13: / Line 13: @@
 The <code>ValueAccessors</code> acts as a combined dynamic value resolver. It is the '''preferred way''' to read or edit values in the UI because of its built-in fallback logic:
 # '''Trait Lookup:''' First attempts to resolve the value via a trait with the specified name.
-# '''Property Fallback:''' If no trait is found, it queries a regular UBIK Property with that name.
+# '''Property Fallback:''' If no trait is found, it queries a regular {{UBIK}} Property with that name.
 # '''Default:''' If neither exists, it returns <code>null</code>.
 === 2. TraitByName (Traits Only) ===
-A dedicated collection (<code>ObservableTraitDictionary</code>) that exclusively loads and initializes traits. Unlike the <code>ValueAccessors</code>, this does not fall back to regular properties.
+TraitByName is a dedicated collection (<code>ObservableTraitDictionary</code>) that exclusively loads and initializes traits. Unlike the <code>ValueAccessors</code>, this does not fall back to regular properties.
 * '''Usage:''' When you explicitly want to query ''only'' traits (e.g., read-only display in the UI).
 === 3. Values (Raw Data) ===
 This is a combined getter that returns the raw value directly from the dictionary, instead of providing a complex <code>TraitViewModel</code> or <code>PropertyViewModel</code>.
-* '''Usage:''' For pure display purposes or evaluations
+* '''Usage:''' For pure display purposes or evaluations.
 ----
 == Commands (Set & Create Values) ==
@@ Line 32: / Line 40: @@
 * '''If the trait exists:''' The value will be overwritten.
 * '''If a property exists:''' The property's value will be overwritten (if it is not locked/read-only).
-* '''If neither exists:''' A new <code>TraitViewModel</code> is created and added to the UBIKContent.
+* '''If neither exists:''' A new <code>TraitViewModel</code> is created and added to the {{UBIK}} content.
 ----
-== Customizing / UI Integration (XAML Examples) ==
+== XAML Customizing / UI Integration ==
-To display traits in custom XAML templates, make them editable, or create new ones, standard UBIK controls like <code>EvalExpression</code> or <code>SfListViewExt</code> are used. Here are real-world code examples to guide you:
+To display traits in custom XAML templates, make them editable, or create new ones, standard {{UBIK}} controls like <code>EvalExpression</code> or <code>SfListViewExt</code> are used.
 === 1. Pure Display of All Traits (List View) ===
@@ Line 128: / Line 136: @@
 [[Category:Client|Traits]]
 [[Category:MAUI|Traits]]

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

@@ Line 172: / Line 172: @@
 {{UnderConstructionStart}}
-{{Hint|{{Version/WinXSince|5.1.0.0}}{{Version/MobileSince|5.1.0.0}} The ItemsSource binding of related WinX/Mobile controls in Xaml now requires only '''PropertyViewModel.SelectiveItems''', which will return the items of an [[Active_List_Client|ActiveList]], or the items of a MetaProperty.SelectiveList, depending on the server-side configuration. Mobile only: In this case, the [[Converters_In_Mobile#List_of_Available_Converters|SelectiveListToItemsConverter]] is outdated and should not be used anymore.}}
+{{Hint|{{Version/WinXSince|5.1.0.0}}{{Version/MobileSince|5.1.0.0}} The ItemsSource binding of related WinX/Mobile controls in Xaml now requires only '''PropertyViewModel.SelectiveItems''', which will return the items of an [[Active_List_Client|ActiveList]], or the items of a MetaProperty.SelectiveList, depending on the server-side configuration. In this case, the [[Converters_In_Mobile#List_of_Available_Converters|SelectiveListToItemsConverter]] is outdated and should not be used anymore.}}
 {{UnderConstructionEnd}}

@@ Line 10: / Line 10: @@
 Classifies an object as a Pick List Task.
-A Pick List Task needs a predefined [[UBIK_Active_Lists|Active List]] to pick from for its value property. The task counts as finished as soon as a list item has been selected. Each List item needs an integer value assigned to it. The value 0 is reserved for the server since it is used to provide a reopening functionality for the task.
+A Pick List Task needs a predefined [[UBIK_Active_Lists|Active List]] to pick from for its value property. The task counts as finished as soon as a list item has been selected. Each List item needs an integer value assigned to it.
 == MetaProperties ==
@@ Line 17: / Line 17: @@
 ! width=30% | Name !! width=20% | Data type !! Comment
 |-
-| VALUE || {{Integer}} || Selected item (Undefined = 0)
+| VALUE || {{Integer}} || Selected item
 |}

← Older revision		Revision as of 15:49, 21 April 2026
Line 23:		Line 23:
	* Fixed an issue where [[SYSCLS_CHILDINFOOWNER\|child count]] indicators did not update when you delete its child objects which only exist locally.		* Fixed an issue where [[SYSCLS_CHILDINFOOWNER\|child count]] indicators did not update when you delete its child objects which only exist locally.
	* Fixed an issue where line breaks (in strings property values) from Windows are not recognized as such on other systems.		* Fixed an issue where line breaks (in strings property values) from Windows are not recognized as such on other systems.
		+
		+
		+	=== 5.1.9 on 2026-04-22 ===
		+	* Fixed an issue that prevented any documents from being uploaded when connecting to 5.1 webservices.

@@ Line 6: / Line 6: @@
 {{Hint|There are no visible differences in the UI between an ActiveList and a MetaProperty SelectiveList.}}
-[[Multi_Select_%28UBIK_Client%29#Editing_common_properties_of_selected_items_.28UWP_only.29|Mass editing]] is currently not supported for Properties containing Active Lists.
+'''Limitations'''
 === XAML ===
@@ Line 46: / Line 49: @@
 </tabs>
 == See also ==

@@ Line 233: / Line 233: @@
 |-
 | SelectiveListToItemsConverter || style="text-align: center;" | ✗ || List of PropertyItems  || IPropertyItem || ||
-Returns all items from a selective list. The converter can only be used in combination with a standard MetaProperty level [[SELECTIVELIST|SelectiveList]], not with an instance level [[Active_List_Client|Active list]].
+Returns all items from a selective list. The converter can only be used in combination with a standard MetaProperty level [[SELECTIVELIST|SelectiveList]], not with an instance level [[Active_List_Client|Active list]]. Further infos see in [[UBIK_WinX_Client_Basics#Selective_List_Properties|Selective List Properties]].
 |-
 | SfDataSourceConverter || style="text-align: center;" | ✗ || DataSource (for ListView) || Double || String (Expression) ||

@@ Line 168: / Line 168: @@
 ==== Selective List Properties ====
-For some properties, the user should be able to select from a predefined set of values. Such a predefined set is called a "selective list" in {{UBIK}}. Furthermore, there are [[Dynamic_Selective_List_(Client)|dynamic selective lists]] that can be filtered or assembled based on dependency property values.
+For some properties, the user should be able to select from a predefined set of values. Such a predefined set is called a "selective list" in {{UBIK}}.
 ==== Properties with value records {{Version/WinXSince|2.5.4}} ====

@@ Line 5: / Line 5: @@
 {{UBIK}} ActiveLists are the representation of such lists. They update dynamically on the client side without requiring an ACM rebuild and can be maintained per instance through server methods.
 {{UnderConstructionStart}}
 = Client Behavior =
 When the user opens an ActiveList:
@@ Line 109: / Line 113: @@
 * ActiveLists are designed for lightweight, instance-specific value lists that can be updated without ACM rebuilds.
 * They are ideal for use cases where list content varies between instances of the same MetaClass.
-* When both an ActiveList and a SelectiveList are defined for the same MetaProperty, the SelectiveList overrides the ActiveList on the client.
+* When both an ActiveList and a SelectiveList are defined for the same MetaProperty, the ActiveList overrides the SelectiveList on the client.
 [[Category:ActiveList|UBIK Active Lists]]
 [[Category:Server|UBIK Active Lists]]

← Older revision		Revision as of 10:01, 20 April 2026
Line 5:		Line 5:

	{{Hint\|There are no visible differences in the UI between an ActiveList and a MetaProperty SelectiveList.}}		{{Hint\|There are no visible differences in the UI between an ActiveList and a MetaProperty SelectiveList.}}
		+
		+	[[Multi_Select_%28UBIK_Client%29#Editing_common_properties_of_selected_items_.28UWP_only.29\|Mass editing]] is currently not supported for Properties containing Active Lists.

	=== XAML ===		=== XAML ===

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

← Older revision		Revision as of 09:52, 20 April 2026
Line 1:		Line 1:
−	~~[[Category:Client]]~~	+

@@ Line 48: / Line 48: @@
 * [[UBIK Active Lists|Active Lists Server]]
 * [[MROCLS PICK LIST TASK|Pick List Task]]
+* [[MRO_Objects_(Client)#Pick_List_Task|MRO Objects (Client) Pick List Task]]
 {{UnderConstructionEnd}}
 [[Category:Client|Active List Client]]
 [[Category:Mobile|Active List Client]]
 [[Category:Version 5.1|Active List Client]]
 [[Category:WinX|Active List Client]]

@@ Line 118: / Line 118: @@
 '''Two-way''' converters can be used with two-way bindings, e.g. a text-box displaying an editable value. If the value updates in the model, the text-box text changes. If the user edits the value, the value in the model behind also gets updated.
 As a clarification, '''Value''' refers to the '''Binding Value''', and '''parameter''' to the '''ConverterParameter'''!
 {| class="wikitable sortable" style="width:100%"
@@ Line 256: / Line 259: @@
 | DataTemplateItemsPanelConverter || style="text-align: center;" | ✗ || ItemsPanelTemplate || Query<wbr/>Details<wbr/>Page<wbr/>ViewModel || || Chooses what '''ItemPanel<wbr/>Template''' to return. Having a parameter with the content "Small" returns the small item template selector.
 |}
 [[Category:Client|Converters In Xamarin]]

@@ Line 8: / Line 8: @@
 If a MetaProperty has both a SelectiveList and an ActiveList, the SelectiveList takes precedence when data is displayed on the client, and the ActiveList is ignored.
 = Client Behavior =
 When the user opens an ActiveList:
@@ Line 22: / Line 23: @@
 For more details see: [[Active List Client]]
 = Server-Side Concept =

@@ Line 216: / Line 216: @@
 Converts a property to a '''boolean''' based on its '''existence'''. If it exists, ''false'' will be returned, else ''true'' or ''null'' (if something couldn't be properly interpreted).
 |-
 | RootAreaTemplateConverter || style="text-align: center;" | ✗ || ContentView || Object || ||
 If the provided value is '''not null''', the '''UBIKRootArea template''' will be returned.

@@ Line 2: / Line 2: @@
 ==Introduction {{Version/WinXSince|5.1.0.0}} {{Version/MobileSince|5.1.0.0}}==
-If an Active List is defined on a [[Instance|Content Object]] that is associated with an [[MetaProperty#Integer|integer]] [[MetaProperty]], the property is displayed like a usual [[UBIK WinX Client Basics#Selective List Properties|SelectiveList]]. An ActiveList (i.e., if it has been configured on the server for a content object) always takes precedence over a MetaProperty SelectiveList. For editing, it behaves exactly the same as with a standard SelectiveList.
+If an Active List is defined on a [[Instance|Content Object]] that is associated with an [[MetaProperty#Integer|integer]] [[MetaProperty]], the property is displayed like a usual [[UBIK WinX Client Basics#Selective List Properties|SelectiveList]] which is based on a [[MetaProperty]]. An ActiveList (i.e., if it has been configured on the server for a content object) always takes precedence over a MetaProperty SelectiveList. For editing, it behaves exactly the same as with a standard [[SELECTIVELIST|SelectiveList]].
 {{Hint|There are no visible differences in the UI between an ActiveList and a MetaProperty SelectiveList.}}
 === XAML ===
-A new SelectiveItems property was added to the PropertyViewModel to enable access to an ActiveList from XAML. No DataTriggers or additional checks are required, as the correct list selection is handled automatically.
+A new SelectiveItems property was added to the PropertyViewModel to enable access to an ActiveList via XAML. No DataTriggers or additional checks are required, as the correct list selection is handled automatically.
 <tabs>
-<tab name="MAUI">
+<tab name="Mobile (MAUI)">
 <source lang = "xml">
 <controls:SfListViewExt
      x:Name="SelectiveList"
@@ Line 26: / Line 28: @@
 <tab name="UWP">
 <source lang = "xml">
 <controls:ComboBoxExt
      x:Name="ComboBox"

@@ Line 1: / Line 1: @@
 {{UnderConstructionStart}}
-==Introduction {{Version/MobileSince|5.1.0.0}}==
+==Introduction {{Version/WinXSince|5.1.0.0}} {{Version/MobileSince|5.1.0.0}}==
-If an Active List is defined on a [[Instance|Content Object]] that is associated with an [[MetaProperty#Integer|integer]] [[MetaProperty]], the property is displayed using the existing icon (the same icon applied to properties with a [[UBIK WinX Client Basics#Selective List Properties|SelectiveList]]), followed by the property's display string and the label of the currently selected list item in a closed drop-down component. An ActiveList (i.e., if it has been configured on the server for the content object) always takes precedence over a MetaProperty SelectiveList
+If an Active List is defined on a [[Instance|Content Object]] that is associated with an [[MetaProperty#Integer|integer]] [[MetaProperty]], the property is displayed like a usual [[UBIK WinX Client Basics#Selective List Properties|SelectiveList]]. An ActiveList (i.e., if it has been configured on the server for a content object) always takes precedence over a MetaProperty SelectiveList. For editing, it behaves exactly the same as with a standard SelectiveList.
-For editing, it behaves exactly the same as with a standard SelectiveList. The client uses a dropdown menu UI component and the dropdown menu allows the user to select exactly one value from the Active List.
+{{Hint|There are no visible differences in the UI between an ActiveList and a MetaProperty SelectiveList.}}
-−
-When the user opens the dropdown:
-* All available options from the ActiveList are displayed as text labels.
-* The label for each option is shown in the language configured on the web service. If a translation for the configured language is unavailable, the label is displayed in the default language.
-* Each option in the ActiveList has an associated unique integer value that is set to the MetaProperty when selected.
-* Only one option can be selected at a time. Selecting an option updates the MetaProperty value immediately.
-−
-Sorting of items in the dropdown:
-−
-* If all options in the ActiveList have unique sort order values, they are displayed in ascending order of these sort order values.
-* If sort orders are not unique, options with the same sort order are sorted in ascending order by their label.
 === XAML ===
-To enable access to an ActiveList from XAML, a new property named SelectiveItems was added to the PropertyViewModel. This property returns the ActiveList if one is configured on the content object; otherwise, it falls back to the SelectiveList defined on the MetaProperty if no ActiveList is available for the content object. Below is an example of how this can be implemented in XAML. For the SelectedItem, it is important to use the PropertyValueToSelectiveItem converter and pass the control’s own ItemsSource path as the ConverterParameter, so that the list can be provided to the converter. This means that no DataTriggers or similar mechanisms are required to switch between ActiveLists and MetaProperty SelectiveLists or to perform any checks.
+A new SelectiveItems property was added to the PropertyViewModel to enable access to an ActiveList from XAML. No DataTriggers or additional checks are required, as the correct list selection is handled automatically.
 <tabs>
@@ Line 50: / Line 39: @@
 </tab>
 </tabs>
 {{UnderConstructionEnd}}
 [[Category:Active List|Active List Client]]
 [[Category:Client|Active List Client]]
 [[Category:Version 5.1|Active List Client]]

@@ Line 182: / Line 182: @@
 * 3.7.1 Build 15480 on 2025/08/11
 ** An issue in UBIK.SmartStudio, where MetaProxyProperties with the same name but different data types were confused with each other, was fixed.
-* 3.7.1 Build 15495 on 2026/04/17
+* 3.7.1 Build 15496 on 2026/04/20
 ** An issue where selective items weren't transported correctly via SmartStudio was fixed.
 ** An issue where saving a situation with system MetaProperties could fail was fixed.