Conga Managed Package Details

Pitcher Conga is a mobile app built on the headless Conga CPQ backend. All master data used in the front end is part of the Conga product. This package focuses on creating staging objects in Salesforce for orders submitted from mobile devices running Pitcher. The Pitcher creates orders based on the staging records by calling the Conga APIs. 

This document describes the contents of the Pitcher Conga Managed Package. Newer versions may have additions, changes, and improvements to the currently listed components. For the complete list of components, please check the "Components List" on the Salesforce Installed Packages section after a successful installation or before installing on the Package Installation screen.

This document describes the contents and configuration of the latest Pitcher Conga 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 Order

• Pitcher Order Line Item

Pitcher Order

Pitcher Conga Managed Package installs below custom fields on Pitcher Order Object. One of these fields is an external ID, and it is used to uniquely identify Pitcher Orders if they are created through the Pitcher application and keep track of their status of sync.

Pitcher Order is used for storing the JSON payloads for Conga Order creation. The Pitcher Order object is the main Object which stores the payload and all the status of the processes which are going on with the Conga Order, from Order creation to Order Acceptance.

Pitcher Order Line Item

Pitcher Order Line Item is used for storing the JSON payload for Conga Line Item creation and the pricing which is coming from Pitcher and the Pricing which Conga Reprice API calculates. Pitcher Conga Managed Package installs below custom fields on Pitcher Order Line Item Object -

Custom Metadata Objects

Pitcher Conga App Settings Metadata Object

Pitcher Conga App Settings metadata is used to give a few functionalities to control in the existing classes for the performance and the unique identification of records for Conga Line Items and bypassing any validation rules on Conga Order object.

Pitcher Conga Managed Package installs nine custom fields on Pitcher Conga App Settings Metadata, as listed in the screenshot below.

Custom Tabs

Pitcher Conga Managed Package installs one custom tab, which is available through the permission set mentioned earlier and can be assigned with additional custom permission sets if required. 

• Pitcher Orders

End-users use pitcher Orders to look into the orders synced from the Pitcher application. 

Apex Classes

Pitcher Conga Managed Package installs 11 Apex Classes listed on the screenshot below. These are used for proper application functionality on Pitcher platform general application usage.

Workflows

Pitcher Conga Managed Package installs one workflow rule, which is mentioned below:

Email Templates

Pitcher Conga Managed Package installs one email template, which is mentioned below:

Permission Sets

Pitcher Conga Managed Package installs two permission sets listed in the screenshot below. These are used for proper access to Pitcher application usage. PITCHER-Conga Rep is targeted at all users that work with Pitcher in the field.

• PITCHER-Conga Admin - This permission set is used to Grant admin access to all Pitcher Conga objects.

• PITCHER-Conga Rep - This permission set is used to Grant write access to Pitcher Conga objects to create new Orders and Order Line Items.

Package Installation

To learn how to install this package, pre & post-installation steps, seeInstalling the Conga Managed Package.

References

• Write Back Technical Document

• Postman Collection

• Sample Request JSON