Missions Managed Package Details

Missions are how the Pitcher presents a group of tasks to users that they are asked to perform. A mission gets completed when a user can work through all its required elements. The result is an assessment of the moment in time when the Pitcher captures Execution records either related to Accounts or Users.

This document describes the contents and configuration of the latest Pitcher Missions Managed Package.

Package Components

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

Custom Objects

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

Mission Object

The Mission (PCH__Mission__c) object is a template that contains assorted content specific to the requirements that need to be fulfilled by a user - for example, a group of tasks or an action plan. A Mission object can contain static content and act as a dynamic container for content defined using the Mission Item object.

Fields and Relationship

Field Label	Field Name	Data Type
Mission Name	`Name`	Text(80)
Created By	`CreatedById`	Lookup(User)
Last Modified By	`LastModifiedById`	Lookup(User)
Owner	`OwnerId`	Lookup(User,Group)
Record Type	`RecordTypeId`	Record Type
Account	`PCH__Account__c`	Lookup(Account)
Allocation	`PCH__Allocation__c`	Picklist
Allocation Logic	`PCH__Allocation_Logic__c`	Picklist
Description	`PCH__Description__c`	Text(255)
End	`PCH__End__c`	Date
Execution Date Next	`PCH__Execution_Date_Next__c`	Date
External Id	`PCH__External_Id__c`	Text(255) (External Id)
Label	`PCH__Label__c`	Text(255)
Language	`PCH__Language__c`	Picklist
Mission (Template)	`PCH__Mission_Template__c`	Lookup(Mission)
Mission Path	`PCH__Mission_Path__c`	Formula (Text)
Mission Path	`PCH__MissionPath__c`	Text(255)
Mission Type	`PCH__Mision_Type__c`	Picklist
Page ID	`PCH__Page_ID__c`	Text(255)
Parent	`PCH__Parent__c`	Lookup(Mission)
Process ID	`PCH__Process_ID__c`	Text(255) (External ID)
Repeat Custom	`PCH__Repeat_Custom__c`	Text(255)
Repeat Every	`PCH__Repeat_Every__c`	Number(18, 0)
Repeat Occurrences	`PCH__Repeat_Occurrences__c`	Number(18, 0)
Repeat Period	`PCH__Repeat_Period__c`	Picklist
Sequence	`PCH__Sequence__c`	Number(18, 0)
Sharing Code	`PCH__Sharing_Code__c`	Text(80)
Skill Mission	`PCH__Skill_Mission__c`	Checkbox
Start	`PCH__Start__c`	Date
TECH_Actions Step Visible	`TECH_Actions_Step_Visible__c`	Formula(Checkbox)
TECH_Allocation Step Visible	`TECH_Allocation_Step_Visible__c`	Formula(Checkbox)
Technical Status	`PCH__Technical_Status__c`	Picklist
Template	`PCH__Template__c`	Checkbox
Type	`PCH__Type__c`	Lookup(Tag)
Unique ID	`PCH__Unique_ID__c`	Text(255) (External ID) (Unique Case Sensitive)
User	`PCH__User__c`	Lookup(User)
Visibility	`PCH__Visibility__c`	Long Text Area(4000)

Resources

Component Name	Component Type
All	List View
User Mission	Record Type
Mission	Record Type
Mission Layout	Page Layout
Account Mission	Record Type
App	Record Type
Mission Builder Layout	Page Layout
Start_Date_Check	Validation Rule
Deep Clone	Custom Link within Salesforce
Mission (Templates)	List View

Mission Item Object

The Mission Item (PCH__Mission_Item__c) object has a master-detail relationship with Mission. It defines the actual content of a Mission.

Fields and Relationship

Field Label	Field Name	Data Type
Mission Item Name	`Name`	Text(80)
Created By	`CreatedById`	Lookup(User)
Last Modified By	`LastModifiedById`	Lookup(User)
Owner	`OwnerId`	Lookup(User,Group)
Active	`PCH__Active__c`	Checkbox
Component ID	`PCH__Component_ID__c`	Text(255)
File Keyword	`PCH__File_Keyword__c`	Text(255)
Label	`PCH__Label__c`	Text(255)
Mission	`PCH__Mission__c`	Master-Detail(Mission)
Parent	`PCH__Parent__c`	Lookup(Mission Item)
Parent Mission	`PCH__Parent_Mission__c`	Lookup(Mission)
Record Type	`RecordTypeId`	Record Type
Required	`PCH__Required__c`	Checkbox
Sequence	`PCH__Sequence__c`	Number(18, 0)

