This section provides information on upgrading Apttus CPQ to the latest version from the previous two releases.

If you have not installed Apttus CPQ, you can contact Apttus Support to request for an installation link, then perform the standard installation as described in Installing Apttus CPQ.

Preparing for Upgrade

Before you upgrade to CPQ on Salesforce Spring 2020, you must ensure the following:

  • You go through CPQ on Salesforce Feature by Release to know about the new features, enhancements, and deprecated features in CPQ since your existing release. After you upgrade CPQ to Spring 2020, you cannot roll back to any previous release.
  • You have the supported platforms and system requirements
  • You have access to the Install Center on the Apttus Community Portal.
  • You have administrator privileges to your Salesforce org.
  • You need not back up your configurations. All configurations you performed since you installed your existing release will remain intact after the upgrade.

Upgrading to CPQ on Salesforce Spring 2020

This section describes step-by-step instructions to upgrade from Winter 2019 and Summer 2019 to Spring 2020. 

You must install the Apttus Base Library package first when you upgrade CPQ to Spring 2020.

Upgrading CPQ from Winter 2019 to Spring 2020

  1. Go to Setup > Installed Packages and ensure that your current Salesforce org has the following Winter 2019 packages installed.

    Product

    Version Name | Version Number

    Apttus Approvals Management
    (Required if you are using Approvals)
    10.2.0077 | 10.77
    Apttus Configuration & Pricing

    11.2.1675 | 11.1675

    Winter 2019

    Apttus Contract Management10.2.0491 | 10.491
    Apttus Contract-Configuration Integration
    (Required if you are using CLM)
    11.2.0123 | 11.123
    Apttus CPQ API11.2.0096 | 11.96
    Apttus CPQ Admin
    (Required if you are using CPQ Admin Console)
    11.2.45 | 11.45
    Apttus CPQ Approvals Management
    (Required if you are using Approvals on CPQ objects)
    10.1.0014 | 10.14
    Apttus Order Management1.0.0000 | 1.0
    Apttus Promotion Management 
    (Required if you are using Promotions)
    1.0.0000 | 1.0
    Apttus Proposal Management
    (Required if you are using Proposal Management)
    9.2.0206 | 9.206
    Apttus Quote/Proposal Approvals Management6.5.0004 | 6.4
    Apttus Quote/Proposal-Asset Integration6.5.0014 | 6.14

    Apttus Quote/Proposal-Contract Integration

    8.2.0053 | 8.53
    Apttus Quote/Proposal-Configuration Integration
    (Required if you are using CPQ and Proposal Management)
    11.2.0312 | 11.312
  2. Ensure that you have the following packages and dependent packages to upgrade to Spring 2020. These packages are required to utilize the new features and enhancements of Spring 2020. These are the minimum required versions; later versions are also supported.

    Product

    Latest Certified Version

    (Version Name | Version Number)

    Apttus Approvals Management
    (Required if you are using Approvals)
    11.0.0114 | 11.114

    Apttus Base Library

    (Required if you are using Apttus Configuration & Pricing)

    1.0.40 | 1.40

    Mandatory package to be installed in the Spring 2020 release.

    Apttus Configuration & Pricing 

    12.0.1719 | 12.1719

    Spring 2020

    Apttus Contract Management 11.0.0518 | 11.518
    Apttus Contract-Configuration Integration
    (Required if you are using CLM)
    12.0.0130 | 12.130
    Apttus CPQ API 12.0.0100 | 12.100
    Apttus CPQ Admin
    (Required if you are using CPQ Admin Console)
    12.0.54 | 12.54
    Apttus CPQ Approvals Management
    (Required if you are using Approvals on CPQ objects)
    11.0.0016 | 11.16
    Apttus Deal Maximizer Setup
    (Required if you are using Deal Maximizer)
    7.5.0046 | 7.46
    Apttus Order Management1.0.0000 | 1.0
    Apttus Promotion Management 
    (Required if you are using Promotions)
    1.0.0000 | 1.0
    Apttus Proposal Management
    (Required if you are using Proposal Management)
    10.0.0210 | 10.210
    Apttus Quote/Proposal Approvals Management6.5.0004 | 6.4
    Apttus Quote/Proposal-Asset Integration6.5.0014 | 6.14

    Apttus Quote/Proposal-Contract Integration

    9.0.0055 | 9.55
    Apttus Quote/Proposal-Configuration Integration
    (Required if you are using CPQ and Proposal Management)
    12.0.0324 | 12.324
  3. Perform the upgrade. The upgrade procedure is the same as the installation procedure. For detailed information on installing CPQ managed packages, see Installing the Apttus CPQ Packages.
  4. After the upgrade is complete, perform the post-upgrade tasks.

