About Release Notes

Apttus Release Notes contain the following information about Merge Service Winter 2019 Release on Salesforce. All implementations will need to have the Comply System properties, however, unless you have installed the Apttus Proposals Management package you do not need Proposal System properties.

Packages: Lists packages that are required to upgrade to this release of the product
New Features: Provides high-level descriptions of new features introduced in this release, with links to more detailed information
Enhancements: Provides high-level descriptions of enhancements to existing features
Resolved Issues: Lists customer-reported issues that are resolved in this release or known issues resolved from previous releases
Known Issues: Lists known issues that are applicable in this release

This documentation may contain descriptions of software features that are optional and for which you may not have purchased a license. As a result, your specific software solution and/or implementation may differ from those described in this document. Please contact your CSM or AE for information on your specific features and licensing.

Packages

The following packages and dependent packages are required to upgrade to this release to utilize all the new features of this release. These are the minimum required versions; later versions are also supported. Separate prerequisites for each feature can be found in the respective guides. The packages marked as (New) are new packages in this release.

Product	Latest Certified Version
Apttus Merge Service (New)	5.7.0.1125

Merge Service Pre-Release Configuration

By default, your production org references the GA version of Merge Service. If you had previously configured Merge Service for pre-release, you will need to change some settings to use the GA version of Merge Service. All Merge Service implementations need to have the Comply System properties. You need to configure Proposal System properties if you have installed the Apttus Proposals Management package.

Use the following URLs to upgrade to the pre-release version of Merge Service:

Merge Webservice Endpoint: https://mergews.apttus.net/cgi-bin/MergeServer/Bin/mmcgi.exe
Remote Site: https://mergews.apttus.net

The following configurations allow you to change your Merge Service or remote site settings:

To change your Merge Service setting

For Comply System Properties

Go to Setup > App Setup > Develop > Custom Settings.
Click Manage for Comply System Properties.
Click System Properties and the Merge Webservice Endpoint setting is displayed.
Change the setting to the merge webservice endpoint URL listed above or another URL provided by Apttus and click Save.

For Proposal System Properties

Go to Setup > App Setup > Develop > Custom Settings
Click Manage for Proposal System Properties.
Click System Properties and the Merge Service Endpoint setting is displayed.
Change the setting to the merge webservice endpoint URL listed above or another URL provided by Apttus and click Save.

To change your Remote Site setting

Go to Setup > Security Controls > Remote Site Settings.
Click Edit for ApttusMergeServer.
Change the Remote Site URL to the remote site URL listed above or another URL provided by Apttus and click Save.
Click Save.

If you would like to be engaged in our Pre-Release program for Merge Service, please reach out to your assigned CSM for details.

New Features

The following features are new to Merge Service in this release.

Updating Agreement Clauses Actions

Merge Service is involved in making a smart clause entry in the Agreement Clauses section with Action as Original when the Contract Management version is greater than 10.470. X-Author Contracts and X-Author Contracts for Cloud are involved in making a smart clause entry in the Agreement Clauses section with Action as Original when the Contract Management version is prior to 10.470.

Define Doc Assembly Rules for File Type Documents

You can now upload file type documents through Contract Mangement and access the document using Doc Assembly Rules.

Marking Smart Clauses as Original in Contract Management

When a document is generated or regenerated in the Contract Management, all the smart clauses are displayed in the Agreement Clauses section with Action as Original. When a document a regenerated, a new entry is created in the Agreement Clauses section even if the same clause already exists.

Ability to Use mergeDocsToPDF2 API to Add Custom Header or Footer Format

You can use mergeDocsToPDF2 API to add custom headers or footers in the merged document. In the Append mode if the horizontal alignment of the existing text is left-aligned, then the new text will be right-aligned. If the existing text is right-aligned, then the new text will be left-aligned. There will be no change in alignment if the text is center-aligned.

Limitations:

