Important Product Information
| MODULE | CHANGE | FROM VERSION | WHAT YOU NEED TO KNOW |
|---|---|---|---|
| Salesforce and MS Dynamics Packages | Quote Opening From the CRM | V13.6 / V13.7 | Previously, the quote in Smart CPQ 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 Smart CPQ Step Navigator in the CRM - in order to provide faster access to Smart CPQ on demand. The downside of this approach was that the pre-opening action was triggered regardless of whether you actually accessed Smart CPQ. As a consequence, if a refresh policy was in place in your quote model, your quote could have been refreshed in Smart CPQ 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 Smart CPQ, potentially impacting later steps of your quoting workflow. As of Smart CPQ 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 Smart CPQ and that any changes made there are synced back to the CRM afterward. Any quote model created before Smart CPQ V13.7 remains on the previous mode by default for backward compatibility. To adopt the new mode described above, please contact your Customer Representative. |
| Smart CPQ | Close and Sync Button Translation | V13.6 / V13.7 | Previously, the User Interface used a hard-coded translation, so the description given by the CloseAndSynchronize action was ignored. Now, for all new customers, the description and corresponding translations from the CloseAndSynchronize action will be displayed in the User Interface. In V13.6, by default for existing customers, this option was turned off. With V13.7, the option will be the active behavior by default for every customer. Conga thus strongly recommends to review the corresponding action descriptions in your quote model to ensure a smooth transition for your end-users. More information is available in the Connect Announcement Forum. |
| Smart CPQ | V13 availability and V12 end-of-life | V12.21 / V13.0 | The General Release of version 13 (V13.0 G-) is available and will be updated on a bi-weekly basis following the usual update calendar of Smart CPQ. It is recommended for all customers to plan a non-regression test on the V13 environment that PROS will make available for you and to report to PROS any regression. In addition, customers having custom code must have this code migrated and compatible with the new technical stack (see Technical Requirements). From this date to April 6, 2025, cloud customers having successfully performed their tests can plan with PROS the date of their final transition to V13 for all their environments. Jointly the version 12 is being upgraded to 12.21 that will start a restricted maintenance period where only security issues and critical incidents will be fixed; no further enhancements will be made to this version. From April 6th 2025, all customers must have migrated on V13. From June 30th 2025, the V12 will officially not be supported anymore. PROS will not deliver any security or bug fix for Smart CPQ version 12 or below, and any correction of an issue reported on these obsolete versions will be delivered only as a fix to be applied to Smart CPQ V13.0 or above. |
| Salesforce Managed Package | Synchronization Error Details | V12.15 (8.53) | 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 those 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 figure out how to grant these rights to this new field. In addition, for backward compatibility purpose, the introduction of this field makes it mandatory to deploy the 8.53 Managed Package before the V12.15 of Performance Quoting. |
| Salesforce Managed Package | Enable Enhanced Domains | V12.14 (8.52) | Starting with the Winter 2023 release, Salesforce introduces a new feature named Enhanced Domains. The official communication is accessible here: https://help.salesforce.com/s/articleView?id=release-notes.rn_security_domains_enhanced_ru.htm&type=5&release=240 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 |
| Salesforce Managed Package | Max. number of SFDC Queued Jobs | V12.14 (8.52) | 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 performances. 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 a "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. |
| Smart CPQ | Versioning Safety Check for Catalogs & Configurations | V12.13 | It has always been mandatory to generate versions for catalogs and configurations in Production environments. But it was still possible to mistakenly reference the working version (not a generated version) when viewing a catalog or configuration from the quote itself. We added a safety check on Production environments that will display a warning popup in the catalog / configuration UI if this case is detected. The safety check will be progressively rolled out by PROS over the course of July. |
| Smart CPQ | Deprecated _SYS_ROW_ITEM in matching rules | V12.12 | Starting from the 12.12, the usage of the system column ROW ITEM (_SYS_ROW_ITEM) in the matching rules of a line template is deprecated. You can leverage Business properties of the current item being added in order to identify line templates. Starting from the 12.14, it won't be possible to activate a quote model using the ROW ITEM (_SYS_ROW_ITEM) in the matching rule. |
| Smart CPQ | Smart CPQ SDK Deprecation | V12.12 V12.14 | The SDK used for the modeling of Performance Quoting models is deprecated from V12.12. PROS recommends to complete the migration to the Quote Designer before the End Of Life of the SDK that will occur in V12.14 |
| Smart CPQ | Permissions on open catalog, open configuration and move rows actions | V12.12 | In Performance Quoting, the actions "open catalog", "open configuration" and "move rows" are now taking into account user permissions. User permissions on these actions are defined in the Permissions section of the Quote Designer. Quote models have to be updated accordingly in order to take into account this change. This affects only new versions of Quote models. Existing quote models are not affected while a new version of the model is not published. If a new version is published without taking into account this change, permissions will be taken into account and the user won't be able to use these actions anymore. |
| Smart CPQ | Display/Availability of open configuration and move rows actions | V12.12 | In Performance Quoting, the actions "open configuration" and "move rows" are now taking into account the grid widget definition. In order to be available on a given grid widget, these actions have to be added on the widget in the Actions list. Quote models have to be updated accordingly in order to take into account this change. This affects only new versions of Quote models. Existing quote models are not affected while a new version of the model is not published. If a new version is published without taking into account this change, permissions will be taken into account and the user won't be able to use these actions anymore. |
| Smart CPQ | Feature retirement Quote Layout V1 | V12.13 | V1 of the Quote layout/UI, which was deprecated since the version V11.0, will retire in version V12.13. |
| MS Dynamics Managed Solution | Replacement of ADAL by MSAL library for the Azure Active Directory authentication | 3.0+ | This release 3.0 introduces the replacement of the MS ADAL library by the new MSAL library for Azure Active Directory authentication. PROS strongly recommends the migration to this new MSAL library. The steps to do so are described on Connect in the following page. Using the ADAL library is still possible with this new release of the PROS managed solution. However, Microsoft being responsible for the life cycle of the ADAL library, PROS cannot commit on how long this compatibility will be ensured. |
| Smart CPQ Quote Designer | Component type for scale pricing data providers | V12.11 V12.12 | Until V12.11, defining a data provider for scaled pricing in Smart CPQ Quote Designer required the declaration of a unique component type for the Real Time Pricing Engine. Starting in V12.11, the declaration of this component type is deprecated and PROS strongly recommends to stop using it. Pricing Managers have now the flexibility to define which component type should be used to return a scaled price to CPQ directly in the corresponding pricing method in PROS Control and RTPE. Please see Modeling Scale Pricing for more details. Starting in V12.12, the Component Name field is not available anymore for new Data Providers. If you were using the field before V12.12, it is still available but will be automatically removed if you empty it. PROS thus recommends to remove any Component Name field and manage the use of Component Types in your pricing method in Control and RTPE. |
| SFDC Managed Package | End of Browser Access for Mobiles | All Versions | With their Summer Release 2020, Salesforce now prevent mobile devices from accessing SFDC via Web Browser (Safari, Firefox, Chrome, Edge, etc.). Mobile devices should instead use the Salesforce mobile app. This means that to open Smart CPQ, mobile devices will have to use the Salesforce mobile app. See https://help.salesforce.com/articleView?id=000349471&language=en_US&type=1&mode=1 for more details. |
| MS Dynamics Managed Solution | Web Client End of Support | V1.7.0 / V2.3+ | From the release of the new Unified Interface for Dynamics CRM, PROS both supported it and continued supporting the legacy Web Client. From then, Microsoft also continuously encouraged companies to migrate to Unified Interface. As a result, Microsoft officially announced the deprecation of the legacy Web Client starting on October 1st, 2020. This period has been relaxed for 2 months due to COVID-19 situation and the date for deprecation is now officially December 1st, 2020. Based on that statement, PROS decided to stop supporting the legacy Web Client starting with V1.7.0/V2.3+ to be released end of 2020. We strongly encourage you to migrate to the Unified Interface to continue benefiting from all Smart CPQ features. |
| Smart CPQ | PROS Support Permission | V12.4 | For security reasons, PROS users do not have access to your environment by default. However, if you require assistance from PROS, you can authorize PROS Support to log in to your environment. This page details the process to grant access to PROS Support. |
| Smart CPQ | Mandatory Identity Provider Connected to PROS Application Portal | V12.2 | In this new version and to enforce security around our solution, any new Smart CPQ instance must integrate with the customer's existing enterprise identity, authentication, and authorization mechanisms. This provides a familiar single sign-on (SSO) experience for users and leverages the customer's existing security and user management policies; there is no separate user database to maintain. |
| Smart CPQ | SSO between Salesforce And SellingPRO Designer | V12 | For security enhancement the Single Sign On between Salesforce and SellingPRO Designer has been improved and required configuration to fully function with v12. |
| Smart CPQ | JDK 1.8 Azul Zulu | V11.16 | PROS Smart CPQ now only support Azul Zulu JDK 1.8. |
| Smart CPQ | Deprecated ML Security Level | V11.12 | ML Security Level 'Medium' has been deprecated. Remaining Levels are None (for On Prem customers only) and High. Cloud customers currently using 'Medium' will be contacted by our Professional Services to work together on solving any related issue. On Prem customers should use the level 'None' if needed. This change is to ensure security best practices are enforced on our Cloud platform. |
| Smart CPQ | Aliases Flag Management for Price Requests | V11.12 | Pricing requests are now taking into account alias flags (Must Exist / Must Be Answered) both for BRC alias resolution (ex: fpProduct.value/PRGM/pmAnnual.Range[1]) AND getPrice(CPE) calls from ML or APIs. That will be the case if parameter common.pricing.service.checkflagsduringpricescomputation is commented, not found, or equal to false. For more information, please refer to our product Documentation on Connect. |
| Smart CPQ | JDK Support | V11.9 | PROS Smart CPQ now supports JDK 1.8+ only at runtime. All previous versions are not supported anymore. |
| Smart CPQ | HTTP Setup | V11.9 | The application running in non HTTPS mode must have the web.xml files on the CPQ server specifically setup. Consult the Known issues section for more details. |
| Smart CPQ | Discontinuation of Edge Designer | V11.8 | SellingPRO Designer is the official administration tool for Smart CPQ. The access to the former generation -Edge Designer - has been removed from the product suite. |
| Smart CPQ | Deprecated Modeling APIs | V11.1 | To integrate or synchronize an external data repository/data source with CPQ Designer, the ExImp web service (using XML import format) has to be implemented. All other types of integration leveraging direct or indirect calls to modeling APIs are not authorized anymore. |
| Smart CPQ | Deprecated Quote Layout V1 | V11.0 | V1 of the Quote layout is deprecated. Only V2 will be enhanced in future releases and it is now the standard product layout. |
| Smart CPQ | End of Support Notices | From: | CPQ no longer supports the following products: |
| V10.0 | Solaris 10 (32/64 bit) | ||
| V11.7 | Oracle 11g R2 (UTF8) | ||
| V11.7 | iOS8 and previous versions | ||
| V11.7 | Apple Safari V8 and prior | ||
| V11.9 | Any JDK version prior to 1.8 | ||
| V11.10 | Apache 2.2 | ||
| V11.10 | SQL Server 2014 | ||
| V11.10 | Microsoft Internet Explorer V11 and prior | ||
| V11.15 | Jasper 6.2.0 | ||
| V12.0 | JBoss 6.3.3 EAP | ||
| V12.0 | Axis2 1.6 | ||
| V12.6 | Microsoft Edge browser | ||
| V12.14 | Jasper 6.4.3 Word 2019 | ||
| V12.15 | Oracle 11g |