Engage Managed Package Details

The Engage Managed Package allows management of calls, engagement, and interactions for use in Pitcher’s Applications.

This document describes the contents and configuration of the latest Pitcher’s Engage Managed Package.

Package Components

A Package Component is a basic building block of development. Check this Salesforce Package-able Components Documentation for different supported components which can be packaged.

• Package Installation page during installation.

• Installed Packages section after a successful installation.

Custom Objects

Pitcher’s Engage Managed Package installs the following custom objects listed below: 

• Engagement

• Tactic

Engagement Object

The Engagement (PCH__Engagement__c) object stores the configuration of the Pitcher’s Call Interaction feature and is used to determine if the users are on or off interaction with the customer.

Tactic Object

The Tactic (PCH__Tactic__c) object refers to a strategy that can be used to determine the way in which e.g. for Consumer Goods a product is promoted or for Life Sciences, the tactic applied to a specific customer profile. It can be defined as an independent entity or a template. The Engagement Managed Package extends this object to the Promotions Managed Package for use.

Custom Fields

The Pitcher Engage Managed Package extends many custom fields to the following standard SFDC objects as listed below:

Activity

Custom Metadata Objects

Pitcher Engage Managed Package installs the following custom metadata objects listed below:

APEX Managed Sharing Settings (Apex_Managed_Sharing_Setting__mdt)

The APEX Managed Sharing Settings (Apex_Managed_Sharing_Setting__mdt) custom metadata is used to determine the configurations for APEX sharing for certain objects. The package provides metadata records that automatically setup the custom objects that are part of this package. Other packages might add metadata records in case they want to make use of the APEX sharing process within this package.

Mobile Sync Limit Object (Mobile_Sync_Limit_Object__mdt)

This metadata is used together with Mobile Sync Limit. See the Mobile Sync Limit section for more information. Here you only define transaction objects to which Mobile Sync Limit records are related.

Mobile Sync Limit (Mobile_Sync_Limit__mdt)

This metadata is used to set limits on specific checkbox fields on transaction objects defined in the Mobile Sync Limit Object. You can set the maximum number of days after which transaction records will have the specified checkbox deselected. You can also set the type of the record to Transactions so the parent object will have only a specific number of newest records with the specified checkbox set to true, the rest will get automatically deselected whenever the maximum specified is exceeded.

Permission Sets

Pitcher’s Engage Managed Package installs the following permission sets that are used to provide users with suitable access to the Pitcher application:

• PITCHER-Missions Operations - This permission set is used to set permissions for administrators for back-end (Salesforce) usage.

• PITCHER-Missions Rep - This permission set is used to set permissions for front-end users.

Operations users are assumed to be managing content for the field team and Reps are the regular users in the field using Pitcher.

Custom Tabs

The Pitcher’s Engage Managed Package installs the Engagement and Tactic custom tabs that appear when you access the Engagements or Tactic app on Salesforce. These tabs are made available to users through the operations permission set as described above. Any custom additional permission sets can also be used to determine the tab's access.

Package Installation

To learn how to install this package and the post-installation steps, see Installing the Engage Managed Package.