US-20260126989-A1 - FEATURE CONFIGURATION PARITY

US20260126989A1US 20260126989 A1US20260126989 A1US 20260126989A1US-20260126989-A1

Abstract

A method of managing the configuration of software applications by importing different versions of the software, accessing their settings listings, and receiving selections for configurable features. It includes generating a feature parity file to compare the features of different versions and determining whether to distribute the new version based on this comparison. If there is feature parity, the new version is distributed to all endpoints. If not, a clone file is generated and distributed to a subset of endpoints for testing. Based on the test results, the new version is either distributed to the entire network or the clone file is maintained.

Inventors

Tohsheen Bazaz
Nandish KB
Phani Kumar Miryala

Assignees

IVANTI, INC.

Dates

Publication Date: 20260507
Application Date: 20251104
Priority Date: 20241107

Claims (18)

1 . A method of software application configuration management, the method comprising: importing a first version of a software application; accessing a first settings listing of the first version, the first settings listing including one or more configurable features of the first version; receiving selections of settings for the configurable features on the settings listing; distributing the first version of the software application to one or more managed endpoints; storing the selections in a first configuration file for the first version of the application; importing a second version of the software application; accessing a second settings listing of the second version, the second settings listing including one or more configurable features of the second version; prior to distribution of the second version, generating a feature parity file based on the first configuration file and the second setting listing, wherein: the parity file itemizes the configurable features of the first configuration file relative to the configurable features of the second settings listing, and indicates whether each of the configurable features of the first configuration file exist in the second settings listing or are removed in the second settings listing, indicates whether one of the configurable features of the second setting listing did not exist in the configurable file of the first version; in response to the feature parity file indicating that there is feature parity between the first version and the second version, distributing the second version to the endpoints to replace the first version; and in response to the feature parity file indicating that there is not feature parity between the first and the second versions: generating a clone file of the first configuration file and distributing the clone file to all but a subset of the endpoints; receiving selections of settings for the configurable features of the second settings listing; distributing the second version of the software application to the subset of the managed endpoints such that the second version is tested on the subset of the managed endpoints; storing the selections in a second configuration file for the second version of the application; based on a test of the second version in the subset of the managed endpoints, determining that the second version is functional in the subset and distributing the second version to a managed network; and responsive to the second version not being functional in the subset, distributing the clone file to the subset and leaving the clone file operable in the managed network.
2 . The method of claim 1 , wherein the first and the second version are imported into a mobile device management (MDM) system.
3 . The method of claim 1 , further comprising causing display of a user interface that displays at least a portion of the feature parity file.
4 . The method of claim 1 , wherein the accessing the files includes authenticating a system with a vendor of the software application communicating a query to the vendor that includes an API configured to receive the settings.
5 . The method of claim 1 , wherein the importing is from a public application storefront and the accessing is conducted from a vendor.
6 . The method of claim 1 , wherein the feature parity file includes: a first column that includes the configurable features of the first version and the selected setting for each of the configurable features; and a second column that includes the configurable features of the second version, wherein the first and second columns are organized according to the configurable features.
7 . A non-transitory computer-readable medium having encoded therein programming code executable by one or more processors to perform or control performance of operations of software application configuration management, the operations comprising: importing a first version of a software application; accessing a first settings listing of the first version, the first settings listing including one or more configurable features of the first version; receiving selections of settings for the configurable features on the settings listing; distributing the first version of the software application to one or more managed endpoints; storing the selections in a first configuration file for the first version of the application; importing a second version of the software application; accessing a second settings listing of the second version, the second settings listing including one or more configurable features of the second version; prior to distribution of the second version, generating a feature parity file based on the first configuration file and the second setting listing, wherein: the parity file itemizes the configurable features of the first configuration file relative to the configurable features of the second settings listing, and indicates whether each of the configurable features of the first configuration file exist in the second settings listing or are removed in the second settings listing, indicates whether one of the configurable features of the second setting listing did not exist in the configurable file of the first version; in response to the feature parity file indicating that there is feature parity between the first version and the second version, distributing the second version to the endpoints to replace the first version; and in response to the feature parity file indicating that there is not feature parity between the first and the second versions: generating a clone file of the first configuration file and distributing the clone file to all but a subset of the endpoints; receiving selections of settings for the configurable features of the second settings listing; distributing the second version of the software application to the subset of the managed endpoints such that the second version is tested on the subset of the managed endpoints; storing the selections in a second configuration file for the second version of the application; based on a test of the second version in the subset of the managed endpoints, determining that the second version is functional in the subset and distributing the second version to a managed network; and responsive to the second version not being functional in the subset, distributing the clone file to the subset and leaving the clone file operable in the managed network.
8 . The non-transitory computer-readable medium of claim 7 , wherein the first and the second version are imported into a mobile device management (MDM) system.
9 . The non-transitory computer-readable medium of claim 7 , wherein the operations further comprise causing display of a user interface that displays at least a portion of the feature parity file.
10 . The non-transitory computer-readable medium of claim 7 , wherein the accessing the files includes: authenticating a system with a vendor of the software application; and communicating a query to the vendor that includes an API configured to receive the settings.
11 . The non-transitory computer-readable medium of claim 7 , wherein the importing is from a public application storefront and the accessing is conducted from a vendor.
12 . The non-transitory computer-readable medium of claim 7 , wherein: the feature parity file includes: a first column that includes the configurable features of the first version and the selected setting for each of the configurable features; and a second column that includes the configurable features of the second version; and the first and second columns are organized according to the configurable features.
13 . A computer device comprising: one or more processors; and a non-transitory computer-readable medium having encoded therein programming code executable by the one or more processors to perform or control performance of operations of software application configuration management, the operations comprising: importing a first version of a software application; accessing a first settings listing of the first version, the first settings listing including one or more configurable features of the first version; receiving selections of settings for the configurable features on the settings listing; distributing the first version of the software application to one or more managed endpoints; storing the selections in a first configuration file for the first version of the application; importing a second version of the software application; accessing a second settings listing of the second version, the second settings listing including one or more configurable features of the second version; prior to distribution of the second version, generating a feature parity file based on the first configuration file and the second setting listing, wherein: the parity file itemizes the configurable features of the first configuration file relative to the configurable features of the second settings listing, and indicates whether each of the configurable features of the first configuration file exist in the second settings listing or are removed in the second settings listing, indicates whether one of the configurable features of the second setting listing did not exist in the configurable file of the first version; in response to the feature parity file indicating that there is feature parity between the first version and the second version, distributing the second version to the endpoints to replace the first version; and in response to the feature parity file indicating that there is not feature parity between the first and the second versions: generating a clone file of the first configuration file and distributing the clone file to all but a subset of the endpoints; receiving selections of settings for the configurable features of the second settings listing; distributing the second version of the software application to the subset of the managed endpoints such that the second version is tested on the subset of the managed endpoints; storing the selections in a second configuration file for the second version of the application; based on a test of the second version in the subset of the managed endpoints, determining that the second version is functional in the subset and distributing the second version to a managed network; and responsive to the second version not being functional in the subset, distributing the clone file to the subset and leaving the clone file operable in the managed network.
14 . The computer device of claim 13 , wherein the first and the second version are imported into a mobile device management (MDM) system.
15 . The computer device of claim 13 , wherein the operations further comprise causing display of a user interface that displays at least a portion of the feature parity file.
16 . The computer device of claim 13 , wherein the accessing the files includes: authenticating a system with a vendor of the software application; and communicating a query to the vendor that includes an API configured to receive the settings.
17 . The computer device of claim 13 , wherein the importing is from a public application storefront and the accessing is conducted from a vendor.
18 . The computer device of claim 13 , wherein: the feature parity file includes: a first column that includes the configurable features of the first version and the selected setting for each of the configurable features; and a second column that includes the configurable features of the second version; and the first and second columns are organized according to the configurable features.

