Configuring profile-level permissions for new features

If you are using Remedyforce profiles or custom permission sets to manage permissions for your users, you might need to manually configure the updated profile-level permissions in a release. The following table lists the conditions in which you must manually configure profile-level permissions after you have self-upgraded or BMC has automatically upgraded your organization. However, if are using Remedyforce permission sets instead, you only need to enable new features after your organization is upgraded.

Upgrade option

Condition

Self-upgrade

You can self-upgrade to the latest version of Remedyforce by manually installing the Remedyforce managed package that is available on Salesforce AppExchange. The option to self-upgrade your organization is available only until the scheduled dates for the automatic upgrade by BMC.

You do not want to assign out-of-the-box Remedyforce permission sets and you did not configure the Remedyforce access levels for profiles in your organization (Step 2. Choose Security Level in the Package Installer wizard).

Automatic upgrade

BMC automatically upgrades all sandbox and production organizations on predefined dates. This automatic upgrade process is similar to how Salesforce pushes platform updates to your organization. For information about the dates on which BMC automatically upgrades sandbox and production organizations, see Release-schedules.

You do not want to assign out-of-the-box Remedyforce permission sets to your users.

If you are upgrading from a few releases prior to the latest release, you must configure the updated profile-level permissions in each interim release. BMC recommends that you first update profile-level permissions in the release that immediately follows your current release. You can then update the profile-level permissions in each subsequent release until the latest release. For example, if you are upgrading from version 20.14.02 to 20.15.02 (Spring 15), you must first configure the updated profile-level permissions in versions 20.15.01 (Winter 15) and then update profile-level permissions in 20.15.02.

Important

If you are using profiles instead of permission sets to manage permissions for users, BMC strongly recommends that you start using Remedyforce permission sets. You can assign multiple permission sets to your users to control the accessibility of Remedyforce.

You are required to assign the permission sets to your users only once. The next time a major release is automatically pushed to your organization, these permission sets are automatically updated. Moving to permissions sets ensures that the automatic upgrade process is simplified and requires minimal manual post-upgrade configuration.

To enable the enhanced profile user interface

The Salesforce enhanced profile user interface enables you to apply all changes to a profile from a single page. For more information about the enhanced profile user interface, see the Salesforce Help.

  1. Navigate to Setup > Customize > User Interface.
  2. In the Setup section, select the Enable Enhanced Profile User Interface check box.
    Salesforce_EnhancedProfileUI.gif
  3. Click Save.

To configure permissions for profiles after upgrade

This procedure is based on the enhanced profile user interface provided by Salesforce. For more information, see To enable the enhanced profile user interface.

  1. Navigate to Setup > Manage Users > Profiles.
  2. Click a profile for which you want to configure permissions, such as ServiceDesk Staff.
  3. On the Profile Overview page, perform the following actions to configure permissions for new Visualforce pages:
    1. In the Apps section, click Visualforce Page Access.
      VF_Pages.gif
    2. In the Visualforce Page Access section, click Edit.

    3. From the Available Visualforce Pages list, select the Visualforce pages that are required for the selected profile. 
      The following topics list new Visualforce pages, Apex classes, objects, and fields added in each release. If you are upgrading from a few releases prior to the latest release, you must configure the updated profile-level permissions for each interim release. If a Visualforce page or Apex class is already available, proceed to the next page or class listed in the table.

    4. To move the selected pages to the Enabled Visualforce Pages list, click the right arrow.
    5. Click Save.
  4. In the Visualforce Page Access section, click Profile Overview.
  5. On the Profile Overview page, perform the following actions to configure permissions for new Apex classes:
    1. In the Apps section, click Apex Class Access.
      APEXClasses.gif
    2. In the Apex Class Access section, click Edit.
    3. From the Available Apex Classes list, select the Apex classes that are required for the selected profile.
    4. To move the selected classes to the Enabled Apex Classes list, click the right arrow.
    5. Click Save.
  6. In the Apex Class Access section, click Profile Overview.

  7. On the Profile Overview page, perform the following actions to configure permissions for new objects and fields in 20.15.02:

    1. In the Apps section, click Object Settings.
      Objects.gif
    2. In the All Objects Settings section, click an existing object that has new fields in 20.15.02.
    3. Click Edit.
    4. (Only if the selected object is new in 20.15.02) In the Object Permissions section, enable the appropriate permissions for the selected profile.
    5. In the Field Permissions section, enable the appropriate permissions for new fields in the selected object.
    6. Click Save.
    7. Click Object Settings.
    8. Repeat step 5b to step 5g for all updated objects in 20.15.02.
  8. Repeat step 2 to step 5 for the following profiles:
    • ServiceDesk Client
    • ServiceDesk Change Manager
    • System Administrator
    • Profiles for which you configured the ServiceDesk Change Manager, ServiceDesk Client, and ServiceDesk Staff levels of access when you installed the managed package.

Related topic

Post-upgrade-procedures-repository

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*