This section is a repository of the post-upgrade procedures that you must perform after your organization is upgraded to the latest version of BMC Remedyforce. You must perform these procedures after each upgrade and for both self-upgrade and automatic upgrade.
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.
|Release||Enabling new features||Updated profile-level permissions|
|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)||Enabling new features in 20.21.01||20.21.01 profile-level permissions|
|20.20.02 (Summer 20)||Enabling new features in 20.20.02||20.20.02 profile-level permissions|
|20.20.01 (Winter 20)||Enabling new features in 20.20.01||20.20.01 profile-level permissions|
|20.19.02 (Summer 19)||Enabling new features in 20.19.02||20.19.02 profile-level permissions|
|20.19.01 (Winter 19)||Enabling new features in 20.19.01||20.19.01 profile-level permissions|
|20.18.02 (Summer 18)||Enabling new features in 20.18.02||20.18.02 profile-level permissions|
|20.18.01 (Winter 18)||Enabling new features in 20.18.01||20.18.01 profile-level permissions|
|20.17.02 (Summer 17)||Enabling new features in 20.17.02||20.17.02 profile-level permissions|
|20.17.01 (Winter 17)||Enabling new features in 20.17.01||20.17.01 profile-level permissions|
|20.16.01 (Summer 16)||Enabling new features in 20.16.01||20.16.01 profile-level permissions|
|20.15.03 (Summer 15)||Enabling new features in 20.15.03||20.15.03 profile-level permissions|
|20.15.02 (Spring 15)||Enabling new features in 20.15.02||20.15.02 profile-level permissions|
|20.15.01 (Winter 15)||Enabling new features in 20.15.01||20.15.01 profile-level permissions|
|20.14.02||Enabling new features in 20.14.02||20.14.02 profile-level permissions|
|20.14.01||Enabling new features in 20.14.01||20.14.01 profile-level permissions|
|20.13.02||Enabling new features in 20.13.02||20.13.02 profile-level permissions|
|20.13.01||Enabling new features in 20.13.01||20.13.01 profile-level permissions|
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.
Randy reeves Reeves
Randy reeves Reeves
As per the table in this page, it looks as follows.
So, something is not OK here. Either the first column has to be 20.18.01?
or all the other columns need to be aligned with Summer 18 including the version title in the first column.
Please clarify and correct asap to avoid further confusion.
Hi Vijay Kankipati,
I have corrected the information.
Thanks but, the second link is not working, it's going to an "Oops" page.
Even the rich text editor has immediately changed it to "Broken link"
Apologies for the inconvenience, Vijay Kankipati. The link was internal, hence the issue. I have pointed it to the correct location now.
Do let me know in case you face any further issues.