You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given that Collect is running and managed by MDM
When I change the device_id key in my MDM system
Then I should see that reflected next time I look at the settings or access deviceid from a form
Given that Collect is running and managed by MDM
When I change the settings_json key in my MDM system and those settings are invalid
Then nothing should happen in Collect
Given that Collect is running and managed by MDM
When I change the settings_json key in my MDM system and those settings include a URL+username combination that matches an existing project
Then that project should be updated to match the settings pushed by MDM
Given that Collect is running and managed by MDM
When I change the settings_json key in my MDM system and those settings include a URL+username combination that does NOT match an existing project
Then a new project should be created with all of the settings I pushed
Pushing new settings should not change the active project.
The text was updated successfully, but these errors were encountered:
Some users manage their device fleets with Microsoft Intune, TinyMDM and other mobile device management solutions.
We've had request to set the device id and full settings from MDM.
These values should be updated at app launch and any time the settings are changed on the MDM system.
For full settings, we can use a JSON string following the settings format.
Given that Collect is running and managed by MDM
When I change the device_id key in my MDM system
Then I should see that reflected next time I look at the settings or access deviceid from a form
Given that Collect is running and managed by MDM
When I change the settings_json key in my MDM system and those settings are invalid
Then nothing should happen in Collect
Given that Collect is running and managed by MDM
When I change the settings_json key in my MDM system and those settings include a URL+username combination that matches an existing project
Then that project should be updated to match the settings pushed by MDM
Given that Collect is running and managed by MDM
When I change the settings_json key in my MDM system and those settings include a URL+username combination that does NOT match an existing project
Then a new project should be created with all of the settings I pushed
Pushing new settings should not change the active project.
The text was updated successfully, but these errors were encountered: