Conga Release Notes contain the following information about Conga TurboEngines Winter 2020 Release.
Packages: Lists packages that are required to upgrade to this release of the product
- System Requirements and Supported Platforms: Lists requirements and recommendations for installing this release
New Features: Provides high-level descriptions of new features introduced in this release, with links to more detailed information
- Enhancements: Provides high-level descriptions of enhancements to existing features
- Resolved Issues: Lists customer-reported issues that are resolved in this release or known issues resolved from previous releases
- Known Issues: Lists known issues that are applicable in this release
This documentation may contain descriptions of software features that are optional and for which you may not have purchased a license. As a result, your specific software solution and/or implementation may differ from those described in this document. Please contact your CSM or AE for information on your specific features and licensing.
The following packages and dependent packages are required to upgrade to this release to utilize all the new features of this release. These are the minimum required versions; later versions are also supported. Separate prerequisites for each feature can be found in the respective guides. The packages marked as (New) are new packages in this release.
Latest Certified Version
(Version Name | Version Number)
Conga Base Library (New)
1.2.123 | 1.123
Before installing or upgrading Conga managed packages, you must review the dependency matrix for each managed package. You can refer to the package dependency matrix at Conga Packages Dependency Matrix.
System Requirements and Supported Platforms
The following table lists the minimum requirements for installing and using Conga TurboEngines.
|System Requirement||Minimum Supported Version|
|Operating System||Standard Salesforce.com requirements. See Salesforce PDF.|
Conga supports the following browsers:
Conga recommends the latest stable version of the browser for the best performance.
Internet Explorer is not supported.
The following features are new to Conga TurboEngines in this release.
Importing a callback
The Import feature provides a mechanism to import the callback project (.zip file). Using this feature, you can move the callback code to a different environment if required.
For more information on the Importing feature, refer to Managing TurboEngine Callbacks in the TurboEngines Winter '20 Administrator Guide.
Related Pricing Callback Interface
The interface provides you the capability to define custom logic for calculating the pricing for related product line items. The prices in the related product line items are dependant on the price of other line items.
For more information on the Related Pricing callback, refer to Pricing Callback Class for TurboPricing in the TurboEngines Winter '20 Administrator Guide.
The following section describes existing features that are changed (or are no longer supported) in this release.
TurboConfig Data Sync
Administrators can now leverage TurboEngine Data Sync services for TurboConfig product configuration master data. TurboEngine Data Sync is a service provided parallel to the Flexible Computing Platform for syncing master data between Conga applications and TurboEngines at regular scheduled intervals and on-demand. TurboConfig administrators can now make use of the TurboEngine Data Sync Admin application to configure and manage master data sync.
For more information on TurboEngines Data Sync, refer to About TurboEngines Data Sync in the TurboEngines Winter '20 Data Sync Administrator Guide.
You can now enable simple or complex objects for push-based sync. This takes advantage of PushTopic Events in Salesforce that notify the data sync service when one or more records have been created, updated, or deleted, or when changes have been made to a record based on a specific PushTopic query. When you enable an object for PushTopic sync, any time activity in Salesforce meets the criteria for a PushTopic Event, the corresponding object and its data will be synced for the applicable consumer profile.
For more information about push-based sync, refer to Enabling Objects for Push-Based Sync in the TurboEngines Winter '20 Data Sync Administrator Guide.
You can now create sync indexes for objects added to sync settings. You can create sync indexes with user-friendly names to increase performance significantly for objects with a significant amount of records.
For more information on sync indexes, refer to Creating Sync Indexes in the TurboEngines Winter '20 Data Sync Administrator Guide.
Data Sync Email Notifications
Administrators can now enable email notifications in the TurboEngines admin application to send email notifications to the administrator account whenever a sync operation fails or is partially successful. Administrator can enable and configure email notifications in the TurboEngines Data Sync Admin application.
For more information on email notifications, refer to Managing Email Notifications in the TurboEngines Winter '20 Data Sync Administrator Guide.
Changes and Additions to Run History Status
The following changes and additions have been made to sync status in data sync Run History:
- 'Partial Success' status has been added to the list of possible statuses displayed in Run History and Run Details. 'Partial Success' indicates that the sync was successful for some object but failed for one or more objects. Administrators can view details and take action from the Run History tab.
- 'Queued' status has been changed to 'Preparing'.
- 'Cancelled' status has been changed to 'Aborted'.
For more information on sync run history, refer to Working with Data Sync Run History the TurboEngines Winter '20 Data Sync Administrator Guide.
Retry Data Sync
You can now retry a sync operation from the Run Details screen. Retrying data sync is available when a sync for one or more objects fails during the sync process. You cannot retry a sync with the status 'Aborted'.
For more information on retrying data sync, refer to Retrying Data Sync in the TurboEngines Winter '20 Data Sync Administrator Guide.
Download Sync Error Report from Run Details
You can now download an error message report from Run Details after one or more objects fail to sync. The error messages report contains detailed error message information for debugging issues encountered during sync.
For more information on downloading error message reports, refer to Viewing and Evaluating Error Messages in the TurboEngines Winter '20 Data Sync Administrator Guide.
The following table lists the known issues resolved from the previous release.
|Case Number||Conga Internal ID||Description|
|NA||CPQ-44779||Replacement Rules based on criteria does not execute until the user clicks on finalize.|
|NA||CPQ-44752||Getting "Price Pending" error on "Finalize" when Option with price method "Flat Price" is added under bundle and option quantity is updated, repriced, and then finalized.|
|NA||CPQ-44836||Option to Option exclusion constraint rule is not supported.|
|NA||CPQ-44615||Usage Price Tiers are not shown within the popup for the finalized cart.|
|NA||CPQ-44832||A feature flag called "Enable Selling Term Rounding" does not work partially.|
|NA||CPQ-44827||User is unable to finalize if they have "Check on Finalization" type of constraint rule.|
|NA||CPQ-44817||The update cart line items request is sending a pricing status of complete, however, the response has the pricing status flipped back to pending.|
Auto-included primary line products are not getting auto-removed when you remove the condition product. This behavior is observed when Constraint Rule Execution Mode is set as either CMS or Server.
The following table provides the cumulative list of known issues up to this release.
|Conga Internal ID||Description|
In TurboPricing flow, when you copy the bundle with multiple options, CPQ displays an error.
|CMS-700||When using Match In Location, CPQ displays an error after adding the condition and action for different countries.|
When you delete the condition of an Action, the action is also getting deleted along with the condition.
|CMS-701||When configuring Match In Location, the error message is displayed continuously after deleting the actions.|
|CMS-702||In TurboConfig flow, CPQ displays an error after selecting the cloned condition.|
When you update the quantity of cloned option after cloning it, the blank values are displayed for all the attributes of cloned options.
|CMS-704||The original and cloned actions are deselected and added an extra clone for action after cloning a condition and action products.|
|CMS-705||Only one success message appears after adding the condition twice,|
|CMS-706||When performing repeat inclusion, an error message is not displayed after deleting the action from the mini cart.|
|CMS-707||When configuring Repeat Inclusion, the error message displayed for the prompt is disappeared.|
|CPQ-44694||The price factor (Bundle Only) adjustment is not supported.|
|CPQ-44665||Line item formula fields dependent on Salesforce default value fields should be added under view cart custom fields and custom pricing fields in config system properties.|
|CPQ-44599||Promotions with "Contains" operator in criteria does not work.|
|CPQ-44767||Line Items are not shown on the cart page when it is added with the filter condition.|
|CPQ-44671||Line item objects do not get updated in backend after reprice. Set APTS_AlwaysSaveAfterTurboPrice admin setting to true to see the expected behavior.|
|CPQ-43929||User needs to reprice if products are added from inclusion prompt.|
|CPQ-44773||Manual adjustment on option product calculates the wrong price for another option.|
|CPQ-44823||The user is unable to select option product quickly on the configuration page. This behavior is observed when Constraint Rule Execution Mode is set as either CMS or Server.|
|LS-4860||When an object is added with the option "Include all fields including future fields" an index cannot be added for the object.|
|LS-4895||Some objects in seed data are not protected (made read-only) when the option "Include all fields including future fields" is enabled.|
DOC ID: CTEWIN20RN20201104
DOC ID: CTEWIN20RN20201104