Loading
Salesforce now sends email only from verified domains. Read More
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 Winter `23

            You are here:

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

            Patch Releases Winter `23

            Periodically, we add patch releases for Winter '23. Check back here for information.

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

            CME 240.22.5.900.472.24

            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
            In the CPQNext Basket operation, the Pricelog data isn’t being populated correctly. For example, the start and end dates are in the wrong format, and the promotionId isn’t being populated. This patch fixes the issue.
            Order Management Plus: There was an issue when the catalog record was being loaded and flush was called internally that causes blocks the thread due to java.util.concurrent.ConcurrentHashMap.compute updating multiple keys. This issue has been resolved.

            CME 240.22.4.900.472.23

            This patch contains fixes to Contract Lifecycle Management to ensure features work correctly. Install this patch release to apply the fixes.

            Issue Description
            Starting March 2024, DocuSign has deprecated OAuth 1.0 authentication. You can continue using OAuth 1.0 authentication, until March 2024.

            Salesforce recommends using the more secure OAuth 2.0 for DocuSign. We’ve introduced a custom implementation for you to switch from OAuth 1.0 to OAuth 2.0 authentication.

            If you upgraded to 240.22.4 (which supports OAuth 2.0) from 240.11, and plan to start using OAuth 2.0 immediately, set the DocuSignAuth to OAuth 2.0.If you continue to use OAuth 1.0 until March 2024, or are setting up DocuSign for the first time, you don’t need to change the custom settings.

            Note
            Note In OAuth 2.0, the DocuSign Send On Behalf Of (SOBO) functionality is supported only through Named Credential. To send or sign DocuSign on behalf of another user, create a Send On Behalf field in the User object and assign the Send on Behalf named credential from that field in the user’s page. See Setup Send on Behalf of Another User.

            Here are the steps to create the custom settings:

            1. From Setup, in the Quick Find box, enter Custom Settings.

            2. Click Custom Settings.

            3. Click G and click Manage next to General Settings.

            4. Click New.

            5. Enter Name as DocuSignAuth.The name and value fields are case-sensitive.

            6. Enter Value as OAuth 2.0.

            7. Save your changes.

            See Also:

            CME 240.22.3.900.472.22

            This patch contains fixes to Enterprise Sales Management, Order Management, and OmniStudio to ensure features work correctly. Install this patch release to apply the fixes.

            Issue Description
            When you tried to upgrade your sandbox org from CME 236.2.23 to CME 240.19.900.472.14, the upgrade failed. This patch fixes this issue.
            If the orchestration scope was set to global and an order was amended, some orchestration items were created without appropriate dependencies. This logic has been fixed.

            CME 240.22.2.900.472.20

            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
            You have created attribute override, but the overridden value is not available in the Getoffersdetails response. When attribute value is overridden along with attribute metadata, getOfferDetails API doesn't show overridden attribute metadata in the response. This patch fixes the issue.
            Unable to add or find product description in Basket API response. Description field is missing in the related node of product2 in the basket response for each offer. Description is not a part of compiled data and response. This patch fixes the issue.

            CME 240.22.1.900.472.18

            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
            You were not able to invoke core services in your unit tests. The issue arises because the flow is not allowed to enter the core when the context is coming from a unit test and hence it returns an empty map.

            To invoke the core service from your unit test, add the below code to your setup. 

            vlocity_cmt__GeneralSettings__c toggleSetting = new vlocity_cmt__GeneralSettings__c(Name = 'FixToggleList', vlocity_cmt__Value__c = 'UnitTestContextBypass');
