This section describes the minimum post-upgrade procedures that you must perform after your organization is upgraded to the latest version of BMC Remedyforce. Performing these procedures ensures that your existing functionality is not affected. You must perform these procedures in case of both self-upgrade and automatic upgrade.
In addition, you must also grant your users appropriate permissions to the new and updated Visualforce pages, Apex classes, objects, and fields in BMC Remedyforce.
For information about resolving a few issues that you might face after upgrading to the latest version of BMC Remedyforce, see known issues and workarounds.
Note
For the complete list of procedures that you must perform to enable new features that are delivered in each release of BMC Remedyforce, see Enabling new features.
The following table lists the options for updating user permissions to the latest version of BMC Remedyforce. Based on your requirements, select the appropriate option.
Option for updating user permissions | Details |
---|---|
After your organization is upgraded, assign out-of-the-box BMC Remedyforce permission sets to your users. | Assigning permission sets |
Self upgrade your organization to the latest version. During the self upgrade process, you must configure the BMC Remedyforce access levels for profiles in your organization. Select this option if you do not want to assign out-of-the-box BMC Remedyforce permission sets to your users. | Self-upgrading by installing the managed package |
After your organization is upgraded, manually configure the updated profile-level permissions. Select this option if you do not want to assign out-of-the-box BMC Remedyforce permission sets and you do not want to configure the BMC Remedyforce access levels for profiles in your organization during self upgrade. | Configuring profile-level permissions for new features |
The following table lists the minimum post-upgrade procedures that you must perform for each release. If you are upgrading from a few releases prior to the latest release, you must perform the procedures for each interim release. BMC recommends that you first perform the procedures for the release that immediately follows your current release. You can then perform the procedures in each subsequent release until the latest release.
Release | Minimum post-upgrade procedures to be performed |
---|---|
20.17.012(Summer 17) |
For more information, see Minimum post-upgrade procedures for BMC Remedyforce 20.17.02 (Summer 17). |
20.17.01 (Winter 17) |
For more information, see minimum post-upgrade procedures for BMC Remedyforce 20.17.01 (Winter 17). |
20.16.01 (Summer 16) |
For more information, see minimum post-upgrade procedures for BMC Remedyforce 20.16.01 (Summer 16). |
20.15.03 (Summer 15) | None |
20.15.02 (Spring 15) | None Note: After upgrading to version 20.15.02 or later, Remedyforce Administrators might start receiving emails that list impacted records in your organization. For more information, see minimum post-upgrade procedures for BMC Remedyforce 20.15.02 (Spring 15). |
20.15.01 (Winter 15) |
For more information, see minimum post-upgrade procedures for BMC Remedyforce 20.15.01 (Winter 15).
|
20.14.02 | None |
20.14.01 |
For more information, see minimum post-upgrade procedures for BMC Remedyforce 20.14.01. |
20.13.02 |
For more information, see minimum post-upgrade procedures for BMC Remedyforce 20.13.02. |
20.13.01 |
For more information, see minimum post-upgrade procedures for BMC Remedyforce 20.13.01. |
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.
If you are upgrading from version 20.17.01 or earlier, perform the following minimum post-upgrade procedures:
After upgrading to the Summer 17 release, you must manually configure permissions to add attachments while sending emails from the Actions menu or Activity Feed in Remedyforce Console.
The following table lists the permissions that you must assign for Temporary Attachment object:
Profile | Permission |
---|---|
ServiceDesk Change Manager | Read, Edit, Create, Delete |
ServiceDesk Client | Read, Edit, Create |
ServiceDesk Staff | Read, Edit, Create, Delete |
System Administrator | Read, Edit, Create, Delete, View All, Modify All |
After upgrading to the Summer 17 release, you must manually configure permissions to continue using hyperlink formula fields, such as Launch Console, Record#+, Collision, and Reply fields.
This procedure is based on the enhanced profile user interface provided by Salesforce. For more information, see Salesforce Help.
From the Available Visualforce Pages list, select the BMCServiceDesk.ConsoleRedirect
Visualforce page.
To move the selected page to the Enabled Visualforce Pages list, click the right arrow.
For new Salesforce organization in Winter 17, instead of the Attachment object, File object is used for attaching files. You must perform the following steps to continue using the Attachment object for accessing and viewing attachments.
Perform the following steps, only if you are using the Salesforce Lightning Experience and you want to view category parent tree.
If you are upgrading from version 20.16.01 or earlier, perform the following minimum post-upgrade procedures:
This procedure is based on the enhanced profile user interface provided by Salesforce. For more information, see Salesforce Help. From the Available Visualforce Pages list, select the To move the selected page to the Enabled Visualforce Pages list, click the right arrow.BMCServiceDesk.DeepView
Visualforce page.
If you are upgrading from version 20.15.03 or earlier, perform the following minimum post-upgrade procedures:
After upgrading to the Summer 16 release, you must manually enable the display of new fields on some existing forms. By default, users can only view the field labels on the form. The following image shows an example of the Service Outage form on which you must enable the display of new fields. The following table lists the forms on which you must enable the display of new fields after the upgrade: This procedure is based on the enhanced profile user interface provided by Salesforce. For more information, see Salesforce Help. In the Field Permissions section, enable permissions for the new fields in the object that you have selected: Field ServiceDesk ServiceDesk System Existing Form UI Location New fields that must be enabled after the upgrade Service Outage form Remedyforce Administration > Manage Workflows and Other Processes > Service Outage Action form Remedyforce Administration > Configure Application > Actions Service Outage Category form Remedyforce Administration > Configure Application > Categories Suggested Owners & Queue Auto Assignment form Remedyforce Administration > Configure Application > Suggested Owners & Queue Auto Assignment Queue To enable the display of new fields on existing forms
Actions
Categories
Service Outage
Suggested Owner Mappings
Object
Staff
Change Manager
AdministratorActions
Applies to Service Outage Read Edit Edit Categories
Broadcasts Edit Edit Edit Change Requests Edit Edit Edit Problems Edit Edit Edit Releases Edit Edit Edit Tasks Edit Edit Edit Service Outage
Display in Self Service Edit Edit Edit Outage Status Edit Edit Edit Root Cause Edit Edit Edit Suggested Owner Mappings
Assigned Queue Read Read Create, Read, Edit, Delete
After upgrading to the Summer 16 release, an error message is displayed when system administrators, change managers, or staff members click the Filter icon in the Change Schedule window. This procedure is based on the enhanced profile user interface provided by Salesforce. For more information, see Salesforce Help. From the Available Visualforce Pages list, select the To move the selected page to the Enabled Visualforce Pages list, click the right arrow.To enable the search filter in the Change Schedule
BMCServiceDesk.ChangeScheduleFilter
Visualforce page.
No minimum post-upgrade procedures are required for BMC Remedyforce 20.15.02 (Spring 15). However, after upgrading to version 20.15.02 or later, Remedyforce Administrators might start receiving emails that list impacted records in your organization.
Remedyforce administrators are users for whom the Remedyforce Administrator check box is selected. Impacted records are active templates, Service Request Definitions (SRDs), suggested owners, and Service Level Agreements (SLAs) that reference deleted data in other objects. For example, you might have created a template that sets the assigned user to Emma User but since the template was defined, Emma User is no longer with your company.
In BMC Remedyforce 20.15.02, a new Remedyforce Configuration Data Integrity Tool has been added to help Remedyforce administrators identify records that reference deleted data in other objects. The tool uses the Remedyforce Utility Service to run a batch job daily at 12:00 A.M. Greenwich Mean Time (GMT) to identify these impacted records for you. If an impacted record is found, an email with the Remedyforce Configuration Data Integrity report is sent to Remedyforce administrators. For more information, see Verifying configuration data integrity.
Note
After upgrading to version 20.15.02 or later, when you click the Remedyforce Administration tab for the first time, the Remedyforce Utility Service is automatically started and the scan job is run. If impacted records are found, an email with this report is sent to Remedyforce administrators.
If you are upgrading from version 20.14.02 or earlier, perform the following minimum post-upgrade procedures:
System administrators must manually enable users to view the Chat Sessions by Account and Category report and the BMC Remedyforce Chat Dashboard.
From the Salesforce Spring 15 release, Salesforce ended support for HTML Area type components. Because Remedyforce Search is an HTML Area type component, BMC has provided Remedyforce Search Version 2, which is a Visualforce component. If you were using the Remedyforce Search component before upgrading to version 20.15.01, you must enable the new Remedyforce Search Version 2 component. Remedyforce Search Version 2 is displayed on the left side bar component in the application.
To add the Remedyforce Search Version 2 check box to Home page layouts, perform the following actions:
Navigate to Setup > Customize > Home > Home Page Layouts.
On the Home Page Layouts page, click a Home page layout; for example, Remedyforce Home.
On the Home Page Layouts page, click Edit.
On Step 1. Select the components to show page, in the Select Narrow Components to Show section, perform the following actions:
Select the Remedyforce Search Version 2 check box.
Clear the Remedyforce Search check box.
Click Save.
Starting with version 20.15.01, the BMC Remedyforce documentation is available on the docs.bmc.com documentation portal. If you have converted a trial organization to a production organization and then upgraded to BMC Remedyforce version 20.15.01 or later, you might not be able access the updated online documentation from the BMC Remedyforce panel on the left side bar component in the application.
To get the updated link to the latest online documentation, you must select the BMC Remedyforce (Installed Package: BMC Remedyforce) check box on the page layout assigned for your profile.
If you are upgrading from version 20.13.01 or earlier, perform the following procedure to enable staff members to view incident and task details on the Remedyforce Console, Incident Console, and Task Console tabs. This procedure is based on the enhanced profile user interface provided by Salesforce. For more information, see to enable the enhanced profile user interface .
From the Available Visualforce Pages list, select the following Visualforce pages:
BMCServiceDesk.ConsoleIncidentDetail
BMCServiceDesk.ConsoleTaskDetail
To move the selected pages to the Enabled Visualforce Pages list, click the right arrow.
Click Save.
Note
You can also choose to assign the out-of-the-box ServiceDeskStaff permission set to staff members. In this case, you do not have to manually enable access to the BMCServiceDesk.ConsoleIncidentDetail
and BMCServiceDesk.ConsoleTaskDetail
Visualforce page for the profile assigned to your staff members.
If you are upgrading from version 20.13.01 or earlier, perform the following procedure to enable staff members to view records in a few lookup windows. These lookup windows enable staff members to search and link records.
The following are examples of lookup windows that do not display records to staff members:
Primary
Client
attribute displays no records.This procedure is based on the enhanced profile user interface provided by Salesforce. For more information, see to enable the enhanced profile user interface .
From the Available Visualforce Pages list, select the BMCServiceDesk.SearchAndLink
Visualforce page.
To move the selected page to the Enabled Visualforce Pages list, click the right arrow.
Click Save.
Note
You can also choose to assign the out-of-the-box ServiceDeskStaff permission set to staff members. In this case, you do not have to manually enable access to the BMCServiceDesk.SearchAndLink
Visualforce page for the profile assigned to your staff members.
If you are upgrading from version 20.12.02 or earlier, perform the following minimum post-upgrade procedures:
<c:SRMInputDisplay RequestNumber="{!relatedto.BMCServiceDesk__FKRequestDetail__c}" />
<BMCServiceDesk:SRMInputDisplay RequestNumber="{!relatedto.BMCServiceDesk__FKRequestDetail__c}" />
Incident
#(Ref:IN:{!BMCServiceDesk__Incident__c.Name}) has been created and
assigned to {!BMCServiceDesk__Incident__c.OwnerFullName}
subject="Service Request #{!relatedto.Name}
Replace with the following text: subject="Service Request #(Ref:IN:{!relatedto.Name})
Note
All other code on that line should remain untouched. The new line will look like this:
<messaging:emailTemplate
subject="Service Request #(Ref:IN:{!relatedto.Name}) has been created"
recipientType="User" relatedToType="BMCServiceDesk__Incident__c">
The following table lists the issues that you might face after upgrading to the latest version of BMC Remedyforce.
Issue | Description | Workaround |
---|---|---|
77345 | If you are using BMC Remedyforce CMDB 1.0, on the List View Customization tab (Remedyforce Administration > Application Settings > List View Customization), in the Business Service list view, the Class Name field is displayed twice in the Selected Fields list. | To resolve this issue, perform the following steps:
|
77674 | While migrating from Self Service 1.0 to Self Service 2.0, the following error message is displayed:
| To resolve this issue, click OK in the error message box. Self Service 1.0 is successfully migrated to Self Service 2.0. |
77675 | When users click the Submit a Ticket tile in Self Service 2.0 (Remedyforce Self Service tab), an error message is displayed. | To resolve this issue, perform the following steps:
|
6 Comments
James Lerch
Shubhangi Apte
James Lerch
Shubhangi Apte
Shubhangi Apte
Amit Jaiswal