You are here:
Patch Releases Winter `21
Periodically, we add patch releases for Winter '21. Check back here for information
If you're looking for installation links, contact Salesforce Customer Support for help.
CMT 109.1.6.2 Patch Release
This patch contains fixes to Salesforce Industries Communications, Media, and Energy to ensure features work correctly. Install this patch release to apply the fixes.
Issue |
Description |
|---|---|
Updated to Apache Log4j 2.17.1 to fix critical security issues. See Apache's documentation: Apache Log4j Security Vulnerabilities |
CME 109.1.6.900.393.12 Patch Release
This patch contains fixes to Order Management to ensure features work correctly. Order Management users should install this patch release.
Issue |
Solution |
|---|---|
The E2E health check was too aggressive, marking the system as non-operational if there was no response within the configured timeout period. For example, if the E2E check payload occurred before a catalog sync event, it was blocked until the entire catalog sync was completed, which could take 20 to 40 seconds. If there was a burst of orders before the E2E check payload occurred, the check would only be processed after all the order payloads because AWS Lambda processes them serially in a shard. This could stop orders from being submitted to Order Management Plus. |
The check for E2E health is removed before submitting an order. Orders are no longer queued even if the E2E check fails. You can manually fail the E2E check by reducing the timeout: Go to Custom Setting → XOMSetup → and set OMPLMonitoring.E2E.requestTimeoutMs to 1000. |
XOMStoredPayloadsManager could not handle multiple payload attachment cases. Some orders had 700 attachment payloads. Orders were caught in an indefinite queuing loop and were never submitted. This permanently marked the environment order submit status as Queuing, thus slowing down order provisioning. |
XOMStoredPayloadsManager was changed to handle multiple attachments, preventing a queuing loop for orders. |
When submitting orders to a production environment, the order fulfillment status was set to Rejected, blocking orders from completing successfully. |
A fix was applied so that all orders complete successfully so they can be activated. |
Orchestration items remained in Pending state indefinitely. The order was submitted but due to failed orchestration, the order was not submitted to the downstream application. The Start milestone remained in Pending state and therefore all other orchestration items in the plan remained in Pending state. This issue is related to Order Submit via the Partner/Community User context. |
startOrchestrationItemsAndSetReadyState was changed to match orchestration items by ID rather than using the index so the orchestration plans execute properly. |
CME 109.1.5.1.900.393.11 Patch Release
This patch contains fixes to CME, Contract Lifecycle Management, and Order Management to ensure features work correctly. CME, Contract Lifecycle Management, and Order Management users should install this patch release.
Issue |
Solution |
|---|---|
In CLM, the Vlocity Action toolbar did not automatically refresh after record fields had been updated. Vlocity Flex Cards also did not refresh after adding an action to the Flex Card. |
A fix was applied so the Vlocity Action toolbar automatically refreshes after record fields are updated. |
The Vlocity Action Toolbar on the Order Details page did not refresh the page correctly, so the corresponding action buttons did not display when you tried to use the progress bar to change the status of an order. After a manual refresh, the page displayed correctly. |
The action toolbar is refreshed to display the corresponding action buttons without needing to refresh the browser. |
Orchestration items remained in Pending state indefinitely. The order was submitted but due to failed orchestration, the order was not submitted to the downstream application. The Start milestone remained in Pending state and therefore all other orchestration items in the plan remained in Pending state. |
startOrchestrationItemsAndSetReadyState was changed to match orchestration items by ID rather than using the index so the orchestration plans execute properly. |
When a false condition was retained for a child product in a bundle, the Top Order Item scope for the child destination product had an add action without an Inventory Item and the bundle destination product had a Modify action with an Inventory Item. |
A fix was applied so that the destination bundle and child products both have a No Change action with an Inventory Item. |
During Change of Plan (CoP), the Top Order Item scope Fulfillment Request Line (FRL) items were not merged when source OrderItems were Disconnect/Replace and Add/Replace. |
Bundling rules now apply so that Modify/ReassignFRL items are merged. |
CME 109.1.5.900.393.10 Patch Release
This patch contains fixes to CME, Contract Lifecycle Management, and Order Management to ensure features work correctly. CME, Contract Lifecycle Management, and Order Management users should install this patch release.
Issue |
Solution |
|---|---|
In CLM, the Vlocity Action toolbar did not automatically refresh after record fields had been updated. Vlocity Flex Cards also did not refresh after adding an action to the Flex Card. |
A fix was applied so the Vlocity Action toolbar automatically refreshes after record fields are updated. |
Orders were moved to the Fallout queue and rejected when Order Management could not obtain a transaction due to database issues. Once in the Fallout queue, orders required manual intervention. |
A fix was applied so orders do not move to the Fallout queue when a CannotCreateTransactionException occurs. Order Management automatically retries the order submission. |
In Order Management, the kafka2sfdc pod restarted when it received a ConcurrentPerOrgLongTxn error response with a 500 http code. This error may occur due to governor limits that limit long-running transactions. This in turn caused a delay in sending notifications to SFDC and also raised many false alerts for Cloud Engineering monitoring. |
ConcurrentPerOrgLongTxn limit exceeded is a transient exception, so the kafka2sfdc pod retries the request instead of failing and restarting the pod. |
When assigning a DocuSign recipient as Carbon Copy in Contract Lifecycle Management, the |
A fix was applied so the Recipient Type remains as Carbon Copy. |
In Order Management, skipped orchestration items remained in the table with running orchestration items, which increased the size of the table dramatically. Every time a worker started, it scanned the running table. The huge size of the table would cause a very slow worker start and sometimes even a failure to start. Restoration required manual intervention by Cloud Engineering. |
A fix was applied to ensure that skipped orchestration items are removed from the running table. |
A User object has an Order Management Plus Enabled field that controls whether a specific User record is synchronized to the OM Plus database. However, when only this field was changed from false to true, the record was not sent to OM Plus, and an Administrator needed to change any other field on the record (e.g., Name or Username) to initiate a sync. |
A fix was applied so catalog sync delta is generated when only the OM Plus Enabled field is modified. |
Customers were unable to use the Hybrid CPQ cart if there were large numbers of products added in a bundle. A Device requires a minimum of 1 child item(s) error occurred while adding a large bundle that had more than 60 products. Products did not appear in the cart. Issues occurred with pagination when bundles had virtual products in the hierarchy. |
This fix allows customers to load a cart with many products using pagination even when products have virtual products in their hierarchy. |
When the UOW mode was enabled, multicurrency did not work and threw the following error: FIELD_INTEGRITY_EXCEPTION, The price book entry currency code is different than the one assigned to the Quote. When Multi-Currency is enabled in an org, there can be multiple price book entries for a single product. The price book selection logic did not consider currency code in the UOW enabled mode. This led to the selection of multiple price books with the first entry being overwritten by the later ones. |
If multicurrency is enabled, then a map is created based on currency code. UOW mode works correctly when set to True. |
CME 109.1.4.900.393.8 / OM Plus cme-109.1.4-4 Patch Release
This patch contains fixes to the Order Management user interface and functionality to help improve usability and performance. Order Management and Digital Commerce users should install this patch.
Issue |
Solution |
|---|---|
A regression was introduced in a CME 109.0.X patch where the Digital Commerce remoteAction API AddToBasket no longer supported the offerDetails parameter. The workaround was to use the productConfig parameter. |
The Add To Basket After Config API supports the offerDetails parameter and the productConfig parameter. Both these parameters are the same. |
The rollback of an orchestration plan got stuck in progress when all orchestration items were finished. In some cases, orders were not activating, so no further changes could be made to services associated with the order, requiring manual intervention. |
When an orchestration plan is completed, an extra verification is required to ensure all dependent orchestration items of the plan’s last orchestration items are in their final state. If all dependent items are in their final state, then the plan can be completed and orders activated. |
Supplemental orders were erroneously rejected if the same product was canceled and added back in the supplemental order and the order item for that product had an orchestration item with global scope and this item was in Ready state when the supplemental order was submitted. |
Order Management can handle a status/action combination of frozen/create when computing compensation. |
The addition of a promotion with “basketAction:AddAfterConfig” failed when adding the promotion to the basket. This returned an "Unable to Process Basket Operation” error and prevented Digital Commerce from performing the basket operation. |
The exception occurred because Digital Commerce inserted the same Order Line item twice while inserting the promotion. Duplicate order line items were created, making it difficult for Digital Commerce to pick the correct order line item against the passed basket wrapper Item ID. |
