Loading
Get Started with Communications, Media, and Energy & Utilities (CME)...
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Patch Releases Spring `21

            You are here:

            1. Salesforce Help
            2. Docs
            3. Communications, Media, and Energy & Utilities Managed Package

            Patch Releases Spring `21

            Periodically, we add patch releases for Spring '21. Check back here for information.

            If you're looking for installation links, contact Salesforce Customer Support for help.

            CME 230.7.6.900.408.17 Patch Release

            This patch contains a fix to Order Management to ensure features work correctly. Install this patch release to apply the fix.

            Issue

            Solution

            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.

            OM PLUS: CME 230.7.5-2 Patch Release

            This patch contains a fix to Order Management Plus to ensure features work correctly. Install this patch release to apply the fix.

            Issue

            Solution

            Orchestration plans with a large number of items took too long to complete and failed with an exception.

            In orchestration plans where a large number of items were skipped, the processing of the plan failed with unexpected exception errors. This fix optimizes the processing of skipped items in Order Management Plus to ensure that such orchestration plans resolve without errors.

            OM PLUS: CME 230.7.4-5 Patch Release

            This patch contains fixes to Order Management Plus to ensure features work correctly. Install this patch release to apply the fix.

            Issue

            Solution

            Orchestration plan updates failed with a Null Pointer Exception.

            When Order Management Plus processes a supplemental order and original orchestration items are in Failed or Fatally Failed state, orchestration plan updates fail and the supplemental order is rejected with an error. With this fix, Order Management Plus processes these scenarios correctly, and the orchestration plan is updated successfully.

            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

            OM PLUS: CME 230.7.3 Patch Release

            This patch contains fixes to Order Management Plus to ensure features work correctly. Install this patch release to apply the fix.

            Issue

            Solution

            With the introduction of the PII masking implementation, some scenarios were overly masked. That is, there were asterisks where the customer wanted to see data.

            You can now ship application logs before PII masking is applied to your S3 bucket.

            However, there is a known issue with this patch: When logs are shipped to S3, the sourceName and sourceCategory columns show the actual word container at the end of the values instead of the name of the container.

            For example, if the container is named completer, the log says something like sourceCategory=kubernetes/sample/container rather than sourceCategory=kubernetes/sample/completer

            Apache Log4j had some security issues.

            Updated to Apache Log4j 2.17.0 to fix critical security issues. See Apache's documentation: Apache Log4j Security Vulnerabilities

            CME 230.7.2.900.408.16 Patch Release

            This patch contains fixes to Salesforce Industries Digital Commerce and Order Management Plus to ensure features work correctly. Install this patch release to apply the fixes.

            Issue

            Solution

            Creating a cart using the Digital Commerce (Cacheable) basket APIs fails due to the error “Unable to construct Basket or basket may not be available for given key”.

            Cache entries of the type orderConfiguration and cartContext are inserted in the CachedApiResponse table in the wrong order. This occurs due to a race condition between these two types. A fix was applied to prevent the race condition.

            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.

            CME 230.7.1.900.408.15 / OM Plus: cme-230.7.1-5 Patch Release

            This patch contains fixes to Salesforce Industries Order Management to ensure features work correctly. Order Management users should install this patch release.

            Issue

            Solution

            Jeopardy Management interfered with orchestration item execution and reopened the completed callout. This led to the failure of the orchestration items that were completed in the first execution.

            Updates for Jeopardy Management are localized and include only StartDate__c DueDate__c JeopardySafetyInterval__c and ExpectedCompletionDate__c in the orchestration item DML(updates) and excludes Status and other non-related fields.

            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.

            The assetization process updated number values to string values in the JSONAttribute and Attribute selected values field.

            A fix was applied so the assetization process updates number values correctly in the JSONAttribute field.

            After quoting, child Asset Reference Ids were duplicated, causing inconsistencies in the Move, Add, Change, Delete (MACD) process. Asset Reference Ids were the same for products added at the same time to multiple sites. This allowed the first order for the first site to proceed normally. However, it modified orders on other sites, moving the initially created asset to the new site.

            A fix was applied so that child Asset Reference Ids are not duplicated.

            PII masking impacted a customer solution to collect statistical information. Logs were masked once the environment variable was configured for masking.

            An environmental variable switch was introduced that allows you to turn off PII log masking.

            CME 230.7.900.408.14 Patch Release

            This patch contains fixes to Salesforce Industries Configure Price Quote (CPQ) to ensure features work correctly. Customers that use Order Management Integration Layer (for example, Order Management Standard and Order Management Plus users) should install this patch release.

            Issue

            Solution

            After a supplementary order is rejected, the isChangesAllowed flag is incorrectly set to true for all commercial order products in the original order. Therefore, CPQ rejects the canceled order as the point-of-no-return (PONR) settings of the original order are ignored.

            A fix ensures that when a supplementary order is rejected, isChangesAllowed is reset to the value it was set to before the order was canceled.

            CME 230.6.900.408.13 Patch Release

            This patch contains fixes to Salesforce Industries Contract Lifecycle Management (CLM) to ensure features work correctly. CLM users should install this patch release.

            Issue

            Solution

            When the Contract Start Date field in a Contract with 100 or more line items is updated; a SOQL 101 Limit Exception error appears because the CLM trigger runs a query in a loop.

            A fix allows Contract Start Date updates for Contracts with 100 or more line items.

            CME 230.5.900.408.12 Patch Release

            This patch contains fixes to Salesforce Industries CME, CLM, and Order Management Plus. Users of these products should install this patch release.

            Issue

            Solution

            Duplicate products in the cart result in duplicate AssetReferenceId values in the related contract line items after order submission.

            A new Contract Management Configuration Setup setting named DisableCLIUpdatesBasedOnOrders was introduced to bypass the duplication of AssetReferenceId in the contract line items on order submission. When the DisableCLIUpdatesBasedOnOrders setting is added and set to true, it will disable the auto-update of the contract line items. To create this setting, go to Setup > Custom Settings > Contract Management Configuration Setup and click Manage > New.

            You will also need to manually map the opportunity, quote, and order to contract line in the Field Mapper or run the Field Maps Maintenance job.

            From the Source Object section of the Field Mapper, select the source object and destination object to map to the contract line item:

            Opportunity:

            • Source Object: Opportunity Product<OpportunityLineItem>

            • Destination Object: Contract Line<name space>__ContractLineItem

            Quote:

            • Source Object: Quote Line Item <QuoteLineItem>

            • Destination Object: Contract Line<name space>__ContractLineItem

            Order:

            • Source Object: Order Product<OrderItem>

            • Destination Object: Contract Line<name space>__ContractLineItem

            From the Fields Map section of the Field Mapper, select the source object and destination object for opportunity, quote, and order:

            • Source Field: <namespace>_AssestReferenceId_c

            • Destination Field: AssestReferenceId<namespace>_AssestReferenceId_c

            Some orders submitted from Salesforce to Order Management Plus were not moving to the In Progress state after submission and remained in the Submitted state once accepted by Order Management Plus. Order Management Plus then progressed the order regardless of the status in Salesforce because the order had already sent the notification. Once completed, the order sent an Activation notification.

            A fix was applied so the Order Management integration layer notification processor properly handles exceptions and applies notifications. Orders in production display their status according to the notification or response received from Order Management Plus.

            When products were added to the cart for an order, their prices did not appear.

            An API version was updated so prices appear when you add products to the cart for an order.

            Processing of supplementals orders became stuck under conditions that involved a lot of orchestration items, which impacted deployment and raised concerns about performance under high load.

            Improvements were made to the AmendRollbackPlanGenerator so supplemental orders are processed faster when there are a lot of orchestration items.

            Orchestration items became stuck in Pending state if the dependency was Discarded, preventing supplemental orders from completing. When a base order was created, then amended, part of the plan was discarded. The orchestration item that followed the discarded orchestration item became stuck in Pending state.

            A fix was applied so the query considers discarded and canceled orchestration items. Pending items are transitioned to Ready as soon as dependencies are resolved, for example, moved to Discarded state.

            Customers received an Attempt to de-reference a null object error when adding products to their cart. Customers were unable to add a product to the cart when there was a custom validation implementation of the Product Validation Interface that did not implement UOWSupportedInterface and Unit of Work mode was set to True. This impacted their deployment and further testing because they rely on Unit of Work for greater performance.

            A fix was applied so you can add products to the cart without error when Unit of Work mode is True.

            CME 230.4.900.408.11 Patch Release

            This patch contains fixes to Contract Lifecycle Management (CLM) and Order Management (OM) to ensure features work correctly. CLM and OM users should install this patch release.

            Issue

            Solution

            A SOQL query limit was reached when attempting to load a Vlocity Action Toolbar on the Case Record Page.  A SOQL query appeared to be generated for each active Action in the org, which limited the ability to add more actions and resulted in an error of too many SOQL queries. This caused a complete halt to development because new actions are required, but an error was generated every time the Case Record Page was viewed.

            A fix was applied so you can add actions on the Case Record page without error.

            Orders were rejected when their order items had an optional date or datetime attribute without any value. Customers could not process such orders. These orders were rejected because Order Management Plus expected all date or time attributes to have a value.

            The validation ignores null or empty values. Orders are successfully submitted to Order Management Plus when their order items have an optional date or datetime attribute with a null value.

            In disconnect scenarios, the order decomposition process did not propagate the correct attribute values to the technical products.

            A new Order Management setting named AttrMappingFromDisconnectedOLIEnabled was introduced to bypass the Disconnect Action check and propagate the attribute value. When the AttrMappingFromDisconnectedOLIEnabled custom setting is added and set to true, propagation from the disconnected order line item occurs and the attribute value is passed to the technical product.

            For information about adding a custom setting, see Add a Custom Setting to Order Management

            ChangeToQuote functionality did not work for the override price. ChangeToQuoteManual adjustments were applied but disappeared when pricing was run again. When a manual adjustment was applied and pricing was run, manual adjustment records were deleted and only the data was stored in the Pricing Log. When pricing was run again, no adjustment records were found and the data was removed from the Pricing Log, leaving manual recurring prices unapplied to the quote line items.

            ChangeToQuote functionality considers the asset’s manual override price and reflects that in the Quote Cart’s line items. Assets created from orders or quotes that have manual adjustments work correctly with change to quote.

            The getCarts API threw a list index out of bounds error when navigating to CPQ for an opportunity. No cart operations could be executed and you could not create an Opportunity Cart.

            The code checks for an empty list so the getCarts API runs successfully and the Opportunity Cart can be created.

            Assets were not being repriced after running the repricing Apex so you could not reprice assets.

            A fix was applied so you can reprice assets without issues.

            CME 230.3.1.900.408.9 Patch Release

            This patch contains fixes to Enterprise Sales Management to ensure features work correctly. Enterprise Sales Management users should install this patch release. After you install this patch, migrate the required CME components to your org.

            Issue

            Solution

            Clone functionality did not render the product in the cart and previously added products disappeared. When you clicked the Clone button, the UI indicated cloning was successful but the Cart Refresh did not show the cloned product. Other products disappeared. This behavior caused an inconsistent UI with cloned products.

            A fix was applied so the cloned products show in the UI without any discrepancies. You can clone and delete child items in a bundle, add a cloned item to the Summary tab, and create an order from it.

            CME 230.3.900.408.8 Patch Release

            This patch contains fixes to Enterprise Product Catalog (EPC) and Order Management (OM) to ensure features work correctly. EPC and OM users should install this patch release.

            Issue

            Solution

            The object layout did not work as expected after upgrading to CME Spring ‘21. The layout section of the object type contained duplicate attributes under the wrong facet but the attributes for certain products did not appear. You could not access the object layout.

            A fix was applied to the getObjectLayoutById API so it longer returns duplicate sections for the new Product Designer. The object layout works as expected after upgrading to CME Spring ‘21.

            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 230.2.2.900.408.7 Patch Release

            This patch contains fixes to CME, Contract Lifecycle Management, and Communications and Media Application Suite to ensure features work correctly. CME, Contract Lifecycle Management, and Communications and Media Application Suite users should install this patch release.

            Issue

            Solution

            When assigning a DocuSign recipient as Carbon Copy in Contract Lifecycle Management, the ContractEnvelopeStatusScheduler converted any contract recipient from Carbon Copy to Unknown. This behavior also occurred when a signer designated a new signer using DocuSign. The original signer type was updated to Carbon Copy, but was then stored as Unknown after the batch job ran. Carbon Copies of the contracts were not sent.

            A fix was applied so the Recipient Type remains as Carbon Copy.

            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.

            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 Unit of Work (UOW) mode was enabled, multicurrency did not work and threw the following error: “FIELD_INTEGRITY_EXCEPTION, The price book entry currency code is different from the one assigned to the Quote”. This led to an incorrect currency code when adding an item to the cart.

            A fix was applied to allow multi-currency to work as expected when UOW mode is set to True.

            The Product sidebar did not display the correct prices with multi-currency enabled.

            A fix was applied so the Product sidebar displays the correct prices with multi-currency enabled.

            Some calculation matrices failed to upload on new versions. When trying to import a new version by uploading a CSV into a calculation matrix, it failed even if the CSV file used was downloaded from a different version of the same calculation matrix and no changes were made.

            Calculation matrices successfully upload on new versions.

            In Enterprise Sales Management, the cart did not obey relationships defined on products, which prevented customers from using Product Relationships. Rule messages (such as recommend) did not appear in the cart.

            In Enterprise Sales Management, the cart displays Product Relationship error messages. The Recommendation message appears at the cart level.

            In Enterprise Sales Management, when a child product was added to the cart and cloned, an error message appeared and the page kept loading. However, once the page was refreshed, you could see that this product was cloned successfully.

            Cloning and deleting of child product items in the bundle works without error.

            CME 230.2.1.900.408.6 Patch Release

            This patch contains fixes to Communications and Media Application Suite to ensure features work correctly. Communications and Media Application Suite users should install this patch release.

            Issue

            Solution

            In Enterprise Sales Management, products did not show the required attributes in the cart. If the product had child products, then you could click the product name and see the attributes. However, it was not possible to amend the attributes on the lowest level child products. At run-time, you could not edit required attributes when read-only attributes are present as well.

            Code was added to handle multiple attribute categories. Code was also added to maintain this.editAttribute data for multiple categories. Attributes are now editable as if you were configuring the same order in hybrid CPQ.

            In Enterprise Sales Management, picklist attribute values were not updating in the backend but the UI showed otherwise. The values did not persist and settings such as Add to Location and Add to Subscriber were not enabled.

            A fix was applied so the values persist. After completing all attributes, settings such as Add to Location and Add to Subscriber are enabled.

            CME 230.2.900.408.4 / OM Plus cme-230.2-8 Patch Release

            This patch contains fixes to Order Management and Digital Commerce to improve functionality and performance. Order Management and Digital Commerce should install this patch.

            Issue

            Solution

            Adding a Promotion to the empty basket with “basketAction":"AddAfterConfig” did not add the Promotion to the basket and returned the error message, “Unable to Process Basket Operation". At the same time, you could add a promotion with “basketAction":"AddAWithNoConfig” without issue.

            A fix was applied so you can add the promotion to the basket with “basketAction = AddAfterConfig” without any error.

            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.

            You needed to enable the OMplus property for users and make a dummy change to Name, Email, and Username to regenerate Sync Delta Objects for the catalog and synchronize the user to Order Management Plus for logging purposes.

            You can regenerate Sync Delta Objects for the catalog and synchronize the user to Order Management Plus without issue.

            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.

            FRL items are merged.
             
            Loading
            Salesforce Help | Article