1. Navigate to Setup > Develop > Custom Settings.
2. Click on the Manage link next to Comply System Properties.
3. Click Edit to edit System Properties. The System Properties form is displayed.

   
   
   

4. Configure the System Properties described in the following table.

   #	Property	Description
   1	Enable Version Control	Check this box to enforce a check-in/check-out policy for agreement documents. This setting must be enabled when "Enable Document Versioning" is checked. Note: This property existed in Contract Management versions prior to 8, so this property may already be enabled.
   2	Enable Document Versioning	Check this box to enable Document Versioning. All new agreement records created in your org uses Document Versioning after this setting is enabled. Enable Version Control must be enabled for Document Versioning to work properly. Enabling Document Versioning changes the value of the Version Aware agreement field to TRUE for all new agreements after the property is activated. The Version Aware field is a flag that tells Conga CLM to use Document Versioning for a specific record. Important: It is recommended that once a record is flagged as Version Aware, you do not disable this field, as versioning becomes undefined for the agreement record in question. Instead, ensure that records which should not use Document Versioning do not have the field enabled when they are created (see the section on Workflow Rules below.) To enable or disable Document Versioning for specific Agreement records, see To add the Version Aware field to Agreement Layouts.
   3	Use Agreement Locks for Versioning	Check this box to use Agreement locks for versioning instead of document-level locking: If enabled, all agreement documents are locked (by the user checking out) when any one of them is checked out. If disabled, only checked out documents are locked (by the user checking out) – any other agreement documents which have not yet been checked out can be checked out for editing.
   4	Document Naming Convention	Specify a value to apply a custom naming convention for all agreement documents at generation, check-in and signature events. The following attributes permitted when formulating a document naming convention are: %checkintype% %action% %templatename% %user% %timestamp% %version% Agreement attributes such as %:Name%. Note: any variable prefixed by ':' represents a field on the Agreement object. If the property contains a null value (i.e., if left blank), the current default naming convention is used: %:Name%_%action%_%templatename%_%timestamp% Example agreement document name using the default naming convention: SOW_Regenerated_SOW ABC_2015-08-07
   5	Document Structure FX2 For Imported Docs	Check this box to make document structure FX2 format for all offline documents (created or imported). If not checked, all offline documents are created in the "pre-existing" format. Tip: This property only applies to offline agreements created from the agreement or user Home page links in Salesforce. The format of offline agreements created using X-Author for Contracts depends on user input from X-Author.

1. Navigate to Setup > Develop > Custom Settings and click Manage link next to Comply System Properties.
2. Click Edit.
3. Configure the document naming convention field value as: %:Name%_%templatename%_%timestamp%_%version%
4. Click Save.

1. Navigate Objectse to Setup > Create > Merge Event.
2. Go to the Action custom field.
3. Add the following two values to the picklist:
   • Check Out
   • Revert Check Out

   After adding values, your merge action picklist should appear as shown in the following image:

   
   
   

1. Create a new workflow rule for Document Versioning. See the section on Managing Workflow for assistance with setting up a Workflow Rule in Salesforce.
2. Specify your Workflow Rule Action as a "Field Update" (the rule updates the Version Aware field).
3. Use Apttus__APTS_Agreement__c.Apttus__VersionAware__c as the field value in your rule.

Use this approach when your organization wants all new agreement records to use Document Versioning automatically, without requiring per-record configuration.

1. Configure Comply System Properties for versioning.
   1. Navigate to Setup > Develop > Custom Settings .
   2. Click Manage next to Comply System Properties, then click Edit.
   3. Select the Enable Version Control checkbox.
   4. Select the Enable Document Versioning checkbox. After this property is enabled, all new agreement records created in the org use Document Versioning. The Version Aware field is automatically set to TRUE for all new agreements.
      Note: It is recommended that once a record is flagged as Version Aware, you do not disable this field, as versioning becomes undefined for that agreement record. Ensure that records which should not use Document Versioning do not have the field enabled at creation.
   5. Optionally, select Use Agreement Locks for Versioning to lock all agreement documents when any one of them is checked out. If this property is not selected, only the checked-out document is locked. Other documents in the same agreement can still be checked out independently.
   1. Click Save.
