About feature flags
Once a flag is created, you can easily enable and disable features in your application - giving you full control over how users are able to interact with your application.
There is an important relationship between Applications, Environments, and flags that allows for increased reusability and scalability.
Applications are the highest-level in the hierarchy, encompassing unique environments and flags underneath them. Applications should reflect the individual products and services your organization may have. It should not reflect one app in several states of servers.
Environments represent your deployment pipeline: production, staging, or testing. CloudBees Feature Management supports working with multiple Environments. Refer to the Environments article for more information.
Flags are shared between Environments, but each environment feature flag configuration is different.
A flag default value is the value of the flag that is created when defining flags in the code. Default values are mandatory and flags cannot be created without them. They will be served when there is no configuration available (for any reason) or no other value overrides it.
A boolean flag is false by default. To override the value, pass the desired value to the flag.
A string flag has an explicit configuration for its default value. In most languages, the first value would be the default value followed by an array of potential values.
The Flags overview screen lists all flags, when the flag was created, when it was last updated, if they are linked to a feature, specific platforms, and shows which environments that use the flag.
You can sort table contents by selecting a column heading. The Name, Created, Updated, and Impressions columns can be sorted in ascending or descending order.
Select a flag to view details about its audience, settings, and audit logs.