Welcome to Headwind MDM Q&A, where you can ask questions and receive answers from other members of the community.

0 votes
I thought that when I added and saved an application on the web screen, I would be notified immediately and it would be installed on my device.

However, this was not actually the case.

Therefore, after adding the application, i was able to notify the device by calling the "/private/push" API.

Is there any way to notify the terminal from the web screen?

Also, what is the difference between "appConfigUpdated" and "configUpdated" in the messageType of the "/private/push" API?
by (140 points)
Which version of Headwind MDM web panel are you using? Sounds like a bug but in newer version this should not happen.
I do not know how to check the version of WAR.

I followed the instructions on this page and downloaded it from Github.
git clone https://github.com/h-mdm/hmdm-server.git
The version can be viewed by clicking the user name in the top right corner, and then "About".
The version displayed is 4.05.1.

1 Answer

0 votes

The issue sounds like a bug. You're right, clicking the "Configurations" icon in the application list doesn't trigger Push messages (the method responsible for it is ApplicationResource.java:updateApplicationConfigurations()). We will fix it in further version, but this may take time.

The Push message is sent by the backend, not by the frontend (is called by the Java code of the server component). See, for example, DeviceResource.java:updateDevice(), which is calling pushService.notifyDeviceOnSettingUpdate().

A correct Push message notifying Headwind MDM on the configuration update and processed by the launcher is configUpdated

A message of type appConfigUpdated is sent when application settings are updated. Since it doesn't affect the Headwind MDM launcher, it is not processed by the launcher. Third party apps can subscribe to receive this message - it means they need to refresh their configuration. See for details: https://h-mdm.com/headwind-mdm-api/

by (12.8k points)
Thank you for your answer.

I think there are times when you don't want to be notified and installed on the device immediately after saving the application.

For example, I call the device notification API only at 8am to update the application.
I don't want it to be updated at any other time.

Therefore, either keep a setting to notify the device immediately after the application is saved or not, or create a "Notify device immediately" button on the web screen without notifying the device after saving.