Comply System Properties

This is only applicable when Auto Enable Reconciliation is selected.

• If Auto Enable Reconciliation is True and Allow Reconciliation Selection Override is True, the Reconcile checkbox is by default selected on check-in. The user can also deselect (override) the Reconcile button.
• If Auto Enable Reconciliation is True and Allow Reconciliation Selection Override is False, the Reconcile checkbox is by default selected on check-in. The user cannot deselect (override) the Reconcile button.
• If Auto Enable Reconciliation is False, the user can select or deselect the Reconcile checkbox on check-in. However, the Reconcile checkbox is disabled if there is no smart field in the agreement document.

Select this field to automatically insert the Agreement Number Field For Imported Docs field value into the header and the latest timestamp into the footer of an agreement document. This field is available for Generate, Import and Offline actions. For more information about when to use this field, refer to Agreement Number/Header Configuration.

The value of the latest timestamp for the footer is taken from the User Account Timezone field on Salesforce.

Enter a recipient role (Contract Owner, Logged-in XAC user, or both) to receive asynchronous check-in email notifications.

Supported Values: Contract Owner, Logged-in XAC user, or both

Default Value: Both

Select the checkbox to auto-select the asynchronous check-in checkbox available on the X-Author Contracts Check-in pop-up window.

Select the checkbox to allow a user to link an offline document to an existing major version of a document.

Allows you to add a semicolon-separated list of user profiles/permission sets that will use the Contract Management Lite license.

Default value: Apttus_Lite

Allows you to add a list of semicolon-separated email addresses to receive the Contract Management Lite License usage report.

Sample value: sysadmin@example.com; admin@example.com; exec@example.com

Specify a value to apply a custom naming convention to all agreement documents at generation, check-in and signature events.

When formulating a document naming convention, the permitted attributes are:

• %checkintype%
• %action%
• %templatename%
• %user%
• %timestamp%
• %version%

Agreement attributes such as %:Name%.

Note: Any variable prefixed by ":" represents a field in the Agreement object. If the property contains a null value (i.e., if left blank), the 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

For more information on using the document version in the document naming convention, refer to Enabling Contract Document Versioning.

Enable Document Versioning

Select this box to enable template versioning. All new templates created in your org will use template versioning after this setting is enabled.

For more information, refer to Enabling Template Versioning.

Specify the format in which the date and time will be shown in the generated agreement. When a new document is imported into the system, it will include the date in the left of each page's footer, in the format selected above. For a list of supported date and time formats, refer to the Setting date and time format for the footer.

The value of the latest time stamp for the footer is taken from Salesforce's User Account Timezone field.

You can add the number of rows of the large objects (agreement or quote line items and objects defined using the APTS_LargeDocSObjects property) to retrieve in each batch iteration to build the data source for the template.

The default value for Large Doc Process Batch Size is 1000, and the maximum is 2000. You can define a value lower than 2000, based on template complexity.

Sample value: 500

When the number of agreement line items in the contract exceeds this value, the contract is considered a large document. This property is applicable only for generating documents but not for regenerating or generating supporting documents.

The default and maximum Large Doc Threshold value is 10000. You can define a value lower than 10000. Setting a value of -1 for the Large Doc Threshold invalidates the setting.

Sample value: 1000

Enter the merge web service endpoint. For example https://merge.congacloud.com/cgi-bin/MergeServer/Bin/mmcgi.exe.

For Google Drive, enter the merge webservice endpoint as https://<base-address>/api/integrate/v1/execute.

Allows you to specify the comma-separated playbook filter names that should inherit filter value from template attributes on clicking the Playbook tab in X-Author. 

Sample value: Category, Subcategory

Enables parallel review for related agreements when you send a related agreements document in DOCX with the type as Agreement Document. If the checkbox is selected and a user sends a related agreement for review, a review cycle is created for related agreements. If the checkbox is left unselected and a user sends a related agreement for review, a review cycle is not created and the related agreement documents are considered supporting documents.

Ensure that the Parallel Review property is enabled.

Comma-separated list of statuses and status categories for which check-in and check-out actions are restricted in X-Author for Contracts.

Sample value: In Authoring, Other Party Signatures, Submitted Request

Use this property to set the orphan period of temporary email templates to use in conjunction with the CleanupJobScheduler Apex class. The default value of this property is set to 4 hours. 

For more information, refer to Temporary Email Template Cleanup.

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 one of them is checked out. 
• If disabled, only checked-out documents are locked (by the user checking out). Any other agreement documents that have not yet been checked out can be checked out for editing.

Select the checkbox to use a common email address for email communication. You must configure the Organization-Wide Email Address Display comply system property to use an organization-wide email address.