Reports, Queries, and the Template Builder (4 of 6)
In order for a Composer Solution to bring in data from Salesforce and merge it into a template, we must first specify on the back-end of the Solution what data should be referenced, and from where within Salesforce. To do this, we need build Salesforce Reports, or SOQL Queries. If you’ve already built Salesforce reports and want to reference them in this Solution, click on Add Report Data from the Solution Manager screen. The list on the left-hand side will show all available Salesforce Reports that can be added to this Solution. Click the Report you’d like to reference, give the report an alias, and then click Add Report to Solution Record on the top of the page. Any data within the report we selected can now be referenced in the Template Builder of this Solution, which we will cover in the last portion of this section. With Query Data, we can source any data needed for our Solution, and apply conditional criteria for when and why the query should source data. Start by clicking Add Query Data. This page will display any queries that have been in the past, and can be added to the current Solution. If no queries have been built in your Salesforce instance, the list on the left will be empty. To build a new query, click Create New Conga Query Record. As a best practice, always be specific with what data is being sourced in the Query by creating a naming convention. Once the query is named, click Save. From this page, we can either write out our Query manually through the SOQL Select Statement field, or click on the arrow drop-down on the upper-right corner, and select Conga Query Builder for a more guided building experience. Step 1 of the Query builder will ask us to specify a base-level Object to start referencing data. In Step 2, we can select which fields we need to reference for templates in this Solution. You can either hand-select the fields you need by double-clicking, or use the double-arrow to select all fields from that Object. Note that you can optionally select additional fields to reference from any of the Parent or Lookup objects as they relate to the base-level Object of this query. In Step 3, we can apply conditions for how or why this data should be selected. For example, if we only wanted to reference data from Closed Opportunities, we could select “Stage” in the field, “equals” as the Operator, and “Closed” as the value. This will create a condition for this query, and any data pulled from this query, and into a template, will only pull from Opportunities whose stage field equals “Closed.” The 4th and final step of the query builder is simply for testing purposes. We can insert Salesforce record IDs into the PV values, and test the query we just built, ensuring that it is pulling data the way we specified. Once we click Save, we can close the Query window, and refresh the Query page in Solution Manager. Once refreshed, we can now search for our newly created Query, select it, and add it to our Solution record. Now that we’ve gathered and built what data needs to be sourced and used in our templates for this Solution, we can now begin to design our Templates. From the Solution manager record, we must first click Create Button: this will unlock the Template Builder portion of this Solution, where we can begin our template designs. After clicking Access Template Builder, select a sample record to reference from the left, then click on Select Sample Record, followed by clicking Access Template Builder. This will launch a sample version of the Solution currently being built. Once Composer is launched, click on Tools and Settings from the upper-righthand corner, and select Template Builder. The Template Builder will give us a list of the specific Salesforce Reports and Conga Queries that were added to this Solution. By expanding the Query or Report that we have added to this Solution, we can find the field that needs to be added to our Template, and double click. The result is what we call a Merge Tag, and should be copy and pasted into the Template or Email Template we are designing for this Solution. Be sure to select the appropriate Copy Field Format on the bottom left before using. You can also more easily copy and paste the selected Merge Tag by clicking on the manila page icon at the bottom of the screen.
In Most Recent
Adding a Table to a Collaborate Document
Learn to add generic tables to your Collaborate document using the editor tool.
3 ways to streamline your CLM processes
As an Agent of Change within your organization you are often challenging the status quo to improve how things get done and you don't have time to waste on inefficient, risky CLM practices.
How to install and configure Conga Sign
Join us as we run through how to install Conga Sign from the Salesforce AppExchange, configure the product, and send a document for eSignature. Installation :12 Configuration :58 Send for eSignature 2:36 Resources 3:56
Editing a Document in Conga Collaborate
Learn how to edit a document in Conga Collaborate
Conga Collaborate Metadata Overview
Learn how metadata templates work in Conga Collaborate and how to use metadata in your documents once templates are set up.
3 benefits of moving to eSignature
Let’s face it. Wet signatures are hard to get! To keep your business moving forward you need a new way to execute deals and agreements. Here are 3 benefits of moving to electronic signature.