This document notes the major software developments for IntelleDoc Solutions from version 6.53 to 9.121.
IntelleDoc Solutions have been updated to improve metadata structure and include SIGNiX support for signers that have multiple signing locations. Reference: CHANGE-8196
IntelleDoc Solutions have been updated to preserve data related to Borrower Authorized Signer capacity when resuming a Compliance Safety Net session so data does not have to be re-entered. Reference: CHANGE-8118
The latest calculation engine update from Sherman & Associates is included in this version of IntelleDoc Solutions. This affects only those users who are licensed for Payment Calculations in Compliance Safety Net. Reference: CHANGE-8099
IntelleDoc Solutions have been updated to address an issue where attempting to execute job tickets for deposit transactions would result in intermittent errors. Reference: CHANGE-7875
IntelleDoc Solutions have been updated to support digital signature initials without a mapping path for a specific financial institution. Reference: CHANGE-8156
IntelleDoc Solutions have been updated so that Configuration correctly displays licensed products. Reference: CHANGE-8054
The latest calculation engine update from Sherman & Associates is included in this version of IntelleDoc Solutions. This affects only those users who are licensed for Payment Calculations in Compliance Safety Net. Reference: CHANGE-7761
IntelleDoc Solutions have been updated to address an issue where the DepositHolderEntityIDList would not always display all entities as expected. Reference: CHANGE-7982
IntelleDoc Solutions have been updated to support a CleanEntityNames job ticket call to prevent deletion of middle and last names that match the first name for entities during the TXL merge process. Reference: CHANGE-7818
IntelleDoc Solutions have been updated to add support for the use of checkboxes in static custom documents. Reference: CHANGE-7763
IntelleDoc Solutions have been updated to address an issue related to passing in null values when launching a new instance of Compliance Safety Net. Reference: CHANGE-7693
IntelleDoc Solutions have been updated to accommodate the SIGNiX limit of 100 characters for field length. Reference: CHANGE-7610
Internal logic has been modified to add support for suffixed data in Multiple Account transactions. Reference: CHANGE-7620
The latest calculation engine update from Sherman & Associates is included in this version of IntelleDoc Solutions. This affects only those users who are licensed for Payment Calculations in Compliance Safety Net. Reference: CHANGE-7480
IntelleDoc Solutions have been updated so that visible borders have been removed from the e-sign template for IMM digital signature providers. Reference: CHANGE-7540
IntelleDoc Solutions have been updated to prevent the interest rate from rendering as the scientific notation representation of a numeric value in some instances. Reference: CHANGE-7499
IntelleDoc Visualizer has been updated to support generation of TXL files. Reference: CHANGE-7441
IntelleDoc Solutions have been updated to add support for the creation of promptable UCC-1 descriptions. If these descriptions are defined in Configuration, they will appear on the UCC tab in Compliance Safety Net. Reference: CHANGE-7015
IntelleDoc Solutions have been updated to address an issue where the DocuSign e-signature date would be displayed over the word (SEAL) and made the year portion of the date unreadable. Reference: CHANGE-6615
Some third-party upgrades were performed to improve the security of IntelleDoc Solutions. Reference: CHANGE-7487
IntelleDoc Solutions have been updated to support a Referenced Security Documents tab that has been added to the Loans workflow of Compliance Safety Net to capture document references. Reference: CHANGE-7019
IntelleDoc Solutions have been updated prevents partial document packages from being returned in production settings. In the event of a document render failure, end users will not receive any documents, which safeguards the integrity of the transaction regardless of failure reasons. Reference: CHANGE-7466
Compliance Service has been updated to provide better error handling. Reference: CHANGE-7393
IntelleDoc Solutions have been updated to address an issue that was causing the update of Sherman config files to fail. Reference: CHANGE-7311
IntelleDoc Solutions have been updated to address an issue where Transaction Server references were missing from our external NuGet server. Reference: CHANGE-7430
Compliance Service has been updated to support PDF downloads. Reference: CHANGE-7231
IntelleDoc Solutions have been updated to support PDF downloads. Please note that you must update calls to the new WSDL. Reference: CHANGE-7230
IntelleDoc Solutions have been updated so that the models support returning a URL in the JobOutputData. Reference: CHANGE-7228
A new endpoint has been added to IntelleDoc Solutions to support document retrieval external to the render response. This update was made to reduce the size of the render response. Reference: CHANGE-7221
IntelleDoc Solutions have been updated to address an issue where the DL2137 Request for TIN And Certification W9 document listed the incorrect signer for co-borrowers. Reference: CHANGE-7305
The latest calculation engine update from Sherman & Associates is included in this version of IntelleDoc Solutions. This affects only those users who are licensed for Payment Calculations in Compliance Safety Net. Reference: CHANGE-7175
Internal logic has been updated to ensure that the DL6050 Garnishment Protection Waiver, DL6613 Name Affidavit, and DL2137 Request for TIN And Certification W9 documents render properly with IntelleDoc versions 9.91 and higher. Reference: CHANGE-7191
Prior to this update, the DCL would log an error message for every DSL call and every document selected by this call. These messages would appear in the responses, increasing the payloads to Compliance Safety Net and were logged by both systems. As a result of this update, document selection logic messages have been removed from our responses. This update was made to reduce the size of our responses and increase overall performance. Reference: CHANGE-7201
IntelleDoc Solutions have been updated to improve the way certain entity paths are handled. This update was made to support an upcoming change related to signing agent functionality. Reference: CHANGE-7132
IntelleDoc Solutions have been updated to support job ticket calls that suppress TouchedDatapoints and DocumentInfo from the RenderDocument response. Partners who do not use this information can reduce the size of these responses and increase overall performance. Please note that you must update calls to the new WSDL. Reference: CHANGE-7154
IntelleDoc Solutions have been updated to support combining applications for joint applicants using Credit Applicant associations. Reference: CHANGE-7143
IntelleDoc Solutions have been updated to address an issue where the SelectDocuments API response would randomly return additional content, making the payload and response time increase significantly. Reference: CHANGE-7152
The latest calculation engine update from Sherman & Associates is included in this version of IntelleDoc Solutions. This affects only those users who are licensed for Payment Calculations in Compliance Safety Net. Reference: CHANGE-6951
Internal logic has been updated related to the payoff amounts displayed on the DL6060 Summary Of Loan Decision document. Reference: CHANGE-6982
IntelleDoc Solutions have been updated to include SmartSign Plus API support. Reference: CHANGE-6833
IntelleDoc Solutions have been updated to address issues with entity and role associations. Please note that you must update calls to the new WSDL. Reference: CHANGE-6429
IntelleDoc Solutions have been updated to allow users to hide optional fields in Compliance Safety Net that are not defined in Configuration. Reference: CHANGE-6434
IntelleDoc Solutions have been updated to address an issue where suffixed selection criteria was not functioning as expected when SelectDocuments/RenderDocument functionality to render documents is used. Reference: CHANGE-6786
IntelleDoc Solutions have been updated to add support for SIGNiX to the generic sidecar. Please note that you must update calls to the new WSDL. Reference: CHANGE-6578
IntelleDoc Solutions have been updated to improve the scalability of the Compliance Service application. Reference: CHANGE-5496
CHANGE-6242 and CHANGE-6603 attempted to address an issue where deleting portions of a concatenated field in Compliance Safety Net would result in deleted values rendering on documents. Additional work has been completed to address an issue that would result in an XML parsing error. Reference: CHANGE-6643
IntelleDoc Solutions have been updated to include Adobe Acrobat Sign e-signature support. Reference: CHANGE-6629
CHANGE-6242 attempted to address an issue where deleting portions of a concatenated field in Compliance Safety Net would result in deleted values rendering on documents. Additional work has been completed to address an issue where deleting concatenated fields that included nonindividual data would result in an XML parsing error. Reference: CHANGE-6603
CHANGE-3765 added functionality so that a supplemental FXL file is automatically discovered by IntelleDoc Solutions and is used to extend a document’s data dictionary. It was discovered that this functionality worked correctly for SelectDocuments and RenderDocument requests but did not work correctly for RenderDocumentSet requests. IntelleDoc Solutions have been updated to correct this issue. Reference: CHANGE-3925
IntelleDoc Solutions have been updated so that the Visualizer WSDL is in sync with the referenced Compliance Service WSDL. Reference: CHANGE-6418
IntelleDoc Solutions have been updated to address an issue where deleting portions of a concatenated field in Compliance Safety Net would result in deleted values rendering on documents. Reference: CHANGE-6242
IntelleDoc Solutions have been updated so that the IMMeSign generic sidecar returns the entity ID instead of the party index. Reference: CHANGE-6405
IntelleDoc Solutions have been updated to address issues related to the handling of DocumentDataValues in Compliance Safety Net. Reference: CHANGE-6253
IntelleDoc Solutions have been updated to support e-signature document suppression. Reference: CHANGE-6233
The latest calculation engine update from Sherman & Associates is included in this version of IntelleDoc Solutions. This affects only those users who are licensed for Payment Calculations in Compliance Safety Net. Reference: CHANGE-6261
IntelleDoc Solutions have been updated to revert a recent change due to unexpected WSDL impact. Reference: CHANGE-6256
IntelleDoc Solutions have been updated to address an issue where the digital signature generic sidecar DocumentID did not always match for Documents and Signers. Reference: CHANGE-6180
IntelleDoc Solutions have been updated to add support for IMMeSign to the generic sidecar. Please note that you must update calls to the new WSDL. Reference: CHANGE-6041
Version 9.74 of Compliance Service included an update to the WSDL file that may necessitate a software update for partner applications. This version is now available in DEV and TEST to verify if software changes are required to use this version to render documents. This change was made to support a new digital signature provider. Reference: CHANGE-5963
IntelleDoc Solutions have been updated to improve the behavior of hidden and locked data as it relates to the Partner TXL. Reference: CHANGE-5963
IntelleDoc Solutions have been updated to improve the sorting of multiple data elements when alphabetical sorting is used. Reference: CHANGE-5855
IntelleDoc Solutions have been updated to address an issue where document-specific values in DocumentDataValues would display on all documents instead of only the expected documents. Reference: CHANGE-5849
IntelleDoc Solutions have been updated to address an issue where leading printline tags in static document fields would result in an error. Reference: CHANGE-5960
IntelleDoc Solutions have been updated to address an issue where entity names could fail to render as expected on documents. Reference: CHANGE-5885
IntelleDoc Solutions have been updated to add support for DocuSignXY to the generic sidecar. Please note that you must update calls to the new WSDL. Reference: CHANGE-5846
IntelleDoc Solutions have been updated to incorporate several changes to the returned generic sidecar metadata file. Reference: CHANGE-5658
IntelleDoc Solutions have been updated to support High Cost Mortgage and Higher Priced Mortgage Loan qualification analysis, and Sherman calculation messaging has been updated to reflect this implementation. Reference: CHANGE-4263
CHANGE-4078 attempted to improve the performance of IntelleDoc Solutions and address minor issues with memory and threading. An internal root cause analysis determined that objects were being left in memory unexpectedly. This ticket resolves the issue by making calls to the dispose method for the objects in the affected classes and properly releasing those resources. Reference: CHANGE-5606
IntelleDoc Solutions have been updated to include Document SubStatus functionality by adding a Document Limiter button to Compliance Safety Net to support partial document return. Reference: CHANGE-5455
The latest calculation engine update from Sherman & Associates is included in this version of IntelleDoc Solutions. Reference: CHANGE-5335
An update has been made to address an error related to the DatapointNameComparer component of IntelleDoc Solutions. CHANGE-5309
IntelleDoc Solutions have been updated to remove a deprecated NuGet package from the IntelleDoc NuGet repository. Reference: CHANGE-4106
IntelleDoc Solutions have been updated to separate the third-party iTextSharp NuGet package from the main IntelleDoc NuGet repository. Reference: CHANGE-5262
Internal logic has been updated to improve the performance of IntelleDoc Solutions and address minor issues with memory and threading. Reference: CHANGE-4078
IntelleDoc Solutions have been updated to provide improved error messaging related to Sherman Calculations. Reference: CHANGE-5111
IntelleDoc Solutions have been updated to parse XML files in a way that meets PCI Data Security Standard third-party scan requirements. Reference: CHANGE-5083
IntelleDoc Solutions have been updated to include e-signature support for a specific institution. Reference: CHANGE-4775
The ResizeDynamicField function has been modified to properly resize the height of the digital signature field and round the calculated height to the nearest integer instead of truncating. Additionally, a minimum height of 0.347 inches has been applied. Reference: CHANGE-4948
In support of multiple accounts, we made an internal class change to IntelleDoc Solutions. It was discovered that this property was unnecessarily being serialized and included in API output. This serialization has been removed to prevent any potential performance issues. Reference: CHANGE-4917
It was discovered that the first two characters of a Sherman exception message may not always display for users. This issue has been corrected. Reference: CHANGE-4916
IntelleDoc Solutions have been updated so that when the font size adjustment is applied, it does not override the font size attribute in the OXL file content. This content is generally used for barcodes and adjustments applied may make barcodes unreadable. Reference: CHANGE-4804
IntelleDoc Solutions have been updated so that when the font size adjustment is applied, it does not override the font size attributes for model form dynamic documents. These documents are designed with very strict formatting and adjustments applied to this content would make these documents noncompliant. Reference: CHANGE-4803
IntelleDoc Solutions have been updated to include unique e-signature tags for multiple signature lines on a single document for users of the MeridianLink e-signature output option. Reference: CHANGE-4152
IntelleDoc Solutions have been updated to address a versioning issue with the build process. Reference: CHANGE-4712
IntelleDoc Solutions have been updated to honor the DocumentDataValues provided for each document when presented as a defaultable TXL file. Please note that this behavior is not applicable when a mapping path is provided; mapping path values take precedence over datapoint values. Reference: CHANGE-4605
Null checks have been added to allow the evaluation of “or” conditions without throwing errors. Reference: 4607
IntelleDoc Solutions have been updated to make enhancements to license keys, including the addition of UCC-1 E-Filing support. Reference: CHANGE-4403
IntelleDoc Solutions have been updated to support opening multiple deposit accounts in a single transaction. Reference: CHANGE-3315
IntelleDoc Solutions have been updated to include an updated version of the Sherman Calculation Engine to better support construction loans. This affects only those users who are licensed for Payment Calculations in Compliance Safety Net. Reference: CHANGE-3903
There were some isolated data entry scenarios where suffixed datapoint information that was edited in Compliance Safety Net was being sent to IntelleDoc Solutions in a way that could potentially cause erroneous linking and invalid ID warning messages. Reference: CHANGE-4260
Prior to this update, IntelleDoc Solutions logged closed loan counts for Sherman Loans and Associates. As a result of this update, IntelleDoc Solutions have the ability to log all closed loans, regardless of Sherman usage. Reference: CHANGE-3922
Mapping paths have been updated so that issuing institutions are separated out per document when multiple Control Agreement documents are returned in a transaction. Reference: CHANGE-3901
IntelleDoc Solutions have been updated to address an issue where the HELOC Agreement document was displaying incorrect margins. Reference: CHANGE-4112
Prior to this update, scenarios that involved multiple collateral types would result in Hypothecator signature blocks being displayed on collateral-related documents where they were not expected. As a result of this update, Hypothecator signature blocks should only appear on appropriate collateral-related documents. Reference: CHANGE-3780
IntelleDoc Solutions have been updated to change the datapoint used to indicate if a document is a recordable document. When this change was initially merged, IntelleDoc Solutions could not mark documents as recordable, but that issue has been resolved. Reference: CHANGE-3872
There were situations where documents would not always render as expected due to datapoint references that were not included in that document’s data dictionary. As a result of this update, a supplemental FXL file is now automatically discovered by IntelleDoc Solutions and is used to extend a document’s data dictionary. Reference: CHANGE-3765
IntelleDoc Solutions have been updated to address an issue where attempting to replace default repayment language would result in unexpected spacing behaviors. Reference: CHANGE-3686
IntelleDoc Solutions have been updated to provide improved error messaging related to digital signature values. Reference: CHANGE-3611
IntelleDoc Solutions have been updated to support an Other Entity Role option for the association level of a dynamic custom document in Configuration. Reference: CHANGE-3809
Version 9.44 of IntelleDoc Solutions included a calculation engine update from Sherman & Associates. It was discovered that there was an issue with the calculation of odd first payment loans. IntelleDoc Solutions have been updated with a new version of the Sherman Calculation Engine to correct this issue. Reference: CHANGE-3790
Prior to this update, partners could modify job tickets in a way that would increase the font size of only recordable documents by the number of specified points. IntelleDoc Solutions have been updated to extend this functionality; partners can now modify job tickets in a way that will decrease the font size of not only recordable documents, but the entire document set. Reference: CHANGE-3683
The latest calculation engine update from Sherman & Associates is included in this version of IntelleDoc Solutions. This affects only those users who are licensed for Payment Calculations in Compliance Safety Net. Reference: CHANGE-3747
Prior to this update, attempting to render a custom document with a certain combination of scripted data would result in an error. Reference: CHANGE-3754
Support for DocuSign has been updated to remove date stamps from initialed fields. Please note that no changes have been made to these date stamps for full signature fields. Reference: CHANGE-3403
IntelleDoc Solutions have been updated to include an additional option of immediately sending emails when using IMM eSign transaction forwarding. Reference: CHANGE-3584
IntelleDoc Solutions have been updated to support HTML rendering for transactions. Reference: CHANGE-3213
IntelleDoc Solutions have been updated to address an issue where checking the Make blank line checkbox in Compliance Safety Net would not always be saved in transaction data. Reference: CHANGE-3581
IntelleDoc Solutions have been updated to address performance issues and slow response times related to the Compliance Safety Net Session API call. Reference: CHANGE-3534
CHANGE-2969 added support for direct send to IMM for e-signatures. Additional changes have been made to also support RenderDocumentSet job ticket calls in this process. Reference: CHANGE-3368
Changes have been made to resolve data flow issues and improve functionality of the Uniform Residential Loan Application (URLA) and URLA Additional Borrower documents. Reference: CHANGE-3025
IntelleDoc Solutions have been updated to add optional TRID calculations for partners licensed for Payment Calculations in Compliance Safety Net. These new calculations may be enabled in Configuration and include the amounts of Closing Costs Financed, Down Payment/Funds From Borrower, and Funds For Borrower. Reference: CHANGE-3327
IntelleDoc Solutions have been updated to support data flow to static custom documents in Compliance Safety Net in the same way as static stock documents. Reference: CHANGE-2983
IntelleDoc Solutions have been updated to allow the creation of user-defined lists of data element options in Configuration. Reference: CHANGE-2415
Several enhancements were made to the Assignment of Leases and Rents document. Reference: CHANGE-2347
IntelleDoc Solutions have been updated to address an issue with logging closed loan counts for Sherman Calculation Engine users. Reference: CHANGE-3452
Prior to this update, the use of square brackets in entity and collateral IDs could cause IntelleDoc Visualizer to crash. Updates have been made to correct this issue. Reference: CHANGE-3449
IntelleDoc Solutions have been updated to allow multiple data sets from the same category to be associated with a single selection group in Configuration. This new functionality is currently only supported for the Credit Card workflow. Reference: CHANGE-2981
CHANGE-3378 added a new SignerIdOverride property to digital signature JSON values to override index value in PDF field names for DocuSign and was only relevant for platform systems that use MeridianLink as an e-signature output option. This functionality has now been extended to platform systems that use DocuSign and DocuSignXY as e-signature output options. Reference: CHANGE-3395
IntelleDoc Solutions have been updated to lock certain APY calculator fields to prevent users from modifying data, since this could result in compliance violations. Reference: CHANGE-3343
IntelleDoc Solutions have been updated to add a new SignerIdOverride property to digital signature JSON values to override index value in PDF field names for DocuSign. This update is only relevant for those particular platform systems that use MeridianLink as an e-signature output option. Reference: CHANGE-3378
CHANGE-3339 attempted to address an issue where sending a Transaction request only returned a single PDF file. Additional updates have been made to correct this issue. Reference: CHANGE-3341
CHANGE-2969 added support for direct send to IMM for e-signatures. Additional changes have been made to fully support transaction forwarding access through a DCL JSON call. Reference: CHANGE-3334
IntelleDoc Solutions have been updated to add licensing for consumer credit card lending. Reference: CHANGE-3007
Several enhancements have been made to documents related to Resolutions. Reference: CHANGE-3380
IntelleDoc Solutions have been updated to support consumer credit card lending. Reference: CHANGE-3169
In the previous version of IntelleDoc Solutions (only released to the DEV environment), there was an issue where sending a Transaction request only returned a single PDF file. This issue has been corrected and sending a Transaction request now returns all PDF files. Reference: CHANGE-3339
IntelleDoc Solutions have been updated to include an updated version of the Sherman Calculation Engine to support custom accrual methods for farm credit lending institutions. Reference: CHANGE-3298
IntelleDoc Solutions have been updated to address a data handling error when attempting to use the Payment Calculations workflow in Compliance Safety Net. Reference: CHANGE-3279
IntelleDoc Solutions have been updated to support direct send to IMM for e-signatures. Reference: CHANGE-2969
There were some situations where partner platform systems that render transactions with separate PDF files would have issues rendering documents. This issue has been corrected. Reference: CHANGE-3264
IntelleDoc Solutions have been updated to support a barcode font that includes human readable text. Reference: CHANGE-3225
IntelleDoc Solutions have been updated to address an issue where HELOC fees could not be changed and would revert automatically to the values pulled in from Configuration. Reference: CHANGE-3205
This change implemented support for: (1) the 30⁄360 accrual method when calculating an Effective Interest Rate on closed-end loans; and (2) a custom accrual method when calculating odd first payment loans. Reference: CHANGE-3078
IntelleDoc Solutions have been updated to add a data anonymization call to the DCL. Reference: CHANGE-3208
Prior to this change, there were some configuration combinations that resulted in duplicate Loan Summary documents being rendered for the transaction. IntelleDoc Solutions have been updated to better handle these situations and return a single Loan Summary document. Reference: CHANGE-3203
IntelleDoc Solutions have been updated to support JSON in the DCL interface. Reference: CHANGE-3187
IntelleDoc Visualizer has been updated to include a TXL/JSON converter. Reference: CHANGE-3181
IntelleDoc Solutions have been updated to support SBA Lending transactions. Reference: CHANGE-3166
CHANGE-2960 modified the behavior when providing a document library version number. Additional updates have been made to improve this behavior. Reference: CHANGE-3138
Some third-party upgrades were performed to improve the security of IntelleDoc Solutions. Reference: CHANGE-2870
Prior to this update, there were times when static documents would fail to render if digital signatures were missing. IntelleDoc Solutions have been updated to improve the handling of these situations. Reference: CHANGE-3157
IntelleDoc Solutions have been updated to randomize the generation of job identifiers. Reference: CHANGE-2946
IntelleDoc Solutions have been updated to address several HTML output issues related to spacing, text, and formatting in Configuration. Reference: CHANGE-2912
IntelleDoc Solutions have been updated to address an issue where PDF previews would not always render as a combined document when expected. This issue occurred when the transaction included PDFs that were uploaded from Configuration. Reference: CHANGE-3032
IntelleDoc Solutions have been updated to support the addition of new workflows in Compliance Safety Net. Reference: CHANGE-2875
Configuration has been updated to allow users to add and suppress standard TruStage Compliance Solutions documents from the Manage Content tab of the Selection Groups activity. When this functionality is turned on, Configuration makes an API call with the current document library and license key and returns a list of all standard documents that the institution is licensed for. These additions and suppressions are reflected in Compliance Safety Net transactions.
Please note the following:
Reference: CHANGE-1874, CHANGE-2419
IntelleDoc Solutions have been updated to support custom accrual methods. Reference: CHANGE-3023
Internal logic has been updated to appropriately link authorized signers to non-individual authorized signers, fiduciary appointees, or trustees. Reference: CHANGE-2750
IntelleDoc Solutions have been updated to address an issue where the URLA would sometimes result in an error. This was caused by an invalid suffix and has been corrected. Reference: CHANGE-2956
Internal logic has been updated to improve the performance of IntelleDoc Solutions. Reference: CHANGE-2475
Prior to this update, Compliance Safety Net would always use the latest retro version of a document library, regardless of what version number was provided. Internal logic has been updated so that providing all three segments of the document library version (2019.600.0) uses that specific version if it is available, while providing two segments (2019.600) uses the latest patched version. Reference: CHANGE-2960
Previously, an unhandled exception would cause the IntelleDoc Transaction Server Service to crash. This error is now handled in a way that is more informative and prevents the IntelleDoc Transaction Server Service from crashing. Reference: CHANGE-2899
There were some situations where Base64 strings would render on documents instead of logos as expected. This issue has been corrected. Reference: CHANGE-2845
Prior to this update, the Spousal Notice of Credit Transaction would render with an error when the non-participating spouse was also the Hypothecator. This was caused by an issue with role filtering and has been corrected. Reference: CHANGE-3130
There were some scenarios where commercial transactions involving several pieces of collateral would cause system instability, including long wait times or session timeouts in Compliance Safety Net. This issue has been corrected. Reference: CHANGE-3084
IntelleDoc Solutions have been updated to address an issue with a specific partner’s integration to DocuSign. Please note that this issue has been confirmed to be isolated and that other partners and clients should not be affected by this issue. Reference: CHANGE-3079
IntelleDoc Solutions have been updated to remove the Byte Order Mark from the Digital Signature Provider sidecar in responses and files. Reference: CHANGE-3057
Prior to this update, there were some scenarios where users with a specific configuration could not download documents using the Deal Maker functionality in Compliance Safety Net. This issue has been corrected. Reference: CHANGE-3049
Various pieces of DocuSign metadata have been updated to improve the user experience. Reference: CHANGE-2959
Prior to this update, when attempting to render documents for multiple entities and roles in the same transaction, the documents would not always render as expected. This issue has been resolved. Reference: CHANGE-2982
IntelleDoc Solutions have been updated to correct association issues by resolving mapping paths with guarantor signer and attestor roles. Reference: CHANGE-2842
CHANGE-2641 extended the support for Adobe Sign. Some of the documents produced for this integration were not able to be imported by Adobe Sign. This issue has been corrected. Reference: CHANGE-2807
IntelleDoc Visualizer has been updated to support a config ID that suppresses the Payment Calculation workflow of Compliance Safety Net. Reference: CHANGE-2711
Prior to this update, there were occasional failures with decrypted FXLs due to inadvertent content changes. This issue has been corrected. Reference: CHANGE-2628
IntelleDoc Solutions have been updated to remove the deprecated ShermanPath setting. Reference: CHANGE-2613
Prior to this update, there were situations where the ordering of entity IDs in the CollateralOwnerEntityIDList would switch and cause an error. This issue was caused by IntelleDoc incorrectly handling multiple TXLs and has been corrected. Reference: CHANGE-2376
IntelleDoc Solutions have been updated to the Microsoft .NET framework 4.8. Reference: CHANGE-2791
Compliance Service has been updated to support the option to only display bar codes on the first page of documents. Reference: CHANGE-2747
IntelleDoc Solutions have been updated to support TruStage Compliance Solutions’ online account opening solution. Reference: CHANGE-2506
There was an issue where the commercial RESI preview showed missing data and did not render as expected. This issue has been corrected. Reference: CHANGE-2764, BUG-6305
IntelleDoc Visualizer has been updated to replace all master/slave terminology with primary/subordinate. Reference: CHANGE-2698
IntelleDoc Solutions have been updated to allow non-cloud partners to write PDFs to disk. Reference: CHANGE-2581
There were some scenarios where data was disappearing from card application transactions. This issue has been corrected. Reference: CHANGE-2411
INTELLEDOC-3419 added initial Adobe Sign support. Additional updates have been made in IntelleDoc Solutions to extend and improve the support for Adobe Sign. Reference: CHANGE-2641
There was an issue where some borrower authorized signers and their titles were rendering on documents incompletely or incorrectly. This issue has been corrected. Reference: CHANGE-2725
There were certain situations where signature blocks were missing information on rendered documents. This was caused by an issue with role filtering and has been corrected. Reference: CHANGE-2724
The last release attempted to resolve an issue where the Certification of Beneficial Ownership document was not rendering in certain scenarios due to an IntelleDoc association issue. Additional changes were made and this issue is now resolved. Reference: CHANGE-2699
There was an issue where users could not edit their static custom documents after updating Compliance Safety Net. This issue has been resolved. Reference: CHANGE-2697
Internal logic has been updated to improve the stability of the automated testing tool used by TruStage Compliance Solutions. Reference: CHANGE-2665
CHANGE-2280 added support for DocuSign that included fixed and absolute positions for fields and tabs. Additional updates have been made in IntelleDoc Solutions to add support for a second eSignature SignatureMetaData format that provides the field positions of the tabs. Reference: CHANGE-2584
Compliance Service has been updated with a new product feature called Deal Maker. Deal Maker outputs documents in an unlocked PDF for editing by an institution’s counsel. Please contact TruStage Compliance Solutions for more information about licensing this product offering. Reference: CHANGE-2396
IntelleDoc Solutions have been updated to remove password protection from custom documents. This allows users to modify their custom documents as needed after transaction rendering. Reference: CHANGE-2378
IntelleDoc Solutions have been updated to support more predictable timing of Sherman file downloads. Reference: CHANGE-2587
Several updates were made to improve the performance of IntelleDoc Visualizer. Reference: CHANGE-2580
IntelleDoc Solutions have been updated for cloud partners to embed non-standard fonts by default. Previously, the default behavior was to embed all fonts. Reference: CHANGE-2482
There was an issue where the Certification of Beneficial Ownership document was not rendering in certain scenarios due to an IntelleDoc association issue. This issue was limited to versions 2.25 to 2.31 of Compliance Safety Net and is now resolved. Reference: CHANGE-2501
IntelleDoc Solutions have been updated to correct an issue with the size of some signature fields. Reference: INTELLEDOC-2301
IntelleDoc Solutions have been updated for non-cloud partners to correct an issue where document sets would fail to render if they included PDF input files. Reference: IR-18291
IntelleDoc Solutions have been updated to correct a document selection issue that was caused when invalid characters were used in datapoint names. Reference: IR-18370
Compliance Service has been updated to correct an issue where certain characters supplied to entity middle name/initial fields were not rendering in the output documentation. Reference: CHANGE-2139
Support for DocuSign has been updated to include fixed and absolute positions for fields and tabs. Reference: CHANGE-2280
IntelleDoc Visualizer has been updated to connect to the Cloud for internal TruStage Compliance Solutions triage and data analysis only. This feature is not yet intended for external use by partners. Reference: CHANGE-2301, CHANGE-2324
Updates have been made to support individual borrowers pledging commercial collateral in consumer transactions. This update was made available in document library version 2019.199.0. Reference: CHANGE-2177
Updates have been made to correct an issue where the debug option to output a merged TXL was inadvertently broken. Reference: INTELLEDOC-3361
There were some situations where there was a significant increase in the amount of time it took to render documents for the first time after updating. This issue has been corrected. Reference: INTELLEDOC-3606
Previously, assets and liabilities were not being filtered correctly. This caused incorrect data on some documents. This has been corrected. Reference: CHANGE-2083
IntelleDoc Solutions have been updated to add an additional SignatureProviderType option of MeridianLink which is an E-Signature output option implemented for compatibility with particular platform systems. Reference: CHANGE-1929
The 2019 Q1 calculation engine update from Sherman & Associates is included in this update. This affects only those users who are licensed for the Payment Calculation workflow in Compliance Safety Net.
Previously, code and logic existed around certain key data elements for the Deposit DSL. This code and logic have been moved in the Deposit.FXL. It depends on some updates in this version of the IntelleDoc Solutions components. Document Library 2018.313.0 and later will require this new IntelleDoc Solutions 8.0. Reference: INTELLEDOC-3514
Previously, the FarmProductBuyer association was not always working correctly, leading to scenarios where the user would receive an incorrect number of copies and associated data for the NoticeOfSecurityInterestInFarmProducts.FXL. This has been corrected. Reference: INTELLEDOC-3566
The E-Signature support in IntelleDoc Solutions has a new option for the SignatureProviderType. This option is to output the PDFs ready for the Adobe Sign E-Signature system. Reference: INTELLEDOC-3419
Previously, the E-Signature output support for DocuSign generated sidecar metadata that looked like this:
<Tab>
<RecipientID>BORROWER_ONE</RecipientID>
<Type>SignHere</Type>
<TabLabel>BORROWER_ONE.DocuSignSignHere.l_gnl_name_borr_digitalsignature.borrower1.1</TabLabel>
</Tab>
In certain DocuSign integrations, that system would report an error message saying Page number not specified in tab element. Page Number or AnchorTabItem missing for tab ‘SignHere’.
As of this version of Compliance Service, you will receive this XML with the additional AnchorTabItem which should solve this issue with DocuSign. Example:
<Tab>
<RecipientID>BORROWER_ONE</RecipientID>
<Type>SignHere</Type>
<TabLabel>BORROWER_ONE.DocuSignSignHere.l_gnl_name_borr_digitalsignature.borrower1.1</TabLabel>
<AnchorTabItem>
<AnchorTabString>BORROWER_ONE.DocuSignSignHere.l_gnl_name_borr_digitalsignature.borrower1.1</AnchorTabString>
</AnchorTabItem>
</Tab>
Reference: INTELLEDOC-3410
Previously, an enumerated value with extraneous spaces was considered invalid. For example, “MI ” would return an error if “MI” was the expected value. This rule has been relaxed to trim extraneous spaces before evaluating against the enumeration. Reference: INTELLEDOC-3492
An issue was introduced causing underlying data problems within the Payment Calculation workflow in Compliance Safety Net. A recalculated PrincipalAmount was not updating due to this issue. This has been corrected. Reference: INTELLEDOC-3535
Some additional logging has been added to help pinpoint an intermittent memory allocation issue. Reference: INTELLEDOC-3501
Some requirements regarding how DocumentDataValues data is handled from a TXL have been relaxed (specifically around associations). If you feel this may benefit your integration, please contact TruStage Compliance Solutions technical support for further information. Reference: INTELLEDOC-3499
The Loan Summary will now display the same question text that is used within Compliance Safety Net and Configuration. Reference: INTELLEDOC-2963
The last release had an issue with PDF combining through the Compliance Service. This has been corrected. Reference: INTELLEDOC-3512
Two new actions were added to the SOAP interface for Compliance Service. RenderTransactionSynchronous and WaitForResponseSynchronous are identical to Transaction and CheckForResponse, except that they operate synchronously and provide the jobOutputData in the response. Reference: INTELLEDOC-3502
In the Compliance Utility cloud service, there was an issue with rendering any PDF files uploaded as part of a Configuration Selection Group in the Compliance Service. This issue has been corrected. Reference: INTELLEDOC-3428
An update to the Schema data structure for certain Deposit documents exposed a longstanding algorithm problem with translating TXL data internally. A significant degradation in rendering performance was seen for those documents. This algorithm has been optimized to avoid the performance hit. Reference: INTELLEDOC-3475
An update was made to the eSignLive output option for E-Signature system support. As of this version, documents without signatures will not output the digital signature “sidecar” file. Reference: INTELLEDOC-3176
Previously, a NullReferenceException could occur periodically due to an issue loading Windows fonts when rendering large document packages. This has been corrected. Reference: INTELLEDOC-3470
Miscellaneous performance enhancements were completed. Reference: FLOW-3770, INTELLEDOC-3454, INTELLEDOC-3457
When sending multiple TXLs, there was differing behavior in Compliance Safety Net compared to the Compliance Service when merging the TXLs together. These processes are now consistent. Reference: FLOW-2821, FLOW-2875
Two minor updates were made to support Compliance Safety Net changes. See Compliance Safety Net release notes for more information. Reference: FLOW-2344, FLOW-1982
An update was made to support ongoing development of TRID updates for a future document library version release. Reference: INTELLEDOC-3347
A minor update was made to IntelleDoc Solutions to provide additional information to the Compliance Safety Net application regarding the id of the Entity relationship to Collateral on the Control Agreement document. Reference: FLOW-2013
A patch update was made to resolve a possible thread contention issue. See the Version number note section for more information. Reference: INTELLEDOC-3357
An update to IntelleDoc Solutions was required to enable preservation of all attributes on TXL leaf nodes during the data handling processes of the Compliance Safety Net. Reference: FLOW-1903
The Compliance Safety Net had a feature for automatically identifying, based on the license key of the request, which Financial Institution Simplicity Supplemental FXL should be used in the transaction. This feature has been ported to IntelleDoc Solutions so Platforms integrated with Compliance Safety Net do not have to identify this file in the rendering step with the Compliance Service.
If you are currently adding the Simplicity Supplemental in your transaction rendering calls, this will continue to function as is. The automatic discovery will not be activated. If you have a use case (unit test or similar) where you do not have a Simplicity Supplemental in effect for a transaction render, this feature can be turned off by setting AutomaticSupplementalDiscovery to false. Reference: INTELLEDOC-3337
On the AccountInformation document with certain SignatureProviderType options, the alignment of digital initial fields was off. This has been corrected. Reference: INTELLEDOC-3305, INTELLEDOC-3293
IntelleDoc Visualizer auto-fills missing data in the TXL editor window. A new feature has been added to provide control of this feature on optional data elements. Reference: INTELLEDOC-3283
Previously, invalid id values (TXL format) or suffix values (DXL format) could fail with the message CsiScriptHandler error: An error occurred while parsing EntityName. An example would be an id with an ampersand. The error messaging has been improved to provide more helpful information on the requirements of these id values. Reference: INTELLEDOC-3239
Some performance optimizations have been made to the handling of data collection (such as Entities) within the TXL data format. This should provide a general performance improvement to all operations using the TXL data format. Reference: INTELLEDOC-2431
The Data Collection Logic component has been updated. When the Cloud Cache is used to obtain an FXL file, it keeps a machine cached copy in case other processes that are part of the same transaction need access to the FXL. This should improve DCL performance and the Compliance Safety Net performance. Reference: INTELLEDOC-3339
Corrections to how ByRole Filtering is handled. Borrower, Guarantor, and Hypothecator roles should now be filtered instead of Collateral Owner. Reference: INTELLEDOC-3335, INTELLEDOC-3338
Performance improvements were made to document signature rendering. Reference: INTELLEDOC-2431
TXL files were not being resolved correctly when contenttype of cloudpath was specified. This has been corrected. Reference: INTELLEDOC-3340
LddService is now being reinitialized correctly between requests. This was resulting in inconsistent results and has been corrected. Reference: INTELLEDOC-3145
TruStage Compliance Solutions’ Data Schema has been updated to reflect new attributes for controlling the locking and displaying of fields in workflow (workflowlocked, workflowdisplayed). Reference: INTELLEDOC-3313
In some scenarios, a warning message was displayed saying Supporting entity datapoint could not be found in the datapoint dictionary. This was also being pushed out to various other applications including Compliance Safety Net and Visualizer. This has been corrected. Reference: INTELLEDOC-3333
An internal refactoring of processing TXL data was implemented that should yield general performance improvements in Compliance Safety Net and Compliance Service calls. Additional updates are in process for future versions. No API changes are needed to take advantage of these optimizations. Reference: INTELLEDOC-2431
A new license key option has been added for Compliance Safety Net. This is used for new functionality in Configuration 3.22 to allow controlling the display and editability of Configuration data in the Compliance Safety Net application. Reference: INTELLEDOC-3327, INTELLEDOC-3321
Previously, the Compliance Service WSDL would not respond properly when behind an AWS load balancer. This has been enhanced to be supported in this deployment structure. Reference: INTELLEDOC-3290
New functionality is available in the Compliance Service to validate a license key. Details below:
Operation: Name - GetLicenseKeyInfo
Request data: licenseKey - a string representation of the license key
Response content: status - a string representation of the following status’: valid, invalid, expired expirationDate - a date (yyyy-MM-dd) representation of the date the license key expires
Request structure:
<GetLicenseKeyInfo xmlns="http://www.compliancesystems.com/services/complianceservice/">
<licenseKey>string</licenseKey>
</GetLicenseKeyInfo>
Response structure:
<GetLicenseKeyInfoResponse xmlns="http://www.compliancesystems.com/services/complianceservice/">
<licenseKeyInfo>
<status>string</status>
<expirationDate>date(yyyy-MM-dd)</expirationDate>
</licenseKeyInfo>
</GetLicenseKeyInfoResponse>
Reference: INTELLEDOC-3251
Certain Client License Keys were erroneously triggering an exception after the extension to the license key format in version 7.20. This has been corrected. Reference: INTELLEDOC-3321
Both Transaction and RenderDocumentSet methods did not work when ReturnPartialDocSet was set to true in the Compliance Utility (Cloud Services). This was due to issues accessing the FXL files. This has been corrected. Reference: INTELLEDOC-3298
The JSON interface to the Data Collection Logic (DCL) service will now return a TransactionData element containing the TXL data when calculated values are present. Reference: INTELLEDOC-3292
TruStage Compliance Solutions’ license key structure was extended to support licensing of lending calculation functionality. Existing v3 license keys are backwards compatible. Reference: INTELLEDOC-3255
Previously, when data was modified in IntelleDoc Advisor, newly added datapoint suffixes were included using lowercase letters. Because suffixes are case sensitive, the application has been modified to preserve the case that is entered by the user. Reference: INTELLEDOC-3277
A change made to the internal compilation of FXL files allows reduced FXL file sizes, which aids in performance and memory utilization. Document Library 2017.111.0 and later are all compiled with this change and requires IntelleDoc Solutions 7.17 or greater. Reference: INTELLEDOC-3267
IMM has provided guidance regarding the current naming convention for signature fields when they are to be treated as initials rather than full signatures. The SignatureProviderType of IMM has been updated accordingly. Reference: INTELLEDOC-3269
Previously, an erroneous error message was generated in the log on the Closing Disclosure when the script of the document attempted to remove a value that did not exist for that scenario. The method to remove a value now does not generate an error if the value does not exist. Reference: INTELLEDOC-3259
Previously, the DocumentRenderingTrail encrypted audit information embedded as PDF metadata was not supported through PdfCombine. This version now preserves this information. Reference: INTELLEDOC-3258
Previously, optional data elements from the DSL were not reported as available (“in-play”) through the DCL interface. Updates have been made so that these optional elements are presented through the DCL when appropriate. Reference: INTELLEDOC-3256
Some simplifications of TruStage Compliance Solutions’ Data Schema mapping paths were implemented and corresponding hard-coded data elements in the IntelleDoc Solutions code base were removed. This refactoring change impacted the Lending.FXL in version 2017.118.0. Reference: INTELLEDOC-3248
Previously, some messages raised by JavaScript code within an FXL would not be appropriately added to the status messages from the IntelleDoc Solutions components. This has been corrected. Reference: INTELLEDOC-3234
To support TruStage Compliance Solutions’ Compliance Utility cloud services, you can now optionally specify a document library version for calls to the Compliance Service. The details of this change are documented separately for cloud-based integrations. Reference: INTELLEDOC-3206, INTELLEDOC-3205, INTELLEDOC-3204
Data values are case sensitive, but certain validation rules were not evaluating them this way. For example, “tX” is not equivalent to “TX” but previously, a state code valid value list would not treat the first as invalid. This has been corrected. Reference: INTELLEDOC-3181
Setting FileName for jobTicket.DebugSettings.TxlOutputFilePath could trigger a file access exception. This debug output option was erroneously writing the debug merged TXL file multiple times, leading to the potential for this issue to occur. This has been corrected. Reference: INTELLEDOC-3140
A performance optimization has been implemented to reduce the time required to render a custom document that contains a significant volume of scripted values inside a data element. Reference: INTELLEDOC-3044
Previously, PdfCombine could crash the Transaction Server on a bad unc reference when combining output intended for SignatureProviderType eLynx. This error scenario is now handled, and a message is returned. Reference: INTELLEDOC-2832
Users can elect to include uploaded PDFs in a Configuration selection group. Previously, if the PDF file reference used at render time was incorrect, an error was not reported. This has been corrected. Reference: INTELLEDOC-2688
Output support for DocuSign was modified in order to improve the positioning of the signature locations based on DocuSign’s anchor tag methodology. In addition, automatic support for the use of initials rather than a signature was implemented. Reference: INTELLEDOC-3210, INTELLEDOC-3232.
The new Uniform Residential Loan Application document, currently in development, will require a date format of mm/yyyy. This format was not previously supported and has been added to IntelleDoc Solutions in preparation of this document’s delivery. Reference: INTELLEDOC-3227
Modifications have been made to the Data Collection Logic (DCL) to control the value of jobTicket.Prefs.DocSelectPrefs.IncludeUnderwritingDocs. Reference: INTELLEDOC-3213
An additional e-signature output support option is available as one of the SignatureProviderType options in the Transaction Server job ticket. This option is eSignLive to support platform integrations of the eSignLive by VASCO digital signature system. Reference: INTELLEDOC-3176
Three additional attributes were added to data elements in the Data Schema (XSD). The attributes are Source, Destination, and Version. Configuration and Compliance Safety Net applications will, in the future, publish data with the Source attribute filled in. The remaining data elements and the other attributes are optional to accommodate data that will provide more accurate data traceability (where the data came from, where the data may need to go, and when the data was captured). Reference: INTELLEDOC-3185
In all previous versions of IntelleDoc Solutions, there was an intermittent and low occurrence (internal test rate of 0.005%) of PDF output files becoming corrupt. The cause of this issue is unknown. A solution was found by checking and fixing the internal PDF xref table if that information was inaccurate. This PDF integrity step has been implemented in the Compliance Engine for all PDF outputs. This has a single-digit millisecond impact on rendering time. Reference: INTELLEDOC-2889
An association issue was discovered with the document library change version 2016.484.0, which caused certain entity data not to appear on the CardApplicationATMDebit.FXL (DD8004) for Commercial Accounts. This issue has been resolved. Reference: INTELLEDOC-3201
In some cases, a document-level exception message could be presented with placeholder data elements. This was corrected in the internal TruStage Compliance Solutions document compiler but is noted here to communicate the resolution of this issue. Reference: INTELLEDOC-3197
Recently, IntelleDoc Solutions software was modified to gain some internal efficiencies in the way TruStage Compliance Solutions codes its FXL files. This change had the unfortunate side effect of causing some rendering issues in some very limited and very complicated edge transactions. This release addresses this issue on dynamic document rendering. Releases including and prior to 6.40.1620.0 do not exhibit the issue. However, this issue may impact you if you are running one of three versions: 6.46, 6.53, and 7.0.
Along with this 7.7 release version, we have updated the CSi NuGet server with patch versions of each affected software version to make it as easy as possible for you to take this release. Even though the risks are very limited, we ask that you push this out as soon as possible to ensure clients are not impacted.
The available patched versions are on the CSi NuGet server:
Reference: INTELLEDOC-3192, INTELLEDOC 3166
Previously, the Compliance Engine did not handle associations correctly when a loan had more than one Dairy Product Buyer. The result was a JavaScript error Unable to cast object of type ‘System.Collections.ArrayList’ to type ‘AssociationInfo’ on the Assignment of Proceeds of Dairy Products document (DL4003). This has been corrected. Reference: INTELLEDOC-3178
The call to get the Library Data Dictionary (LDD) has been extended with an optional Boolean property that determines if static FXL files are included in the results. By default, this is false, which retains previous behavior. Reference: INTELLEDOC-3162
Version 6.53 had an issue with handling inline response of combined PDFs. This has been corrected. Reference: INTELLEDOC-3161
Enhancement work was done to allow fillable form fields to be used when combining PDF files. A new property, destination.PdfCombineProperties.LinkFields, can be set to control this. The default setting is true. Reference: INTELLEDOC-3159
When an OXL overlay is in use, a small watermark is rendered on the document. This was displayed as a “CSi” rendered in the bottom right of the document. For some use cases (e.g., recordable documents), this was too obtrusive. An alternate mode has been added which instead changes from the “CSi” overlay to a subtle change to the separator character in the checksums within the document footer. This can be used by setting the job ticket preference of overlayindicator to alternate. Reference: INTELLEDOC-3149
The Data Schema has always had a common list of valid values for EntityType. Previously, this was achieved through a translation table in the IntelleDoc Solutions software. The underlying datapoint data structure has been modified to match the Data Schema combined list. To accommodate integrations that still use our legacy datapoint structure, backward compatibility has been built into IntelleDoc Solutions to ensure old datapoint names and values can still be used. Reference: INTELLEDOC-3104
A new JobTicket preference, ReportCalculatedDatapoints, has been added. When set to true, the job response will return any internal data element values that were calculated during the processing of the given document. Reference: INTELLEDOC-3098
IntelleDoc Solutions has been updated to the Microsoft .NET framework 4.6.2. This version is now required for use with IntelleDoc Solutions.
Major internal refactoring of the IntelleDoc Solutions code base has been completed in this release. This was a substantial update to refresh internal code structures. It should not affect integration interfaces. In addition, performance improvements in processing TXL data have been implemented. Reference: INTELLEDOC-3105
A planned document and DSL change will update the EntityType data elements to use a common valid value list. This has already been in effect for TXL data files and will be a transparent change when using TruStage Compliance Solutions’ Data Schema structure. Data formats that use datapoints and values (e.g., DXL) will see changes. Within the IntelleDoc Solutions code base, backward compatibility has been implemented so old datapoint/value combinations will map to the new ones as needed. More detail will be provided along with the document and DSL change documentation. Reference: INTELLEDOC-3104
A compatibility issue with the IMM E-Signature output acrofields in PDF files has been resolved. Reference: INTELLEDOC-3097
To allow reduced file sizes for output PDFs, an optional property has been added to control whether PDFs will include embedded fonts. The embednonstandardfonts option allows exclusion of Arial and Times New Roman, which are universally present on computer systems of today, so the PDFs will still render in the required fonts even if they are not embedded. Excluding more fonts than these two is not intended for anything other than testing purposes and should not be done for any Production rendering of PDFs, as a subsequent opening of the produced PDF may occur on systems that do not have certain fonts available.
<fontembedding type="embedall"/>
<fontembedding type="embednone"/>
<fontembedding type="embednonstandardfonts"/>
<fontembedding type="embedselective" default="true">
<font namecontains="times" embed="false"/>
<font namecontains="arial" embed="false"/>
</fontembedding>
<fontembedding type="embedselective" default="false">
<font namecontains="3of9" embed="true"/>
</fontembedding>
Reference: INTELLEDOC-2733
The new control type csi.Utility.Datapoints.Datapoint.ControlType.digitalSignature does not have a corresponding value in ComplianceServiceSimple.controltypelist. This caused an unhandled exception in ComplianceServiceSimple.ConvertDatapointListForResponse when that control type occurs in a response. This has been resolved. Reference: INTELLEDOC-3029
The IntelleDoc Solutions NuGet packages have been streamlined in the 7.0 version. The available packages are as follows.
Previously, generation of the Library Data Dictionary (LDD) could fail when a document FXL file included an escaped non-breaking space character. This issue has been resolved.
Changes specific to the previous version of the IntelleDoc Solutions (6.46) impacted the system font handling for certain static documents. That version was not widely released. This issue has been resolved.
Enhancements have been made to the Data Collection Logic (DCL) responses to include any applicable exception messages.
Modifications have been made to properly present values associated with data element names and descriptions generated from document FXL files. Previously, those values were swapped.
Changes have been made to the public interface to include methods for checking the licensing of FXLs. GetLicensedFxls takes an FXL repository path and the client license key as parameters. IsLicensed takes an FXL file path and the client license key.
The IntelleDoc Solutions integration components are multi-tier .NET Remoting applications that include the Transaction Manager, Transaction Server, and Transaction Runner. They provide direct integration with TruStage Compliance Solutions’ IntelleDoc Solutions. They are suited for most Microsoft Windows server environments, from a single server to a multiple or distributed server environment employed wherever high-volume capacity is required, such as with a branch, financial institution, or a processing center.
For environments where direct .NET integration is not possible, Compliance Service provides a web services SOAP interface that acts as a bridge between the platform system and TruStage Compliance Solutions’ .NET components.
IntelleDoc Advisor is an application used to modify data values in order to assess changes in document rendering. It supports IntelleDoc Solutions DXL and FXL file formats. IntelleDoc Advisor provides a convenient environment for viewing datapoint information as it will appear on documents, allowing accurate evaluations to be made regarding structure of both documents and data files.
IntelleDoc Visualizer is an application used to validate the content of TXL data files structured on TruStage Compliance Solutions’ Data Schema. It allows transaction data in a TXL file to be checked against a schema file, flagging data that does not comply with parameters of the schema so that it may be corrected.
It also allows the TXL data file to be exercised against the Transaction Server, TruStage Compliance Solutions’ component for selecting, assembling, and outputting transaction documents. When IntelleDoc Visualizer is installed, the Transaction Server component is automatically installed on the same system to provide access to its functionality.
Custom Document Editor is an application dedicated to the creation of custom documents. Typically, these custom documents are based on existing TruStage Compliance Solutions stock documents, existing image files, or are created from scratch by the document designer. Custom Document Editor includes features that streamline the process for incorporating partner datapoints from a datapoint dictionary and allows JavaScript to be incorporated into the documents to manipulate data as transaction-specific values are input into datapoints.