2. Configure Document Version Properties.
   1. Navigate to Setup > Develop > Custom Settings .
   2. Click the Manage next to Document Version Properties, then click Edit .
   3. Set the Initial Version field to 1 to start document versioning from 1.0.0, or 0 to start from 0.0.0.
   4. Set the Document Regenerate field to Major or Minor to control whether regenerating a document increments the major or minor version number.
      Note: Regenerating a document with a different template than the original restarts version numbering regardless of this setting.
   5. Configure the remaining increment settings, Increment Checkin Final, Increment Checkin with Redlines , and Increment Checkin without Redlines, by specifying Major or Minor for each.
   6. Optionally, select Trim Document Version to display document versions as two-digit values (for example, 1.2 instead of 1.2.0) in the Document Naming Convention.
   7. Click Save.
3. Add Version-Related Merge Event Actions.
   1. Navigate to Setup > Create > Objects > Merge Event .
   2. Go to the Action custom field and add the following two picklist values:
   • Check Out
   • Revert Check Out

   The Merge Event Action picklist is updated with the versioning actions required for Document Versioning to function correctly.

4. Add Document Version related list and Version Aware field to Agreement Layouts.
   1. Add the Document Version related list to your Agreement page layouts so that users can view version details directly from the Agreement record.
      Tip: The Document Version related list is included in the default Agreement Layout in the Apttus Contract Management package. If you are using a custom layout, refer to Salesforce documentation for editing page layouts for custom objects.
   2. Add the Version Aware field to your Agreement page layouts to allow agreement editors to enable or disable Document Versioning for individual agreement records.
      Tip: The Version Aware field is included in the default Agreement Layout in the Apttus Contract Management package.
5. Append version to Document Naming Convention (optional).
   1. Navigate to Setup > Develop > Custom Settings and click Manage next to Comply System Properties.
   2. Click Edit.
   3. In the Document Naming Convention field, enter %:Name%_%templatename%_%timestamp%_%version%.
      Note: If Enable Document Versioning is disabled while %version% is configured in the naming convention, the version attribute is replaced with an empty string in the generated document name.
   4. Click Save.

This topic describes how to use a Salesforce workflow rule to enable Contract Document Versioning selectively for specific agreement types, without enabling versioning globally across your org.

1. Create a new Workflow Rule for the Agreement object.
2. Define the rule criteria as: Agreement: Record Type equals SOW.
3. Set the Workflow Rule Action type to Field Update and configure it to set the Version Aware field (Apttus__APTS_Agreement__c.Apttus__VersionAware__c) to True when the criteria are met.
4. Activate the workflow rule and validate it by creating a new SOW agreement and confirming that the Version Aware field is checked.
   New SOW agreements are automatically flagged as Version Aware. Non-SOW agreements remain unaffected.

This topic describes how to use a Salesforce workflow rule to prevent non-version-aware agreements from being automatically upgraded to Contract Document Versioning upon renewal.

1. Create a new Workflow Rule for the Agreement object.
2. Define the rule criteria as: Agreement: Version Number GREATER than 0.

   This criterion identifies agreements renewed from pre-existing, non-version-aware records. The Version Number field carries a value greater than 0 on renewed records because it is inherited from the original agreement.

3. Set the Workflow Rule Action type to Field Update and configure it to set the Version Aware field (Apttus__APTS_Agreement__c.Apttus__VersionAware__c) to False when the criteria are met.
4. Activate the workflow rule and validate it by renewing an existing non-version-aware agreement and confirming that the Version Aware field is not checked on the renewed record.
   Renewed agreements originating from non-version-aware records are not automatically upgraded to versioning. Their Version Aware field remains false.