AppConfig

Managed parameters of one selected Android or Apple application.

All parameters

Parameter	Purpose and values	Verification and dependencies
Application	Select the application the configuration is created for.	The application must support managed configurations; check the version and platform.
KEY	The exact parameter name from the application schema.	Case and nesting are defined by the application developer. Do not use made-up keys from generic examples.
Type	String, Integer, Boolean, or Double.	The type must match the application schema: the string true is not Boolean true.
VALUE	The parameter value of the selected type.	String — text; Integer — a whole number; Boolean — a logical value; Double — a number with a fractional part.
Add/remove parameter	Changes the list of pairs in this configuration.	After removal, check whether the application resets the value or keeps the previous one locally.

Limitations and dependencies

One profile targets one application. Saving a key in MDM does not confirm that the application has read it. For SuperApp, use the confirmed schema of the specific version; restrictions of an external viewer are not equivalent to control of data inside SuperApp.

Creating and assigning

Create a configuration, fill in the parameters, and run the preliminary check. After saving, assign recipients. Start with a single test device.

Verifying application

In the device card, check the assignment and the recent contact. In client events, find the processing result, then check the feature itself on the device. If the feature did not change, check the management channel, platform, delivery, and compatibility.