In Append or Overwrite mode only text is supported. Images and graphics are not supported.
In Append mode, any existing word table, repeat table, or repeat section structure in the header or footer is not retained and is converted to plain text. The text from the table or section is appended with the new value.
If the text value is not set in the custom footer configuration, then the Date Time format configured in the comply system property is considered as the default value. The Date Time format string (e.g. ddMMyy) is displayed but not the actual date.
The font provided in the custom header or footer are displayed based on the following factors:
- If the font is supported by the PDF viewer then the same font is displayed.
- If the font is not supported by the PDF viewer, then the font may be replaced with an appropriate font as per the PDF viewer or may not display properly.
When the page size differs for the different documents merged, the header and footer will be inconsistently displayed.
When header or footer is added in Turkish, Russian, or Chinese language few characters are not getting added.

Enhancements

Inserting Page Break

You can now use the Insert Page Break option in Contract Management when you use Dynamic Document Assembly Rulesets to insert clauses in X-Author Contracts.

Limitations:

If the dynamic segment is the last element in the document, an additional empty page is created at the end of the document.
When there is an image in the Doc Assembly Component content, page breaks might be inconsistent.
If the Doc Assembly Component type is attachment or attachment_parent and the content of the attachment ends exactly when it has reached the character limit of the page, then an empty page might be inserted as a result of the page break.
If the text wrapping for images and shapes is other than In Line With Text, the page breaks might be inconsistent.

Resolved Issues

The following table lists the issues resolved in this release.

Case Number	Apttus Internal ID	Description
CAS-16925-M9T8P6	MS-1448	Insert page break option in Doc Assembly Ruleset component was not working.
CAS-17563-M9J2S5	MS-1423	Doc Assembly Rule was not compatible with File type documents in Salesforce Lightning.
DFCT0064797	MS-1429	Merge service did not remove clause list metadata from document generation.
NA	MS-1455	When multiple documents were combined through Merge Service, the resulting document was not reconcilable.
NA	MS-1462	A user was unable to use Sort Order and Conditional Expression functionality together.

Known Issues

The following table provides the cumulative list of known issues up to this release.

Apttus Internal ID	Issue
MS-1478	Regenerating with redlines corrupts the agreement document when the document has an image or hyperlink.
MS-1381	When a user generates an agreement document with special characters in the agreement line items, the special characters are replaced with its ASCII equivalent.
MS-1465	A user gets 500 response while processing a smart cart request when source type was file.
MS-1412	When Conditional Segment in X-Author Contracts for Cloud templates has Less Than and Not Equal To operator for the date field, the field-level validation fails.
MS-1385	When the Parallel Review setting is enabled and Version Aware is disabled, a user was able to edit the documents sent for review with protection.
MS-1475	When Conditional Segment in X-Author Contracts for Cloud starts with an operator, the condition fails.
MS-1482	When a user inserts Doc Assembly Ruleset, the user gets an error that one of the input documents has invalid items.
MS-1477	A decline in performance is observed while generating a proposal containing more than 40,000 line items.
MS-1476	On sending a request to combine documents through CreateWordPackage API, a user guide returns 500 error response.
MS-1474	A user observed incorrect number precision is added for Switzerland (fr-CH) locale.
MS-1465	When a user uploads an XML document as a File after switching to Salesforce Lightning, the user is unable to generate document for a proposal after adding proposal line items. Workaround: Attachments that are uploaded as Files are supported when the Salesforce API version as part of the SOAP URL sent in the request to MergeService is greater than or equal to 31.0.
MS-1381	When a user-generated an agreement document with special characters in the agreement line items, the special characters in the document are replaced with ASCII characters.
MS-1345	Revised document changes are not available on the final merged document when you perform the following tasks: Generate an agreement. Change a few values in Contract Management on Salesforce. Regenerate the agreement with the same template used for generating the agreement. Go to X-Author Contracts for Cloud > Compare tab. Merge the generated document version and regenerated document version.
MS-1318	The Reference field does not display a currency symbol according to the reference object while generating an agreement.

Apttus Copyright Disclaimer

Error rendering macro 'excerpt-include'

User 'null' does not have permission to view the page.

DOC ID: MSSFWIN19RN20191130

Download PDF

Merge Service on Salesforce Winter 2019 Release Notes