Important

Ensure that the Conga_Composer Remote Site is activated in your org. Orgs that upgrade to a new version of Conga Orchestrate must activate the Conga_Composer Remote Site. Activating the Remote Site is not required for new installations of Conga Orchestrate. For more information on activating the Conga Composer Remote Site, see Activating the Conga Composer Remote Site for Generate Document Steps.

It is highly suggested to use the new Composer Endpoint URL to maximize document generation performance and Composer's suite of parameters within a Generate Document step leveraging Composer.

The new Composer Endpoint URL generates documents more quickly when firing a Generate Document Step. It also provides administrators with access to more Composer parameters, to further customize the document generation process.

To use the new Composer Endpoint URL in a Generate Document Step:

  1. Navigate to Conga Orchestrate Setup.
  2. Click Document Merge under the Partner Integrations section.
  3. Click the Conga Composer tab.
  4. Select Composer Integration 2.0 (Recommended).

Caveats and Known Issues

The Conga Orchestrate Product Team is aware of these issues and is actively working on a resolution to resolve them.

  • You cannot send emails with Conga Email Templates when using the new Composer Endpoint (Composer Integration 2.0) in an Orchestrate Process.
  • You cannot use QVar parameters when using the new Composer Endpoint (Composer Integration 2.0) in an Orchestrate Process.
  • The QueryStringField parameter is not supported when using the new Composer Endpoint (Composer Integration 2.0) in an Orchestrate Process.
  • If Composer documents are not being generated using the new Composer Endpoint 2.0, we recommend that you use Composer Endpoint 1.0 instead.