00181601

The platform event processing failed when activity volume reached approximately 250,000 events, causing the SVMXA360__ApplicationEventBus__e process to exceed Salesforce platform limits. This issue surfaced during high activity periods, particularly when large numbers of assets and maintenance plans were processed in scheduled batches. The failure occurred because a trigger on the Application Event Bus object was republishing events that were already published by the Entitlement engine, effectively duplicating event traffic and rapidly consuming platform event limits. As asset volumes increased, this duplicate publishing behavior amplified system load and caused the event threshold to be hit.

14.0

00180498

Users without the required Asset 360 license were able to access and use Asset 360 features, such as creating field work orders and cases, despite receiving initial access error messages. Although the system displayed You don’t have access to this record warnings, it still allowed record creation after mandatory fields were completed. This occurred because the Salesforce platform did not validate the license for custom LWC components, allowing unlicensed users to execute Asset 360 functionality.

14.0

00180081

Issue: The contract was generated using the currency defined in the selected Service Contract Plan instead of matching the currency of the related Account when creating a Service Contract from an Account. Even if the currency field was updated through a trigger, the Service Contract continued to reflect the plan’s currency, preventing alignment with the Account currency.

Resolution: The Create Service Contract Apex action is enhanced to retrieve the updated currency values. The enhancement ensured that the method fetched and used the updated currency field values during subsequent processing, allowing the Service Contract currency to correctly match the Account currency. Users need to write custom trigger on the apex method for this to work. Without the custom trigger, it won’t pick from Account.

14.0

00179937

After upgrading to release 13.100.2, updating a Service Contract through the wizard successfully created a Contract Line Item (CLI) but failed to generate the corresponding Contract Price Line Items (CPLIs). Although the wizard displayed a success message and the CLI was created, the related CPLI list remained empty. This was a regression issue because the previous fix in release 12, which ensured CPLI generation during contract updates, had not been ported to release 13. The problem impacted pricing data for all contracts updated after the production upgrade.

14.0

00174292

When the Maintenance Plan Process was executed from Asset 360 Admin, the MPLN_ProcessBatch job consistently failed with the error Too many SOQL queries: 201. The failure occurred because, during preventive maintenance work order creation, additional SOQL queries were consumed while applying reference-field mappings and record-type mappings. As multiple work orders were generated, the cumulative query count exceeded Salesforce governor limits, causing the batch job to terminate with the SOQL limit error.

N/A

In the Asset360 application, the close X icon on Lightning Web Component (LWC) modal windows in the Asset Admin area was not visible to users. On the Setup Home page, when opening Wizard properties and other LWC-based dialogs, such as Manage Child Assets and certain PSC or entitlement-related modals, the icon did not appear, even though clicking in its expected position still closed the window. This behavior occurred consistently across affected LWC modals, creating a usability issue because users could not see a clear visual control to close the dialogs.

14.0

00174279

When the Preventive Maintenance Plan process finished running in Asset 360, the expected Application Log was not attached to the Maintenance Plan Completion Log. After reviewing the related records for the process run, no Application Log entries were found, leaving users without the necessary execution details.

13.0

00174125

The issue occurred in Asset 360 Admin when seed data for Wizards and Expressions failed to restore after running the recommended post-install script in a new sandbox. Initially, the customer found all seed data, including Wizards, Transactions, Expressions, and Object Mappings, missing. Although executing the script successfully repopulated seed data for Transactions, Object Mappings, and Screens, but the Wizards and Expressions sections remained empty.

13.0

00172726

After a recent upgrade, the Create Contract Line Item Apex Action did not function as expected. This defect impacted on API integrations, where users encountered failures when attempting to create contract line items using the Salesforce REST API. The issue emerged due to changes in validation logic introduced during the upgrade, affecting implementations that depended on previous behavior.

Specifically, when a contract line item was created via the REST Explorer with required fields such as ServiceContractId, SMAX_SAPContractLineNumber__c, and Asset, the request failed due to an error in the Contract Line Item After Save process. The new validation required a plan to be associated with the Contract Line Item or Asset record, and if absent, the API rejected the record.

13.0

00166998

A defect occurred in the batch processing of technical attribute updates through the API, where not all intended records were successfully updated. The failure happened despite successful execution of all batches, leading to incomplete data updates and missed expectations in automated processing.

