[[File:UI_WinX_Customizing_Version.png|thumb|alt=Customizing Version|Customizing Version]]
* The version information of the UI customizings is available on the archive document and is displayed together with the client version at the bottom of the login page. Currently there's no additional UI to display a list of versions, so the version of a randomly chosen archive will be displayed in case multiple are present. Also, the version information only becomes available after a user logins in (which grants access to the content).
=== Known Issues ===
Sometimes, unpacking UI customizing archives might fail because the app cannot overwrite some files which are being used in the current UI. A typical example of this is related to using the Image control.
In the example below, an image file "UBIK.png" under the "Demo" customizing folder is referenced by an Image control. If an archive containing a set of UI customizings with the same name "Demo" is received on the client, the unpacking will fail because the UI is still holding onto the file, which blocks the unpacking.
<syntaxhighlight lang="xml">
<Grid>
<Image ...
Source="ms-appdata:///local/xaml/Demo/Images/UBIK.png" />
</Grid>
</syntaxhighlight>
This tends to happen with image files used in the login/home page since that's where users are most likely at when UI customizing archives are received. In such cases, one can use the following converter technique so that the image files can be safely deleted even when they are being displayed.
<syntaxhighlight lang="xml">
<Grid>
<Grid.Resources>
<x:String x:Key="logo">ms-appdata:///local/xaml/Demo/Images/UBIK.png</x:String>
</Grid.Resources>
<Image ...
Source="{Binding Source={StaticResource logo}, Converter={StaticResource PathToImageConverter}}" />
</Grid>
</syntaxhighlight>
{{Attention|The converter essentially creates a copy of the image file in the device memory. While solving the deletion problem, it does add up the memory consumption. So one should be cautious about using this converter too much especially when the images are relatively large.}}
{{Hint|An easy way to verify whether the failing of unpack is related to the deletion is to check in Windows Explorer whether there are files that can not be manually deleted in the target unpakcing folder before closing the {{UBIK}} app. If that's the case, please check the customizings and see if there's any reference to those files that can not be deleted. When the problem is not solvable with the above mentioned technique, please [https://support.augmensys.net/scp/index.php create a ticket with sufficient details] or manually delete the files after closing the app.}}
[[Category:Client|Deploy UI Customizings (Client)]]
[[Category:Pages with broken file links|Deploy UI Customizings (Client)]]
[[Category:WinX|Deploy UI Customizings (Client)]]