Promoting a Task or Process
Promotion is the application lifecycle management tool in SAP Cloud Integration for data services. It allows you to copy and move a task or process from one environment to the next available environment, for example, from Sandbox to Production.
Use the Sandbox environment to create and edit objects.
Once the design phase is done, promote tasks and processes to the Production environment where no further modification is allowed on the objects to be executed.
Only a user with the Administrator role can promote a task or process.
You can modify tasks and processes in Sandbox after they have been promoted. Most changes do not affect the already-promoted version in the Production environment until they are promoted; changing the name of a task or process, however, directly takes effect in the next environment in the promotion path.
You may see the following icons in the Promoted column:
The version of the task or process in this environment has
been promoted to the next environment in the promotion path and the versions match.
The version of the task or process in this environment has
been modified after being promoted and therefore does not match the version in the next environment in the promotion path. You must
promote the modified task or process to the next environment for them to match.
Therefore, after editing a task or process, move the modified version to the next environment in your promotion path when you are ready by promoting it on the Projects tab. Promote the tasks within a process before promoting the process itself. For more information, see Edit a Task or Process.
If no projects exist in the Production environment when you promote a task or process from Sandbox to Production, the system creates a new project in Production called Default and places the promoted task or process into this project.
Datastore configurations
When a task or process is promoted from Sandbox to Production for the first time, its datastore configuration information is automatically carried over to the Production repository. The Administrator needs to edit and verify the datastore configuration information in the Production repository to make sure the datastore is pointing to the correct productive repository.