Information on configuring Conga Composer for Salesforce Lightning. Try the Lightning Migration Assistant.

  • Configure Conga Composer for Lightning
    • The Salesforce Lightning Experience combines the new Lightning Design System, Lightning App Builder and Lightning Components to enable anyone to quickly and easily create modern enterprise apps within Salesforce. The changes to the Salesforce interface will require customers update their Conga Composer solutions when they switch to Lightning.
  • Lightning Readiness Items for Conga Composer
    • The listed items must be addressed to make your Conga Composer solutions Lightning Ready.
  • Convert Non-OAuth Buttons to OAuth
    • Composer buttons that do not use OAuth security (Open Authorization) must be converted to OAuth buttons in order to work in Salesforce Lightning.
  • Convert Data Gathering Reports to Conga Queries
    • Salesforce reports used to gather data for Conga templates must be converted to Conga Queries to work in Salesforce Lightning. Conga templates that merge data from those reports must also be updated.
  • Add the Query to the Composer Solution Using an Alias
    • Now that the Conga Query has been created, you need to replace the ReportId parameter in the button URL with the QueryId parameter.
  • Update Affected Templates
    • After replacing reports with queries and adding them to the Composer solution using aliases, the final step is to update affected templates.
  • Other Considerations
    At this point, the main concerns of migrating Conga Composer to Salesforce Lightning have been addressed. However, you may have other considerations based on your specific implementation of Conga Composer.