Resources

Component Name	Component Type
Item	Record Type
Mission Item Layout	Page Layout
Section	Record Type

Account Execution Object

The Account Execution (PCH__Account_Execution__c) object stores the results of account executions done by the user while assigning missions to accounts.

Fields and Relationship

Field Label	Field Name	Data Type
Execution ID	`Name`	Auto Number
Created By	`CreatedById`	Lookup(User)
Last Modified By	`LastModifiedById`	Lookup(User)
Owner	`OwnerId`	Lookup(User,Group)
Account	`PCH__Account__c`	Lookup(Account)
End (Actual)	`PCH__End_Actual__c`	Date/Time
Execution Date (Actual)	`PCH__Execution_Date_Actual__c`	Date/Time
Execution Date (Planned)	`PCH__Execution_Date_Planned__c`	Date
External ID	`PCH__External_ID__c`	Text(255) (External ID) (Unique Case Sensitive)
Mission	`PCH__Mission__c`	Lookup(Mission)
Mission (Account)	`PCH__Mission_Account__c`	Lookup(Mission)
Parent	`PCH__Parent__c`	Lookup(Account Execution)
Start (Actual)	`PCH__Start_Actual__c`	Date/Time
Status	`PCH__Status__c`	Picklist
Technical Status	`PCH__Technical_Status__c`	Picklist
Unique ID	`PCH__Unique_ID__c`	Text(255) (External ID) (Unique Case Sensitive)
Visit	`PCH__Visit__c`	Lookup(Engagement)
Visit (PP)	`PCH__Visit_PP__c`	Lookup(Pitcher Presentation)
Visit ID	`PCH__Visitid__c`	Text(255) (External ID) (Unique Case Sensitive)

Resources

Component Name	Component Type
Account Execution Layout	Page Layout
All	List View

Account Execution Item Object

The Account Execution Item (PCH__Account_Execution_Item__c) object has a master-detail relationship with the Account Execution object. It stores the actual content of the completed account execution.

Fields and Relationship

Field Label	Field Name	Data Type
Execution Item ID	`Name`	Auto Number
Created By	`CreatedById`	Lookup(User)
Last Modified By	`LastModifiedById`	Lookup(User)
Owner	`OwnerId`	Lookup(User,Group)
Brand (Product)	`PCH__Brand_Product__c`	Text(255)
Category (Product)	`PCH__Category_Product__c`	Text(255)
Comment	`PCH__Comment__c`	Long Text Area(4000)
Compliance	`PCH__Compliance__c`	Checkbox
Execution	`PCH__Execution__c`	Master-Detail(Account Execution)
Execution Date (Actual)	`PCH__Execution_Date_Actual__c`	Formula (Date/Time)
Execution Date (Planned)	`PCH__Execution_Date_Planned__c`	Formula (Date)
External ID	`PCH__External_ID__c`	Text(255) (External ID) (Unique Case Sensitive)
Facings	`PCH__Facings__c`	Number(18, 0)
Label	`PCH__Label__c`	Text(255)
Mission	`PCH__Mission__c`	Lookup(Mission)
Mission Item	`PCH__Mission_Item__c`	Lookup(Mission Item)
Mission Item ID	`PCH__Mission_Item_ID__c`	Text(255)
Product	`PCH__Product__c`	Lookup(Product)
Promotion	`PCH__Promotion__c`	Lookup(Promotion)
Response (Long Text)	`PCH__Response_Long_Text__c`	Long Text Area(40000)
Response (Number)	`PCH__Response_Number__c`	Number(15, 3)
Response (Text)	`PCH__Response_Text__c`	Text(255)
Row ID	`PCH__Row_ID__c`	Text(255)
Stock	`PCH__Stock__c`	Number(18, 0)
Technical Status	`PCH__Technical_Status__c`	Picklist

Resources

Component Name	Component Type
Account Execution Item Layout	Page Layout

User Execution Object

The User Execution (PCH__User_Execution__c) object stores the results of executions done by users while submitting missions.

Fields and Relationship

