Data driven interfaces for decoupling components of a management system from manufacturer and platform of managed client devices
Disclosed are examples related to data driven interfaces for decoupling management system components from a manufacturer or a platform of client devices managed by the management system. In some examples, among others, a system can generate a data driven interface template that can be used to cause rendering of a data driven user interface for configuring a profile payload of a device profile for the client device. The system can generate, based on values associated with the data driven user interface, a profile document in an instance in which values are obtained from the data driven user interface. In some aspects, the profile document is a generic representation of the profile payloads for the platform, the manufacturer or the type of the client device.
1. A non-transitory computer-readable medium storing a plurality of instructions executable by a computing device, the plurality of instructions being configured to cause the computing device to at least:
generate a data driven interface template for decoupling at least one component of a management service from a platform, a manufacturer or a type of a client device;
render, based at least in part on the data driven interface template, a data driven user interface for configuring at least one of a plurality of profile payloads of a device profile;
generate, based at least in part on a plurality of values associated with the data driven user interface, a profile document in an instance in which the plurality of values are obtained from the data driven user interface, wherein the profile document comprises a generic representation of the device profile for the platform, the manufacturer or the type of the client device;
store the profile document in a command queue associated with a client device matching the device profile, wherein the client device is enrolled as a managed device with a management service; and
cause the client device to retrieve the profile document from the command queue.
2. The non-transitory computer-readable medium of claim 1 , wherein the instructions are further configured to cause the computing device to at least:
cause a device readable document based at least in part on the generic representation to be created in an instance in which the client device is notified to install the profile document.
3. The non-transitory computer-readable medium of claim 2 , wherein the instructions are further configured to cause the computing device to at least:
generate the device readable document based at least in part on reformatting the generic representation for the platform, the manufacturer or the type of the client device; and
provide the device readable document to the client device.
4. The non-transitory computer-readable medium of claim 1 , wherein the computing device generates the data driven interface template based at least in part on metadata for managing, based at least in part on the at least one of the profile payloads, at least one feature of the client device associated with the platform, the manufacturer or the type of the client device.
5. The non-transitory computer-readable medium of claim 4 , wherein the instructions are further configured to cause the computing device to at least:
obtain an input file comprising the metadata.
6. The non-transitory computer-readable medium of claim 4 , wherein the instructions are further configured to cause the computing device to at least:
generate a user interface comprising an editor for obtaining an edited version of the metadata, wherein the user interface is configured to render a preview of the data driven user interface based at least in part on the edited version of the metadata.
7. The non-transitory computer-readable medium of claim 1 , wherein the data driven user interface comprises a form, wherein the plurality of values are obtained in the instance in which the form is submitted.
8. A system, comprising:
at least one computing device; and
program instructions executable in the at least one computing device that, when executed by the at least one computing device, cause the at least one computing device to:
generate a data driven interface template for decoupling at least one component of a management service from a platform, a manufacturer or a type of a client device;
render, based at least in part on the data driven interface template, a data driven user interface for configuring at least one of a plurality of profile payloads of a device profile;
generate, based at least in part on a plurality of values associated with the data driven user interface, a profile document in an instance in which the plurality of values are obtained from the data driven user interface, wherein the profile document comprises a generic representation of the at least one of the plurality of profile payloads for the platform, the manufacturer or the type of the client device;
store the profile document in a command queue associated with a client device matching the device profile, wherein the client device is enrolled as a managed device with a management service; and
cause the client device to retrieve the profile document from the command queue.
9. The system of claim 8 , wherein the program instructions cause the computing device to:
cause a device readable document based at least in part on the generic representation to be created in an instance in which the client device is notified to install the profile document.
10. The system of claim 9 , wherein the program instructions cause the computing device to:
generate the device readable document based at least in part on reformatting the generic representation for the platform, the manufacturer or the type of the client device; and
provide the device readable document to the client device.
11. The system of claim 8 , wherein the computing device generates the data driven interface template based at least in part on metadata for managing, based at least in part on the at least one of the profile payloads, at least one feature of the client device associated with the platform, the manufacturer or the type of the client device.
12. The system of claim 11 , wherein the program instructions cause the computing device to:
obtain an input file comprising the metadata.
13. The system of claim 11 , wherein the program instructions cause the computing device to:
generate a user interface comprising an editor for obtaining an edited version of the metadata, wherein the user interface is configured to render a preview of the data driven user interface based at least in part on the edited version of the metadata.
14. The system of claim 8 , wherein the data driven user interface comprises a form, wherein the plurality of values are obtained in the instance in which the form is submitted.
15. A method, comprising:
generating, by a computing device, a data driven interface template for decoupling at least one component of a management service from a platform, a manufacturer or a type of a client device;
rendering, based at least in part on the data driven interface template, a data driven user interface for configuring at least one of a plurality of profile payloads of a device profile;
generating, based at least in part on a plurality of values associated with the data driven user interface, a profile document in an instance in which the plurality of values are obtained from the data driven user interface, wherein the profile document comprises a generic representation of the at least one of the plurality of profile payloads for the platform, the manufacturer or the type of the client device;
store the profile document in a command queue associated with a client device matching the device profile, wherein the client device is enrolled as a managed device with a management service; and
cause the client device to retrieve the profile document from the command queue.
16. The method of claim 15 , further comprising:
causing, by the computing device, a device readable document based at least in part on the generic representation to be created in an instance in which the client device is notified to install the profile document.
17. The method of claim 16 , further comprising:
generating, by the computing device, the device readable document based at least in part on reformatting the generic representation for the platform, the manufacturer or the type of the client device; and
providing, by the computing device, the device readable document to the client device.
18. The method of claim 15 , wherein the computing device generates the data driven interface template based at least in part on metadata for managing, based at least in part on the at least one of the profile payloads, at least one feature of the client device associated with the platform, the manufacturer or the type of the client device.
19. The method of claim 18 , further comprising:
generating, by the computing device, a user interface comprising an editor for obtaining an edited version of the metadata, wherein the user interface is configured to render a preview of the data driven user interface based at least in part on the edited version of the metadata.
20. The method of claim 15 , wherein the data driven user interface comprises a form, wherein the plurality of values are obtained in the instance in which the form is submitted.