Configuring Deploy/Send Changes

Objectives

After completing this lesson, you will be able to:
  • Configure the deploy/send changes functionality.
  • Create a deployment package of one or more components.

Configuration of the Deploy/Send Changes Functionality

Illustration of the screen, on which the Deploy/Send Changes functions are configured

The Deploy/Send Changes functionality enables you to send changes made in one SAP CPQ environment (such as sandbox or test) to another (such as production).

For example, imagine that you made several changes to a product in your sandbox environment (for instance, you added formula rules, attribute triggers, and global scripts). After running tests and concluding that the changes don't break your existing customizations, you can use the Deploy / Send Changes feature to send and deploy the product to the production environment.

The Deploy / Send Change functionality is accessed from SetupGeneralDeploy / Send Changes.

Note

Multiple target environments can be connected to the current environment.

Deployment Package

Deployment Setup

The figure shows the entry page for the deployment setup.

On the Deployment Setup tab, the user connects the current environment, also known as the source environment, to the target environments where changes will be deployed. This process ensures that updates and configurations are transferred smoothly from the source environment to other environments, such as testing or production.

To set up the current environment, the user selects Add Current Environment in the Current Environmentsection. A popup displays pre-filled details for Environment Type, URL (without http), and Domain. After choosing Save, the environment appears in the list, ready for editing or deletion.

For the target environment, users can deploy changes by selecting Add Connected Environment in the Connected Environment section. After choosing the environment type (Test, Production, Sandbox), the user enters the destination URL and tenant name. The system auto-fills the Username and Password fields. Once saved, the connected environment is added and ready for use.

Deploy/Send Process (Source)

The figure shows the screen for creating a new package.

SAP CPQ objects can be combined into a package. These packages are referred to as package components or change types. Deployment packages enable combining one or more SAP CPQ objects, such as products, users, and templates. A package can then be deployed to the target environment. Changes can be made to the deployment package as many times as needed.

Administrators can create a deployment package in SAP CPQ or upload an existing deployment package with the following options:

  • Create a new package or upload existing deployment package.
  • Select the destination environment.
  • Select and add the required components.

Note

The size limit for deployment packages is 200 MB.

The system uses the system ID to match entities in the source and the target environment. If there's an entity in both environments with the same system ID but with a different name, the system displays an error and the deployment will be unsuccessful. The message in the user interface states the name of the entity that caused the issue. To fix the issue, change the system ID or the name of the scripts.

The figure shows the screen, which is used to add custom fields.

You need to enter a meaningful name or description for the added component. For example, enter Custom Fields as a name. Then, select all or individual fields as needed. Each component displays a corresponding checklist.

Further possible data for creating deployment packages.

The selected components now display as part of the deployment package.

The figure highlights the Status of different packages.

Each deployment package displays a corresponding status. There are options to clone, edit, delete, send, download, or send a package.

The figure shows the pop-up for confirming the update of Custom Fields.

After deploying completed package of components to target environment, the user needs to define:

  • Order
  • Component-specific questionnaire (example shown on above image)