Description

CROSS-REFERENCE TO RELATED APPLICATION This application claims priority to and the benefit of Indian Provisional Application No. 202411085352, filed November 7, 2024, which is incorporated herein by reference in its entirety. FIELD The embodiments described in this disclosure are related to mobile device management (MDM) processes, and more particularly to systems and methods of feature configuration visualization and feature parity confirmation between software application versions. BACKGROUND Endpoint devices such as mobile devices may be managed in systems referred to as mobile device management (MDM) system and unified endpoint management (UEM) systems. In general, MDM and UEM systems implement a service that enables a central system or a central console to control software applications and device settings on the endpoint devices. Control of the software applications and device settings may improve security posture of the endpoint devices and network or enterprise resources that are accessible to the endpoint devices. An aspect of the software application management is application configuration, which is also referred to as a restriction schema. In application configuration, a list of features supported by an application or used at runtime may be provided to an administrator at the central console. Selection of settings of the features configures the application prior to it being published to the endpoint devices. Review and selection of the settings for the features may consume resources of the administrator. New or updated versions of the software application may change one or more of the features. The changes to the features may result in inoperability after the updated versions are published to the endpoint devices. Moreover, elimination of features may remove or alter a setting that was previously selected by the administrator, which may result in security vulnerabilities or changes to use limitations by the endpoint devices. However, in conventional MDM and UEM systems, the updated versions may be dynamically published without administrative oversight or the administrator may be tasked with review of the features of the updated versions to ensure the upgraded version consistently applies the application configuration of a previous version. Accordingly, there is a need in MDM and UEM systems to enable feature visibility and feature parity confirmation. The subject matter claimed herein is not limited to embodiments that solve any disadvantages or that operate only in environments such as those described. Rather, this background is only provided to illustrate one example of a technology area where some embodiments described herein may be practiced. The object and advantages of the embodiments will be realized and achieved at least by the elements, features, and combinations particularly pointed out in the claims. It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are not restrictive of the invention, as claimed. SUMMARY According to an aspect of an embodiment includes a method of software application configuration management. The method may include importing a first version of a software application. The method may include accessing a first settings listing of the first version. The first settings listing may include one or more configurable features of the first version. The method may include receiving selections of settings for the configurable features on the settings listing. The method may include distributing the first version of the software application to one or more managed endpoints. The method may include storing the selections in a first configuration file for the first version of the application. The method may include importing a second version of the software application and accessing a second settings listing of the second version. The second settings listing including one or more configurable features of the second version. Prior to distribution of the second version, the method may include generating a feature parity file based on the first configuration file and the second setting listing. The parity file itemizes the configurable features of the first configuration file relative to the configurable features of the second settings listing. The parity file may indicate whether each of the configurable features of the first configuration file exist in the second settings listing or are removed in the second settings listing and may further indicate whether one of the configurable features of the second setting listing did not exist in the configurable file of the first version. The feature parity file may include a first column that includes the configurable features of the first version and the selected setting for each of the configurable features and a second column that includes the configurable features of the second version. The first and second columns may be organized according to the c