Document Generation with Conga Composer
When you choose Conga Composer as the selected application, the options available must be from the same object type as the definition to which you want to add a Generate Document step. Document generation occurs in background mode.
The Source picklist allows you to choose one of the following options:
- Template: Uses the process object’s ID as the master object record.
- Solution: Uses the Custom Button URL field on the selected solution record.
- Custom Button: Uses the configured button URL. Only button URLs that begin with
/apex/APXTConga4__Conga_Composerwill display as options.
For Solution and Custom Button options:
- You must predefine a template in the Composer solution or button with the TemplateID parameter.
- Allowed merge fields are process object and user merge fields in parameters.
- When creating a Composer solution or button URL for a Generate Document step, the button URL can only contain merge fields that start with
"{!User.", "{!ProcessObject." (object definition is triggered by), "{!Today()}", and "{!Now()}". Other merge fields or formulas in the button URL are not supported. - Template fields are also supported.
- Embedded URL formulas are not supported.
- A workaround is to build a formula field on the process object and include it in the URL.
Note: When using a lookup field as the value of the OFN parameter, only the record ID displays as the file name. A workaround is to use a QVar to pull in the record name.