insert toggleSetting;
            In Standard Digital Commerce, the compile promotions fails for Promotions with zero active Products as Promotion Items. When you add an inactive product as the only promotion item to a promotion, the compile promotions job fails with a null pointer exception. This patch fixes the issue.

            CME 240.22.900.472.17

            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
            When creating the attributes for Product Specification and Product Offering, the attribute values were assigned incorrectly.

            This patch fixes this issue.

            After installing this patch, create the required TMForumDefaultAttributeCategory custom metadata in your Salesforce org.

            1. From Setup, in the Quick Find box, enter Metadata, and then click Custom Metadata Types.

            2. Click Manage Records associated with Vlocity Integration Setting.

            3. Click New.

            4. Create the TMForumDefaultAttributeCategory custom metadata with these values:

              • Label: TMForumDefaultAttributeCategory

              • Type of API: TMForum

              • API Name: TMForum

              • Key: AttributeCategoryName

              • Default Value: TMForum

              • Vlocity Integration Setting Name: TMForumDefaultAttributeCategory

            GetOfferDetails API call returns wrong adjustment or override prices.

            When the same product is added multiple times as a promotional Item with different offer context, pricing adjustment of the latest promotional Item overrides pricing adjustment of other promotional Items. This patch fixes the issue.

            To apply this fix, add the following toggle:

            1. From Setup, in the Quick Find box, enter Custom Settings and then select Custom Settings.

            2. Navigate to General Settings.

            3. Click Manage next to General Settings.

            4. Click New.

            5. Add the following information:

              • Name: FixToggleList

              • Value: FixPromoItemWithMultipleCtx

            6. Click Save.
            In certain scenarios, when you created a MACD order, the promotion for a child asset moved to a different child asset. This patch fixes this issue.
            Consider a case where product A required product B, and you added both products to the cart. The Add to Location button remained enabled even after you removed the required product, that is, product B. This patch fixes this issue.
            Unable to create cart from basket using Digital Commerce API when the trimmode is True & the CreateCartFromContextKey is set asTrue. Group Cardinality validation is failing for virtual item when the trim mode is enabled. This patch fixes the issue.
            When you created a move order, multiple order discount entries with incorrect Actions were displayed. This patch fixes the Action field of the original OrderDiscount object by changing it to 'Deactivate'. By default, the Action field's values are not displayed. However, if you want to see the Action field, customize the cpq-cart-discounts template.
            In some scenarios, attribute-based pricing didn't work as expected. This patch fixes this issue.

            CME 240.21.900.472.16

            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
            When you apply promotion, some fields are not returned in the promotion and the adjustment node. Promotional Adjustments contains extra fields when compared to the offer adjustments fields. The value of the extra fields is calculated in the pricing service but is not added by default in the adjustments node. This patch fixes the issue. Now the Sequence field in Promotion Node and vlocity_cmt_EstimatedEndDate_c field in adjustment node are returned.

            CME 240.20.900.472.15

            This patch contains fixes to Salesforce Industries Communications, Media, and Energy, Enterprise Sales Management, and Order Management Standard to ensure features work correctly. Install this patch release to apply the fixes.

            Issue Description
            Custom Pricing implementations couldn’t access the V2XLITransaction class. Due to this, they couldn’t mark items as new or dirty and custom changes weren’t saved to the memory.

            Any XLIs (OrderItem, QuoteLineItem, OpportunityLineItem records) that are modified in a custom pricing implementation aren’t saved to the system. To save them, use the FlowStaticMap class in custom pricing implementations to set the markDirty keys of the XLIs. Note that you can only use this fix for modifications of in-memory objects. If the items are queried again, the logic will override any existing objects that were present in the dirty map.FlowStaticMap.flowMap.put('markDirty', itemsToMarkDirty);

            Example:

            global inherited sharing class CustomPricingImplementation implements GlobalInterfaces.PricingInterface, UOWSupportedInterface
{
  global void priceLineItems(SObject parent, List<SObject> itemList) {
    String nsp = 'vlocity_cmt__';
    List<SObject> itemsToMarkDirty = new List<SObject>();
    for(SObject item: itemList) {   
      item.put(nsp + 'OneTimeCharge__c', 100);
      item.put(nsp + 'RecurringCharge__c', 400);
      itemsToMarkDirty.add(item);
    }
    vlocity_cmt.FlowStaticMap.flowMap.put('markDirty', itemsToMarkDirty);
  }
}
            When updating attributes with a numeric value in the Enterprise Sales Management working cart, the page automatically refreshed before you entered the complete number. This patch fixes this issue. Now the page only refreshes when you enter the number and click somewhere on the page.
            In Order Management, under certain circumstances, even if the XOM.EnableXOMTriggers custom setting was not selected, Order Management was executing XOMTaskTrigger. This patch fixes that issue. OM now honors the XOM.EnableXOMTriggers custom setting in every case.

            CME 240.19.900.472.14

            This patch contains fixes to Salesforce Industries Communications, Media, and Energy, OmniStudio and Order Management Plus to ensure features work correctly. Install this patch release to apply the fixes.

            Issue Description
            Users with customer community licenses couldn’t apply discounts to MACD orders. Industries CPQ was previously checking for license access to all related sObjects before applying discounts. Instead, Industries CPQ now checks for access for relevant sObjects instead. This patch allows customer community users to apply discounts to MACD orders.
            When you called a basket API with duplicate CachedAPIResponse__c records, the API returned an error.

            This patch fixes the issue.

            After installing this patch, clear the L2 cache to remove incorrect data populated in cache. Run the following script to clear the cache:

            vlocity_cmt.TelcoAdminConsoleController controller = new vlocity_cmt.TelcoAdminConsoleController();
