The feature serves the purpose to establish the cloud mindset by making the move to the continuous feature delivery. Continuous feature delivery shifts the focus on delivering new functionality incrementally.
A Feature follows an easy workflow with the following statuses:
The following table shows you which activities related to the transport section are available in the respective feature statuses:
|Ready for Deployment||Yes||Yes||Yes||Yes|
The available project roles enable different actions with respect to features. The following table provides an overview of the most important actions possible:
It is always ensured that transports are deployed to the test system before all transports assigned to a feature can be deployed to the production system. Prior to the deployment of a Feature to production the approval for deployment needs to be given by the change & release manager (at the moment project lead or project admin).
Deployment of features
In this example the released transports O11K900079 and O11K900332 will be deployed to the target tenants.
In this example only the transports in status "Released" will be deployed to the target tenants. Indicator here is the mentioned dark grey color in contrast to the light grey color of the target tenants for the transports still in status "Modifiable".
Safeguard deployment to production
To ensure that a production system can only be delivered with a new feature in status "Ready for Deployment" you must assign the production system to the product role "Production" in the Project Landscape app.