Changes
Created AppConfig Page
In enterprise environments, there are sometimes hundreds of employee phones centrally managed by some EMM (Enterprise Mobility Management) software. This not only allows to limit the apps available for use (via a company-internal store ("Company Play Store")) and remotely wipe devices (in the case of lost devices and fired employees), it also allows you to remotely set configurations of these apps to ease user experience. There are different types of management, like fully managed phones that belong to the company but also privately-owned phones with a work profile.
Starting with App Version 4.0.0, the Ubik Xamarin app will support managed app configuration for configuring profiles. That removes the need to manually copy over a Ubik Profile to every phone and importing it before its users can use Ubik. Historically, there was also the need to deploy the customizing ("XAML") before the app could be properly used, however, this has been solved already with the help of the XAML rollout feature.
== Function ==
The new '''''profile rollout''''' feature allows for the rollout of up to 9 individual [[Settings|Ubik Profiles]]. The configuration supports the [https://appconfig.org/ AppConfig.org] standard, allowing compatibility to almost every EMM software. During the application start, the current configuration values are read and profiles created (with <code>.managed.profile</code> ending). All profiles created by the system will be updated to the current configuration during the startup phase, allowing recently configured profiles to appear and no longer configured profiles to be removed. Other profiles added to the Ubik application will not be affected by this system (except they have a <code>.managed.profile</code> ending for some unknown reason). Clearing all profiles also clears the configured profiles, and the app needs to be restarted for them to update.
On Android, the system makes use of the Android Restrictions System. On iOS, the Capabilities System is used. These libraries are native to the system and widely supported.
== Configuration==
Microsoft Intune is just one of the EMM systems that will work with Ubik. This is the system that Augmensys uses for internal testing. For other EMM systems, the process will be similar.
For Intune, an Application Configuration Policy can be defined. It is possible to limit the scope of this policy to groups, devices, and even device management types. In the Configuration Designer, the desired values can be chosen, but for Ubik, all of them do the same and only differ by the number. For other EMM systems, this might be different, but you should end up with something similar-looking.
It is currently possible to define 9 Ubik profiles using this technology.
All that's necessary to get the profile rolled out is to open a profile in your favorite text editor (we recommend Visual Studio Code or Notepad++) and copy the entire content into the configuration value. If your EMM system doesn't want to paste in multi-line strings, use an XML-minifier first.
[[Category:Xamarin|Managed App Configuration]]
Starting with App Version 4.0.0, the Ubik Xamarin app will support managed app configuration for configuring profiles. That removes the need to manually copy over a Ubik Profile to every phone and importing it before its users can use Ubik. Historically, there was also the need to deploy the customizing ("XAML") before the app could be properly used, however, this has been solved already with the help of the XAML rollout feature.
== Function ==
The new '''''profile rollout''''' feature allows for the rollout of up to 9 individual [[Settings|Ubik Profiles]]. The configuration supports the [https://appconfig.org/ AppConfig.org] standard, allowing compatibility to almost every EMM software. During the application start, the current configuration values are read and profiles created (with <code>.managed.profile</code> ending). All profiles created by the system will be updated to the current configuration during the startup phase, allowing recently configured profiles to appear and no longer configured profiles to be removed. Other profiles added to the Ubik application will not be affected by this system (except they have a <code>.managed.profile</code> ending for some unknown reason). Clearing all profiles also clears the configured profiles, and the app needs to be restarted for them to update.
On Android, the system makes use of the Android Restrictions System. On iOS, the Capabilities System is used. These libraries are native to the system and widely supported.
== Configuration==
Microsoft Intune is just one of the EMM systems that will work with Ubik. This is the system that Augmensys uses for internal testing. For other EMM systems, the process will be similar.
For Intune, an Application Configuration Policy can be defined. It is possible to limit the scope of this policy to groups, devices, and even device management types. In the Configuration Designer, the desired values can be chosen, but for Ubik, all of them do the same and only differ by the number. For other EMM systems, this might be different, but you should end up with something similar-looking.
It is currently possible to define 9 Ubik profiles using this technology.
All that's necessary to get the profile rolled out is to open a profile in your favorite text editor (we recommend Visual Studio Code or Notepad++) and copy the entire content into the configuration value. If your EMM system doesn't want to paste in multi-line strings, use an XML-minifier first.
[[Category:Xamarin|Managed App Configuration]]
