Upgrade Process
To upgrade from a lower server package to the Active Maintenance Window (AMW)
As part of our commitment to provide value for our customers, ServiceMax has continued to develop new features/functions in our releases. From time to time, as we move away from old technologies or the use of VF pages, we identify opportunities to optimize the size of the technology package. For example, many VF pages have not been used for many releases, and these will be removed from the package. As a result, some of our customers' Core Patch Upgrade Processes may need to be adjusted.
All obsolete classes and VF pages have been removed from the managed package. Deprecated classes and VF pages have also been de-referenced in all applicable Patch releases. For more information on deprecated VF pages, see Migrating Deprecated VF Pages.
Customers using these deprecated or deleted components may see some functional impact. However, the VF pages and classes have been emptied since the 21.2 release, and no issues have been reported. This impact appears to be a corner scenario, and any additional issues will be handled case by case.
Customers must upgrade to the minimum patch version with no references to the old classes or VF pages. For more details, refer to the following table for the minimum patch versions.
The two-step process to upgrade to ServiceMax Core 23.1 and above releases are as follows:
1. Upgrade to a patch version of the current release that does not have references to the deleted components. For more details, refer to the following table for the minimum patch versions.
2. Upgrade to the ServiceMax Core 23.1 release or above.
 |
• If you have ServiceMax's Upgrade team do your upgrades, they will take care of this two-step process.
• If you are already on one of the minimum patches (or higher) listed in the following table, you can upgrade directly to the latest release version.
|
Minimum Required Patch Version to Avoid a Two-step Upgrade Process
The following table provides details on the minimum patch version to avoid a two-step process.
|
ServiceMax Version
|
Minimum Patch Version Number / Month
|
||
|---|---|---|---|
|
25.1
|
25.10000.14 / June 2025
|
||
|
24.2
|
24.20000.33 / June 2025
|
||
|
24.1
|
24.10000.48 / June 2025
|
||
|
23.2
|
23.20000.63 / March 2025
|
||
|
23.1
|
23.10000.63 / December 2024
|
||
|
22.2
|
22.20000.61 / July 2024
|
||
|
22.1
|
22.10000.9 / July 2022
|
||
|
21.2
|
21.20000.52 / July 2022
|
||
|
21.1
|
21.10000.78 / September 2022
|
||
|
20.2
|
20.20000.111 / September 2022
|
||
|
20.1
|
20.10000.202 / September 2022
|
Deprecated Custom Actions and Settings
Several unused Custom Actions and Settings have been removed from the ServiceMax Core package. When upgrading your org to the latest release, the existing Custom Actions and Settings list in the table will still be available in the org. The administrator need not take any action. The details of the deprecated custom actions and settings are given in the following table:
|
Custom Action Button Name and Settings
|
API Name
|
|---|---|
|
Custom Actions
|
|
|
Close Work Order(OTH020)
|
WORD_CloseWO
|
|
Activate Contract(OTH008)
|
SCON_Activation
|
|
Cancel Contract(OTH009)
|
SCON_Cancelation
|
|
Renew Contract(OTH035)
|
SCON_Renewal
|
|
Cancel Parts Request(OTH019)
|
WORD_CancelWOReqRec
|
|
Dispatch Technician(OTH016)
|
DCON_DispatchConsole_JS
|
|
Settings
|
|
|
CONF005_SET090 (Page to Manage SFM Data Validation Rules)
|
SFM_BusinessRules
|
|
CONF005_SET080 (Page to Manage SFM Expressions)
|
SFM_Expressions
|
|
CONF005_SET057 (Page to Manage SFM Migrator)
|
SFM_Migrator
|
|
CONF005_SET052 (Page to Manage SFM Designer)
|
SFM_TDM_Designer
|
|
WORD005_SET001 (Estimate/Usage Lines VF Page Name)
|
WORD_CreateWOEstUsgLines
|
Reference Topics