You are here:
Configuring CPQ Platform Cache
An org cache is necessary so you can use CPQ. Your org should have a platform cache named CPQPartition. If the CPQPartition does not exist, create a default partition and name it CPQPartition.
You are allocated a minimum of 10 MB cache space to distribute on your org. Allocating a value of 1 MB to each partition allows you to use all of the features of CME.
After applying Salesforce Industries Communications, Media, and Energy package upgrades, the vlocity_cmt cache partitions' cache usage resets to zero. Allocate adequate space for the vlocity_cmt cache partition, CPQPartition, after the upgrade.
Using the cache improves performance and response time for some operations, especially in large, deep hierarchical product bundles.
CME uses the platform cache for the following items:
-
Caching the complete hierarchy for product bundles in the shared catalog.
When you run the Refresh Platform Cache (Full) job without selecting any price list filters on the Vlocity CMT Administration tab, CME copies the shared catalog's complete hierarchy, including the details of all product child items, and caches that information in the org level cache layer. If you don't run this job, CME caches the hierarchy at run time when a product is used for the first time. This job also updates stored filterable attributes.
When you run the Refresh Platform Cache (Full) job after selecting one or more price list filters on the Vlocity CMT Administration tab, CME copies the shared catalog's hierarchy data pertaining to the selected price lists. The data includes details of all product child items.
When you add or modify any product bundle or product child item, you must run the Product Hierarchy Maintenance job to create a flat data store of the complete product hierarchy.
Then run Refresh Platform Cache (Full) to copy the hierarchy to the platform cache and invalidate the older cache values. You can also run the Refresh Platform Cache (Incremental) job to copy the changed hierarchy data to the platform cache. The incremental job doesn't update any unmodified data in the platform cache.
-
Caching the complete hierarchy for all products in a particular price book.
When you click Refresh Pricebook on the Price Book record detail page, CME calculates the complete hierarchy, including the details of all product child items, and caches that information in the org level cache layer. If you don't click Refresh Pricebook, CME caches the hierarchy at run time when a product is used for the first time. Refreshing the price book also updates stored filterable attributes. If the Refresh Pricebook button is not visible, you must expose it. See Expose the Refresh Pricebook Button.
NoteWhen you add or modify any promotion, product, or product child item, refresh the price book to invalidate the older cache values and cache the updated values. For more information, see Refresh the Price Book.
-
Caching product IDs to add by default when the product is selected.
CME caches the product IDs for all of the products with a quantity greater than zero in a bundle. This applies to each root product available.
-
Caching the complete map with the key and values as the product wrapper for an entire bundle.
The map contains the complete product hierarchy with the bundle root ID as the key. CME generates a unique key value mapping all products wrapped in a bundle using the crypto class by passing the product hierarchy path as an argument. There is one map cached for each bundle in an entire price book.
-
Caching a list of all product and promotion IDs.
CME caches a complete list of all product IDs in a particular bundle. Instead of iterating over the product bundles map, uses this list directly whenever a process requires a complete list of product IDs in a bundle. Use this when merging product child items across line items.
In addition, Salesforce Industries Communications, Media, and Energy releases from Summer '17 to Summer '19 use the session cache for context rules. The cache allocation depends on the number of context dimensions used and varies from org to org.
To set the cache:
- From Setup, in the Quick Find box, enter Platform.
-
Click Platform Cache.
On the Platform Cache Partition page, if the CPQPartition appears, go to step 3.
If the CPQ Partition does not appear, go to Create a Platform Cache Partition.
- Next to CPQPartition, click Edit.
- In the Session Cache Allocation list, in the Organization box enter a number between one and five. One is recommended.
- In the Org Cache Allocation list, in the Organization box, enter a number between one and five. One is recommended.
- Click Save.
- Creating a Platform Cache Partition
Your managed package comes with a platform cache partition and you can create a new one if needed. - Enable the CPQ Cache
The CPQ cache comes enabled as part of the managed package. However, if you need to enable the CPQ cache, you first create the CPQ cache partition. - Enable Platform Cache for Calculation Procedures and Matrices
You can enable the platform cache so you can use - Refresh the Price Book
Refresh your price book depending on which release you are using.
