Variables
Variables are the elements that can change within a Feature.
For example, if you have a Feature that controls a new UI element, a Variable could be the color of that element.
By default, upon creation of a Feature, a `Boolean Variable`` will be created which has the same name as the Feature's key for easier reference.
Be sure to check out our advanced variable documentation which covers topics like:
Managing Variables
To view the Variables and Variations within a Feature, navigate to the 'Variables' section on a Feature page sidebar. This will lead the user to a table containing all of the Variables used by this Feature and all of their values across all Variations:
Each Feature manages its own set of Variables. By default, upon creation of a Feature, a Boolean Variable will be created which has the same name as the Feature's key for easier reference.
On the Feature page, there are indicators for each Variable that inform you of the following:
- if a Variable has been seen in code (if Code References have been enabled)
- if evaluations have been seen
These indicators are helpful when setting up features. They help to confirm proper setup, and aid in Variable cleanup once a Feature has completed it's lifecycle.
Hover over these indicators for more detail about a Variable's code references & evaluation information.
Depending on the Feature type, the default Variations will be pre-set. For example, the most common feature type is a Release Flag, and it will have two variations - "Variation OFF" and "Variation ON", with the boolean Variable being set to false and true, respectively.
For more information on variations please visit the variations section of the documentation.
Global Variables Dashboard
You can also view variables through the Variables dashboard, a collection of all Variables used within a project on a single list. In more complex or longer running projects, the Variables dashboard is useful to quickly find exactly what Feature is controlling a Variable (if any).
To navigate to this page, use the Variables button on DevCycle dashboard's top bar, which will lead you to the Variables list which will show:
| Variable Name | The name given to the Variable upon its creation |
| Feature | The name of the Feature that is currently managing a variable. Note that Variables can only be managed by a single Feature at a time. If you wish to change what Feature is managing a Variable, first remove that Variable from a feature as outlined in Creating Variables and Variations. If the Variable is NOT being managed by a Feature, this column will note the lack of Feature. Click on a Feature name to navigate directly to the Feature managing this Variable |
| Type | The type of the feature flag. This type can one of: Boolean, JSON, Number, Boolean, or String. |
| Created At | The time this Variable was first created. |
Variable Details
To access variable details, click "View Info" on the Variables list page for your Desired Variable. This page contains two sections:
| Section | Description |
|---|---|
| Variable Info | This section allows for the modification of the display name of the Variable, as well as the ability to provide a more detailed description of the Variable. |
| Code References | The Code References section is a collection of all of the areas within your codebase this Variable is actually being referenced, with a link out to the exact location within your GitHub codebase. |
To use the Code Refs feature, the DevCycle action for Code References must be enabled within your repository.
Creating a New Variable
A user can add as many Variables as they desire by simply clicking the "Add Variable" button.
Give your new Variable a key, a type, and its values for each of the current Variations.
The unique Variable key is used to reference the Variable in code. Variables cannot be used in multiple existing Features, so their keys must be unique.
The Variable Type helps enforce consistent usage across the team to avoid type mismatches in different use cases.
Variables may be the following types:
- Boolean
- String
- Number
- JSON
The Variable Values for each Variation will be what the Variable's value will be in SDK and API responses if a targeting rule is targeting those specific Variations.
For JSON variables, the only allowable Values are JSON objects with key-value pairs.
Updating a Variable
DevCycle allows users to edit the Variable Type of existing variables. We understand the importance of type-safety in variable management in addition to having flexibility when creating & editing variables. As such, editing unassociated variable versus associated variables differs slightly so you have as much context as possible on the ramifications of changing a variable type & its impact on your code.
Unassociated Variables
To edit an unassociated Variable, navigate to the Variable Details page of the variable you want to edit and select the new type from the dropdown.
Associated Variables
If a variable is currently associated with a feature, changes to the Variable Type must be done on the associated feature page. Once on the feature page, click on the edit icon next to the variable key and select a new Variable Type from the dropdown and click Update.
Be cautious when editing variable types as any code that is evaluating this variable must also be updated to expect the new type. A mismatch in variable types between the dashboard and your code will result in your code always returning the default value.
Removing a Variable
To remove a Variable from a feature, simply click on the edit icon next to the variable key and select the option to remove the variable from the variable edit modal.
Removing a Variable from this page does not completely remove the Variable from DevCycle. The Variable will still be visible in the Variable Dashboard, but it will not be associated with any features.
Taking this action will cause all references to the Variable in any code usage to default only to the default value used in your codebase.
To fully delete a Variable you must do so via our Management API.
Archiving a Variable
Archiving Variables is a good way to clean up the DevCycle dashboard and ensure that it is easy to understand which Variables are available for use and which should no longer be leveraged going forward.
To archive a Variable it must first be removed from any active features. Variables can be archived at the same time as removing from a feature. When the option to remove has been selected the confirmation modal will also provide the option to archive the Variable.
If a Variable is not archived when it is removed from a feature it will remain active, but it won't be associated with any features and the default value will be delivered whenever the Variable is evaluated in code. If you are archiving a Variable from the Variable list or Variable details page, the Variable must be in this unassociated state.
When archiving a Variable from the Variable list or details page you will need to confirm your desire to archive by entering the Variable's key in the archive confirmation modal.
Once archived, Variables can be viewed by toggling the Variable status filter to either All or Archived Variables on the Variable list page. From here Variables can also be unarchived if desired.
Re-associating a Variable
DevCycle has the ability to re-use existing variables and re-associate them to different features.
In the Variable Key input field, a drop down will display all unassociated, unarchived variables that can be re-associated to your feature while also providing you the option to add a net new variable.
If you select an existing, unassociated variable from the dropdown, the Variable type will be populated with the type of the selected variable and cannot be changed.
If you input a variable key that matches an existing archived variable, the error below will appear, as you must first unarchive the variable.
To use it, click the hyperlinked "variable" text, and you'll be directed to the archived variable page where you can unarchive it.
If you want to move a variable between features, you must first remove it from the previous feature, making it unassociated.