The APTS_AccountHierarchyFields property allows you to add up to four fields to display on an account's agreement hierarchy. If no value is provided for the property, the Account Name, Account Number, and Account Owner fields are displayed. For more information, see Viewing Account's Agreement Hierarchy.

When the APTS_ActivateDocumentsPublishAll property is set to true, all documents are selected for publishing but users can turn the Publish toggle on or off. When the APTS_ActivateDocumentsPublishAll property is set to false, all documents are unselected for publishing but users can turn the Publish toggle on or off.

When the APTS_ActivateDocumentsSelectable property is set to true, users can select or unselect documents on the Activate Agreement page. When the APTS_ActivateDocumentsSelectable property is set to false, users cannot select and unselect documents on the Activate Agreement page.

When the APTS_ActivateDocumentsSelectAll property is set to true, all documents on the Activate Agreement page are selected. When the APTS_ActivateDocumentsSelectAll property is set to false, all documents on the Activate Agreement page are unselected.

This admin entry allows you to add a comma-separated list of parent objects other than Apttus__APTS_Agreement__c and documentVersionDetails to sync documents from that object.

This admin entry enables adding a comma-separated list of objects other than Apttus__APTS_Agreement__c, Attachment, and ContentDocumentLink that you need to sync to the Conga Platform for CLM.

This property allows you to increase document storage size based on the Salesforce size limit. If the Salesforce storage limit for your org is increased to 25 MB or more, you must update this property to allow users to upload documents with the increased size limit. If this property is not configured, the value is 5 MB.

The APTS_AgreementHierarchyFields property allows you to add up to four fields that must be displayed on the Agreement Hierarchy page. If no value is provided for APTS_AgreementHierarchyFields property, the Agreement Number and Status Category fields are displayed. For more information, see Viewing Agreement Hierarchy.

This admin entry allows you to override the default naming convention for agreements generated on amending an agreement.

By default, the system appends 'Amend' to the base agreement name and assigns it to the new agreement. You can set the numbering value to be started from a desired number. For example, to start the numbering from 1, you need to specify 1 in the Code of this admin entry.

If you set this admin entry to false, the system modifies the agreement name as per the default behavior i.e. APTS_AgreementName_Default admin entry.

If you set both, APTS_AgreementName_Amend and APTS_AgreementName_Default to false, the system appends 'Amend' to the agreement name as many times as the action is performed. For example, after each amendment, the agreement name is updated to HP_MSA_Amended, HP_MSA_Amended Amended, HP_MSA_Amended Amended Amended,...

This admin entry allows you to override the default naming convention for agreements generated on cloning an agreement.

By default, the system appends the 'Copy' to the base agreement name and assigns it to the new agreement. You can set the numbering value to be started from a desired number. For example, to start the numbering from 1, you need to specify 1 in the Code of this admin entry.

If you set this admin entry to false, the system modifies the agreement name as per the default behavior i.e. APTS_AgreementName_Default admin entry.

If you set both, APTS_AgreementName_Renew and APTS_AgreementName_Default to false, the system appends 'Renew' to the agreement as many times as the action is performed. For example, after each renewal, the agreement is updated to HP_MSA_Renewed, HP_MSA_Renewed Renewed, HP_MSA_Renewed Renewed Renewed,...

This admin entry allows you to define a naming convention for the agreement generated on amending, cloning, or renewing an agreement.

If you set its value to true, the system appends the following for each action to the base agreement name and assigns it to the new agreement:

• for clone action: appends "Copy"
• for renew action: appends "Renewed"
• for amend action: appends "Amended"

For example, if you clone an agreement named HP_MSA, the cloned agreement is named HP_MSA Copy. If you clone the cloned agreement, the resulted agreement is named HP_MSA Copy Copy.

You can assign numbers to agreements resulted after cloning, amending or renewing by configuring an action-specific admin entry. For more information, see APTS_AgreementName_Amend, APTS_AgreementName_Clone, APTS_AgreementName_Renew.

