Limitations of APS settings branding
Modified on: Sat, 18 Nov 2023 5:31 AMOriginal Publishing Date:
2020-01-22
2020-01-22
Symptoms
Settings values from the brand are not applied to instance and/or are not passed to verification script when it's called. Instead, settings from resource type are used.
Cause
There are the following limitations to aps branding in POA:
- Branding does not work for global settings, except for entry point branding*.
- Branded settings are not applied on verification stage.
- Settings with 'login' and 'password' classes, or 'password' type, are not branded.
-
Avoid words 'login' and 'password' in branded setting IDs. They have the same effect as 'login' and 'password' classes.
- note: entry point is branded by setting with class="access_point", example application - Open-Xchange.
Resolution
- Move branded settings from global to top service, with 'hidden' attribute assigned.
- Don't expect branded values to be passed to verification script. Rely on default values from resource type.
- For branded settings, don't use 'login' and 'password' classes, 'password' type, 'login' and 'password' in setting ID.
Example application: BackupAgent