product updates

Reporting: Missing Default Value

Zenmanage recently released a new report to help you better understand how your feature flags are being used. This report will help you identify which flags your app is using and whether you have a default value set for each flag.
A screen capture from Zenmanage showing the new missing default value report available for each project environment.
Each flag listed in the report lacks a default value. Additionally, if a row is highlighted, your app is using that flag. This is an essential distinction because your app may need to handle scenarios that can't reach Zenmanage correctly.
The report can be found under the reports section for any project environment.
A screen capture from Zenmanage showing how to find the new missing default value report.
Why is the default value significant in your software development lifecycle?
The default value for a flag is used when your app can't reach Zenmanage, or there is an issue with the response. Without a default, you need to handle the case when the app doesn't get a value when you evaluate a flag.
A caveat to keep in mind with default values is that you may want to periodically ensure that the default is what you want. When you release a new feature behind a feature flag, initially, you may want the default value to keep the feature off. After you turn it on, you may want to ensure that the default is on. Periodically verifying that will help ensure your users have the best experience.
Understanding your feature flag default values will ensure the best user experience for your users and team.
Did you like what you read? Share it with a friend.