Cryptlex Documentation
  • Welcome to Cryptlex!
  • Getting Started
    • Overview
    • Licensing Models
  • License Management
    • License Templates
    • Implementing License Models
    • Custom License Fields
    • Meter Attributes
    • Creating Licenses
    • Renewing Licenses
    • Extending Licenses
    • Suspending Licenses
    • Revoking Licenses
    • Maintenance Policies
  • User Management
    • Roles
    • Creating Users
    • Authenticating Users
    • Organizations
    • Resellers
    • Customer Portal
    • Reseller Portal
    • Google SSO
    • SAML SSO
  • Feature Management
    • Overview
    • Feature Flags and Product Versions
    • Use Cases
    • Creating Product Versions
  • Release Management
    • Overview
    • Creating Releases
    • Distributing Releases
  • Node Locked Licenses
    • Overview
    • Using LexActivator
      • Using LexActivator with C, C++ and Objective C
      • Using LexActivator with C#
      • Using LexActivator with VB.NET
      • Using LexActivator with Java
      • Using LexActivator with Delphi
      • Using LexActivator with Python
      • Using LexActivator with Go
      • Using LexActivator with Node.js
      • Using LexActivator with Ruby
      • Using LexActivator with Android
      • Using LexActivator with iOS
      • Using LexActivator with Flutter
    • Using Web API
    • Offline Activations
    • Proxies and Firewall
  • Floating Licenses
    • Overview
    • Hosted Floating License Server
    • On-Premise Floating Licenses
      • LexFloatServer
      • Using LexFloatClient
        • Using LexFloatClient with C, C++ & Objective C
        • Using LexFloatClient with C#
        • Using LexFloatClient with VB.NET
        • Using LexFloatClient with Java
        • Using LexFloatClient with Delphi
        • Using LexFloatClient with Python
        • Using LexFloatClient with Node.js
        • Using LexFloatClient with Go
        • Using LexFloatClient with Android
        • Using LexFloatClient with iOS
      • Offline Floating License
  • Named User Licenses
  • Timed Trials
    • Verified Trials
    • Unverified Trials
  • Licensing Docker Apps
  • Webhooks
  • Automated Emails
  • Web Integration
    • Personal Access Tokens
    • Using Web API
    • Using Zapier
    • Using FastSpring
    • Custom Development
  • Changelog
    • Web API
    • LexActivator
    • LexFloatClient
    • LexFloatServer
  • Legal
    • Terms of Service
    • Privacy Policy
    • Subprocessors
    • Data Processing Addendum
    • Service Level Agreement
    • Security, Privacy, and Compliance
    • Open Source Licenses
  • Cryptlex On-Premise
    • Overview
    • System Requirements
    • Server Layout
    • Installation Guide
      • Docker Compose
      • Kubernetes
    • Configuring Client Libraries
    • Monitoring and Error Reporting
Powered by GitBook
On this page
  • Entitlements within software
  • Testing
  • Changes without deployment
  • Value-based changes
  1. Feature Management

Use Cases

Some of the numerous cases in which our feature management suite can be used are:

  • Entitlements within Software

  • Testing

  • Changes without Deployment

  • Value-based changes

Entitlements within software

Creating Feature Flags for functionality you want to control among product flavours allows for hassle-free management. Example: When shipping your software, you want to have three variants: Lite, Pro, and Max with different features. For each variant, you can easily create a Product Version and within the Product Version, features defined by the Feature Flags can be enabled or disabled.

SaaS plans like Basic, Pro, Enterprise etc. can also be maintained using Product Versions.

Testing

The creation of different Product Versions allows you to test new functionality, turn off malfunctioning code, present different variations to different users(A/B Test) and much more. Example: You decide to test new functionality within your application with a select few users. To do this you can easily create a new Product Version in which the Feature Flag related to the new functionality is enabled and then link the user licenses to the newly created Product Version.

Changes without deployment

You can easily change the values of a Feature Flag using our admin portal or Web API. This is essentially useful when you want to change values that are causing errors in your application. Example: Your analytics plugin was updated with the new release of your application, however, this new plugin seems to be causing unexpected issues on your user's devices. If you have associated the usage of analytics with a Feature Flag, simply disabling the flag will stop your application from malfunctioning.

Value-based changes

Feature Flags in Cryptlex have an optional 'Data' field. This allows you to associate a String value with your Feature Flag. This is especially useful when you need to debug your application on the go. Example: Your application has set a certain data entry to be invalidated in 20ms, however, this has caused various errors after the recent Android update. Setting the value in a Feature Flag allows you to change the value from Cryptlex and have it reflected in your application.

PreviousFeature Flags and Product VersionsNextCreating Product Versions

Last updated 9 months ago