Field Label	Field Name	Data Type
Execution ID	`Name`	Auto Number
Created By	`CreatedById`	Lookup(User)
Last Modified By	`LastModifiedById`	Lookup(User)
Owner	`OwnerId`	Lookup(User,Group)
Comments	`PCH__Comments__c`	Long Text Area(32768)
End	`PCH__End__c`	Date/Time
End (Actual)	`PCH__End_Actual__c`	Date
End (Planned)	`PCH__End_Planned__c`	Date
Execution Author	`PCH__Execution_Author__c`	Lookup(User)
Execution Date	`PCH__Execution_Date__c`	Date/Time
Execution Date (Actual)	`PCH__Execution_Date_Actual__c`	Date/Time
Execution Date (Planned)	`PCH__Execution_Date_Planned__c`	Date
External ID	`PCH__External_ID__c`	Text(255) (External ID) (Unique Case Sensitive)
Last Execution	`PCH__Last_Execution__c`	Checkbox
Manager Execution	`PCH__Manager_Execution__c`	Checkbox
Mission	`PCH__Mission__c`	Lookup(Mission)
Parent	`PCH__Parent__c`	Lookup(User Execution)
Score	`PCH__Score__c`	Number(15,3)
Skill Execution	`PCH__Skill_Execution__c`	Checkbox
Start	`PCH__Start__c`	Date/Time
Start (Actual)	`PCH__Start_Actual__c`	Date
Start (Planned)	`PCH__Start_Planned__c`	Date
Status	`PCH__Status__c`	Picklist
Technical Status	`PCH__Technical_Status__c`	Picklist
User	`PCH__User__c`	Lookup(User)
Visit	`PCH__Visit_PP__c`	Lookup(Pitcher Presentation)

Resources

Component Name	Component Type
User Execution Layout	Page Layout

User Execution Item Object

The User Execution Item (PCH__User_Execution_Item__c) object has a master-detail relationship with the User Execution object. It stores the actual content of the completed user execution.

Fields and Relationship

Field Label	Field Name	Data Type
Execution ID	`Name`	Auto Number
Created By	`CreatedById`	Lookup(User)
Last Modified By	`LastModifiedById`	Lookup(User)
Owner	`OwnerId`	Lookup(User,Group)
Account	`Account__c`	Lookup(Account)
Comments	`PCH__Comments__c`	Long Text Area(32768)
Execution	`PCH__Execution__c`	Master-Detail(User Execution)
External ID	`PCH__External_ID__c`	Text(255) (External ID) (Unique Case Sensitive)
Label	`PCH__Label__c`	Text(255)
Mission Item (Deprecated)	`PCH__Mission_Item__c`	Lookup(Mission Item)
Mission Item ID	`PCH__Mission_Item_ID__c`	Text(255)
Response (Long Text)	`PCH__Response_Long_Text__c`	Long Text Area(40000)
Response (Number)	`PCH__Response_Number__c`	Number(15, 3)
Response (Text)	`PCH__Response_Text__c`	Text(255)
Score	`PCH__Score__c`	Number(15, 3)
Value (Max)	`PCH__Value_Max__c`	Number(15, 3)

Contract Execution Object

The User Execution (PCH__Contract_Execution__c) object stores the results of contract executions

Fields and Relationship

Field Label	Field Name	Data Type
Account	PCH__Account__c	Lookup(Account)
Comments	PCH__Comments__c	Long Text(32768)
Commercial Encoding	PCH__Commercial_Encoding__c	Picklist
Contact	PCH__Contact__c	Lookup(Contact)
Contract Template	PCH__Contract_Template__c	Lookup(Mission)
Email	PCH__Email__c	Email
End Date	PCH__End_Date__c	Date
Parent Contract	PCH__Parent_Contract__c	Lookup(Contract Execution)
Pitcher Presentation	PCH__Pitcher_Presentation__c	Lookup(Pitcher Presentation)
Signature Date	PCH__Signature_Date__c	Date
Signed By	PCH__Signed_By__c	Text(255)
Start Date	PCH__Start_Date__c	Date
Status	PCH__Status__c	Picklist

Resources

Component Name	Component Type
Contract Execution Layout	Page Layout

Contract Execution Item Object

The User Execution Item (PCH__Contract_Execution_Item__c) object has a master-detail relationship with the Contract Execution object. It stores the actual content of the completed contract execution.

Fields and Relationship

