Patch Releases Summer `21

The GetOfferDetails API response has incorrect or incomplete entries due to incorrect PriceResult entries.

The GetPrice job has a limit of 10K PriceResultEntries (PLEs) that can be fetched at a time. If the total PLEs to be processed exceeds 10K, then some of the entries are not fetched. As a result, the GetOfferDetails API response for the missing PLEs will not be available.

To resolve this issue, an additional promotional item filter was added to the query. This reduces the number of PriceResultEntries (PLEs) fetched to be processed by the GetPrices batch job during cache warmup.

For this fix to take effect, perform the following steps:

1. Go to Setup.
2. Search for Custom Settings.
3. Navigate to General Settings.
4. Click Manage next to General Settings.
5. Click New.
6. Add the following information:
   • Name: FixToggleList
   • Value: DCPriceResultPromoFilter
7. Click Save.

For this fix to take effect you must add the following CPQ configuration setup custom setting. Setting Name: ReplaceOfferPLEFilter

Setting value: True

Orchestration item details were failing to open in the Lightning environment.

This patch fixes that issue.

For Order Management Plus, orders that do not originate in Salesforce (sometimes called "repro" orders) used to be sent as an update to Salesforce. This update was unnecessary and caused fallouts.

These orders are no longer sent to Salesforce.

In pre-release instances (GS0), the installation or upgrade of Summer '21 failed.

This patch fixes this issue.

Order Management Plus customers encountered an error when editing OrderPricing fields.

This issue was fixed.

When you submitted an order, the Submitted to OM Time field wasn't updated.

With this fix, the field is updated as expected when you submit an order.

When UoWMode was enabled and you applied a promotion to the cart, the Sequence field was Null.

With this fix, the Sequence (Vlocity_cmt__Sequence__c) field is populated as expected.

In some scenarios, applying promotions when UoWMode was enabled resulted in a "Too many SOQL queries" error.

With this fix, an error is not displayed when applying promotions.

Searching for a manual queue during the "Assign To" operation in Order Management Plus didn't work in organizations with many manual queues.

Searching for a manual queue now works even in organizations with many manual queues.

The Spring framework that Order Management Plus worked with was possibly vulnerable to exploits.

Order Management Plus as updated to a later version of the Spring framework.

The Order Submit Fallout page in Order Management Plus sometimes failed to load records when there were a lot of fallouts.

Order Management Plus has introduced a new “Record Fetch Size” attribute to the Vlocity OM Plus Admin page. That attribute is set to 50 for Fallout children. A fetch size of 50 is manageable, so this new setting allows the page to load properly even when there are many fallout records in the list.

Order Management Plus did not populate the Promotion reference in Order Pricing objects.

Now OM Plus populates the Promotion reference in Order Pricing objects.

For MACD orders, the deleteAppliedPromoItems method generated a new record in orderPricing without the appliedPromotionId.

With this fix, the deleteAppliedPromoItems method works on MACD orders as expected.

Order Management used Salesforce Platform API Version 19 which is being retired by Salesforce.

Versions 7.0 through 20.0 of the Salesforce Platform API are being deprecated in the Summer '22 release. See Salesforce Platform API Versions 7.0 through 20.0 Retirement.

This patch updates the calls to the latest version of the APIs.

The orchestration plan view didn’t load in Salesforce Classic UI.

With this fix, the orchestration plan view loads as expected in Salesforce Classic.

Products are displayed in the cart based on the price book rather than the price list

With this fix, products are displayed in the cart based on the price list.

Upgrades from v106 (Fall 2019) to the new version failed while executing the migration script.

The script is fixed, and upgrade works correctly now.

The order payload expected by Order Management Plus changed in v107 (Winter 2020). Any custom service sending orders directly to Order Management Plus (rather than going through CPQ) before v107 failed after upgrading to any newer version.

Incoming service for Order Management Plus is fixed, and now accepts both legacy and new formats.

When UoWMode is set to true, the priceCart API returns pricing information of all the line items in the cart rather than the specific line items specified in the request.

With this fix, the API only returns the pricing information for the line items that you specify in the call. For more information on this API, see Run Pricing for Items to Cart.

When processing large orders, the orders failed with heap size errors.

This fix optimizes the processing of large orders to prevent heap size errors. To use this fix, enable it using custom settings:

1. Go to the App Launcher and enter CMT.

2. Under Items, click Vlocity CMT Administration.

3. Under Custom Settings, click CPQ Configuration Setup.

4. Click Add.

5. In the Name field, enter RunPCPInUpdatePostExecuteMethod.

6. In the Setup Value field, enter False.

7. Repeat steps 4 to 6 for RunPCPInAddPostExecuteMethod.

8. In the Lightning environment, click the Settings gear icon, then click Setup.

9. In the Quick Find field, type Custom Settings, then click Custom Settings.

10. Find General Settings and click the Manage link next to it.

11. Click New.

12. In the Name field, enter FixToggleList.

13. In the Value field, enter CMT-9413-2,CMT-9413 and click Save.

The currency wasn't displayed on the submit order panel of the cart.

This fix ensures that the relevant currency is displayed.

In LWC OmniScripts, radio buttons and their labels were overlapping.

In some scenarios, radio buttons and their labels in OmniScripts were overlapping. With this fix, radio buttons and their labels appear as expected in OmniScripts.

Apache Log4j had some security vulnerabilities.

For Order Management Plus, the Apache Log4j package was updated to 2.17.1 to fix critical security vulnerabilities. See Apache's documentation: Apache Log4j Security Vulnerabilities.

When UoWMode is set to true and you perform a MACD on an asset that has a promotion applied, creating an order causes an Apex heap size error.

This fix uses a custom setting to fix this issue. This custom setting optimizes MACD orders that includes assets with active promotions to prevent the error.

To configure the custom setting:

1. In the Lightning environment, click the Settings gear icon, then click Setup.

2. In the Quick Find field, type Custom Settings, then click Custom Settings.

3. Find General Settings and click the Manage link next to it.

4. Click New.

5. In the Name field, enter FixToggleList.

6. In the Value field, enter CMT-9413-2,CMT-9413 and click Save.

Advanced rules that made multiple attribute modifications on a line item didn't work as expected.

When a rule made multiple attribute modification actions to a line item, the modifications didn't persist. This occurred when the last set of actions didn't modify the line item even if previous actions did make modifications. This fix ensures that such rules work as expected.

Apache Log4j had some security vulnerabilities.

Updated to Apache Log4j 2.17.1 to fix critical security vulnerabilities. See Apache's documentation: Apache Log4j Security Vulnerabilities.

OmniScripts that call a chainable Integration Procedure IP with top-level caching did not work as expected.

In an Omniscript, calling a chainable Integration Procedure with top-level caching didn't result in chaining. This issue has been fixed in classic Omniscripts. To prevent this problem, the OmniScript sends the original payload to the chainable Integration Procedure instead of a generic payload.

You can't enter more than 15 digits in a Data Mapper.

This patch allows you to enter more than 15 digits in a Data Mapper.

Empty date fields in Vlocity Cards display an error.

This patch adds a check for empty, undefined, or null date fields.

You cannot move an asset within the same account.

If you created an order to move an asset within the same account, the order was rejected. With this fix, you can move an asset within the same account.

In an org that uses JSONAttribute v2 with UOWMode set to true, actions that call the postCartItems API fail with a "System.LimitException: Apex heap size too large" error.

This patch uses a custom setting to fix this issue. This custom setting limits the number of price book entries that are processed while preparing the hierarchy. For example, when you add a product to the cart, the price book entries related to that product or hierarchy are processed rather than all the entries in the bundle.

To configure the custom setting:

1. In the Lightning environment, click the Settings gear icon, then click Setup.

2. In the Quick Find field, type Custom Settings, then click Custom Settings.

3. Find General Settings and click the Manage link next to it.

4. Click New.

5. In the Name field, enter FixToggleList.

6. In the Value field, enter CMT-9413 and click Save.

In an org that uses JSONAttribute v2 with UOWMode set to true, actions that call the postCartItems API fail with a "System.LimitException: Apex heap size too large" error.

This patch uses a custom setting to fix this issue. This custom setting limits the number of attribute overrides that are processed when preparing the hierarchy. For example, when you add a product to the cart, the override attributes related to that product or hierarchy are processed rather than all the override attributes in its bundle.

To configure the custom setting:

1. In the Lightning environment, click the Settings gear icon, then click Setup.

2. In the Quick Find field, type Custom Settings, then click Custom Settings.

3. Find General Settings and click the Manage link next to it.

4. Click New.

5. In the Name field, enter FixToggleList.

6. In the Value field, enter CMT-9413 and click Save.

There were some minor security vulnerabilities in Industries Order Management.

Various security updates and improvements.

When running a Line Item Attributes Conversion job, the updates failed with a "STRING_TOO_LONG, Attribute Metadata Changes: data value too large" error message.

This patch fixes this issue by doing the following:

• Increases the field size to allow for larger metadata changes.

• Limits the batch query response to 50 million records.

• Minimizes the values property in the metadata changers field.

When running the GetOfferDetails API, the call failed with a heap size error.

This fix resolves heap issues for Digital Commerce APIs by trimming the fields from the Attribute Categories in the getOfferDetails Response

When moving from the current step to the previous step in an Omniscript, the Date/Time element adds an hour to the time field.

The base component daytimepicker Lightning Web Component displays and converts the time to be one hour ahead of the time that you enter. This is due to a daylight savings time calculation. This fix ensures that the time is calculated and displayed correctly.

When UOWMode is set to true, you can’t update attributes in HybridCPQ.

This fix ensures that you can update attributes as expected.

Setting UOWMode to true can block advanced rules

This fix ensures that advanced rules work as expected when UOWMode is set to true.

The error message “Required attribute missing” doesn't appear.

This fix ensures that the error message appears when required.

The number of order item fields returned by the getcartItems API call varies based on the status of the UOWMode parameter.

This fix ensures that the setting of the UOWMode parameter doesn't affect the number of order item fields returned.

Enabling the V2 Attribute Model doesn’t upgrade the attributes of some order line items to V2

If your org is configured as follows:

• V2 Attribute model enabled.

• Custom settings for CPQ such as ValidateAndUpgradeV2Attributes set to true.

Order Management Integration Layer didn’t upgrade the attributes of order line items. This fix ensures that Order Management Integration Layer upgrades attribute model for all order line items that haven't been converted.

When selecting a new attribute in the cart, the values of existing attributes weren’t reset or updated.

This fix ensures that when selecting a new attribute any existing attributes are reset or updated.

The scheduled job for contract envelope status update failed because the scheduler was unable to fetch the timestamp of the last scheduled job. It resulted in the Contract Document Envelope status not changing from Sent to Completed after the contract was signed by the recipient using the DocSign e-signature functionality.

This fix resolves the contract envelope status scheduler job failure issue and now the Contract Document Envelope status updates successfully.

Note

If you were using a workaround, we recommend undoing the interim workaround and installing the 232.7 patch release to resolve the scheduled job failure issue.

Mapping rules in the decomposition relationship object were not visible after upgrading to the Industries Spring 2021 release. Mapping rules did not appear if an attribute category name included an apostrophe.

A fix was applied so mapping rules in the decomposition relationship object are visible after upgrading to the Industries Spring 2021 release.

In the Reports tab of the Sales Console app, you can't see the details of case records. This happens when the layout of the Cases page includes the Vlocity Action toolbar.

With this fix, the details of the case records are correctly displayed.

When V2AttributeModel is enabled, rules don't work. When you add a product to the cart, the line item value of AttributeMetadataChanges__c is not populated when there is more than one action for a rule.

With this fix, rules work as expected when V2AttributeModel is enabled.

When UOWMode is set to true, you cannot update attributes in HybridCPQ.

With this fix, you can update attributes as expected.

When processing a large order in Order Management Plus, the order can fail due to a database exception. When an order is processed, all related catalog records are called to populate the cache. If the query has more than 72272 IDs, a limit is hit in the Postgres database.

With this fix, the number of entries in the query is limited to ensure that the database correctly processes it.

For Order Management Plus deployments, you cannot update AWS Lambda functions because NodeJS 10.x is no longer supported by Amazon Web Services.

This fix upgrades the AWS Lambda runtimes to NodeJS 14.x.

Context rules do not work in ESM due to which you cannot manage the eligiblity of offers.

With this fix, context rules work as expected.

When a guest user generates a .pdf using the singleDocxLwcGuestUser OmniScript, the .pdf file is not attached to the object for which it is generated, such as a contract, account, or an opportunity.

This fix ensures that .pdf files attach to the objects for which they're generated.

For existing assets, a removed child line item is not saved. The product isn't disconnected, or removed.

This issue occurs when UOWMode is set to True, but it doesn't occur when UOWMode is set to False. With this fix, you can remove, or disconnect, a line item in an existing asset.

Orchestration items fail in certain callouts

Any custom code that uses the OrchItem.getOrderItemId() method was failing with a NullPointerException error. This fix updates the behavior of the method to enable multiple order items to be associated with the same orchestration item. The method returns the swimlane order item id.

When creating an enterprise quote using Enterprise Sales Management, the AssetReferenceId was not copied to ParentItemId and RootItemId of parent and child products respectively.

You can set UseAssetReferenceIdForParentAndRoot to True to improve performance. However, if you created an enterprise quote, the AssetReferenceId wasn’t copied to the ParentItemId and RootItemId of parent and child products. This issue affected custom logic that looked for AssetReferenceId in the ParentItemId and RootItemId fields of items in the cart. With this fix, the AssetReferenceId is correctly copied to parent and child products.

You couldn’t edit the hover text of the required label in OmniScripts.

With this fix, you can change the hover text of the required label. This fix allows you to add hover text for the label in multiple languages.

To edit the hover text, go to Setup. In the Quick Find box, enter Custom Labels, then select Custom Labels. Search for the OmniRequired label and edit it to update the value.

The Use Translations checkbox in Data Mapper Extracts was deselected automatically after a few seconds. The result was that translations weren't returned.

With this fix, you can select or deselect the Use Translations checkbox, and the selection doesn't change by itself.

When you clicked the How to Launch button in OmniStudio Designer, an error message was displayed.

This patch fixes this issue.

When you clicked Apply to Group in a multi-site cart, member quotes weren't created.

This patch fixes this issue.

Alignment, spacing, and other styling issues in generated PDF documents.

This fix resolves the alignment, spacing, and other styling issues in generated PDF documents.

Activating nested FlexCards fails and times out.

When deploying nested FlexCards with Vlocity Build Tool, FlexCards do not activate and time out. This fix ensures that Vlocity Build Tool retries if the API times out for the FlexCards.

When a running orchestration item in an Amend on Amend plan gets compensated, it remains in Running state, blocking the progress of compensation items. Hence the plan gets stuck.

For this scenario, this fix ensures that the compensated Running Orchestration Item is updated to the Amended state. This ensures that the compensation orchestration items and the plan progress as expected.

This new rule only comes applies if the XOMSetup FrozenRunningCompItemsAmendedEnabled parameter is set to true. By default, this parameter isn’t set in an org. If the parameter doesn’t exist in the org or is set to false, the new rule doesn't come into effect. This ensures that it’s backward compatible for existing customers that don't want the new behavior.

After updating FlexCards with flyouts, the next FlexCard is displayed rather than updating the displayed FlexCard.

If you use a nested field value as the Render Key, the FlexCards fly out moves to the next item instead of updating the existing item. With this fix, you can use a nested field value as the render key.

When an item in the Skipped state is canceled, it moves to the Discarded state instead of the Canceled state. In certain scenarios, this can cause a loop in the orchestration plan which distorts the plan.

With this fix, any items that you cancel in the Skipped state now move to the Canceled state.

The Energy & Utility Contact Center Console used Vlocity Cards with custom LWCs. These  LWCs did not support the custom labels used in the console application, and also did not offer multi-language support.

Vlocity Cards were converted to FlexCards to provide flexibility for component customization and multi-language support. Some of the FlexCards were also enhanced with new custom LWC components. These new LWCs are now part of the managed package and use custom labels for multi-language support on Translation Workbench.

Document generation did not work on iPad Safari, preventing store agents from generating, emailing, and printing the PDF documents they are legally required to give customers, and thus, not able to complete orders.

Salesforce supports Safari on iPad IOS 13 +, so .docx and PDF files are created and attached to the record.

An issue occurred in a Vlocity card where the layout showed "No records to display" even after the data was successfully fetched from the data source (VIP). The Vlocity card embedded an LWC that extended the leftProfileState. When the card loaded, this state came as undefined and an error appeared in the console. Addresses with special whitespace characters were breaking the profile state card in LWC Cards.

An extra check was added for replacing special characters before the JSON interpolation occurs. This fix works for data source results with special characters including whitespace characters.

You could not disable the trigger present in the Project object. Without the ability to disable the trigger, you could not run an approval process on this object. This prevented the use of projects functionality.

Added a custom setting so you can disable the managed trigger for the Project object.

Customers were unable to upgrade their environment from CME Spring '21 to CME Summer '21 due to a test class error when installing the managed package. The package installation failed because the code filtered on a field that is encrypted in the org.

The managed package code no longer references fields that are usually encrypted, such as names, addresses, etc., so the package installs successfully in the environment.