In this case, when the batch was executed to update 1700 asset records, only 1600 technical attribute records were updated. One of the nine batches failed due to a timeout exception, specifically common.apex.runtime.impl.ExecutionException, which also triggered a platform event log record. Investigation revealed that the API request failed when duplicate asset names were included, even though recordId was correctly passed. This discrepancy led to approximately 600 technical attribute records not being updated.

13.0

00166179

The issue occurred in the Service Console FSI app within the users’ org when users accessed a PSC record and clicked Manage. Although all records were displayed correctly, the page continued to show a loading indicator. This misleading behavior caused confusion, as it appeared that the page had not fully loaded despite the data being visible.

13.0

00167416

The issue occurred on the Asset page in Asset 360 when users attempted to open the warranty term under asset coverages. A component error appeared due to a failure triggered by the asset hierarchy configuration using an expression. Specifically, the error was caused by an undefined getBoundingRect function. This was a regression defect introduced by the PSC search expression builder enhancement in version 12.0.

13.0

00172109

00172071

00172214

00172052

00172117

00172024

00172195

00172155

00172205

00172041

00172007

00172064

00172031

The issue occurred after the Summer '25 upgrade when opening the Asset 360 Admin Page, which resulted in a component error. This was caused by Salesforce's update to the Lightning Tree component that introduced stricter validation for the href attribute, requiring a properly formatted URL string. Previously, the setup page used the current page reference object to set the href for parent nodes, which worked without issue. However, with the new sanitization logic in place, this method no longer met the validation criteria, causing the component to fail.

13.0

00170119

The Application log records were not created because the hourly platform events limit was exhausted. This occurred when there were many Technical Attribute API calls in batch classes.

13.0

00167416

A component error occurred when the Asset Hierarchy component was clicked. This happened after an expression was added to the Select criteria to display matching records on hierarchy field in the Asset object.

13.0

00166998

The batch class failed to update all Technical Attribute records when a large number of assets were processed.

13.0

00168806

An Apex CPU limit exceeded error occurred when Work Rule templates were loaded from the Maintenance Plan template.

13.0

00161770,

00166042

A null pointer exception was returned instead of a meaningful error message when Assets were added to a Service Contract through the API.

13.0

00169517

The Contract Line Item Enrichment API created duplicate values when it processed more than one Contract Line.

13.0

00166179

In the Asset 360 Console app, the tab name showed as 'Loading' when the user clicked the 'Manage' button from the PSC result lines component.

12.0

00163167

The Create Contract Line Item Apex method does not behave the same way during the Create and Update scenarios.

12.0

00166042,

00161770

The Apex method does not return a meaningful message when the Product or Product Family is matched with the Service Contract Plan and the Asset.

12.0

00164487

An error occurred in the Search Criteria component when search results exceeded 7,500 lines per PSC search.

12.0

00164056

The component popup was not displayed when the user clicked timeline entries in the Asset Timeline.

12.0

00159213

The hover popup was not displayed when the user navigated through records in the Asset Hierarchy.

12.0

00163408

The wizard processing failed and an error occurred when the developer name of a custom wizard step matched that of a seeded wizard step.

12.0

00150324,

00149913

The last field and the next options were hidden from the record screen on the Salesforce mobile app when the user invoked the Service Process Wizard from the record page instead of the quick action.

Also, the user was unable to go to the previous screen from a Transaction flow on the iPhone device because of the missing Cancel button.

Resolution: On iPhone devices, you can now exit the SPM Wizard quick action screen by tapping Cancel on the top left of the screen in the Salesforce mobile app.

For more information, see Access SPM Wizard.

11.0

00152160

The Asset Transfer record page in the Salesforce mobile app started flickering when the user launched the Asset 360 app from the Product Request screen.

11.0

00149916

The user was unable to select the state specific to the selected country in the SPM transaction. When the user selected a state, another state with the same state code was updated in the State field.

11.0

00153080

Packaged SPM wizards failed to process after the user upgraded the org.

11.0

00157578

User was unable to scroll through search results and select a value in lookup fields in SPM.

11.0

00158169

User was unable to create object mapping that contained a field value as 0 forthe fields of type Currency, Number, Percentage, and Geolocation.

11.0

00156103

Asset timeline hover pop-ups did not display at the correct area on screen when the device had a large monitor.

11.0