Asset 360 Release Information > Asset 360 Release Notes
Asset 360 Release Notes
ServiceMax Asset 360 comes with the following features and capabilities.
Topics:
Features and Enhancements
This section lists the impacted features in the Asset 360 releases.
Feature
Category (New Feature/Defect/Enhancement)
Description
Version Introduced/Impacted
Maintenance Plan Processing: Enhanced Scalability for Large-Volume Batch Processing
Enhancement
When processing a large number of Maintenance Plans across one or more Maintenance Plan Processes, the scheduler could encounter batch processing errors such as heap size limit exceptions and oversized batchable instances. These issues occurred because all eligible Maintenance Plan Processes scheduled for the same time were picked up together in a single batch, and the combined volume of plans and related records could exceed Salesforce governor limits.
This enhancement introduces three improvements to ensure reliable and scalable Maintenance Plan processing:
• Dynamic Batch Splitting: The Maintenance Plan Process scheduler now dynamically calculates the total volume of Maintenance Plans across all eligible processes and intelligently splits them into separate batch jobs. Each batch is capped at a configurable threshold, default being 10,000 Maintenance Plans, to ensure execution stays within safe processing limits. Maintenance Plans belonging to a single process are never split across batches. If a process exceeds the threshold, it is processed in its own dedicated batch. When more than five batch jobs are created, Salesforce runs five jobs concurrently while the remaining jobs are queued and executed as capacity becomes available.
• Heap Size Threshold Monitor: A dynamic heap-usage safeguard has been introduced in the logging framework. When heap utilization reaches 90% during batch execution, additional log entries are automatically skipped to prevent the batchable instance from exceeding the Apex heap size limit of 12 MB. This reduces the risk of heap overflow and serialization errors during long-running processes.
• Maintenance Plan Assignment Threshold: A new configurable setting has been added to limit the number of active Maintenance Plans that can be assigned to a single Maintenance Plan Process. When the configured limit is reached, users receive a validation error upon attempting to assign additional plans.
Business administrators are no longer required to contact ServiceMax Support to disable the detailed logging. They can now navigate to Asset 360 Admin Setup > Maintenance Plan Processing > Settings and configure the setting with the following details:
• Setting Name: Maintenance Plan Assignment Threshold
• Setting Type: Number
• Default Value: 10,000
Recommendations:
• When a single maintenance asset is associated with each plan, use batch sizes of 10 or 20, and keep the Maintenance Plan Assignment Threshold at or below 10,000. Ensure not to schedule more than 20 Maintenance Processes at the same time.
• When 1,000 maintenance assets are associated with a single plan, use a batch size of 1, and keep the Maintenance Plan Assignment Threshold at or below 100.
• To avoid Salesforce governor limits, distribute Maintenance Plans across multiple processes so that each process remains within the configured threshold. It is also important to maintain that the maximum asset per process should not exceed 10000, in any configuration.
* 
If threshold is set beyond the recommended limits, then there are chances to hit governor limits.
14.0
Maintenance Plan Processing: Enhanced Capability for Handling Oversized Batch Processing
Enhancement
The Standard Maintenance Plan Process in Asset 360 Admin did not run consistently. While it sometimes executed successfully, it frequently failed with errors related to heap size and oversized batchable instances. The issue was linked to excessive detailed logging and high CPU usage, which caused instability during long-running processes.
This enhancement introduces two improvements:
• disabling detailed logging to significantly reduce heap consumption
• applying CPU-time optimizations, including query refinements in record type mappings, to streamline execution
Customers are required to contact ServiceMax Support to disable detailed logging via the following configuration details:
• Custom Setting Object: Global Properties
• Name: GP805
• Key: COMMON_ORG_SETTINGS
• Value: True (default)
13.0
Condition-Based Maintenance Plan: Enhanced Sort Order Feature to Support Multiple Work Rule Scenarios
Enhancement
The issue occurred when executing the Maintenance Plan Process using a maintenance plan that contained over 15 rules. Despite multiple rules meeting their condition-based, frequency-based, or time-based criteria, only one work order was generated. This work order appeared only after a rule was modified to evaluate as false and the process was re-run. Each time the process was executed, other valid rules that should have triggered work order generation did not, indicating a failure in handling multiple qualifying work rules during the plan execution.
The sort order feature is enhanced to support multiple scenarios depending on the values. The updated use cases are as follows:
• If the sort order is blank, work orders are generated for all qualified rules.
• If the sort order is defined, a work order is generated for a single qualified rule.
• If multiple work rules share the same sort order value, work orders are generated for all qualified rules with that same sort order while still adhering to the overall sort order logic.
For more information, refer to Define Work Rule Template.
13.0
Product Service Campaigns: Additional Values for 'Maximum Number of Search Results Generated per PSC Search' Setting
Enhancement
This enhancement introduces new values for the 'Maximum Number of Search Results Generated per PSC Search' setting, allowing users to select up to 5000 and 7500 search results
This change ensures that the system can handle more extensive searches without errors, improving overall user experience.
For more information, see Managing PSC Configuration Settings
12.0
Product Service Campaigns: Enhanced User Experience for PSC Search Expression Builder
Enhancement
This enhancement improves the user experience in the PSC Search Expression builder by introducing a more intuitive and efficient way to select fields as parameters. The new design replaces the modal with a drop-down, adds filtering functionality, and limits drill-down levels to enhance usability and reduce user errors.
• Improved Field Selection: Users can now quickly filter and select fields from a drop-down list, making it easier to find the desired parameters without scrolling through long lists. For more information, see Adding Asset Search Criteria.
• Enhanced Usability: The new design reduces the number of clicks required to assign a field as a parameter, streamlining the process.
• Limited Drill-Down Levels: Users can drill down into related fields up to two levels, simplifying the selection process and improving performance.
• Legacy Modal Option: Administrators can enable the old modal design for users who need to drill down more than two levels. For more information, see Managing PSC Configuration Settings.
12.0
Asset 360 Tooling: End of Support for SFDX Command Plugins
Change
SFDX command plugins are no longer supported.
The administrators must utilize the SF-style commands to migrate the configuration items from one org to another. This change is due to Salesforce deprecating the SFDX-style commands and recommending the use of SF-style commands. For more information, see the Move from SFDX to SF.
For more information about SF command plugins, see SF Command Plugins for Migration.
12.0
Product Service Campaigns: Bulk Loading Asset Criteria for PSC Search
New Feature
End users can now bulk-load asset field criteria for a PSC search. For example, users can upload a .csv file containing asset serial numbers or other matching information as columns in a table. The bulk-loaded asset criteria are then used to generate PSC result lines for the asset records matching the criteria.
For example, end user can upload a .csv file containing serial numbers of 1000 assets that they want to recall. They can create a PSC that generates return orders for these assets.
The Bulk Load Asset Criteria component is added to the Product Service Campaign Lightning record page layout. Using this component, end users can upload the .csv containing asset criteria.
This capability helps users to:
• Save time, as they need not create multiple PSC search expressions and run the search multiple times.
• Combine data from multiple spreadsheets into a single PSC search.
• Ensure that duplicate result lines are not created even if they are working with multiple files of information.
For more information, see Bulk-Loading Asset Criteria.
11.0
Asset 360 Tooling: Introduction of SF-Style Command Plugins in Asset 360 Tooling
New Feature
SFDX command plugins have now been changed to SF-style commands.
It is recommended that the administrator use SF-style commands to migrate the configuration items from one Asset 360 org to another. The Retrieve, Validate, and Deploy SFDX-style commands have been replaced with SF-style commands.
This change aligns with Salesforce deprecating the SFDX-style commands and recommending using SF-style commands.
* 
New configuration items added in the 11.0 release can only be migrated using the SF-style commands.
For more information, see SF Command Plug-ins for Migration.
11.0
Product Integration: Issue Reporting and Product Feedback
New Feature
To align with PTC’s model-based closed-loop digital strategy, a process is introduced that automatically sends incidents identified by the service organizations. It also sends any product-related feedback to the product design and quality teams to:
• Proactively address non-conformance issues jointly with Service Organizations.
• Streamline product improvement opportunities discovered by the Service Organizations.
• Resolve non-conformances as quickly as possible to prevent any recurrence.
To achieve this, a new setup configuration option, named Issue Report Setup, has been introduced.
Administrators can configure the Issue Report option and add it as a wizard step to the Work Order or Installed Product object. This gives them a key role in the process, and ensures its smooth operation.
Technicians can access the Issue Report option in the web and SFS app to submit any issues or provide product feedback directly to the product engineering team for further evaluation and resolution. Technicians can attach files with the issue report.
For more information on configuration, refer to Configure Issue Report and Feedback.
For more information on submitting an issue report and product feedback, refer to Submit on Web or Submit on the SFS Mobile App.
11.0
Mobile: SFS Mobile Configurations
New Feature
The Asset 360 Admin Setup now has new module called Mobile Configuration.For SFS users, administrators can create configuration to enable access to A360 mobile components at user level or profile level. A default mobile configuration has been seeded. If SFS user has no predefined assignment, then the default mobile assignment is applied.
For more information, refer to Mobile Configuration.
11.0
System Settings: System Settings to Manage Packaged Flows
New Feature
A new system setting has been introduced in the Asset 360 Setup screen, allowing business administrators to enable or disable the packaged standard flows.
The setting takes precedence over the individual flow-level setting. It eliminates the need to deactivate package flows again that are activated by the Salesforce platform during package upgrade.
For more information, refer to Package Flow Management.
11.0
Servigistics: Servigistics Integration - Field Stock Optimization
New Feature
ServiceMax has launched a Parts Planning and Optimization feature powered by Servigistics. This functionality enables organizations to optimize inventory levels at their Field Stocking Locations. It extracts demand details, parts master data, product replacement information, current inventory levels, and inventory locations from ServiceMax. These inputs are processed through Servigistics’ optimization algorithms, which then provide optimized inventory levels by location and product.
11.0
Product Service Campaigns: Support to Generate Multiple Output Types from a Single PSC Result Line
Enhancement
End users can now select multiple delivery methods for a single PSC result line and have various outputs generated based on their selection. This enhancement enables end users to obtain multiple delivery outputs for a single PSC result line.
For example, end users can select return and work orders as output delivery methods for a PSC result line. When the result line has outputs generated by the PSC engine, a Work Order output record and a Return Order output record are created. This helps the end user generate both a return order and a work order for an impacted asset in a single PSC result line.
11.0
Product Service Campaigns: Ability to Re-run PSC Search After Delivering Outputs
Enhancement
End users can now re-run the search on a Product Service Campaign, even if PSC Result Lines have already been generated and their delivery outputs created. This enhancement helps end users re-run the defined search, provide coverage for any potential new assets that meet the search criteria, and add them as additional PSC result lines.
Rerunning the PSC search does not erase the previously generated result lines. Also, duplicate result lines are not created.
This enhancement helps end users to:
• Utilize long-term Product Service Campaigns, with a single campaign spanning multiple months or years and accurately identifying impacted assets.
• Incorporate updates to assets from the manufacturer or updates provided by Technical Attributes to a campaign already in use.
• Spend less time generating result lines for a campaign, as they do not have to add result lines manually for individual assets.
11.0
Product Service Campaigns: Configurable Columns in the PSC Manage Results Table
Enhancement
The PSC Manage Results table now has configurable columns. End users can dynamically manage results found by a PSC search. They can personalize their results table by rearranging the columns on the screen or adding columns for any custom fields they have configured in the PSCI object.
This enhancement helps end users curate their experience in PSC result lines per their requirements.
End users can:
• Add and remove columns
• Resize and rearrange columns
11.0
Product Service Campaigns: Ability to Delete a PSC Record and Its Related Records with One Click
Enhancement
Users can delete a PSC record and all its related records such as search criteria and result lines in a single click. Previously, deleting the PSC record did not result in deleting all its related records. An SPM Wizard step is introduced to delete the PSC record, which also deletes all the associated child records when it deletes the PSC record. If a PSC with results has already delivered output records from those results, then the wizard for deleting the PSC is disabled. ServiceMax recommends not deleting PSCs with generated outputs to preserve an audit trail within the org.
For more information, see Deleting a PSC Record.
11.0
Product Service Campaigns: Ability to Delete PSC Search Criteria
Enhancement
Users can now delete search criteria created for a PSC record. Previously, there was no provision to delete a search criteria fully.
Users can now:
• Delete the search criteria for a PSC record without having to delete the entire record.
• Delete the existing single asset search criteria and use the bulk load asset criteria option.
When the search criteria is deleted, the result lines generated from that search criteria are also deleted.
For more information, see Deleting PSC Search Criteria.
11.0
Condition-Based Maintenance Plans: Interval Adjustment When a Work Order is Completed Early
Enhancement
The dynamic interval adjustment capability in condition-based maintenance plans now acknowledges when a work order is completed ahead of the set milestone. Previously, interval adjustment was performed only for work orders that completed later than the set milestone.
This enhancement ensures that an asset's subsequent maintenance work order is automatically adjusted based on the current maintenance work order's completion status for the same asset. Work orders completed and closed later than expected will inform the interval adjustment logic on when to calculate the work rule's next milestone.
This enhancement helps end users to create realistic maintenance schedule, based on the on-ground data.
For more information, see Defining Work Rule Templates.
11.0
Condition-Based Maintenance Plans: Processing Run Performance Improvements
Enhancement
Performance improvements are achieved in maintenance plan processing job runs. The data volume per batch size has been increased, and optimal process run performance is ensured.
11.0
Entitlement: Bypass Service Contract Validation
Enhancement
A new configuration option has been added to the Application Settings object, allowing administrators to bypass the validation of the End Date value for Service Contract records.
This enhancement empowers administrators to adjust the Entitlement engine, enabling the End Date of a Service Contract record to be set to a date earlier than that of the Contract Line Item record.
For more information, refer to Bypass Service Contract Validation.
11.0
Upgrading the Asset 360 Package: Run Auto-configurator
Enhancement
Administrators must run the Auto-Configurator now using the A360 Migration Tool after installation or upgrades. The ability to run Auto-Configurator through A360 Admin has been removed to enhance the security of the system and ensure external tools are not being initiated from within the Salesforce Platform.
For more information, refer to Run Auto-configurator.
11.0
Asset 360 Tooling: Configuration Migration Tool
Enhancement
Administrators can now migrate the following configurations from one org to another using Migration Tool and SF commands plug-ins:
• Mobile Configurations
• Custom Flow Settings
For more information, see Configuration Migration Tool.
11.0
Technical Attributes: Enabling the Technical Attributes Component
Enhancement
Administrators can now enable or restrict end users to update technical attribute values for assets. When enabling the Technical Attributes component for Asset records, they can restrict the end users from having access to update the values and allow them to only view the technical attribute values.
This enhancement enables administrators to provide privileges to end users to update technical attribute values selectively.
11.0
Was this helpful?