Query Template
Using template filtering rules, you can set up user-defined filters to narrow the list of templates that display for tasks that involve previewing or generating documents. For example, for agreement templates created for multiple regions, you should only be able to select templates for the region to which they belong. The template filter uses agreement fields and related child object fields to select the templates to display.
|
User Permissions Needed | |
|---|---|
|
To create, edit or delete a query template |
Query Template: Read, Create, Edit, Delete Agreement: Read Template: Read |
Limitation
You cannot define more than 44 query templates. If you define more than 44 query templates, the Template Selection page that appears while generating documents does not display templates.
Inserting an Amendment Template
You can insert an Amendment Template in the available choice of templates while generating an agreement in the state: In Amendment=In Amendment status.
Use Case: Creating a Query Template for Filtering Agreement Templates
This use case describes how you, as a System Administrator, create a Query Template to filter the document templates that appear during agreement document generation, preview, or regeneration. Once configured, users can only select templates appropriate to their agreement's language and record type.
- The agreement record contains a Language picklist field with values such as English and Spanish (field API name: Language__c).
- Template records contain a corresponding Language field (field API name: Apttus__Language__c).
- An NDA record type exists for the agreement object (for example, NDA-<yourinitials>).
- You have system administrator permissions in Conga CLM.
Business Context
Organizations that generate agreements across multiple regions or languages require a reliable way to present only the appropriate document templates to users. Manually selecting from an unfiltered list of templates introduces the risk of using the wrong template, leading to compliance issues or inconsistent contract output.
By configuring query templates with qualifiers and filters in Conga CLM, you can define filtering rules that automatically match agreement record attributes, such as language, record type, or region, to the corresponding document templates. This ensures that users see only the templates relevant to their context, reducing errors and improving document generation efficiency.
Overview
This use case describes how to create a query template that filters document templates based on a field value match between the agreement record and available template records. It demonstrates how you can configure query template qualifiers and filters so that only templates matching the agreement's language are presented during document generation.
This use case provides an example of how to configure query template filtering rules. The query template looks for a match between fields on the agreement and template records. For example, the agreement record contains a Language field with the possible values of English or Spanish, while the template record contains a similar Language field. By comparing and finding a match between the Language field values on the agreement record and template records, the query template presents the appropriate template for document generation.Your implementation may vary. For more information about query templates, see Query Templates.
- System Administrator: Configures query templates, qualifiers, and filters in Conga CLM.
- Sales Representative: Generates or regenerates agreement documents using the filtered templates.
Scenario
A system administrator at a company using Conga CLM needs to ensure that when a sales representative generates an agreement document, only templates matching the agreement's language are available for selection. The company has agreements in English and Spanish, and separate NDA templates exist for each language.
Without query template filtering, a sales representative would see all available templates and would have to manually identify and select the correct language-specific template. By creating a query template with a qualifier and filter, the administrator ensures that the template list is automatically narrowed based on the Language field value on the agreement record.
In this example, the administrator creates a query template that matches the Language field on the agreement record to the Language field on available template records. When a sales representative opens an agreement in English, only English-language templates are presented. The same logic applies to Spanish agreements.
- Select the Query Templates tab.
- Click New.
- On the Query Template Edit screen, enter 1 as Sequence.
- Retain all other default values and Save.
- Click New Query Template Qualifier from the Qualifiers related list.
- Enter 1 as Sequence.
- Retain Agreement as Object.
- Type RecordType.Name for the Field value.
- Retain Comparison Operator as equal to.
- Type NDA-ACME in the Value field. This must be an exact match to your record type label.
- Retain Apttus__APTS_Agreement_c in the SObject Type.
- Click Save. Click QT-#### (top right of page) to navigate back to your query template record.
- Click New Query Template Filter from the Filters related list.
- Enter 1 as Sequence.
- Type (or copy) Apttus__Language__c for the Field value.
- Retain Comparison Operator as equal to.
- Type (or copy) Apttus__APTS_Agreement__c.Language__c in the Value field.
- Click Save.
- An agreement with Language set to English displays only English-language NDA templates.
- An agreement with Language set to Spanish displays only Spanish-language NDA templates.