Methods and apparatuses for providing framework for selective execution of application features
View Patent ↗A method, apparatus and computer program product are provided in order to provide a framework for selective enablement of application features. An example of the method includes receiving, via an electronic communications interface, client credential information indicating at least one user or client facility, executing a first instance of an application by a processor, the first instance of the application comprising at least one feature selectively enabled or disabled by the framework, determining, during execution of the first instance of the application, a feature identifier associated with the at least one feature, retrieving feature information from a client feature table using at least the client credential information, determining whether the at least one feature is enabled for the at least one user or client facility, and, in response to determining that the at least one feature is enabled for the at least one user or client facility, executing the at least one feature.
1. A method for providing a framework for selective enablement of application features, the method comprising:
receiving, via an electronic communications interface, client credential information indicating at least one user or client facility;
executing a first instance of an application by a processor, the first instance of the application comprising at least one application feature selectively enabled or disabled by the framework, wherein the at least one application feature comprises a section of application code wrapped by a particular set of wrapper functions;
determining, during execution of the first instance of the application, a feature identifier associated with the at least one application feature;
retrieving feature information from a client feature table using at least the client credential information;
determining, based on the feature identifier and the feature information, whether the at least one application feature is enabled for an application execution context associated with the at least one user or client facility; and
in response to determining that the at least one application feature is enabled for the at least one user or client facility, causing the at least one application feature to be executed.
2. The method of claim 1 , further comprising:
retrieving metadata information associated with the at least one application feature from a feature metadata table;
determining a column of the client feature table based at least in part on the at least one application feature metadata; and
accessing data stored in the column of the client feature table when determining whether the at least one application feature is enabled for the at least one user or client facility.
3. The method of claim 1 , further comprising:
retrieving metadata information associated with the at least one application feature from a feature metadata table;
determining, based upon the metadata information, that the at least one application feature is not a beta feature; and
executing the at least one application feature in response to determining that the at least one application feature is not a beta feature.
4. The method of claim 1 , further comprising:
determining, a first time, whether the at least one application feature is enabled during execution of the first instance of the application, where a first result of the determining is that the at least one application feature is not enabled;
disabling the feature in response to determining that the at least one application feature is not enabled during execution of the first instance of the application; and
determining, a second time, whether the at least one application feature is enabled during execution of the first instance of the application, where a second result of the determining is that the at least one application feature is enabled.
5. The method of claim 1 , wherein the client facility is a healthcare facility.
6. The method of claim 1 , further comprising editing the client feature table to enable or disable the at least one application feature without rebuilding the application.
7. The method of claim 1 , further comprising:
editing, by a testing component, the client feature table to enable the at least one application feature for the first instance of the application;
editing, by the testing component, the client feature table to disable the at least one application feature for a second instance of the application; and
executing the second instance of the application such that the at least one application feature is disabled for the second instance of the application.
8. An apparatus for providing a framework for selective enablement of application features, the apparatus comprising:
application circuitry configured to:
execute a first instance of an application, the first instance of the application comprising at least one application feature selectively enabled or disabled by the framework, wherein the at least one application feature comprises a section of application code wrapped by a particular set of wrapper functions; and
feature management circuitry configured to:
receive, via an electronic communications interface, client credential information indicating at least one user or client facility;
determine, during execution of the first instance of the application, a feature identifier associated with the at least one application feature;
retrieve feature information from a client feature table using at least the client credential information;
determine, based on the feature identifier and the feature infori ation, whether the at least one application feature is enabled for an application execution context associated with the at least one user or client facility; and
in response to determining that the at least one application feature is enabled for the at least one user or client facility, cause the at least one application feature to be executed.
9. The apparatus of claim 8 , wherein the feature management circuitry is further configured to:
retrieve metadata information associated with the application feature from a feature metadata table;
determine a column of the client feature table based at least in part on the application feature metadata; and
access data stored in the column of the client feature table when determining whether the at least one application feature is enabled for the at least one user or client facility.
10. The apparatus of claim 8 , wherein the feature management circuitry is further configured to:
retrieve metadata information associated with the application feature from a feature metadata table;
determine, based upon the metadata information, that the application feature is not a beta feature; and
execute the at least one application feature in response to determining that the at least one application feature is not a beta feature.
11. The apparatus of claim 8 , wherein the feature management circuitry is further configured to:
determine, a first time, whether the at least one application feature is enabled during execution of the first instance of the application, where a first result of the determining is that the at least one application feature is not enabled;
disable the application feature in response to determining that the at least one application feature is not enabled during execution of the first instance of the application; and
determine, a second time, whether the at least one application feature is enabled during execution of the first instance of the application, where a second result of the determining is that the at least one application feature is enabled.
12. The apparatus of claim 8 , wherein the client facility is a healthcare facility.
13. The apparatus of claim 8 , wherein the feature management circuitry is further configured to edit the client feature table to enable or disable the at least one application feature without rebuilding the application.
14. The apparatus of claim 8 , wherein the apparatus comprises testing circuitry configured to:
edit the client feature table to enable the at least one application feature for the first instance of the application;
edit the client feature table to disable the at least one application feature for a second instance of the application; and
execute the second instance of the application such that the at least one application feature is disabled for the second instance of the application.
15. A non-transitory computer readable storage medium comprising instructions that, when executed by a processor, configure a processor to:
receive client credential information indicating at least one user or client facility;
execute a first instance of an application, the first instance of the application comprising at least one application feature selectively enabled or disabled by the framework, wherein the at least one application feature comprises a section of application code wrapped by a particular set of wrapper functions;
determine, during execution of the first instance of the application, a feature identifier associated with the at least one application feature;
retrieve feature information from a client feature table using at least the client credential information;
determine, based on the feature identifier and the feature information, whether the at least one application feature is enabled for an application execution context associated with the at least one user or client facility; and
in response to determining that the at least one application feature is enabled for the at least one user or client facility, cause the at least one application feature to be executed.
16. The computer readable storage medium of claim 15 , further comprising instructions that configure the processor to:
retrieve metadata information associated with the at least one application feature from a feature metadata table;
determine a column of the client feature table based at least in part on the at least one application feature metadata; and
access data stored in the column of the client feature table when determining whether the at least one application feature is enabled for the at least one user or client facility.
17. The computer readable storage medium of claim 15 , further comprising instructions that configure the processor to:
retrieve metadata information associated with the at least one application feature from a feature metadata table;
determine, based upon the metadata information, that the at least one application feature is not a beta feature; and
execute the at least one application feature in response to determining that the at least one application feature is not a beta feature.
18. The computer readable storage medium of claim 15 , further comprising instructions that configure the processor to:
determine, a first time, whether the at least one application feature is enabled during execution of the first instance of the application, where a first result of the determining is that the at least one application feature is not enabled;
disable the at least one application feature in response to determining that the at least one application feature is not enabled during execution of the first instance of the application; and
determine, a second time, whether the at least one application feature is enabled during execution of the first instance of the application, where a second result of the determining is that the at least one application feature is enabled.
19. The computer readable storage medium of claim 15 , wherein the client facility is a healthcare facility.
20. The computer readable storage medium of claim 15 , further comprising instructions that configure the processor to edit the client feature table to enable or disable the at least one application feature without rebuilding the application.