Constants are exposed in the cloud portal to manage its value. This is often very handy, but not always. Some constants are just technical values that need to be reusable, but that do not need to be visible or editable in the cloud portal.
Examples:
Such constants now clutter the list of constants.
So I suggest to include an option in a constant to make it private so it will not be visible in the cloud portal.
Done :-)
Now private constants are released, but with a different purpose (keeping secrets private). You should definitely rename this idea 😉
This idea is to target the difference between Configurable in Runtime vs Configurable Design time.
I totally agree there is a need for such a configuration constant. The main goal is to unclutter the list of configurable constants, so they should be at least environment independent. Maybe ‘private’ is not the best naming, but having a Boolean property ‘configurable in runtime’ added as setting, just like the ‘offline available’ setting.