A feature flag (also known as a feature toggle) in software development is a mechanism that allows developers to enable or disable specific features of an application at runtime without deploying new code. 


This function purposely to deploy new features without making them visible to users, or make features visible only to specific subsets of users and environments and lessen the risk of feature when release by observe the behavior of the system and services under increasing load, collect user feedback and make changes, and limit the error if something goes wrong


Who use feature flags?

  1. QA to test functionality in production and validate changes.
  2. IT department to manage which end users get beta to access the feature
  3. Specific user to test in production.

Use Cases:

  1. Testing in Production
    Deploy a feature in a real production environment but only activate it for internal users or beta testers.

  2. Gradual Rollout
    Slowly release new functionality to a small percentage of users before rolling it out to everyone.

  3. A/B Testing
    Enable different versions of a feature to compare user interaction and behavior.

  4. Instant Rollback
    If a new feature causes unexpected problems, it can be instantly turned off, avoiding a redeployment.



Feature Flags - Manage > Feature Flags

  1. Name                 : The name should be specific and unique. It is to indicate which feature to have flags
  2. Base Company  : The BU's that have the access to the feature
  3. Description         : Details about the feature flags
  4. On/ Off                : Toggle to on or off the feature to be access to user
  5. Status                 : Either active or deleted



Case where the feature flags is active, the feature cannot be access to view, add, delete and edit item