Total Pageviews

Sunday, June 10, 2012

Conga Composer - A how to do guide for first time users (2) (Basic Use)


In my last blog we went about the process of installation of Conga Composer in your Org from scratch.
Now comes the real thing using Conga Composer for your various reporting and document generation needs.
Once installation is complete you will notice that a button with following particulars has been added to most of the standard/native objects in your org:-
1. Label -Conga Composer
2. Name- Conga_Mail_Merge
Please refer to the screenshot below for clarity:-



With exception of some standards objects the above button is added to all the standard objects. Standard objects in which the above button is not added automatically:-
1. Asset
2. Product
3. Ideas
4. Campaign
5. Campaign Member
6. Task
Now lets analyze this button a bit closely. For that we can investigate the details of this button from the button detail page.


The button URL of the Conga Button is  -  https://www.appextremes.com/apps/Conga/PointMerge.aspx?sessionId={!API.Session_ID}&serverUrl={!API.Partner_Server_URL_80}&id={!Account.Id}
The above is the very basic "Conga Button" which has the following components :-
1. The URL of Conga Server - https://www.appextremes.com/apps/Conga/PointMerge.aspx
2. The parameters which accompany this button viz. 
a. Sessionid - Provides the sessionid of the active salesforce session provided by the global variable -     !API.Session_ID
b. serverURL - This is the URL of the salesforce org which is unique for each org - furnished by -{!API.Partner_Server_URL_80}
c. id - This is the id of the master object through which all the data / information will be fetched.
d. There will be other parameters too like reportid and queryid which we will take up when we dig deeper into queries and reports as a data source.
Now let try to use this button and see what data is returned using the above button - notice the above button is placed on account object hence the data returns will that of the account record corresponding to the id specified in the button URL . Lets put the button on the account detail page layout and navigate to an account record. 








Now lets click on the "Conga Composer" button and see what happens.When we click the button the following screen appears:-

The "View Data" link on the above screen shows you the data which is available for generating document and /or reports.When we click on "View Data" link the available data in the form of an excel is downloaded to your system/ computer . For Clarity refer to the following screenshots.

When you save the excel as prompted by the above screen the following data is shown in the form of an excel. 

In the above screen shot the data of the master object which is available for merge and document generation is shown.


 In the above screen shot the data of the Org  (Like orgid, address,etc) which is available for merge and document generation is shown


 In the above screen shot the data of the Logged-in User  (Like username, address,etc) which is available for merge and document generation is shown

The column headings in the above generated excels is used for creating the word template for creating merge documents. We will dive into "Template Creation" in my next blog in this series.




  


2 comments:

  1. Hey Is there any information or any admin guide for Conga contracts for Contract CLM process?

    ReplyDelete
  2. I am unable to access cross object fields. e.g. I have a custom object Visit which has a lookup relationship to Account. But I am unable to access account fields in the template builder if I choose Visit as the Master data source. I tried using formula fields but didnt work either. Kindly help. I am new to Conga.

    ReplyDelete