Field Label	Field Name	Data Type
Comments	PCH__Comments__c	Long Text(32768)
Contract Execution	PCH__Contract_Execution__c	Master-Detail
Label	PCH__Label___c	Text(255)
Response Long	PCH__Response_Long__c	Long Text(32768)
Response Number	PCH__Response_Number__c	Number(15,3)
Response Text	PCH__Response_Text__c	Text(255)

Resources

Component Name	Component Type
Contract Execution Item Layout	Page Layout

Custom Fields & Resources

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

Activity

There are below fields and resources which has been extended to this package -

Fields and Relationship

Field Label	Field Name	Data Type
Account Execution	`PCH__Account_Execution__c`	Lookup(Account_Execution__c)
Mission	`PCH__Mission__c`	Lookup(Mission__c)
Mission Item ID	`PCH__Mission_Item_ID__c`	Text(255)
User Execution	`PCH__User_Execution__c`	Lookup(User_Execution__c)

Allocation

There are below fields and resources which has been extended to this package -

Fields and Relationship

Field Label	Field Name	Data Type
Mission (Template)	`PCH__Mission_Template__c`	Lookup(`Mission__c`)

Resources

Component Name	Component Type
`Mission_Allocation`	Record Type

Engagement

There are below fields and resources which has been extended to this package -

Fields and Relationship

Field Label	Field Name	Data Type
Missions (Actual)	`PCH__Missions_Actual__c`	Number(18,0)
Missions (Planned)	`PCH__Missions_Planned__c`	Number(18,0)

Instance Sharing

There are below fields and resources which has been extended to this package -

Fields and Relationship

Field Label	Field Name	Data Type
Mission	`PCH__Mission__c`	Lookup(Mission__c)

Big Objects

Execution (Execution__b)

This big object is created for mapping Account Execution (PCH__Account_Execution__c) object.

Fields and Relationships

Field Label	Field Name	Data Type
Account	`PCH__Account__c`	Text(18)
Created By Id	`PCH__Created_By_Id__c`	Text(18)
Created Date	`PCH__Created_Date__c`	Date/Time
Execution	`PCH__Execution__c`	Text(18)
Execution Date (Actual)	`PCH__Execution_Date__c`	Date/Time
Execution Date (Planned)	`PCH__Execution_Date_Planned__c`	Date/Time
Execution Name	`PCH__Execution_Name__c`	Text(255)
External ID	`PCH__External_ID__c`	Text(255)
Is Deleted?	`PCH__Is_Deleted__c`	Text(3)
Last Modified By ID	`PCH__Last_Modified_By_Id__c`	Text(18)
Last Modified Date	`PCH__Last_Modified_Date__c`	Date/Time
Mission	`PCH__Mission__c`	Text(18)

Execution Item (Execution_Item3__b)

This big object is created for mapping Account Execution Item (PCH__Account_Execution_Item__c) object.

Fields and Relationship

Field Label	Field Name	Data Type
Brand (Product)	`PCH__Brand_Product__c`	Text(255)
Category (Product)	`PCH__Category_Product__c`	Text(255)
Compliance	`PCH__Compliance__c`	Text(255)
Created By ID	`PCH__Created_By_Id__c`	Text(18)
Created Date	`PCH__Created_Date__c`	Date/Time
Execution	`PCH__Execution__c`	Text(18)
Execution Item	`PCH__Execution_Item__c`	Text(18)
Execution Item Name	`PCH__Execution_Item_Name__c`	Text(255)
Facings	`PCH__Facings__c`	Number(18, 0)
IsDeleted?	`PCH__IsDeleted__c`	Text(3)
Last Modified By ID	`PCH__Last_Modified_By_Id__c`	Text(18)
Last Modified Date	`PCH__Last_Modified_Date__c`	Date/Time
Mission	`PCH__Mission__c`	Text(18)
Mission Item	`PCH__Mission_Item__c`	Text(18)
Product	`PCH__Product__c`	Text(255)
Promotion	`PCH__Promotion__c`	Text(255)
Stock	`PCH__Stock__c`	Number(18, 0)

Custom User Interface

CanvasAppHolder

This is an Aura Component Bundle that includes the configuration of the Experience Builder and loads it on package installation. This aura component uses logic to open the canvas app URL based on mission allocation.

If it’s User → Custom label Instore_Experience_Keyword is used to populate canvas URL
If it’s Account → Custom label Coaching_Experience_Keyword is used to populate canvas URL

