Skip to main content
Conga Support

Salesforce: Configuring Product Pages

What

Product pages allow you to automatically create individual pages within a Conga Collaborate document for each child record on your launching object.

Why

Using product pages, you can design a full page that uses dynamic content associated with a product to create individual pages for product offerings.  Product pages also allow you to access grandchildren records off of your launching object, so you could display the Quote Line Items associated with each Quote on an Opportunity.  Note: If you are using the standard Quote object in Salesforce, use the Quote Pages feature.

How

This is an advanced feature that requires knowledge of auto-generated content as well as a good understanding of how data is structured within Salesforce and interpreted in Conga Collaborate. 

Permissions: Conga Collaborate System Administrator  

This article will use the following example to guide you in setting up product pages:

We have set up an Opportunity hierarchy where we have a parent Opportunity custom object and a related child Opportunity object.  We want to create a document that launches from the parent Opportunity record and contains one page for each child Opportunity record, complete with data from the child Opportunity record and the child’s Opportunity Product data.

Terminology: In this scenario, the parent Opportunity custom object will be the document launching object (where you click the New Document button), and the child Opportunity object will be the data source for the product page (the product page launching object).  Each child Opportunity will contain Opportunity Products, which act as grandchild records of the launching object.  The terms launching object and product page launching object will be used throughout this article, so make sure you understand which is which in your use case.

Mapping Data for Product Pages
Product page variables must be mapped in their own object, otherwise known as the product page launching object, within the Salesforce Integration page.  Follow these steps:  

  1. From your user dropdown in the top right corner, go to Administration > Integrations > Salesforce > Edit
  2. Select your product page launching object in the Incoming Data section.  In our example, this would be the standard Salesforce Opportunity object
  3. Map the fields you want to use that live on that object
  4. Map child-level product page variables to use as auto-generated content.  In our example, these would be fields that are on the Opportunity Products object
  5. Confirm the setup of your product page mapping. In our example, it would be:
    1. Parent Opportunity variables mapped as their own launching object
    2. Child Opportunity variables mapped as their own launching object
    3. Opportunity Product variables mapped as children of the child Opportunity
    4. The Incoming Data section within the Salesforce Integration page looking something like this:




Creating Product Pages
Product pages are created as content pages within your Conga Collaborate Content library.  Follow these steps to build a product page template:
  1. Go to Content
  2. Click +Add New button
  3. Click Page
  4. Add the content for your product page
    1. Add static content - text, images, links, etc.
    2. Add dynamic Salesforce content
      1. Insert product page launching object variables in {{double braces}}.  In our example, these would be fields on the Opportunity object
      2. Insert product page child variables within [square brackets] and use the appropriate data-source.  In most use cases, this involves creating an auto-generated table.  In our example, these would be fields on the OpportunityLineItems object
  5. Name your product page.  Naming a product page is one of the few scenarios in which you can use variables in the title of the page. Child object variables are often included in a page’s name to differentiate the pages 
    1. Determine the field in Salesforce that will name your page.  This must be a field on the product page launching object (in our example, the Opportunity object)
    2. Make sure the field is mapped in the Salesforce Integration page
    3. Copy and paste the API name of the field into your product page title surrounded by {{double braces}}
    For example, if your child Opportunity name variable was Name, you could name your page Product Option – {{Name}} or just {{Name}}.  In the latter example, if you had two child Opportunities with the names of New Business and Renewal, the product pages in your generated document would be named New Business and Renewal, respectively.
Configuring Product Pages
Product pages are configured within the Salesforce Integration settings in Conga Collaborate.  Follow these steps to set up Product Pages:
  1. From your user dropdown in the top right corner, go to Administration > Integrations > Salesforce > Edit
  2. In the Manage Features section, click on the Product Settings tab
  3. Fill out the Product Section Title field.  This names the section within your Conga Collaborate document where you want product pages to be created
    1. If you type in the name of a current section of your template, the generated product pages will be added to that section
    2. If you type a new section name, this section will be added at the end of your generated document
  4. Check the Create Product Pages checkbox
  5. Choose a Page Template.  Select the Asset page you built in the Creating Product Pages section
  6. (Optional) Define a page include filter.  This filter lets you include only pages for child records that meet the filter criteria.  Using our example of the Opportunity Hierarchy from earlier, you might set a filter where a product page for the child Opportunities is only included if that child Opportunity has a stage of Proposal Creation
    Example syntax: Stage == 'Proposal Creation'
  7. Select your child object in the Custom Line Item Object Name field.  In our example, it would be Opportunity
  8. Type in the Salesforce API name for the field that holds the ID of the parent object to the object you selected in step 7.  This would be something like ParentOpportunityID in our example.  No brackets are included around the API name
  9. (Optional) Define the field on your child object by which to sort the product pages within the document
  10. Select your document template from the list on the right.  You can select multiple templates by Ctrl+clicking the templates you want to use
  11. Click Save

Mapping Templates
Product Pages only work when template mapping is enabled for the template you chose in step 10 above.  Reference the article for more information on how to do this.

Launching your Document
Once all the above steps have been completed, create a document from within Salesforce.  If everything was configured correctly, your generated document will contain a page for every child record on your launching object and each page will be populated with the content and data you defined in your Content page template. 

  • Was this article helpful?