If you have configured APTS_AgreementName_Default admin entry and action-specific admin entries with Code as 1, the agreements are named as follows each time when an action is performed on the agreement:

• for clone action: HP_MSA Copy 1, HP_MSA Copy 2, and so on
• for renew action: HP_MSA Renew 1, HP_MSA Renew 2, and so on
• for amend action: HP_MSA Amend 1, HP_MSA Amend 2, and so on

This admin entry allows you to override the default naming convention for agreements generated on renewing an agreement.

By default, the system appends 'Renew' to the base agreement name and assigns it to the new agreement. You can set the numbering value to be started from a desired number. For example, to start the numbering from 1, you need to specify 1 in the Code of this admin entry.

If you set this admin entry to false, the system modifies the agreement name as per the default behavior i.e. APTS_AgreementName_Default admin entry.

If you set both, APTS_AgreementName_Renew and APTS_AgreementName_Default to false, the system appends 'Renew' to the agreement as many times as the action is performed. For example, after each renewal, the agreement is updated to HP_MSA_Renewed, HP_MSA_Renewed Renewed, HP_MSA_Renewed Renewed Renewed,...

This property allows you to define the status and status category of an agreement to be updated after all clauses in the agreement are approved, canceled, or rejected. When this property is not configured, the status and status category of an agreement are not updated after all clauses in the agreement are approved, canceled, or rejected .

When the value of the APTS_AppendVersionNumberToMergedDocs admin entry is true and the Document Versioning Properties are enabled, a version number is appended to merged documents' names.. For more information, see Merging Documents in Salesforce Lightning.

You can use this admin entry when you want to clone, amend or renew agreements with many documents. By default, the admin entry is set to false.

When the APTS_AsyncCloneAmendRenew admin entry is set to true, the cloning, amendment, or renewal process of an agreement happens asynchronously in the background. This allows the user to continue working on other agreements without interruption. After the cloning, amendment, or renewal process is complete, the user receives an email notification.

When you amend, clone, or renew an activated agreement record, with documents present in the Agreement Documents-related list, the process occurs in synchronous mode. When you amend, clone, or renew an agreement record that is not activated, with documents present in the Document Versions-related list, the process occurs in asynchronous mode.

