Release Information Filtering Options
When you use SAP SuccessFactors release information, you see terms that we use to help you narrow the list of changes to those that you want to see.
We choose a title that helps you distinguish among the changes. Use it as a shorthand for the feature when discussing it with colleagues or SAP SuccessFactors.
We write a short description of the feature so that you can scan it to understand the feature. Use the description to understand, at a glance, what the change is: what is the thing that we’re delivering?
We often use modules to divide up our system. After interviews with customers, we settled on a set of modules that you use to divide our system into parts that you can understand. In many cases, the modules overlap with products, but not always. Use module to filter to the parts of our application that matter to you.
When we go to market, we talk about our features: parts of our software that offer your business benefits. You often see features when we highlight our products. We want you to filter our list by the features that matter to you.
Type is an SAP release information term that we use across products. It attempts to describe the type of change - for example, is this something completely new or is it a change to an existing feature?
Major or Minor
Major or minor describes the impact of the feature on your business. We don't have a hard definition of major and minor because we want to use it to flag impact as a person would sense it.
A series of phases that describe the state of development of a software product or feature. Software lifecycle phases go from experimentation and co-innovation, to general availability, to deleted. The phases help customers understand when they should adopt software and when they should start planning migration to another method of solving their business case.
Beta: A software lifecycle phase when features are made available for non-productive use so that customers can validate upcoming solutions from SAP.
Early Adoption: A software lifecycle phase when you can opt-in to features for productive use, but the features can have limitations and prerequisites that affect expected functionality.
General Availability: A software lifecycle phase when features are ready for productive use by all licensed customers. The features have no unexpected prerequisites or limitations.
Deprecation: The gradual phasing-out of a software or programming language feature. A feature or method marked as deprecated is one that is considered obsolete and whose use is discouraged. The feature still works in the current version of the software, although it may raise error messages as warnings. These serve to alert the user to the fact that the feature may be removed in future releases.
Deleted: The lifecycle phase when a feature is no longer available for productive use. You should now be using an alternative method for your business scenario.
Configuration type describes what you need to do to adopt the feature.
Universal changes are available without configuration.
Admin Opt-in features require you, as the customer, to take action to adopt the feature.
Admin Opt-out features require you, as the customer, to take action if you don’t want to adopt the feature.
Provisioning Opt-in features require action from SAP SuccessFactors or sometimes a partner to adopt the feature.
Provisioning Opt-out features require action from SAP SuccessFactors or sometimes a partner if you do not want to adopt the feature.
A reference number is a unique ID of the feature or change. Use it to discuss features with SAP SuccessFactors or among your team.
The software version is our major version that the change or feature applies to. Use it to filter to the set of features and changes that apply for the release you’re adopting. We keep older versions in the viewer so that you can go back and see all changes to a feature or module over time.
Valid as Of
Our software goes into production on a date. We consider the production date the date that the feature or change is available to you and your employees. The Valid as Of date is useful for features that don’t follow the major release cycle: changes that occur monthly, for example, or on a patch.
Latest Document Revision
Although we strive to have the correct information the first time, we do make mistakes in our release information. When we make a mistake, we update the Latest Document Revision date and in the details, we provide a note to describe the change. You can use the Latest Document Revision to filter to the release information that we have revised recently.