Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 21 Next »

Introduction

Sometimes the business requirement is to have different Pulsar behaviour for different roles/groups of users. As an example, we need to show different default values for the same fields for the same objects based on different roles/groups.

In Order to Achieve this functionality, we need to set up Sharing settings for the PulsarSetting object for the Org. The path for the same is as follows:

Setup >> Security Controls >> Sharing Settings >> Manage Sharing Settings for "PulsarSetting"


Priority Value on PulsarSetting

We need to add Priority Value on Every Pulsar Settings based on the business requirement.

  • Add Priority = 100 for all Pulsar Settings used by all Roles/Groups
  • Add Priority = 101 for Pulsar Settings specific Roles/Groups
  • Add Priority = 102 for Pulsar Settings specific Roles/Groups

You can create a separate set of Pulsar Settings as per the requirements and then use Sharing Settings to implement role-based access.


Setup

Below are the steps for Setting Up Sharing Settings for Pulsar

  • "Edit", Organization-Wide Defaults
    • Update Default Internal Access to "Private"
    • Update Default External Access to "Private"
    • "Select", Grant Access using Hierarchies

  • Create New PulsarSettings Sharing Rules using PulsarSetting Priority Values
    • Provide the Rule Name
    • Select "Based On Criteria"
    • Update Filter Logic Based on Business Requirements
    • Assign the Rule to Specific Roles/Groups
    • Keep the access Level as "Read Only"

For some Profiles like System Administrator, we have View All Permissions for the PulsarSettings Object. Sharing Settings will not work for users with these Profiles.

Example

  • No labels