Start Your Conga Composer Solution Out Right – Requirements Gathering

Subscribe to Our Blog

Get weekly updates
straight to your inbox

Submit your email address to subscribe.

By submitting this form you confirm that you agree to the storing and processing of your personal data by Conga as described in our Privacy Statement.

When setting up any solution with Conga Composer, it’s important to first identify what information you want to include in your document. Spending some time at the start of your Composer project determining your needs will make for smoother sailing as your build your solution.

The location of the data and the relationship between objects often dictates your master object – the object from where your users will launch your solution. You might begin building your solution on Object A, but then realize you need to pull in data from Object D, and no relationship exists between the two objects. Save yourself wasted time and frustration by identifying the information you need ahead of time. Determining the necessary data also provides you with a better sense of what method(s) you might need to retrieve the data. Once you have determined the necessary data to include in your document, you should also settle on the “look” of your document. Is there an existing document template you can modify to use with Conga Composer? This can be a great start.

PRO TIP: Sketch out the format for your document before moving further along with your solution.

If there is not an existing document template, how does the company want to present the information? Tables? Calculations? Grouping by product family? Will you need to “brand” your document with your company logo and colors? Similar to building a house, you’ll want to have a blueprint and design in mind before you start pouring the foundation.

After defining the document’s data and design, establish the desired output method for your document. Will the document need to be emailed out automatically? Or saved as an attachment on the record? Maybe the end user is simply generating the merged document and downloading a copy. If you’ve put the work in to create a great solution, make sure it will be accessible.

A final consideration in the requirements gathering process is who will run the Conga Composer solution. What are those users’ Salesforce roles, permissions and permission sets? If you are using Salesforce reports in your Conga Composer solution do your users have the ability to export reports? If they are lacking this permission, users will not see any data coming from a report in the merged document. Field-level security is another factor to keep in mind. If user profiles do not have visibility enabled for a field, the merged document will not show any data from that field.

PRO TIP: Get stakeholders involved. Involving key decision makers in the process of building the Conga Composer solution is helpful to gain traction and adoption for your solution.


Leave a Reply

Your email address will not be published. Required fields are marked *