Custom Labels

Custom Label helps in translations into various languages.

Name	Description
`Instore_Experience_Keyword`	This has been used in the canvas app Url population
`Coaching_Experience_Keyword`	This has been used in the canvas app Url population

Custom Metadata

Pitcher Missions Managed Package installs the following custom metadata components listed below:

Lightning Builder (Lightning_Builder__mdt)

This custom metadata helps in setting up Lightning builder-related setup. This is the parent metadata record for Lightning_Builder_Type__mdt

Fields and Relationships

Fields and Relationships are part of Pitcher Apps.

Managed Metadata Records

Name	Field Values
`Mission Builder`	Active = true Lightning Builder Type = Mission Record Type = <blank> View = Full Screen

Lightning Builder Type (Lightning_Builder_Type__mdt)

This custom metadata helps in setting up Lightning builder-related setup. This is the parent metadata record for Lightning_Builder_Item__mdt

Fields and Relationships

Fields and Relationships are part of Pitcher Apps.

Managed Metadata Records

Name	Field Values
`PCH__Mission__c`	None

Lightning Builder Item (Lightning_Builder_Item__mdt)

This custom metadata helps in setting up Lightning builder-related setup. This is the parent metadata record for Lightning_Builder_Table_Item__mdt

Fields and Relationships

Fields and Relationships are part of Pitcher Apps.

Managed Metadata Records

<blank>	Field Values
`Mission Actions`	Active = true Canvas App Developer Name = <blank> Canvas App Parameters = <blank> Controller Class = EXT_MissionBuilderActions Destination (Mapping Field) = <blank> Destination (Object) = <blank> Lightning Builder = Mission_Builder Page Layout (Name) = <blank> Sequence = 90.0 Show Clone Action = true Show Delete Action = false Source (Object) = <blank> Title = Mission Actions Type = Actions
`Mission Allocation`	Active = true Canvas App Developer Name = <blank> Canvas App Parameters = <blank> Controller Class = <blank> Destination (Mapping Field) = <blank> Destination (Object) = <blank> Lightning Builder = Mission_Builder Page Layout (Name) = <blank> Sequence = 40.0 Show Clone Action = <blank> Show Delete Action = <blank> Source (Object) = <blank> Title = Mission Allocation Type = Allocation
`Mission Canvas`	Active = true Canvas App Developer Name = pitcheratlas Canvas App Parameters = <blank> Controller Class = <blank> Destination (Mapping Field) = <blank> Destination (Object) = <blank> Lightning Builder = Mission_Builder Page Layout (Name) = <blank> Sequence = 15.0 Show Clone Action = false Show Delete Action = false Source (Object) = <blank> Title = Mission Canvas Type = Canvas
`Mission Details`	Active = true Canvas App Developer Name = <blank> Canvas App Parameters = <blank> Controller Class = <blank> Destination (Mapping Field) = <blank> Destination (Object) = <blank> Lightning Builder = Mission_Builder Page Layout (Name) = PCH__Mission Builder Layout Sequence = 10.0 Show Clone Action = <blank> Show Delete Action = <blank> Source (Object) = <blank> Title = Mission Details Type = Details

Lightning Builder Table Item (Lightning_Builder_Table_Item__mdt)

This custom metadata helps in setting up Lightning builder-related setup. This is the parent metadata record for Lightning_Builder_Allocation_Item__mdt

Fields and Relationships

Fields and Relationships are part of Pitcher Apps.

Managed Metadata Records

<blank>	Field Values
`Mission Detail Tech Status Autofill`	API Name (Source) = <blank> API Name (Destination) = PCH__Technical_Status__c Active = true Data Type = text Display = false Filter = false Label Field = Template Lightning Builder Item = Mission_Details Permission = Read / Write Search = false Sequence = 20.0 Value = Draft
`Mission Detail Template Autofill`	API Name (Source) = <blank> API Name (Destination) = PCH__Template__c Active = true Data Type = boolean Display = false Filter = false Label Field = Template Lightning Builder Item = Mission_Details Permission = Read / Write Search = false Sequence = 10.0 Value = true

Lightning Builder Allocation Item (Lightning_Builder_Allocation_Item__mdt)

This custom metadata helps in setting up Lightning builder-related setup. This is the basic setup item for lightning builder.

Fields and Relationships

Fields and Relationships are part of Pitcher Apps.

