New Composer Endpoint URL for Generate Document Steps
Note: 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 Conga Orchestrate installations. For more information on activating the Conga Composer remote site, see Activating the Conga Composer Remote Site to Generate Document Steps.
It is best 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.
Using the new Composer Endpoint URL in a Generate Document
- Go to Conga Orchestrate Setup.
- Click Document Merge under the Partner Integrations section.
- Click the Conga Composer tab.
- Select Composer Integration 2.0.
Limitations
When using the new Composer endpoint (Composer Integration 2.0) in an Orchestrate process:
- You cannot send emails with Conga email templates.
- You cannot use QVar parameters.
- The QueryStringField parameter is not supported.
If the new Composer endpoint 2.0 does not generate Composer documents, use Composer endpoint 1.0 instead.
In the 1.0 or 2.0 integrations with Composer in an Orchestrate process, the DV0 parameter is not supported .
