June23.10.27 Release Notes

In these release notes, you can find packages, requirements, features, enhancements, fixed issues, and known issues for the CPQ June23.10.27 release. For documentation updates, see What's New in CPQ Documentation.

This documentation may describe optional features for which you have not purchased a license; therefore your solution or implementation may differ from what is described here. Contact your Customer Success Manager (CSM) or Account Executive (AE) to discuss your specific features and licensing.

Packages 

The following packages and dependencies are required to upgrade to this release and use its new features. These are the minimum required versions; later versions are also supported. Prerequisites for each feature can be found in its documentation. Packages marked (New) are new for this release.

These release notes reflect the change in version number of the packages marked as (New). Only internal defects were resolved in this release.

You can register your org for the Conga Upgrade Program. Conga Upgrade Program is an automated tool that upgrades packages available in your Salesforce org (Production or Sandbox) to the latest versions. In addition, it also ensures all the Conga published managed packages are on the latest versions for your registered orgs. For more information, see Registering for Conga Upgrade Program.

For more information on installing Conga managed packages, refer to Installing CPQ Packages. For more information on upgrading Conga managed packages, refer to Upgrading CPQ.

Salesforce is starting the process of moving away from Workflow Rules and transitioning to Flow. Hence, Conga recommends that you temporarily migrate all Conga Managed workflows in CPQ to Flows. For more information, see Migrating a Workflow Rule to Flow.

System Requirements and Supported Platforms 

For information pertaining to the requirements and recommendations you must consider before you proceed with the installation of the Conga product, see System Requirements and Supported Platforms Matrix.

Upgrade Notes

For more information on the prerequisites and post-upgrade tasks, see Upgrading CPQ.

Before you upgrade the CPQ packages in your org to June '23 release, please note the following points:

• If the CPQ package in your org is on any of the following releases, you must upgrade it to the Winter '20 patch (Winter20.02.26) before upgrading it to June '23 release:

  Release	Package
  Spring '20 or earlier release	Packages older than 12.0.1719 | 12.1719
  Summer '20 patch older than Summer20.02.26	Packages older than 12.1.1787.99 | 12.1787.99
  Winter '20 patch older than Winter20.02.26	Packages older than 12.2.1839.48 | 12.1839.48

• If the CPQ package in your org is on any of the following releases, you can directly upgrade it to June '23 release:

  Release	Package
  Latest Summer '20 patch (Summer20.02.26 or later)	12.0.1719 | 12.1719 or later
  Latest Winter '20 patch (Winter20.02.26 or later)	12.2.1839.48 | 12.1839.48 or later
  Spring '21 and any Spring '21 patches	13.0.1882 | 13.1882 or later
  Summer '21 and any Summer '21 patches	13.1.1921 | 13.1921 or later
  December '21 and any December '21 patches	13.2.1969 | 13.1969 or later
  May '22 and any May '22 patches	14.0.1995 | 14.1995 or later
  September '22 and any September '22 patches	14.1.2038 | 14.2038 or later
  February '23 and any February '23 patches	15.0.2061 | 15.2061 or later
  June '23 and any June '23 patches	15.1.2090 | 15.2090 or later

New Features 

There are no new features in this release. Keep checking the Conga Documentation Portal for new updates.

Enhancements

The following enhancements are new to CPQ in this release.

Cart Action Button Behavior for Repricing

The Cart action buttons have been improved to promptly disable upon clicking Reprice in the summary view and will remain disabled until the transaction is complete. This addresses the issue of buttons re-enabling before the transaction finishes, thereby preventing potential data inconsistencies and system problems.

Ability to view the status of rebuildCategoryHierarchies

In this release, CPQ enables you to view the status of rebuildCategoryHierarchies when the API has been called and completed successfully. To achieve this, administrator must complete the following.

1. Create an Apex Class
2. Create a new admin entry.

Creating an Apex Class

• Create a new Apex Class with the following code. For more information on creating a new Apex Class, see https://help.salesforce.com/s/articleView?id=sf.ls_create_apex_class_for_apex_action.htm&type=5.

  /**
  *  Apttus Config & Pricing
  *  CustomRebuildCategoryTaskCallback
  *   
  *  @2023-2024 Apttus Inc. All rights reserved.
  */
  global with sharing class CustomRebuildCategoryTaskCallback implements System.Callable { 
     /**
      * Dispatches the call based on the action
      * @param action the action to dispatch
      * @param args the arguments for the action
      * @return the result object 
      */
     public Object call(String action, Map<String, Object> args) {
         switch on action {
             when 'onComplete' {
                 // get the hierarchy id
                 ID hierarchyId = (ID) args.get('hierarchyId');
                 // get the task status
                 String taskStatus = (String) args.get('taskStatus');
                 // only success is reported, but check anyway
                 if (Apttus_Config2.CustomClass.STATUS_SUCCESS == taskStatus) {
                     // do after complete tasks
                 }
                 return true;
             }
             when else {
                 return null;
             }
         }               
     }
  }

  CODE

Creating a new admin entry

• Create a new admin entry APTS_RebuildCategoryCallbackClass with the values as a class name. For more information, see Configuring Admin Settings.

Data Model Changes

There are no data model changes in this release.

Fixed Issues

The following table lists the issues fixed in this release. If any actions are required, they will be listed in this table.

Known Issues

The following table provides the cumulative list of known issues up to this release.

DOC ID: CPQJUN23PRN20231101