Managed Metadata Records

Name	Field Values
`Mission Account Hierarchy`	Active = true Lightning Builder Item = Mission_Allocation Sequence = 20.0 Tab = Account Type = Hierarchy
`Mission Account Single`	Active = true Lightning Builder Item = Mission_Allocation Sequence = 10.0 Tab = Account Type = Single
`Mission Segment Attribute (Account)`	Active = true Lightning Builder Item = Mission_Allocation Sequence = 50.0 Tab = Segment Type = Attribute (Account)
`Mission Segment Attribute (User)`	Active = true Lightning Builder Item = Mission_Allocation Sequence = 60.0 Tab = Segment Type = Attribute (User)
`Mission Segment Tag`	Active = true Lightning Builder Item = Mission_Allocation Sequence = 70.0 Tab = Segment Type = Tag
`Mission User Hierarchy`	Active = true Lightning Builder Item = Mission_Allocation Sequence = 40.0 Tab = User Type = Hierarchy
`Mission User Single`	Active = true Lightning Builder Item = Mission_Allocation Sequence = 30.0 Tab = User Type = Single

Apex Managed Sharing Setting (Apex_Managed_Sharing_Setting__mdt)

The APEX Managed Sharing Settings custom metadata is used to determine the configurations for APEX sharing for particular objects. For more information, see https://pitcher-docs.atlassian.net/wiki/pages/createpage.action?spaceKey=APPS&title=Salesforce%20Apex%20Sharing

Pitcher’s Missions Managed Package installs the following APEX Managed Sharing Settings records to make use of the APEX sharing process within this package:

Fields and Relationships

Fields and Relationships are part of Pitcher Apps.

Managed Metadata Records

Name	Field Values
`Account_Execution`	Active = true Object - PCH__Account_Execution__c Sharing Lookup (Field) - PCH__Account__c Delta Sync: Last Modified = YESTERDAY Full Sync: Date Filter = CreatedDate Full Sync: Date Filter (Period) = LAST_30_MINS Condition (Where Clause) = <Blank> Batch Size = <Blank> Access Level = <Blank>
`Mission`	Active = true Object - PCH__Mission__c Sharing Lookup (Field) - PCH__Account__c Delta Sync: Last Modified = YESTERDAY Full Sync: Date Filter = CreatedDate Full Sync: Date Filter (Period) = LAST_30_MINS Condition (Where Clause) = <Blank> Batch Size = <Blank> Access Level = <Blank>

Object Mapping (Obj_Mapping__mdt)

This Metadata Type helps in configuring source and destination objects for mapping.
Here are below fields it has -

Fields and Relationships

Fields and Relationships are part of Pitcher Apps.

Managed Metadata Records

Name	Field Values
`Account_Execution_to_Execution`	Active = true Object (Source) = PCH__Account_Execution__c Object (Destination) = PCH__Execution2__b Sequence = 1
`Account_Execution_Item_to_Execution_Item`	Active = true Object (Source) = PCH__Account_Execution_Item__c Object (Destination) = PCH__Execution_Item3__b Sequence = 2

Field Mapping (Field_Mapping__mdt)

This Metadata Type helps configure source and destination objects' fields for mapping.
Here are below fields it has -

Fields and Relationships

Fields and Relationships are part of Pitcher Apps.

Managed Metadata Records

Name

Field Values

AE_Account

AE_Created_By_Id

AE_Created_Date

AE_Execution

AE_Execution_Date_Actual

AE_Execution_Date_Planned

AE_Execution_Name

AE_External_Id

AE_IsDeleted

AE_Last_Modified_By_Id

AE_Last_Modified_Date

AE_Mission

AEI_Created_By_Id

AEI_Created_Date

AEI_Execution

AEI_Execution_Item

AEI_IsDeleted

AEI_Last_Modified_By_Id

AEI_Last_Modified_Date

AEI_Name

Trigger Object Settings (Trigger_Object_Settings__mdt)

This metadata Trigger Object Setting is the first step for setting up the Trigger Action Framework for any object

Fields and Relationships

Fields and Relationships are part of Pitcher Apps.

Managed Metadata Records

