Previously, the quote in Conga Smart Configure Price Quote was pre-opened behind the scenes when accessing the CRM quote. The benefit was that the preparation of the CPQ quote opening was done in advance - before you clicked on a step of the Conga Smart Configure Price Quote Step Navigator in the CRM - in order to provide faster access to Conga Smart Configure Price Quote on demand. The downside of this approach was that the pre-opening action was triggered regardless of whether you actually accessed Conga Smart Configure Price Quote.

As a consequence, if a refresh policy was in place in your quote model, your quote could have been refreshed in Conga Smart Configure Price Quote without being synced back to the CRM, i.e. without your knowledge. This could result in a discrepancy between the quote in the CRM and in Conga Smart Configure Price Quote, potentially impacting later steps of your quoting workflow.

As of Conga Smart Configure Price Quote V13.7, a new mode is enabled by default for every new project or quote model. This mode triggers the pre-opening actions only when you click on a step of the quoting workflow in the CRM widget, ensuring that you will access Conga Smart Configure Price Quote and that any changes made there are synced back to the CRM afterward.

Any quote model created before Conga Smart Configure Price Quote V13.7 remains on the previous mode by default for backward compatibility. To adopt the new mode described above, please contact your Customer Representative.

In its continuous effort to secure its platform, PROS has passed the certification for the Salesforce managed package integrated with Conga Smart Configure Price Quote. This certified package in version 8.69 includes security enhancements following the latest best practices defined by Salesforce for their CRM. Some of these improvements may break backward compatibility with the previous version of the Salesforce managed package for Conga Smart Configure Price Quote and require action from PROS customers before its deployment in production on July 21st, 2025.

Please consult the following page to learn more and take action.

From V8.53, a new "CameleonCPQ__SyncInfos__c" field is introduced in the PROS Quote object to store the details of errors occurring during the CPQ sync back. This field is a JSON structure carrying this information. As this field is at the core of the sync error management, it must be granted read and write access rights for the system to be operational and the sync not to fail. Please read the documentation on Connect to learn how to grant these rights to this new field.

In addition, for backward compatibility purposes, the introduction of this field makes it mandatory to deploy the 8.53 Managed Package before the V12.15 of Performance Quoting.

Starting with the Winter 2023 release, Salesforce introduces a new feature named Enhanced Domains. The official communication is accessible here. This impacts the URL format leveraged as part of the integration of Salesforce CRM with PROS Smart CPQ via the PROS App Portal. Migrating to this new format is mandatory and will be enforced by Salesforce in the Spring '23 release. In order to support you on this activation and prevent any disruption in your development or production environments, PROS built a procedure guiding you step by step towards adopting the new URL format introduced by Salesforce.

https://connect.pros.com/community/forums/pros-smart-cpq/action-required-salesforce-winter-23-enable-enhanced-domains

From V8.52, the use of the Custom Setting "Max. number of SFDC queued jobs" has changed. The purpose of this change is to improve the management of parallel synchronization jobs in order to prevent reaching Salesforce governor limits while maintaining a good level of performance.

Previously, the max number of Salesforce jobs in "Holding" status was set to 100, organization wide. When this limit was reached, the package was queuing the synchronization requests in a CPQ-dedicated queue. The "max number of SFDC jobs" setting role was then to lower the hard limit of 100 in order to prevent CPQ from consuming all space in the Salesforce queue.

The logic behind this setting has been reworked, and it now represents the maximum number of simultaneous CPQ synchronization jobs in an "In Progress" state. When over-passing this limit, any new CPQ synchronization job is now managed in a dedicated CPQ job queue to avoid hitting the Salesforce governor limits.

Previously, the quote in Conga Smart Configure Price Quote was pre-opened behind the scenes when accessing the CRM quote. The benefit was that the preparation of the CPQ quote opening was done in advance, before you clicked on a step of the Conga Smart Configure Price Quote Step Navigator in the CRM. This provided faster access to Conga Smart Configure Price Quote on demand. The downside of this approach was that the pre-opening action was triggered regardless of whether you actually accessed Conga Smart Configure Price Quote.

As a consequence, if a refresh policy was in place in your quote model, your quote could have been refreshed in Conga Smart Configure Price Quote without being synced back to the CRM, i.e. without your knowledge. This could result in a discrepancy between the quote in the CRM and in Conga Smart Configure Price Quote, potentially impacting later steps of your quoting workflow.

As of Conga Smart Configure Price Quote V13.7, a new mode is enabled by default for every new project or quote model. This mode triggers the pre-opening actions only when you click on a step of the quoting workflow in the CRM widget, ensuring that you will access Conga Smart Configure Price Quote and that any changes made there are synced back to the CRM afterward.

Any quote model created before Conga Smart Configure Price Quote V13.7 remains on the previous mode by default for backward compatibility. To adopt the new mode described above, please contact your Customer Representative.

Several issues have been resolved regarding the management of the Conga Smart Configure Price Quote Mapping Set entity in Salesforce:

• An issue prevented the good management of two mapping sets with the same name, even with different identifiers
• In certain scenarios where a lot of objects were linked to the quote, it was sometimes impossible to display or access them all from the Mapping Set interface

These issues have now been resolved.