Describe the feature you'd like
Support for custom intents which can be added through managed configuration.
To support settings intents not currently provided by MANAGED SETTINGS, offer the ability to add custom intents within the app configuration. The managed config should support:
Title
Description
Intent
Intents generated will fall under the category Your organisation and sit at the very top of the intents list, above Network & connectivity, and will show an organisation icon (so this will not be customisable).
The intent may be for Settings, or it may be for a custom application, MANAGED SETTINGS will not validate it.
Is your feature request related to a problem? Please describe.
OEMs often customise Android Settings, or add additional settings over what is provided by AOSP. It'd be a never-ending task attempting to support all of these intents natively, but having the option to input a custom intent for a particular OEM offers a simple solution to this problem.
Additional context
As I see this working, the managed configuration will support the addition of multiple nested intent configuration bundles. The admin clicks (+) add within the config to generate a new intent, and fills it out accordingly. Ad infinitum based on the number required. Intents no longer required can be deleted.
Unlike existing intents which bool on or off, custom intents will be added and deleted from the config respectively.
jasonbayton
commented
2 weeks ago
Describe the feature you'd like Support for custom intents which can be added through managed configuration.
To support settings intents not currently provided by MANAGED SETTINGS, offer the ability to add custom intents within the app configuration. The managed config should support:
Intents generated will fall under the category Your organisation and sit at the very top of the intents list, above Network & connectivity, and will show an organisation icon (so this will not be customisable).
The intent may be for Settings, or it may be for a custom application, MANAGED SETTINGS will not validate it.
Is your feature request related to a problem? Please describe. OEMs often customise Android Settings, or add additional settings over what is provided by AOSP. It'd be a never-ending task attempting to support all of these intents natively, but having the option to input a custom intent for a particular OEM offers a simple solution to this problem.
Additional context As I see this working, the managed configuration will support the addition of multiple nested intent configuration bundles. The admin clicks (+) add within the config to generate a new intent, and fills it out accordingly. Ad infinitum based on the number required. Intents no longer required can be deleted.
Unlike existing intents which bool on or off, custom intents will be added and deleted from the config respectively.
↓ Add your vote with a 👍 on this below.