Components
Use the filters and selection to narrow the list by lifecycle stage, version, or both. Each card includes the feature’s release information, business and technical impact, toggle location, and the control for enabling or disabling the feature.
Version tabs
The version tabs under the Release Version, Rollout Version, and Expiration Version tabs are generated tabs from feature data.
- Default state (No version selected): The All tab is selected and all features are displayed.
- Version filter selected (Release Version, Rollout Version, or Expiration Version): The version tabs are generated based on the specific version in which the features are released, rolled out, or expired.
- Version tab selected: The feature list filters the features whose version match the selected version.
List of features
- Feature type: Each feature is classified as a Toggled Feature, Feature, or Defect.
- : Toggled features can be enabled or disabled by clicking the switch or toggle on the feature card.
- Reversible and irreversible features: You can disable reversible features after initial enablement. You cannot disable irreversible features after enablement because of data integrity or technical constraints. The rolloutVersion does not apply to these features.
- Note field: You can add and edit notes in the Note field.
- Business and Technical Impact: Use the
Potential Business Process Impact and Potential Technical Process Impact icons to
determine the feature impact.
This table shows the potential business impact and potential technical process impact values.
Value Potential Business Impact Example of Potential Business Impact: Potential Technical Process Impact Example of Technical Process Impact: None expected
No effect on business processes is expected. No customer action is required.
A bug fix corrects system behavior without changing business processes, manual steps, or required documentation review.
No technical effect is expected. No configuration or integration changes are required.
A bug fix corrects system behavior without changing technical processes, manual steps, or required documentation review.
Minor Minor effect on business processes. Customers may notice small changes but can continue working without action.
A visual or screen change, or an error resolution that may require testing or verification.
Minor technical effect. Customers may need to make small configuration adjustments.
A bug fix changes incorrect behavior and may require testing or verification.
Moderate Moderate effect on business processes. Customers should review the change and may need to adjust their processes.
A change adds functions to an existing feature, adds an optional minor feature, introduces a disabled enablement toggle, or supports a regulatory update.
Moderate technical effect. Customers should review the change and may need to update configurations or integrations.
A change adds imports or exports, updates delivered content or templates, changes processing parameters, or introduces a significant BOD or integration-layer update.
Major For system changes that affect business processes and could require immediate customer action.
A change adds a non-optional feature, changes the user experience or default settings, is not backward compatible, or provides measurable business value.
Major technical effect. Customers must take action to update configurations, integrations, or customizations to avoid disruption.
A change may break customizations, add or update replication sets, change default settings, or update security class rules or roles.