controller.setParameters('{"methodName" : "clearAllCache"}');
controller.invokeMethod();
            In some instances, the XOMOrderSubmitBatchJob.finish was incorrectly timing out and resulting in some failed orders. This patch fixes the issue.
            OmniScript elements with Window Post Message enabled couldn’t be rendered in an OmniOut project. You saw the export 'safePostMessage' (imported as 'safePostMessage') was not found message. This patch fixes the issue.
            When you invoked the getBasket call via cpqAppHandler, the response of the API call was incorrect. On invoking the getBasket call it returns the response in a string format under the result node. The expected response should be a JSON object. This patch fixes the issue.

            CME 240.18.900.472.13

            This patch contains fixes to Salesforce Industries Communications, Media, and Energy, OmniStudio and Order Management Plus to ensure features work correctly. Install this patch release to apply the fixes.

            Issue Description
            When deploying Industries CPQ in LWC, datapacks weren’t migrated using the VBT migration tool. For OmniStudio enabled orgs, VBT failed to find the reference in VlocityRecordSourceKey when migrating datapacks for Industries CPQ in LWC. This patch fixes this issue by updating the Data Mappers.
            OmniScript elements with Window Post Message enabled couldn’t be rendered in an OmniOut project. You saw the export 'safePostMessage' (imported as 'safePostMessage') was not found message. This patch fixes this issue.
            The messaging element in OmniStudio displayed a message that didn't correctly reflect the element's value. For example, when the value of the Messaging element stored in JSON was null, the element still displayed a message.This patch fixes this issue.
            In Order Management Plus, if someone without permissions deleted an attachment used by XOMOrderSubmitBatchJob, the order would fail. This patch fixes this issue. The payload is still not deleted, but the order is submitted successfully.
            In Order Management Plus, there was a limit to the number of orchestration queues allowed, which included soft-deleted queues. With this patch, there is no longer such a limit, which results in successful orchestration even when there are many soft-deleted orchestration queues.
            In Order Management Plus, in the rare case where many decomposition relationships pointed to the same technical product, they were processed incorrectly, which could cause an error. This patch fixes this issue.

            CME 240.17.900.472.12

            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
            The productSpecification and productOffering resources don't return the child items in bundled product specifications and product offerings. By default, these resources return the parent-bundled items in the API responses.

            This issue occurred because the configuration to retrieve child items from bundled product specifications and offerings wasn't supported. This patch enables you to retrieve either the parent or child items from bundled product specifications and offerings.

            To retrieve child items from the productSpecification or productOffering resource, create the required custom metadata and update the Data Mapper Transform in Salesforce for the specific resource.

            1. Create the required custom metadata.

              1. From Setup, in the Quick Find box, enter Metadata, and then click Custom Metadata Types.

              2. Click Manage Records associated with Vlocity Integration Setting.

              3. Click New.

              4. Create the TMForumProductSpecificationUseChildForBu custom metadata for the productSpecification resource with these values:

                • Label: TMForumProductSpecificationUseChildForBu

                • Type of API: TMForum

                • API Name: TMForumProductSpecification

                • Key: UseChildForBundleProduct

                • Default Value: true

                • Vlocity Integration Setting Name:TMForumProductSpecificationUseChildForBu

              5. Create the TMForumProductOfferingUseChildForBu custom metadata for the productOffering resource with these values:

                • Label: TMForumProductOfferingUseChildForBu

                • Type of API: TMForum

                • API Name: TMForumProductOffering

                • Key: UseChildForBundleProduct

                • Default Value: true

                • Vlocity Integration Setting Name:TMForumProductOfferingUseChildForBu

              6. Create the TMForumAllFieldstoQuery custom metadata, which is required for both the productSpecification and productOffering resources, with these values:

                • Label: TMForumAllFieldstoQuery

                • Type of API: TMForum

                • API Name: TMForum

                • Key: AllFieldstoQuery

                • Default Value: true

                • Vlocity Integration Setting Name: TMForumAllFieldstoQuery

                  With these changes, the GET and POST APIs for all TMF 620 API resources return the child items in the responses.

            2. Update the TMF-TMForumProductSpecificationResponseTransform Data Mapper Transform for the productSpecification resource.

              1. On the OmniStudio Data Mappers tab in the OmniStudio app, access the TMF-TMForumProductSpecificationResponseTransform Data Mapper Transform.

              2. Modify the mapping for the bundledProductSpecification node to use the ChildProductId__r field for the Name and ID properties.

              3. Modify the formula for productChildItems:href to use the ChildProductId field instead of the ParentProductId field.

            3. Update the TMF-TMForumProductOfferingResult Data Mapper Transform for the productOffering resource.

              1. On the OmniStudio Data Mappers tab in the OmniStudio app, access the TMF-TMForumProductOfferingResult Data Mapper Transform.

              2. Modify the mapping for the bundleProductOffering node to use the ChildProductId__r field for the Name and ID properties.

              3. Modify the formula for productChildItems:href to use the ChildProductId field instead of the ParentProductId field.

            CME 240.16.900.472.11 / OM Plus: cme-240.16-4

            This patch contains fixes to Salesforce Industries Communications, Media, and Energy, and Order Management Plus to ensure features work correctly. Install this patch release to apply the fixes.

            Issue Description
            Inconsistent behavior of Catalog Product Definition job in Standard Digital Commerce.

            Advanced rules were not executed when linked with an entity filter condition for the basket APIs.

            This patch fixes the issue.

            The Order Management Plus Status job no longer does a version mismatch check.

            		 The Order Management Plus Status job used to check for version mismatches, but no longer does so.
            In Order Management Plus, a modified orchestration plan was incorrect when a supplemental order was applied to the orchestration with multiple running push events. This issue has been fixed.

            CME 240.15.900.472.10 / OM Plus: cme-240.15-2

            This patch contains fixes to Salesforce Industries Communications, Media, and Energy, and Order Management Plus to ensure features work correctly. Install this patch release to apply the fixes.

            Issue Description
            You weren’t able to add products to the cart and got the error “Failed Cache.Org operation for key 'vlocity_cmt__.CPQPartition.OpportunityLineItemproductGroupKeysForRulesTotalCount': Invalid key: max key length is 50”.

            This issue occurred when:

            • The products were in a product relationship.

            • A Vlocity configuration rule was applied to an opportunity line item.

            This patch fixes this issue.

            Before release Spring '21 (230), Order Management Plus truncated incoming account IDs to 15 characters. In Spring '21, to allow external account IDs, we removed this truncation. However, previously provisioned services still had truncated account IDs, which sometimes led to issues for MACD orders.

            		 This has been fixed.

            CME 240.14.900.472.9

            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
            You got the error “You don’t have permission to access IndustriesCPQService. Contact your administrator” when the ‘VPL-TMForumProductSpecification’ integration procedure called the apex class ‘TMFOpenAPIProductService’.

            TMF 620 APIs need the IndustriesCPQ permission set license. CME 240.0.900.468 (Winter `23) introduced an org permission check for the TMF 620 APIs. This check is made for GET and POST APIs of Catalog, Category, Product Specification, Product Offering, and Product Offering Price resources. The check was applied at the REST endpoint entry level and in resource-specific classes that are invoked from integration procedures.

            This patch enables TMF 620 for Managed Package License users so they can also access the TMF 620 APIs.

            GetOffers API doesn’t return any product, if SkinnyCtxDmsnCombinations = true

            and if the rule set associated with the product has more than one rule.

            When SkinnyCtxDmsnCombinations = true

            and if the rule set associated with the product had more than one rule, populate API cache wasn’t generating the catalogCtxEligibilityResult for the catalog.

            This patch fixes the issue.
            Inconsistent behavior of Catalog Product Definition job in Standard Digital Commerce.

            Hierarchy batch job runs but you don’t see entries for compiledOfferHierarchy data other than fieldMetaData present in the CachedAPIResponse table.

            This patch fixes the issue.

            However, advanced rules may not work when linked with an entity filter condition for the basket APIs. This issue is fixed in CME 240.16.900.472.11 minor release.

            CME 240.13.900.472.8

            This patch contains fixes to Salesforce Industries Communications, Media, and Energy and OmniStudio to ensure features work correctly. Install this patch release to apply the fixes.

            Issue Description
            Advanced rules with entity filters that checked for pre-existing assets didn’t work. You got the “ "No such column 'consequenceoffailure' on entity 'Asset'" error while adding a product that already had an asset in the related account. This patch fixes this issue.
            The Root Account (vlocity_cmt__RootAccountId__c) field isn’t cleared when a parent-child relationship is removed in CME 240.8. The vlocity_cmt__RootAccountId__c field must be set to null and the vlocity_cmt__IsRootResolved__c field must be set to false when a parent-child relationship is removed. However, these fields weren’t updated as expected. This patch fixes this issue.
            When UseAssetReferenceIdForParentAndRoot was set to true in the CPQ configuration and you created a cancel order, the vlocity_cmt__RootItemId__c and vlocity_cmt__ParentItemId__c fields were populated with the OrderItemIDs instead of AssetReferenceId__c. This patch fixes this issue.
            When you used the create basket API with basket action AddAfterConfig, the cart creation failed with the error “Unable to parse the attributes. Please review the line item json”. Cart creation was successful when Standard Digital Commerce was disabled. This patch fixes this issue.
            After cloning the parent and child flex cards, when you changed the name of the child flex card, you couldn’t use the Flex card local compiler because the custom labels were compiled incorrectly. This patch fixes this issue.
            For bundled products, with more than 31 line items and 15 attributes, the Cache Catalog Product Definition job fails with “System.LimitException: Apex heap size too large” error.

            This issue occurred when the heap size exceeded 12 MB and the number of Child Product Relationships (CPRs) was 5.

            To fix this issue, configure the CompileOfferCPRConfig CPQ configuration setting to customize the number of CPRs and subsequently reduce the heap size.

            For more information on this setting, see

            CPQ Configuration Settings Reference
            Basket APIs are throwing apex heap size error after core patch deployment that clears the in memory cache info of active snapshots for cache keys. This patch fixes the issue.

            CME 240.12.900.472.7 / OM Plus: cme-240.12-4

            This patch contains fixes to Salesforce Industries Communications, Media, and Energy, Order Management Plus, OmniStudio, and Enterprise Sales Management to ensure features work correctly. Install this patch release to apply the fixes.

            Issue Description
            When a new attribute was added to the Basket, it was noted that the attribute’s default value wasn’t seen in the Basket response. This patch fixes the issue.
            In Order Management Plus, the system could sometimes handle the same orchestration item with two processes at the same time (worker and push event processor), and a deadlock would occur in this case. This patch fixes this issue. Now, in this situation, the system checks if the lock is necessary and removes it if not.
            You weren’t able to upgrade to CME 240.10 and later when you used the Set Values action in an OmniScript. The Set Values action used % for undefined expressions in the JSON tree because of which the expressions couldn’t be resolved. This patch fixes this issue.
            You couldn’t see maps for locations in the Enterprise Sales Management app because the Show Map toggle button was disabled. This patch fixes this issue.

            CME 240.11.900.472.6

            This patch contains fixes to Salesforce Industries Communications, Media, and Energy, OmniStudio, and Advertising Sales Management to ensure features work correctly. Install this patch release to apply the fixes.

            Issue Description
            We fixed an issue where deleting a Data Mapper version cleared data inside other versions of the Data Mapper, including the active version. This issue occurred because all versions of the Data Mapper share the same name. This patch clones the active version of the Data Mapper before deleting the selected version.
            After upgrading to the CME 240.6.x.x release, when you ran the Field Maps Maintenance job, the toast message “Field Maps Maintenance Running…” message persisted indefinitely. Standard Digital Commerce APIs were enabled in the org. You were unable to place orders as a result of this issue. This patch fixes this issue.
            Starting October 04, 2022, DocuSign requires users to authenticate via OAuth 2.0. DocuSign CLM and Generic DocuSign users authenticating via OAuth 1.0 were unable to connect to DocuSign. OmniStudio now supports OAuth 2.0 authentication. Enable OmniStudio to use DocuSign forms by configuring an authentication provider and adding a named credential. This change applies to OmniStudio, not OmniStudio for Vlocity.
            The Promotion_Id and AppliedPromotionId were not inserted in vlocity_cmt__OrderPriceAdjustment__c after Basket To Cart Conversion. This was causing the deletion of order pricing records for adjustments when the pricing is run in the cart. This patch fixes this issue.
            We fixed an issue where IDX Build Tool (formerly called Vlocity Build Tool) didn’t compile custom LWCs locally as expected. When compiling locally, some elements used “c” instead of the namespace. This patch fixes this issue.
            In Advertising Sales Management, Picklist values do not display in the correct order in the UI. This patch fixes this issue.
            In Advertising Sales Management, the​ Save​ button in the Attributes Settings modal is enabled. Even when the required fields for attribute setting are filled, the attribute settings are not getting validated. This patch fixes this issue.
            When modifying a media plan, the ad quote lines are not cloned. This patch fixes this issue.
            After upgrading from CME 232 to CME 240.8.900.472, you weren’t able to add bundled products with minimum, maximum, and default quantities equaling zero to the CPQ cart. You got an error “You can not add more than 0 quantity”. This patch fixes this issue.

            CME 240.10.2.900.472.4

            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
            When you populated the cache using Populate Cache Orchestrator and then used the GetOffersByCatalog API, the API didn’t reuse the data populated during the cache miss, but fetched the data again. This patch fixes this issue.
            When you ran the Hierarchy Batch job after creating products and assigning a PriceListEntry (PLE) to one of them, the job failed with the error “Compiled offer hierarchy is not found. Please run the CPQNext Batch Job”. Catalog Product Relationships (CPRs) were created for all the products. The batch job was successful but there were no records in the cachedAPIResponse table. This patch fixes this issue.
            The response from the getOffers API in Standard Digital Commerce didn’t match the exact response from the getOffers API in Classic Digital Commerce for a few attributes. This patch fixes this issue.
            The Basket API for promotion overrode the attribute value to null if the default value for the attributes was null. This patch fixes this issue.

            CME 240.10.1.900.472.3

            This patch contains fixes to Advertising Sales Management to ensure features work correctly. Install this patch release to apply the fixes.

            Issue Description
            For quotes with a large number of line items, the attribute setting modal gets stuck and the loading symbol spins continuously. This patch fixes this issue.
            Error when clicking "Save & Exit" from the media plan after adding a new product. This patch fixes this issue.
            Unable to access cart after clicking Modify Quote with AdMedia Placement This patch fixes this issue.

            CME 240.10.900.472.2

            This patch contains fixes to Salesforce Industries Communications, Media, and Energy and Order Management to ensure features work correctly. Install this patch release to apply the fixes.

            Issue Description
            Order Management: Industries Order Management did not support JSON Attribute v2. With this patch, Industries Order Management supports JSON Attribute v2.
            The Create Cart API in Standard Digital Commerce had performance issues. The API has now been optimized for better response times.

            CME 240.9.900.472.1

            This patch contains fixes to Salesforce Industries Communications, Media, and Energy, OmniStudio, and Order Management to ensure features work correctly. Install this patch release to apply the fixes.

            Issue Description
            Order Management: When an order is canceled, Industries OM adds compensation tasks to roll back the fulfillment process. If compensation tasks have not been configured, or they're too simple (for example, having only one or two milestones), then a race condition sometimes lead to the cancel order not being completed. That is, it would remain in the In Progress state. This patch fixes the race condition and the cancellation orders can complete rather than stay in the In Progress state.
            The Vlocity Build Tool in OmniStudio wasn't compiling FlexCard Lightning Web Components (LWCs) with the correct namespace. Additionally, the Vlocity Build Tool failed to install a dependency. This patch fixes this issue.
            Cache Catalog Product Definition jobs failed with the error “First error: vlocity_cmt: Too many SOQL queries: 201”. The issue occurred when the ConfigurationSnapshot query was invoked multiple times while inserting new records in the CachedAPIResponse SOjbect. The issue was seen in catalogs with more than 150 Catalog Product Relationships. This patch fixes this issue.
            The GetOfferDetails Digital Commerce API returned null values for fields referenced via a lookup to a custom object. This issue occurred when there was a relational lookup field for a Product2 sObject. The GetOfferDetails API was looking for a key in a map that didn’t have a corresponding product field parameter in the Vlocity API Metadata APIParam__c. This patch fixes this issue.
            The Cache Catalog Product Definitions job would take a long time to complete due to the Populate Cache job being called within. This issue was seen when Standard Digital Commerce was enabled. This patch fixes this issue. See also Optimize the Cache Catalog Product Definition Job.

            CME 240.8.900.472

            This patch contains fixes to Salesforce Industries Communications, Media, and Energy, and Advertising Sales Management to ensure features work correctly. Install this patch release to apply the fixes.

            Issue Description
            Upgrades to CME 240.0.x.x failed with the error “field 'Name' can not be filtered in a query call”. This issue occurred when the Account.Name field was encrypted and the BulkChangeOfPlanServiceTest class queried this field in the where clause of the SOQL query. This patch fixes this issue.
            Upgrades to CME 240.0.x.x failed with the error “field 'Name' can not be filtered in a query call”. This issue occurred when the Account.Name field was encrypted and V2ReplaceAndCompareOffersTest and V2ReplaceOfferServiceTest classes queried this field in the where clause of the SOQL query. This patch fixes this issue.
            Upgrades to Energy and Utilities cloud CME 240.0.x.x failed with the error “field 'Name' can not be filtered in a query call”. This issue occurred when the Account.Name field was encrypted and the SfiEnergySelfServiceUsrRegControllerTest class queried this field in the where clause of the SOQL query. This patch fixes this issue.
            Upgrades to Media Ad Sales Management CME 240.0.x.x failed with the error “field 'Name' can not be filtered in a query call”.

            This issue occurred when the Account.Name field was encrypted and the SFBillingMyInvoicesImplementationTest and SFBillingProfileImplementationTest

            classes queried this field in the where clause of the SOQL query. This patch fixes this issue.

            CME 240.6.900.471

            This patch contains fixes to Contract Lifecycle Management and Advertising Sales Management to ensure features work correctly. Install this patch release to apply the fixes.

            Issue Description
            The Document Generation Process object supports server-side document generation requests and responses. The tokens in the document template are replaced with actual data using the token data mapping. The Token Data field only supports token data values up to 131K characters; therefore, generating documents with larger token data values wasn’t supported. For tokens greater than 131K characters, the server-side document generation will now use token data files to generate documents. The new Token Data Content Document field references large token data files, it supports up to 9.8 million characters for .docx generation and up to 0.24 million characters for .pdf generation for a single user. The character limits may vary based on concurrency. This patch fixes this issue.
            The Geo Targeting segment didn’t display selected values on pagination, and categories with large amounts of data took longer to load. This issue has been fixed.

            CME 240.5.900.470

            This patch contains fixes to ​Salesforce Industries Communications, Media, and Energy, OmniStudio, Order Management, and Enterprise Sales Management​ to ensure features work correctly. Install this patch release to apply the fixes.

            Issue Description
            The Asset to Basket API returned a null pointer exception when it was run on assets created by the Create Cart API. When the Create Cart API was run for baskets with promotions, the order creation was successful. However, the Promotion field in the Object Order Pricing wasn't populated. The issue occurred because the Asset to Basket API expected this field while running on these assets. This patch fixes this issue.
            The Submit Order transaction in Order Management took longer in the CME 240.x release as compared to the 238.x release. This patch optimizes the response time of the Submit Order transaction in Order Management.

            After an upgrade to CME 240.x you had to manually perform certain tasks like:

            • Activating deactivated picklist values for custom object Offer Migration Plan
            • Adding new picklist values for custom object CachedAPIResponse's Type__c field
            		 This patch automates these post-install tasks.
            In Order Management, push upgrades weren't possible, because Field Level Security checks required a manual permission change. This patch fixes this issue.
            In OmniStudio, if you used JAWS 2022 or NVDA to navigate through the Date/Time Properties date picker, with no screen reader, and then attempted keyboard navigation, the visible focus on the date was lost. You were able to navigate through the Date/Time Properties date picker using keyboard controls. The correct date was relayed to you, but the corresponding visual focus was lost. Visible focus was maintained when the date picker was used with VoiceOver on a MAC. This patch fixes this issue.
            In CME 240.x, the Data Mapper version was active regardless of whether versioning was enabled or not. This patch fixes this issue.
            You weren't able to activate OmniScripts in standard runtime if you had activated them with standard runtime disabled in the past. This patch fixes this issue.
            You got an intermittent error "This OmniScript is either inactive or has been replaced with a new version that has not been deployed" on the communities page. OmniScript deploys a new Lightning Web Component (LWC) every time a new OmniScript is activated. The LWC includes the active OmniScript ID in the metadata. When opening the new LWC version in communities, the cache, at times, serves the old metadata, throwing this error even if the OmniScript is active. This error occurs because of a mismatch between the active ID and cached ID. This patch fixes this issue.

            As long as the Lightning Web Security was enabled under session settings, you weren't able to:

            • Create an OmniScript and edit its JSON, Rich Text, or Labels.

            • Activate or debug the OmniScript.

            • Create a Flex Card and edit its JSON, Rich Text.

            • Activate the Flex Card.

            		 This patch fixes this issue.
            In Enterprise Sales Management, when you push upgraded from the Summer '22 release to the Winter '23 release, the enterprise cart page didn't load as expected. This patch fixes this issue.
            When you migrated from CME 238.x to 240.x the header section of the Energy and Utilities Cloud self-service portal broke. You also experienced this issue if you were using 238.x unmanaged components for the self-service community portal. The header flex card in the Energy and Utilities self-service community portal refers to a Lightning Web component. When this component is upgraded to version 240.x, the CSS of the navigation tabs and profile menu components in the header region breaks. This patch fixes this issue.

            CME 240.5.900.470

            This patch contains fixes to ​Salesforce Industries Communications, Media, and Energy, OmniStudio, Order Management, and Enterprise Sales Management​ to ensure features work correctly. Install this patch release to apply the fixes.

            Issue Description
            The Asset to Basket API returned a null pointer exception when it was run on assets created by the Create Cart API. When the Create Cart API was run for baskets with promotions, the order creation was successful. However, the Promotion field in the Object Order Pricing wasn’t populated. The issue occurred because the Asset to Basket API expected this field while running on these assets. This patch fixes this issue.
            The Submit Order transaction in Order Management took longer in the CME 240.x release as compared to the 238.x release. This patch optimizes the response time of the Submit Order transaction in Order Management.

            After an upgrade to CME 240.x you had to manually perform certain tasks like:

            • Activating deactivated picklist values for custom object Offer Migration Plan
            • Adding new picklist values for custom object CachedAPIResponse's Type__c field
            		 This patch automates these post-install tasks.
            In Order Management, push upgrades weren't possible, because Field Level Security checks required a manual permission change. This patch fixes this issue.
            In OmniStudio, if you used JAWS 2022 or NVDA to navigate through the Date/Time Properties date picker, with no screen reader, and then attempted keyboard navigation, the visible focus on the date was lost. You were able to navigate through the Date/Time Properties date picker using keyboard controls. The correct date was relayed to you, but the corresponding visual focus was lost. Visible focus was maintained when the date picker was used with VoiceOver on a MAC. This patch fixes this issue.
            In CME 240.x, the Data Mapper version was active regardless of whether versioning was enabled or not. This patch fixes this issue.
            You weren’t able to activate OmniScripts in standard runtime if you had activated them with standard runtime disabled in the past. This patch fixes this issue.
            You got an intermittent error “This OmniScript is either inactive or has been replaced with a new version that has not been deployed” on the communities page. OmniScript deploys a new Lightning Web Component (LWC) every time a new OmniScript is activated. The LWC includes the active OmniScript ID in the metadata. When opening the new LWC version in communities, the cache, at times, serves the old metadata, throwing this error even if the OmniScript is active. This error occurs because of a mismatch between the active ID and cached ID. This patch fixes this issue.

            As long as the Lightning Web Security was enabled under session settings, you weren’t able to:

            • Create an OmniScript and edit its JSON, Rich Text, or Labels.

            • Activate or debug the OmniScript.

            • Create a Flex Card and edit its JSON, Rich Text.

            • Activate the Flex Card.

            		 This patch fixes this issue.
            In Enterprise Sales Management, when you push upgraded from the Summer ’22 release to the Winter ’23 release, the enterprise cart page didn’t load as expected. This patch fixes this issue.
            When you migrated from CME 238.x to 240.x the header section of the Energy and Utilities Cloud self-service portal broke. You also experienced this issue if you were using 238.x unmanaged components for the self-service community portal. The header flex card in the Energy and Utilities self-service community portal refers to a Lightning Web component. When this component is upgraded to version 240.x, the CSS of the navigation tabs and profile menu components in the header region breaks. This patch fixes this issue.
             
            Loading
            Salesforce Help | Article