Upgrading CPQ from Summer 2019 to Spring 2020

  1. Go to Setup > Installed Packages and ensure that your current Salesforce org has the following Summer 2019 packages installed.

    Product

    Version Name | Version Number

    Apttus Approvals Management
    (Required if you are using Approvals)
    9.0.0015 | 9.15
    Apttus Configuration & Pricing

    11.1.1603 | 11.1603

    Summer 2019

    Apttus Contract Management9.3.0432 | 9.432
    Apttus Contract-Configuration Integration
    (Required if you are using CLM)
    11.0.0120 | 11.120
    Apttus CPQ API11.0.0091 | 10.91
    Apttus CPQ Admin
    (Required if you are using CPQ Admin Console)
    11.1.39 | 11.39
    Apttus CPQ Approvals Management
    (Required if you are using Approvals on CPQ objects)
    9.0.0000 | 9.0
    Apttus Order Management1.0.0000 | 1.0
    Apttus Promotion Management 
    (Required if you are using Promotions)
    1.0.0000 | 1.0
    Apttus Proposal Management
    (Required if you are using Proposal Management)
    9.1.0197 | 9.197
    Apttus Quote/Proposal Approvals Management6.5.0004 | 6.4
    Apttus Quote/Proposal-Asset Integration6.5.0014 | 6.14

    Apttus Quote/Proposal-Contract Integration

    8.1.0052 | 8.52
    Apttus Quote/Proposal-Configuration Integration
    (Required if you are using CPQ and Proposal Management)
    11.1.0297 | 11.297
  2. Ensure that you have the following packages and dependent packages to upgrade to Spring 2020. These packages are required to utilize the new features and enhancements of Spring 2020. These are the minimum required versions; later versions are also supported.

    Product

    Latest Certified Version

    (Version Name | Version Number)

    Apttus Approvals Management
    (Required if you are using Approvals)
    11.0.0114 | 11.114

    Apttus Base Library

    (Required if you are using Apttus Configuration & Pricing)

    1.0.40 | 1.40

    Mandatory package to be installed in the Spring 2020 release.

    Apttus Configuration & Pricing 

    12.0.1719 | 12.1719

    Spring 2020

    Apttus Contract Management 11.0.0518 | 11.518
    Apttus Contract-Configuration Integration
    (Required if you are using CLM)
    12.0.0130 | 12.130
    Apttus CPQ API 12.0.0100 | 12.100
    Apttus CPQ Admin
    (Required if you are using CPQ Admin Console)
    12.0.54 | 12.54
    Apttus CPQ Approvals Management
    (Required if you are using Approvals on CPQ objects)
    11.0.0016 | 11.16
    Apttus Deal Maximizer Setup
    (Required if you are using Deal Maximizer)
    7.5.0046 | 7.46
    Apttus Order Management1.0.0000 | 1.0
    Apttus Promotion Management 
    (Required if you are using Promotions)
    1.0.0000 | 1.0
    Apttus Proposal Management
    (Required if you are using Proposal Management)
    10.0.0210 | 10.210
    Apttus Quote/Proposal Approvals Management6.5.0004 | 6.4
    Apttus Quote/Proposal-Asset Integration6.5.0014 | 6.14

    Apttus Quote/Proposal-Contract Integration

    9.0.0055 | 9.55
    Apttus Quote/Proposal-Configuration Integration
    (Required if you are using CPQ and Proposal Management)
    12.0.0324 | 12.324
  3. Perform the upgrade. The upgrade procedure is the same as the installation procedure. For detailed information on installing CPQ managed packages, see Installing the Apttus CPQ Packages.
  4. After the upgrade is complete, perform the post-upgrade tasks.

Performing the Post-Upgrade Tasks

After you upgrade to this CPQ release, consider the following options and requirements:


Object Maintenance

After upgrading your packages, you must run the object maintenance tasks to synchronize all your previous configurations.

To access the maintenance pages, click the All Tabs icon () to display all tabs and click the link for each required maintenance. When you run maintenance jobs after an upgrade, you must run them in the order below, in the instances described for each:

  • Product Filter Maintenance - After every upgrade, you must run this task, which collects all product filter field values related to a category. The maintenance job updates the required records for all the categories every time you run it. You must also run the maintenance task every time there is a change in products or a change in the filter field values.
  • Category Maintenance - After any product association, removal or hierarchy change, you must run a Category Maintenance job. This de-normalizes the hierarchy into a custom object for reporting and totaling purposes. If category maintenance is not run, the end-user may see incorrect totals on the shopping cart page. 
  • Constraint Rule Maintenance - This should be run after any changes are made to Constraint Rule conditions. If it isn't run, products may not be included or excluded as expected.
  • Bundle Maintenance - When options are added or removed from a bundle, you must use the Update Bundle Components page to run a bundle maintenance job that synchronizes all the bundles and options.
  • When you run bundle maintenance for all bundles, be sure to only click the button once to avoid scheduling multiple unnecessary bundle maintenance jobs. To track the progress of the job, you should go to Setup > Administration Setup > Monitoring > Apex Jobs. You see the bundle jobs and whether they have been completed.
  • Attribute Maintenance - After an attribute group is associated with a category, run this job to associate the attribute with the products that belong to the category.
  • Criteria Maintenance - After any pricing change (rules, dimensions or any criteria change), you must run a Criteria Maintenance job.

    Ensure that you run the Criteria Maintenance job only if you have active rulesets or have made any updates to the active rulesets.

Adding Custom Fields to Config LineItem Custom Fields 

If your implementation uses the custom callback class related to Pricing, Related Pricing, Asset Line Item, and Validation, then the API names of the custom fields referred in the custom callback class must be defined in the following custom setting:

Config LineItem Custom Fields

If the length of the text field exceeds the first column, use the next text fields for this.

Custom Labels for Custom Actions

After upgrading, it is recommended that you create custom labels for any custom actions. Note that you must do it for each flow or action combination, otherwise none of the buttons are displayed on the cart.

For more information, see Configuring Display Actions Settings.