You can access all your Dynamic configs from the CustomFit.ai dashboard. When you create a new Dynamic config, it will appear on the dashboard. You can easily find the Dynamic configs by using the search bar to filter by names. The Dynamic config dashboard provides various information about the configs such as :
A meaningful name of your Config that will allow you to easily locate it in the dashboard.
A unique key of your config to use in your code. Since the configs are identified through a key, CustomFit.ai has provided an option to copy your config key from the dashboard and place it in your code. Each Dynamic config has a unique key.
To efficiently manage the configs we should have the ability to determine when config is active or inactive and when config is safe to remove from your code.
CustomFit.ai makes it easy with the status field. Every config has a status field which reflects the state of the config. For example, if a config status is active then it is currently receiving requests.
Config can be in one of the four states :
New : The config is new and it has not received any requests.
Active : The config is active and it is receiving requests.
Inactive : The config has not received any requests from X days. By default the number of inactive days is set to 7 i.e., if config does not receive any request for 7 days then it is considered as inactive. We can change the number of inactive days.
Full rollout : All users are receiving the same variation of the config from X days. By default the number of full rollout days is set to 7 i.e., if the config is serving the same variation for 7 days then its status is changed to full rollout. We can change the number of full rollout days.
At the top of dashboard you can find the count of configs in each status.
Type column in the dashboard gives information about the type of config. For example, if the config is of type string then in the type column
STRING will be displayed. Other different values can be
variations column in the dashboard gives information about the total number of variations present under the config.
You can enable/disable the config from the CustomFit.ai dashboard if your config is not behaving as expected. With this option, there is no need for you to redeploy your code.
For example, Development and ops teams can use dynamic configs to deploy code when they want and keep those new features hidden until product and marketing teams are ready to share. Product and marketing teams then use the CustomFit.ai dashboard to turn features on/off.
When the config is turned off then the
off variation value of the config will be served. If the config is of a Boolean type then by default false will be set to off variation and for other types by default the last variation will be set as off variation.
Actions column, you can delete a config by clicking on delete icon. Once you click on delete icon a confirmation pop up window appears to confirm your delete action.