The Composer Button UI (2 of 6)
This is the Composer User Interface. If you have not seen a walkthrough of Conga Composer’s User Interface, and want to follow along, we recommend installing one of the Composer Solutions from the Solution Pack, which can be found on Conga’s Support Site, into a Sandbox or Developer org. The first tab on the far lefthand side of the UI will display a list of templates built for, and assigned to this Solution. Templates for Composer can be built in the form of a Word, Excel, Powerpoint, or PDF document. The next tab over is for email templates. Email templates can merge data from Salesforce in the same way that traditional templates can, but must also be built and formatted just as with traditional Templates. The last tab is for local templates, meaning templates that have not yet been uploaded to a Salesforce record. The local template option is recommended for testing purposes, and can be turned on and off through the Composer Setup tab within your Salesforce instance. The Related Contacts drop is mostly used for auto-populating the email address of a contact for Email Templates, and will display related contacts to the record with Account and Opportunity roles. With Output Options, we can choose to convert our template to a PDF, or maintain the original document type. The Action dropdown allows us to select what merges we’d like to perform: a document merge, an email merge, or both simultaneously. With Save a Copy, we can save a copy of our merged document back into Salesforce for future reference, and with Activity Logging, we can keep track of Composer usage from our Salesforce end-users. Once a Composer Solution is launched, an end-user simply selects the document, email, or both, that need to be created, and then clicks merge. With a fully built Composer Solution, we can automate the process of creating documents, and any email communication your organization needs, all with the click of a button.