The asynchronous cloning, amendment, or renewal process only copies the files and attachments of the Agreement and Document Version Detail records in the background. If the documents (are present in either Agreement Documents or Executed Documents, then the files are copied synchronously and not asynchronously.

For more information on cloning, amending, or renewing an agreement, see Managing Agreement Lifecycle Post-Activation.

Publishing a template takes the text from any referenced clauses and enters it inline as part of the template text. This functionality allows the clause template changes to be reflected in the agreement template and creates a newly published version document in the Notes and Attachment section of the Template. Whenever the agreement document generation exceeds 60 seconds, users get a timeout message and this is not an error message. To make sure the status changes during this scenario, add these Admin entries. For more information, see Document Generation Features List.

When the APTS_AsyncMergeEmail property is set to true, you will receive an email notification after the signed document is uploaded in an agreement. For more information, see Document Generation Features List.

The APTS_AutoContentSearchable property automatically enables Content Search on an activated agreement. By setting the flag to true, the system skips the prompt to select attachments for content search. The attachment already selected as part of the activation process will be automatically enabled for content search. For more information, see Routing Documents to Content Libraries and Activating an Agreement.

The APTS_CCIImportAgreementStatusCategory property allows you to configure the visibility of the Intelligent Document Import button on the Agreement Detail page based on the Status Category of the agreement. When the property is not configured and the Status Category of the agreement is Request, In Authoring, In filing, or In Signatures, the Intelligent Document Import button is visible.

The APTS_ComplyConfig admin entry is set up to support various scenarios, including:

• Clone Custom Objects

• Control Agreement Document Restrictions

• Map Agreement Fields with Agreement Obligations

Clone Custom Objects: APTS_ComplyConfig admin entry can be configured to specify the custom objects that need to be cloned as part of the agreement clone, amend, and renew operation.

Control Agreement Document Restrictions: The APTS_ComplyConfig admin entry, along with Enable PDF Security (comply system property), allows you to control restrictions for agreement documents:

• Generated in PDF format.
• Checked-in from X-Author Contracts as Final-to be signed with Create PDF attachment option selected.

Map Agreement Fields with Agreement Obligations: The APTS_ComplyConfig admin entry allows configuring Field Mapping between agreement fields and obligations, to be utilized at the time of agreement document generation or regeneration, to auto-populated agreement obligation fields with relevant agreement fields.

<ComplyConfig>
<AgreementObligationSpec>
<FieldMapping>
<Includes>
<Mapping>Apttus__AgreementObligation__c.Name = Apttus__Agreement__c.Name</Mapping>
<Mapping>Apttus__AgreementObligation__c.Apttus__EndDate__c= Apttus__Agreement__c.Apttus__Contract_End_Date__c</Mapping>
</Includes>
</FieldMapping>
</AgreementObligationSpec>
</ComplyConfig>

<AgreementObligationSpec>
<FieldMapping>
<Includes>
<Mapping>Apttus__AgreementObligation__c.Name = Apttus__Agreement__c.Name</Mapping>
<Mapping>Apttus__AgreementObligation__c.Apttus__EndDate__c= Apttus__Agreement__c.Apttus__Contract_End_Date__c</Mapping>
</Includes>
</FieldMapping>
</AgreementObligationSpec>

The APTS_ContentRecordTypeName property is used to indicate the content type to associate the published documents with. If The property is not specified, no content type will be used. For more information, see Routing Documents to Content Libraries.

The APTS_ContentRepositoryType property allows you to define which content repository must be used for routing documents. The supported setting "content" to use content repository settings for routing documents. The default setting is "document," which routes all activated documents to an Apttus folder. Changing this setting tells the system to use content repository settings for routing documents. For more information, see Routing Documents to Content Libraries.

To activate documents that exceed the file size of 40MB, you must set the value to content or chatter. For more information, see Activating an Agreement.

The APTS_CustomLinksforActionPanel property enables you to add and customize the action panel. For more information, see Enabling and Customizing the Action Panel.

The APTS_CycleTimeReportingEnabled property allows to track the time spent in between two statuses or status Categories. Entry for the specified status changes under Cycle Time Group tab must be created. For more information, see Cycle Time Reporting.

The APTS_DEFAULT_PACKAGE property allows you to connect X-Author for Contracts to both Conga CLM (Contracts for Salesforce) and Conga CLM packages when they are installed in the same org. For more information, see Installing Production X-Author for Contracts.

The APTS_DefaultContentWorkspaceName property is used to indicate the default content workspace to publish the documents selected by the user during the agreement activation process. The user activating the agreement must be a member of the default content workspace. For more information, see Using Agreement Rules to Route Content.

This APTS_DefaultCurrentUserforReview_<ActionName> property allows you to set the logged-in as the default reviewer when sending documents for simple review, parallel review, Microsoft 365 reviews (internal, external, or mixed), or Google Docs review. For example, to set the logged-in user as the default reviewer for a Google Docs review, configure the admin entry APTS_DefaultCurrentUserforReview_SendToGoogleDocsReview. For Microsoft 365 review, use APTS_DefaultCurrentUserforReview_SendToOffice365Review.

The APTS_DefaultEmailContactName property allows you to specify the name of the default contact to resolve merge fields in an email template. To specify the name of a contact to send emails to, if a contact is not defined for the agreement. If The property is not defined and the agreement does not have a primary contact, the merge fields in the email would not be resolved to their values. For more information, see Sending an Agreement Document for Parallel Review.

The APTS_DefaultEmailTemplateFolder property allows you to add the name of the default email template folder. For more information, see Sending an Agreement Document for Parallel Review.

The APTS_DefaultHeaderFooterOptionForMerge property allows you to set the Retain Header and Footer or Custom Header and Footer checkbox selected by default on the Merge Documents page. For more information, see Merging Documents in Salesforce Lightning.

This admin entry allows you to configure a list of internal reviewers for document review. You need to specify users, public groups, or profiles in the admin entry code. When a user sends a document for review, the recipients specified in this admin entry are displayed in the To field by default.

This admin entry allows you to configure a list of internal and external reviewers for Google Docs review. You need to specify public groups, profiles, or users in the admin entry code. When a user sends a document for Google Docs review, only the active recipients listed in this property appear in the Editor field by default. Additionally, the agreement’s primary contact is also included in the Editor field.

This admin entry allows you to configure a list of external reviewers for document review. You need to specify users, public groups, or profiles in the admin entry Code. When a user sends a document for Microsoft 365 external review, the recipients specified in this admin entry are displayed in the To field by default.

{
"Groups": <"group1;group2">,
"profile": <"profile1;profile2">,
"user": <"user1;user2">,
"email": <"emailaddress1;emailaddress2">
}

This admin entry allows you to configure a list of internal reviewers for document review. You need to specify users, public groups, or profiles in the admin entry Code. When a user sends a document for Microsoft 365 internal review, the recipients specified in this admin entry are displayed in the To field by default.

{
"Groups": <"group1;group2">,
"profile": <"profile1;profile2">,
"user": <"user1;user2">,
"email": <"emailaddress1;emailaddress2">
}
                                

This admin entry allows you to configure a list of internal and external reviewers for mixed document review. You need to specify users, public groups, or profiles in the admin entry Code. When a user sends a document for Microsoft 365 review, the recipients specified in this property are displayed in the To field by default.

{
"Groups" : <"group1;group2">,
"profile" : <"profile1;profile2">,
"user": <"user1;user2">,
"email" : <"emailaddress1;emailaddress2">
 }

This admin entry you to configure a list of reviewers for simple or parallel document review. You need to specify users, public groups, or profiles in the admin entry Code. When a user sends a document for simple or parallel review, the recipients specified in this admin entry are displayed in the To field by default.

{
"Groups" : <"group1;group2">,
"profile" : <"profile1;profile2">,
"user": <"user1;user2">,
"email" : <"emailaddress1;emailaddress2">
}                            

This admin entry allows you to configure a list of signatories to a contract document. You must specify users, public groups, or profiles in the admin entry code. When a user sends for a contract document for wet signature, the recipients specified in this admin entry are displayed in the To field by default.

This admin setting determines the default view for document attachments in the activation notification email:

• True: All documents are displayed as de-selected by default.
• False: All documents are displayed as selected by default.

When set to True, this property disables data sync between Salesforce and Conga Platform for CLM. To enable data sync, you must set this value to False.

The APTS_DocumentNamingConvention_<RecordType label name> property allows you to define a specific naming convention for the generated files based on the record types. If there are no naming conventions defined for the record types in the Admin Entry, the Document Naming Convention defined in Comply System Properties is used as the naming convention for the generated files. For more information, see Contract Document Versioning.

The APTS_DocumentSearchBasicFilters property allows you to add fields that must be displayed on the Document Search page in the Basic Filters section. If The property is not defined, Agreement Number, Agreement Name, Owner ID, Status, Status Category, Agreement Start Date, Agreement End Date, Account, and Record Type fields are displayed. If The property is defined, the defined fields along with Account and Record Type fields are displayed. The Account and Record Type fields are displayed irrespective of the property. For more information, see Searching Agreement Documents.

The APTS_DocuSignRetrieveAsCombinedRecordType property enables you to combine the documents, based on the record type, when you send for signatures using DocuSign. If you set to the property to "all;<recordtype>;<recordtype>;<recordtype>", all takes precedence over the record types. This admin entry overrides the system property RetrieveAsCombinedDocument in DocuSign. For more information, see Retrieving DocuSign Certificate of Completion.

Deprecated. For information on the new custom setting, see APTS_XAAddInLoadType.

In the multicurrency enabled orgs, the APTS_DoNotPrefixCurrency property allows you to not prefix currency symbols before the currency-related fields in the generated documents based on the Enable Formatting value in X-Author for Contracts. For more information, see Defining Template Locale.

If no value is added, the viable days of the downloadable link are considered as 7 days and after 7 days the downloadable link will be inaccessible. For more information, see Emailing Multiple Agreement Documents.

The APTS_EditableSmartCCInReadonlyClause property allows you to enable the ability to edit Smart fields inside a read-only clause. If the value is set to True, then users can insert a clause in template and mark it as read-only. After document generation, the smart fields within this read-only clause remain as smart and editable and are included in reconciliation and UFC.

If the value is set to False, then users can insert a clause in template and mark it as read-only. After document generation the fields within this read-only clause are treated as merge fields and are not included in reconciliation and UFC. There will be no impact on clauses with clause behavior - delete read-only.

If this property is not set, the read-only clauses will follow same behavior as a False value.

The APTS_EmailTemplateForReview property allows you to add the name of the email template for Send for Review action. For more information, see Configuring Email Templates in Lightning.

The APTS_EmailTemplateForReviewSignatures property allows you to add the name of the email template to use for Send for Review and Send for Signatures actions. The property is only used if APTS_EmailTemplateForReview and APTS_EmailTemplateForSignatures are not specified. For more information, see Configuring Email Templates in Lightning.

The APTS_EmailTemplateForSignatures property allows you to add the name of the email template for Send for Signatures action. For more information, see For more information, see Configuring Email Templates in Lightning.

The APTS_EnableCustomEmailAddressLookup property enables you to launch the custom Email Address Lookup pop-up for the Send for Review and Send for Signature functionalities. On this page, you can quickly search and select contacts for the Additional To, Cc, and Bcc fields, if there is a large number of contacts (for example, more than one million). For more details, see Sending an Agreement Document for Review and Finalizing an Agreement.

When the APTS_EnableLightningCommunity admin entry is set to true, all users in an org are considered as Lightning Community users and are navigated to the Agreement Detail page after a user clicks New Agreement on an Opportunity.

When the admin entry is set to false, is not added, or has an invalid value, all users in an org are considered as Classic Community users and are navigated to Classic Community after a user clicks New Agreement on an Opportunity.

The APTS_EnableTermExceptionsInAuthor property associates the Agreement Term Exception related list to the Agreement record after you have associated your Term Exception with the clause and the clause is inserted in your agreement template. For more information, see Configuring Agreement Term Exception.

Setting the APTS_EnableValidationForEmailWithoutUserContact property to true displays an error message while sending a document for signatures or review when the email IDs or contacts specified in the To or Additional To fields are invalid. For more information, see Sending an Agreement Document for Parallel Review.

This property along with the ApttusEndReviewByEmailO365 email service allows users to end an Office 365 review via email. For more information, see Configuring Email Service for Ending an Office 365 Review by Email.

This admin entry allows you to add a comma-separated list of namespaces to exclude objects from the wizard dropdown.

If you have configured this admin entry multiple times, then the latest configured admin entry is considered to exclude objects from the wizard dropdown. If this admin entry is not configured, the value provided in the Excluded Namespaces comply system property will be considered to exclude objects from the wizard dropdown.

This admin entry allows you to specify whether the fcorgid field for DocuSign envelopes should be displayed or not. If you specify True as the value for this admin entry, the fcorgid field is displayed under Envelope Custom Fields in DocuSign interface.

This admin setting allows you to hide the Generate button during large document generation and use the Submit button instead. For instance, if the number of agreement line items exceeds the threshold set in the Large Doc Threshold comply system property, the Generate button is hidden. You can also define custom objects as large and set their batch sizes in the APTS_LargeDocSObjects admin property. When you enable APTS_HideGenerateAction and a record exceeds the specified thresholds, the system automatically hides the Generate button.

This admin entry allows you to define a naming convention for the documents generated under the "Generate Supporting Documents" section for agreements. This admin entry supersedes the Document Naming Convention property defined in Comply system properties. If a naming conventions is not defined in this admin entry, the Document Naming Convention property defined in the comply system properties is used.

The attributes permitted when formulating a document naming convention are:

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

The APTS_HighlightFieldsUsingControlPanel allows you to view the Highlight Fields options under the work tab in X-Author for Contracts. When the APTS_HighlightFieldsUsingControlPanel is set to true the Highlight Fields option is visible under the X-Author for Contracts work tab for users, and when set to false, the menu is hidden for users. If the APTS_HighlightFieldsUsingControlPanel admin entry is not added, then by default, the value is set to true. For more information, see Highlighting Smart and Read-Only Fields.

This property adds the primary contact from the agreement to the email's To field when you send for review or signatures.

The APTS_InEffectViewMetadataFields property allows you to add fields that must be displayed on the In-Effect View page in the Agreement Details In Effect section. If The property is not defined, Agreement Name, Agreement Start Date, Agreement End Date, Term (Months), and Total Agreement Value fields are displayed. If the property is defined, only the defined fields are displayed, but not the default fields. For more information, see Accessing In-Effect View.

When you configure this admin entry and check-out an agreement document in X-Author Contracts, you can restore the metadata of a corrupted agreement document. For more information, see Restoring Document Metadata.

When you set the APTS_KeepSectionBreaks admin entry to false, page breaks are not added between merged documents.

By default, CPQ and CLM consider Proposal Line Item and Agreement Line Item as large objects for document generation. In case you used any other object in a template, you must use the APTS_LargeDocSObjects property to define such objects as large objects. You can specify multiple objects as large objects and also provide a batch size for each of these objects.

Whenever the agreement document generation exceeds 60 seconds, the timeout message is displayed. This is NOT an error message. To make sure the status changes during this scenario, add these Admin entries. For more information, see Objects Supporting Document Generation.

The APTS_MS_EnableNameSort property allows you to specify whether the related list should be sorted by the name field in the generated agreement document. When enabled the related lists will be printed in the agreement’s merge documents in the order of the name field of the related list.

Use the APTS_NoISOCurrencyFieldObjects property to add support for custom object generation for objects that do not have a CurrencyIsoCode field (e.g., "EventRelation," "Task," "TaskRelation"). Separate Object names using a comma or new line. The property is only applicable to templates in multi-currency org.

Use the APTS_NoNameFieldObjects property to add support for custom object generation for Objects that do not have a Name field. (e.g., "EventRelation," "Task," "TaskRelation") Separate Object names using a comma or new line.

The APTS_Password property allows you to create a password for protecting Microsoft Word agreements that are generated by the application. It also allows the application to password protect generated Microsoft Word documents.

The APTS_ProfilePermissions property allows you to define custom permissions for user profiles.

The APTS_Protection property allows you to specify whether protection for Microsoft Word agreements that are generated by the application should be on or off. Allows the application to specify protection for generated MS-Word documents. The property must be configured before configuring the Agreement Protection tab.

You can configure this admin entry to specify whether the document attachments for activation notification should be displayed as read only or not.

• True: The check boxes for documents are displayed as read-only i.e. grayed out. Users cannot change the selection for any document.
• False: The check boxes for documents are displayed as editable. Users can change the selection for any document.

The APTS_RecordTypeUpdateOnAmend property enables you to update record type while amending an agreement. If you set to the property to "all;<recordtype>;<recordtype>;<recordtype>", all takes precedence over the record types.

You can ensure that the users import offline documents only of a specific file formats. APTS_RestrictDocumentFileFormat admin entry specifies restricted file formats.. Specify a comma-separated list in case of multiple file formats. If no value is provided for the property, users can import documents in any file format.

If the APTS_RestrictEmailToCurrentUserOnActivate property is set to true, the current user does not receive the agreement activation email notification. For more information, see Activating an Agreement.

APTS_RetainCommentsInTemplate

When APTS_RetainCommentsInTemplate is set to true, the comments added in the original X-Author for Contracts template are displayed in the generated document.

When APTS_RetainCommentsInTemplate is set to true, the comments added in the original X-Author for Contracts template are displayed in the generated document.

When APTS_RetainTemplateName is set to true, the EchoSign agreement record retains the same agreement name as in the selected Adobe agreement template, at the time of sending an agreement for eSignature through the Send for Adobe Sign feature.

If set to false, the EchoSign agreement record retains the CLM agreement name.

When you end a parallel review of an imported document, the reviewed document is merged with the latest reviewed document. If the APTS_RetainFileNameForParallelReviewMergedDocument property is set to true, the merged document will retain the name of the imported document. For more information, see Sending an Agreement Document for Parallel Review.

This property allows you to specify URLs for environments such as QA, Staging, or Dev.

(Optional) You can override the default URLs for the Preview and Production environments with specific URLs for different regions (such as North America, Europe, or Australia) by adding them to the admin property.

Use any of the following URLs per your Conga instance:

{
"QA":"https://rls-qa.congacloud.io",
"Dev":"https://rls-dev.congacloud.io",
"Preview-EU":"https://rls-preview.congacloud.eu",
"Prod-EU":"https://rls.congacloud.eu"
}

Use this property to configure CLM data sync from Salesforce to Advantage Platform.

{
"fwd_sync_url":"https://xxx.congacloud.io",
"organization-id":"5ba45b1e-2264-4063-be5f-xxxxxxxxxxx",
"organization-fid":"datatenant-clmst1-5ba86b1e-2268-4062-be9f-xxxxxxxxx", 
"user-id":"9743f384-c18c-4455-bfaa-xxxxxxxxxx"
}

Prerequisite: The Enable File comply system property must be enabled.

When the value is true, the Enable Content Search step is skipped during activation. To use the APTS_SkipContentSearchForActivation property, the value of the APTS_AutoContentSearchable must be False. For more information, see Activating an Agreement.

The APTS_SkipEmailTemplateSelection property allows you to indicate whether the email template selection step should be skipped. For more information, see Generating an Agreement.

When you are upgrading CLM to Spring '21 or a later version and need to migrate Attachments that are greater than 10 MB in size to Files, you must set this property to true.

Prerequisite: The Enable File comply system property must be enabled.

When the value is true, the remove draft document step is skipped during activation. To use the APTS_SkipRemoveDraftDocumentOnActivation property, the value of the APTS_AutoContentSearchable must be False. For more information, see Activating an Agreement.

This admin entry allows you to add a comma-separated list of status categories that can be blocked for an amended or renewed child agreement. By default, the system blocks updating the agreement if its status category is Terminated, Expired, or Cancelled. To block additional status categories from getting updated, add them to this admin entry, and the system does not change the status category and status of the child agreement.

This property allows you to specify agreement status categories that should not be changed to In Signatures after the agreement document is sent for DocuSign eSignature. Specify multiple status categories separated by comma.

If an agreement has any of the status categories specified in this property, the status remains unchanged after the document is sent for DocuSign eSignature.

This admin entry allows you to add a comma-separated list of status categories that can be updated for an amended or renewed child agreement. By default, the system blocks updating the agreement if its status category is Terminated, Expired, or Cancelled. To allow updates for agreements even when they are in these default blocked statuses, add them to this admin entry, and the system updates the status category and status of the child agreement.

This property allows you to specify agreement status categories that should be changed to In Signatures after the agreement document is sent for for DocuSign eSignature. Specify multiple status categories separated by comma.

If an agreement has any of the status categories specified in this property, the status is changed to In Signatures after the document is sent for DocuSign eSignature.

Values set in this property overrides the values set in APTS_StatusCategoriesToIncludeForDocuSign property.

For example, if Expired status category is specified APTS_StatusCategoriesToExcludeForDocuSign as well APTS_StatusCategoriesToExcludeForDocuSign property, then the status category of the agreement having current status category Expired, will be changed to In Signatures.

When the value of the property is true, you will be unsubscribed from parallel review emails (review completion, review error, and review cycle completion). This property is not applicable for review cancellation and ending review from CLM as the emails are sent from the user's domain.

The APTS_TemplateSelectionGuidance property allows you to add help text in the Template Selection page to guide users to select appropriate templates when users preview documents, generate documents, regenerate documents, and generate supporting documents. The help text is displayed above the template selection section. For more information, see Generating an Agreement.

When you set the APTS_TranslatePickValuesInDocs admin entry to true, the field value gets added in the generated document. If a conditional segment is set, the condition takes both API and values. You can either use API names or Values but not both.

When an administrator sets the APTS_TranslatePickValuesInDocs admin entry to false or does not add the admin entry, the API Name gets added in the generated document by default.

The APTS_UIPageConfig property is used to indicate the visual force page to perform the publish action. The integration module provides the Visualforce page Apttus_Content__PublishContent.

<UIPageConfig>
  <UIAction name="publish_document">
    <CustomPage>
      <Name>Apttus__PublishDocument<
      /Name>
    </CustomPage>
  </UIAction>
  <UIAction name="publish_content">
    <CustomPage>
      <Name>Apttus_Content__PublishContent</Name>
    </CustomPage>
  </UIAction>
  <UIAction name="publish_chatter">
    <CustomPage>
      <Name>Apttus__PublishChatter</Name>
    </CustomPage>
  <UIAction name="review_offlinedocument">
    <CustomPage>
      <Name>Apttus__ReviewOfflineDocumentLightning</Name>
    </CustomPage>
  </UIAction>
</UIPageConfig>

Apttus merge web service endpoint. For more information, see Contract Wizard in Classic.

The APTS_UseWorkflow property disables the creation of a default set of tasks when an agreement is generated. In some cases, the default tasks created to ensure Signing, Scanning, and Attaching the scanned image to the agreement record is redundant or is taken care of by a different workflow process. In such cases, the default behavior of the system needs to be modified to ensure those tasks are not created. For more information, see Managing Workflow.

When you set APTS_WizardPersistHiddenValue to true and you run a wizard containing a field that has a combination of Set this control value and Hide this control input rules, the field value is set in the object you are creating. When you set APTS_WizardPersistHiddenValue to false and you run a wizard containing a field that has a combination of Set this control value and Hide this control input rules, the field value is not set in the object you are creating. For more information, see Configuring Step Input Rules from the Wizard Designer.

The APTS_XAAddInLoadType property allows you to define the installation approach to access the X-Author for Contracts 2.0 add-in. You can use any one of the following supported values:

• centralized - If you install the X-Author for Contracts 2.0 add-in using Centralized Deployment via the Office 365 admin center, set The property value to "centralized". Centralized Deployment supports both Windows operating system and Mac operating system. For more information on installing X-Author for Contracts 2.0 add-in using Centralized Deployment, see Installing Production X-Author for Contracts 2.0.
• sideloading - If you are unable to install the X-Author for Contracts 2.0 add-in using Centralized Deployment in Office 365, alternatively you can install the add-in on the Mac system using the Sideloading approach. If you install the X-Author for Contracts 2.0 add-in on a Mac system using a manifest file, set The property value to "sideloading". For more information, contact Support.
• appsource - If you access the X-Author for Contracts 2.0 add-in using Microsoft Store, set The property value to "appsource". For more information, contact Support.

If The property is not defined, the Centralized Deployment approach is used to access the X-Author for Contracts 2.0 add-in.