Home
This section is a repository of the post-upgrade procedures that you must perform after your organization is upgraded to the latest version of Remedyforce. You must perform these procedures after each upgrade and for both self-upgrade and automatic upgrade.
If you are using Remedyforce permission sets to manage permissions for your users, you only have to enable new features. However, if you are using Remedyforce profiles or custom permission sets to manage permissions for your users, you might also have to manually configure the updated profile-level permissions in a release. For information about configuring profile-level permissions and the conditions in which you must manually configure these permissions, see Configuring-profile-level-permissions-for-new-features.
If you are upgrading from a few releases prior to the latest release, you must enable new features and configure the updated profile-level permissions in each interim release. BMC recommends that you first enable new features and update profile-level permissions in the release that immediately follows your current release. You can then enable features in each subsequent release until the latest release. For example, if you are upgrading from version 20.14.01 to 20.15.01 (Winter 15), you must first enable new features and update profile-level permissions in version 20.14.02, and then enable the new features and update profile-level permissions in version 20.15.01.
To confirm whether you have performed the post-upgrade procedures for previous releases, you can review the following table and verify the set of procedures for each release to which you have previously upgraded. The table links to topics that list the updated profile-level permissions and provides information about enabling new features in each release of Remedyforce.
Release | Enabling new features | Updated profile-level permissions |
|---|---|---|
| 20.25.02 (Summer 25) | Enabling new features in 20.25.02 | 20.25.02 profile-level permissions |
| 20.25.01 (Winter 25) | Enabling new features in 20.25.01 | 20.25.01 profile-level permissions |
20.24.02 (Summer 24) | ||
20.24.01 (Winter 24) | ||
20.23.02 (Summer 23) | ||
20.23.01 (Winter 23) | ||
20.22.02 (Summer 22) | ||
20.22.01 (Winter 22) | ||
20.21.02 (Summer 21) | ||
20.21.01 (Winter 21) | ||
20.20.02 (Summer 20) | ||
20.20.01 (Winter 20) | ||
20.19.02 (Summer 19) | ||
20.19.01 (Winter 19) | ||
20.18.02 (Summer 18) | ||
20.18.01 (Winter 18) | ||
20.17.02 (Summer 17) | ||
20.17.01 (Winter 17) | ||
20.16.01 (Summer 16) | ||
20.15.03 (Summer 15) | ||
20.15.02 (Spring 15) | ||
20.15.01 (Winter 15) | ||
20.14.02 | ||
20.14.01 | ||
20.13.02 | ||
20.13.01 |
This topic provides the upgrade schedules for the listed Remedyforce release version and its patches.
Last updated: August 29, 2025
Update summary: Added details about the Summer 25 release (Version 202502.20) that is generally available on August 29, 2025
Product documentation
To access documentation for the Summer 25 release of Remedyforce, click the following links:
Documentation Home | Release notes and notices | Upgrading | Upgrade FAQs
Remedyforce Hybrid Upgrade/Patch Schedule
Remedyforce Summer 25 Sandbox and Production Self and Automatic Upgrade
| August 29 - September 18 | September 19 | September 20 - October 2 | October 3 |
|---|---|---|---|
| Remedyforce Summer 25 Sandbox Self Upgrade Window | Remdyforce Summer 25 Sandbox Automatic Upgrade | ||
| Remedyforce Summer 25 Production Self Upgrade Window | Remedyforce Summer 25 Production Automatic Upgrade | ||
Note:
- All dates and times listed are Eastern time (New York, USA).
- We recommend that you do not refresh your sandbox organization during the upgrade window as it excludes your organization from the future upgrades.