Differences

This shows you the differences between two versions of the page.

adminhelp:generalsettings:deploy_send_changes_overview:deployment_templates [2019/02/11 03:58]
dperic
adminhelp:generalsettings:deploy_send_changes_overview:deployment_templates [2019/02/11 04:00] (current)
dperic
Line 36: Line 36:
 If you edit the products which are a part of a previously created template and wish to send these product changes to the destination environment, you can reapply the existing template to which these products belong, instead of manually creating a completely new deployment package. Reapplying the template causes the template to automatically obtain the latest product updates from SAP CPQ and populate the package with those product updates. If you edit the products which are a part of a previously created template and wish to send these product changes to the destination environment, you can reapply the existing template to which these products belong, instead of manually creating a completely new deployment package. Reapplying the template causes the template to automatically obtain the latest product updates from SAP CPQ and populate the package with those product updates.
    
-The procedure for reapplying a deployment template is the same as the procedure for [[adminhelp:generalsettings:deploy_send_changes_overview:deployment_templates#Create a Deployment Template|applying a deployment template for the first time]]. Since reapplying the template causes it to automatically obtain product updates from SAP CPQ, you do not need to edit the template in any way.+The procedure for reapplying a deployment template is the same as the procedure for [[adminhelp:generalsettings:deploy_send_changes_overview:deployment_templates#Apply the Deployment Template|applying a deployment template for the first time]]. Since reapplying the template causes it to automatically obtain product updates from SAP CPQ, you do not need to edit the template in any way.
    
-The previous example shows how to create a deployment template named //January Deployment// that contain the following products: //Project Management//, //Software Evaluation// and //Software Implementation// (link here). For the current example, imagine that in February you decide to attach a global script to the //Project Management// product. Instead of manually creating a completely new package to send the product change to the destination environment, you can reapply the template you created for January deployment. Doing that will cause the template to automatically obtain the global script you added to the //Project Management// product and populate the package.+The previous example shows how to [[adminhelp:generalsettings:deploy_send_changes_overview:deployment_templates#Create a Deployment Template|create a deployment template]] named //January Deployment// that contain the following products: //Project Management//, //Software Evaluation// and //Software Implementation//. For the current example, imagine that in February you decide to attach a global script to the //Project Management// product. Instead of manually creating a completely new package to send the product change to the destination environment, you can reapply the template you created for January deployment. Doing that will cause the template to automatically obtain the global script you added to the //Project Management// product and populate the package.
    
 To view the package deployed in January as well as the one deployed in February, go to the **Deployment Packages** tab. In addition, a package can also be downloaded. To download a package, click  To view the package deployed in January as well as the one deployed in February, go to the **Deployment Packages** tab. In addition, a package can also be downloaded. To download a package, click 
You are here: SAP CPQ Online HelpAdmin Page HelpGeneral SettingsDeploy / Send ChangesDeployment Templates