To understand the importance of the features in your application, look at the order in which your application lists features. Your application lists features in order of relevance to the current implementation, with the oldest features at the top by default.
When you update an application, it retains the features from previous versions of the application, as well as from built-on applications. You can reorder features from previous or built-on applications in your current version, which by default your application lists in the following order:
- Features from the current version of your application: from the oldest to the newest.
- Features from earlier versions of your application: based on the order of features in those versions.
- Features from built-on applications: based on the order of features in those
If you have multiple built-on applications, the features follow the order from the built-on application stacks.
To override the default order and emphasize the features that are most important in the current version of your application, you can manually reorder features.
When you reorder the features in either an earlier version of your application or a built-on application, the current version of your application also reflects the changes, unless you customize the default order in the current version.
When you reorder the features in the current version of your application, the new order overrides any other changes that you make to feature order in earlier versions of your application or built-on applications.
You can also reset a custom feature order, back to the default order.
The system places new features that you add to your application at the end of the list of features.
The following figure shows a part of a feature map with features from a current application and built-on applications in a default order:
Previous topic Adopting feature-driven development Next topic Creating features