Name	Field Values
`Account Execution`	Bypass Execution = FALSE Bypass Permission = <Blank> Class Name Flow Input = <Blank> Object = PCH__Account_Execution__c Required Permission = <Blank>
`Mission`	Bypass Execution = FALSE Bypass Permission = <Blank> Class Name Flow Input = <Blank> Object = PCH__Mission__c Required Permission = <Blank>
`User Execution`	Bypass Execution = FALSE Bypass Permission = <Blank> Class Name Flow Input = <Blank> Object = PCH__User_Execution__c Required Permission = <Blank>

Trigger Action (Trigger_Action__mdt)

This custom metadata Trigger Action helps in setting up Trigger Actions for Triggers.

Fields and Relationships

Fields and Relationships are part of Pitcher Apps.

Managed Metadata Records

Name	Field Values
`TA_AccountExecution_defaultStatusToDraft`	After Delete = <Blank> After Insert = <Blank> After Undelete = <Blank> After Update = <Blank> Before Delete = <Blank> Before Insert = Account_Execution Before Update = <Blank> Bypass Execution = FALSE Bypass Permission = <Blank> Class Name = TA_AccountExecution_defaultStatusToDraft Description = Default Status To Draft Flow Name = <Blank> Flow Recursion = FALSE Required Permission = <Blank> Sequence = 10.0
`TA_AccountExecution_deleteVisit`	After Delete = Account_Execution After Insert = <Blank> After Undelete = <Blank> After Update = <Blank> Before Delete = <Blank> Before Insert = <Blank> Before Update = <Blank> Bypass Execution = FALSE Bypass Permission = <Blank> Class Name = TA_AccountExecution_deleteVisit Description = Delete Visit Flow Name = <Blank> Flow Recursion = FALSE Required Permission = <Blank> Sequence = 10.0
`TA_AccountExecution_updateActual`	After Delete = <Blank> After Insert = Account_Execution After Undelete = <Blank> After Update = <Blank> Before Delete = <Blank> Before Insert = <Blank> Before Update = <Blank> Bypass Execution = FALSE Bypass Permission = <Blank> Class Name = TA_AccountExecution_updateActual Description = Update Visit Start Actual Flow Name = <Blank> Flow Recursion = FALSE Required Permission = <Blank> Sequence = 20.0
`TA_AccountExecution_updateActual_upd`	After Delete = <Blank> After Insert = <Blank> After Undelete = <Blank> After Update = Account_Execution Before Delete = <Blank> Before Insert = <Blank> Before Update = <Blank> Bypass Execution = FALSE Bypass Permission = <Blank> Class Name = TA_AccountExecution_updateActual Description = Update Visit Start Actual Flow Name = <Blank> Flow Recursion = FALSE Required Permission = <Blank> Sequence = 10.0
`TA_AccountExecution_upsertVisit`	After Delete = <Blank> After Insert = Account_Execution After Undelete = <Blank> After Update = <Blank> Before Delete = <Blank> Before Insert = <Blank> Before Update = <Blank> Bypass Execution = FALSE Bypass Permission = <Blank> Class Name = TA_AccountExecution_upsertVisit Description = Upsert Visit Flow Name = <Blank> Flow Recursion = FALSE Required Permission = <Blank> Sequence = 10.0
`TA_Mission_PopulateMissionPath`	After Delete = <Blank> After Insert = <Blank> After Undelete = <Blank> After Update = <Blank> Before Delete = <Blank> Before Insert = Mission Before Update = <Blank> Bypass Execution = FALSE Bypass Permission = <Blank> Class Name = TA_Mission_PopulateMissionPath Description = Populate mission path Flow Name = <Blank> Flow Recursion = FALSE Required Permission = <Blank> Sequence = 10.0
`TA_Mission_deleteExistingExecution`	After Delete = <Blank> After Insert = <Blank> After Undelete = <Blank> After Update = <Blank> Before Delete = <Blank> Before Insert = <Blank> Before Update = Mission Bypass Execution = FALSE Bypass Permission = <Blank> Class Name = TA_Mission_deleteExistingExecution Description = Delete Existing Execution Flow Name = <Blank> Flow Recursion = FALSE Required Permission = <Blank> Sequence = 10.0
`TA_UserExecution_validateRequired`	After Delete = <Blank> After Insert = <Blank> After Undelete = <Blank> After Update = <Blank> Before Delete = <Blank> Before Insert = User_Execution Before Update = <Blank> Bypass Execution = TRUE Bypass Permission = <Blank> Class Name = TA_UserExecution_validateRequired Description = validate required user and Mission(before insert) Flow Name = <Blank> Flow Recursion = FALSE Required Permission = <Blank> Sequence = 10.0
`TA_UserExecution_validateRequired_upd`	After Delete = <Blank> After Insert = <Blank> After Undelete = <Blank> After Update = <Blank> Before Delete = <Blank> Before Insert = <Blank> Before Update = User_Execution Bypass Execution = TRUE Bypass Permission = <Blank> Class Name = TA_UserExecution_validateRequired Description = validate required user and Mission(before the update) Flow Name = <Blank> Flow Recursion = FALSE Required Permission = <Blank> Sequence = 10.0

