Features

Features are the core of Fecusio. They are used to represent and control a specific functionality in your application. For example, if you have an emailing tool, you could have an email scheduling feature that you would like to control access to for a certain group of users, a specific user, or even plans. You will need a feature created in Fecusio as a starting point in order to be able to configure it.

Managing Features

Features are managed on the “Features” page. You can create, edit, manage tags for and delete features.

Creating Feature

To create a feature, navigate to the Features page and click the “Create feature” button at the top. An aside will open asking you to provide the following data:

• Name - User-friendly name for the feature.
• Lookup key - Key that will be used for evaluation by your application. These should be unique across the entire workspace.
• Description - Brief description about what the feature represents.
• Tags - Assign one or multiple tags to organize the feature.

Once created, feature is available in all workspace environments.

Note

Once set, lookup key cannot be changed.

Editing Feature

To edit basic feature details like name and description:

1. Click on a feature on the Features page;
2. Once the aside opens, click on the three dots in the top right corner;
3. Pick “Edit” from the dropdown.

Deleting Feature

To delete a feature:

1. Click a feature on the Features page;
2. Once the aside opens, click on three dots in the top right corner;
3. Pick “Delete” from the dropdown.

Managing Feature Tags

To add or remove feature tags:

1. Click a feature on the Features page;
2. Once the aside opens, click on the “Details” tab;
3. Add or remove tags in the “Tags” box.

Managing Feature Flags

A feature flag is an entity that holds feature configuration for each environment. You control access to the feature and carry out rollouts/rollbacks through feature flags.

Configuring Feature Flag

By default, when you create a feature, a flag is automatically created for it in the environment you created the feature in. The flag is created with visibility “none” and disabled by default.

Visibility determines where your flag can be evaluated, and has the following options:

• None - Flag is never returned in evaluation response.
• Server-side - Flag is returned in evaluation response only when using a private environment key. Useful for flags relevant only on the server-side that you do not want exposed publicly.
• Public - Flag is always returned in evaluation response.

Default flag value is the value used when there are no overrides for the identities you are evaluating it for.

Note

Flag configuration is managed per environment.