BMC Remedyforce 20.18.01
Date | Title | Summary |
---|---|---|
June 27, 2018 | 20.18.01.58.78: Patch 3 for version 20.18.01 | The following update has been made in Patch 3 of BMC Remedyforce 20.18.01. Corrected issues: For information about issues corrected in this patch, see Known and corrected issues. |
April 27, 2018 | 20.18.01.58.39: Patch 2 for version 20.18.01 | The following update has been made in Patch 2 of BMC Remedyforce 20.18.01. Corrected issues: For information about issues corrected in this patch, see Known and corrected issues. |
March 23, 2018 | 20.18.01.58.15: Patch 1 for version 20.18.01 | The following update has been made in Patch 1 of BMC Remedyforce 20.18.01. Corrected issues: For information about issues corrected in this patch, see Known and corrected issues. |
December 18, 2017 | 20.18.01 enhancements | Enhancements available in BMC Remedyforce 20.18.01 (Winter 18):
Known and corrected issues in BMC Remedyforce 20.18.01 (Winter 18): For information about issues that are known and corrected in this release, see Known and corrected issues. |
Tips
- To stay informed of changes to this space, place a watch on this page.
- Ready-made PDFs are available on the PDFs and videos page. You can also create a custom PDF.
Related topics
Supported browsers, mobile devices, and integrations
|
User permissions, supported browsers, mobile devices, integrations, and localized versions. | ||
If you are using BMC Remedyforce permission sets to manage permissions for your users, you only have to enable new features. However, if you are using BMC 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 BMC Remedyforce.
Note
After the automatic upgrade to the latest version, Salesforce sets the Running User of the BMC Remedyforce dashboards to BMC Remedyforce. Because of this issue, an error message is displayed when users access these dashboards. To enable users to view the dashboards, you must configure the appropriate user as the Running User after the automatic upgrade. For more information, see Configuring the Running User of dashboards in BMC Remedyforce.
Last updated: March 29, 2023
Update summary:
Added details about the Winter 23 revised build that is to be released on March 31, 2023.
Product documentation
To access documentation for the Winter 23 release of BMC Helix Remedyforce, click the following links:
Documentation Home | Release notes and notices | Upgrading | Upgrade FAQs
BMC Helix Remedyforce Hybrid Upgrade/Patch Schedule
- Remedyforce customers should refer to the Salesforce Trust website for any scheduled platform maintenance dates that may conflict with a Self Upgrade plan.
- Remedyforce Self Upgrading will upgrade and patch your ORG to the latest version available on the date that you Self Upgrade. If a patch is released after your Self Upgrade date, your ORG will be patched to the latest version on the Automatic Patch dates unless you again Self Upgrade to the latest patch release.
- Remedyforce Automatic Upgrade dates only apply to ORGs running the latest major patched version of Remedyforce.
BMC Helix Remedyforce Winter 23 Sandbox and Production Self and Automatic Upgrade
Feb 22 - Mar 16 | Mar 17 | Apr 3 | Mar 18 - Apr 13 | Apr 14 |
---|---|---|---|---|
BMC Helix Remedyforce Winter 23 Sandbox Self Upgrade Window | BMC Helix Remedyforce Winter 23 Sandbox Automatic Upgrade | BMC Helix Remedyforce Winter 23 (revised version) Sandbox Automatic Upgrade1 | ||
BMC Helix Remedyforce Winter 23 Production Self Upgrade Window2 | BMC Helix Remedyforce Winter 23 Production Automatic Upgrade3 |
We are updating the Winter 23 build to fix a few issues. The revised build will be available on March 31, 2023.
1 All sandbox organizations that are using the Winter 23 build will be updated to the revised build during the sandbox automatic upgrade.
2 If your production organization is already using the Winter 23 build, you can wait until the production automatic upgrade or manually update it after the revised version is available.
3 All product organizations that are using the Summer 22 Patch 1 or Winter 23 build will be upgraded to the revised build during the 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.
Comments
Log in or register to comment.