Custom Settings

Pitcher Mission Settings

The Pitcher Mission Settings (PCH__Pitcher_Mission_Settings__c) component includes custom settings for missions. The package includes the following custom field by default, and subscribers can add as many new settings as they need:

Fields and Relationship

Field Label	Field Name	Data Type
Cloning Endpoint Url	`PCH__Cloning_Endpoint_Url__c`	Text(255)

Managed Apps

Pitcher’s Missions Managed Package installs the Experience Builder app that you can configure for live and test environments. The Experience Builder app provides the surface or platform to design your mission’s layout and content. For more information, see, Configuring the Experience Builder.

Here are the three kinds of Experience Builder apps this package contains:

Developer Name	Label
`PCH__atlas`	Experience Builder Live
`PCH__pitcheratlas`	Experience Builder Test
`PCH__atlasprod`	Experience Builder PROD

Custom Tabs

The Pitcher’s Missions Managed Package installs a Mission, Account Execution, and User Execution custom tabs made available to users through the operations permission set described above. Any custom additional permission sets can also be used to determine the tab’s access.

Apex Classes

Pitcher’s Apps Package installs the following Apex Classes that are used for the proper functioning and execution of the missions:

SCH_CallCreateExecutionTagBatch
UserExecutionTriggerHandler
CTL_QueryResultsEndpointControllerTest
CTL_CanvasAppLifeCycleHandlerTest
InsertExecutionHelper
DAT_MissionFactory_TST
SYS_ExperienceBuilderUtilsTest
AccountExecutionTriggerHandler
SCH_ExecutionProcessingBatchScheduler
SYS_CalloutUtils
MissionTriggerTest
CTL_CanvasAppLifeCycleHandler
SCH_MissionAllocationBatchScheduler_TST
EXT_MissionBuilderActionsTest

UpsertVisitOnCreateExecution
CTL_ExecutionScheduler
UserExecutionTriggerTest
BAT_ExecutionCreationBatchProcessV2
RecursiveTriggerHandler
SCH_CallCreateExecutionBatch
EXT_MissionBuilderActions
EXT_MissionBuilder_CTL
SYS_ExperienceBuilderUtils
MissionTriggerHelper
CTL_ExecutionFeed
CTL_ExecutionFeed_TST
SCH_AdjustAccountEngagementVisit_TST
TA_AccountExecution_updateActual

SCH_MissionAllocationBatchScheduler
AccountExecutionTriggerTest
SCH_ExecutionAllocationBatchScheduler
SCH_ExecutionCreationBatchProcessV2
CTL_QueryResultsEndpointController
SCH_AdjustAccountEngagementVisit
TA_Mission_PopulateMissionPath
TA_Mission_deleteExistingExecution
TA_UserExecution_validateRequired
CTL_MissionBuilder
CTL_MissionBuilder_TST
TA_AccountExecution_defaultStatusToDraft
TA_AccountExecution_deleteVisit
TA_AccountExecution_upsertVisit

Apex Triggers

Pitcher APPS Managed Package installs the following Apex Triggers as listed below -

Name	Object	Description
`MissionTrigger`	`PCH__Mission__c`	This includes logic run on trigger event on `PCH__Mission__c` object
`UserExecutionTrigger`	`PCH__User_Execution__c`	This includes logic run on trigger event on `PCH__User_Execution__c` object
`AccountExecutionTrigger`	`PCH__Account_Execution__c`	This includes logic run on trigger event on `PCH__Account_Execution__c` object.

Permission Sets

Pitcher Missions Managed Package installs the following permission sets that are used for proper access on Pitcher application usage:

PITCHER-Missions Operations - This permission set is used to set administrator permissions for the 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.

Package Installation

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