Note

 

This documentation supports the 20.18.02 version of Remedyforce.

To view the latest documentation, select the latest version from the Product version menu.

BMC Remedyforce 20.18.02 Upgrading

Configuring profile-level permissions after self-upgrade or automatic upgrade

Before you begin

If you are not upgrading from the previous release, ensure that you apply profile-level permissions for all releases in between.

Upgrade option

If you are using BMC 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 BMC 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 BMC Remedyforce by manually installing the BMC 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 BMC Remedyforce permission sets and you did not configure the BMC 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 BMC Remedyforce permission sets to your users.

Note

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

You have 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 will ensure 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.
  3. Click Save.

To configure profile-level permissions 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.
    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. 
      For the list of new Visualforce pages, see  20.18.02 profile-level permissions .

      Note

      If a Visualforce page is already available, proceed to the next page 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.
    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. 
      For the list of new Apex classes, see  20.18.02 profile-level permissions .

      Note

      If a class is already available, proceed to the next class listed in the table.

    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:
    1. In the Apps section, click Object Settings.
    2. In the All Objects Settings section, click an existing object that has new fields.
      For the list of new objects and fields and the permissions that you must configure for each profile, see  20.18.02 profile-level permissions .
    3. Click Edit.
    4. (Only if the selected object is new) 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 7b to step 7g for all updated objects.
  8. Repeat step 2 to step 7 for the following profiles:
    • ServiceDesk Client
    • ServiceDesk Change Manager
    • System Administrator
    • Profiles for which you have configured the ServiceDesk Change Manager, ServiceDesk Client, and ServiceDesk Staff levels of access when you installed the managed package

Related topics

Self-upgrading by installing the managed package

Verifying the self-upgrade or automatic upgrade of your organization


Was this page helpful? Yes No Submitting... Thank you
Last modified by Sriraksha Deshpande on May 13, 2019
push_upgrade upgrading

Comments

  1. Vijay Kankipati

    In the section profile-level permissions, steps: 3c and 5c, are referring to the previous version. "see 20.18.01 profile-level permissions ."

    Why? Does it mean there are no additional changes for Summer '18?

    Aug 08, 2018 07:07
    1. Punam Saxena

      Hi Vijay Kankipati,


      The links were incorrectly pointing to the previous version. Have corrected them now.

      Regards,

      Punam

      Sep 06, 2018 04:04
Remedyforce Salesforce standard object schema changes
20.18.02 profile-level permissions
© Copyright 2010 - 2018 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport