Learn how the version attribute in Import Device XML file works.

VHQ uses .XML file to import the device parameters. The importing of parameters into device is basically done through an automated script that generates an XML. In order to perform this action the application version requires specification to identify the device with the relevant application version and update the script to generate the XML. This attribute in the .XML file include placeholders to point to the version on device.

There are few points that you must consider:

• Make sure the relevant XML is imported for the device.
• Once the XML is imported, VHQ checks for the device.

NOTE: Current behaviour applies if the device is not already boarded, depends on what operation is set in XML file such as A, UA, D.

• VHQ checks the Application Version. If version = <Current> then VHQ checks, if the parameters defined for the version that is on the server matches the parameters defined in the in the XML. If any one of the parameters doesn't match it creates an error to specify that the Device ID and the list of parameters in the XML are not defined for the current version on the device. 
• If the parameters defined for the version that is on the server, matches the parameters defined in the XML, the parameters are updated.
• The Version attribute on an Application element is set to a special, recognized string with the value "Current" (case-insensitive). When the Version attribute is set to Current then any Parameters provided in the Parameters element associated with the relevant Application are assigned to the version of software which is presently assigned to the Device.

NOTE: The software assigned to a device may change as part of the import operation and this should also be accounted.

As the attribute Version is set to Current, VHQ identifies the version of My-Application application is associated with the Device ID, via the Reference Set associate to the Hierarchy that the device is being assigned to. VHQ then associates the parameters to the following version.

Devices that are not boarded to VHQ will not have the application version. Therefore, in such an instance we must check for the application version on the server.

For the devices that are getting boarded with software assignment through import or for the devices for which software is getting assigned through import, VHQ currently evaluates the software and parameters using asynchronous backend jobs. Same needs to be changed to make these jobs as synchronous or real-time. Otherwise for such devices parameter import will always fail. During import even if one of the parameters do not match the application parameters present on server for a device, the operation fails for the particular device.