What's New

List of features, enhancements, and defect corrections implemented for Document Management.

This help topic encompasses new features, enhancements, and defect corrections covering all aspects of the Document Management service.

August - 2022

Document Management updated to use .NET 5
Type: Enhancement Reference: PBI 708273 Documentation Impacts: No documentation impact
Summary: Document Management has been updated to use Microsoft .NET 5 in order to keep the application current and to reduce security vulnerabilities.

December - 2021

Document Generation Services (DGS) TransactionID behavior enhanced
Type: Defect Reference: PBI 703561 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: Users reported that the Document Generation Services (DGS) `TransactionID` sent to eOriginal did not match the ID in the request sent to our internal Document Management application. The expected behavior is that Document Management uses the DGS `TransactionID` in the request to create the transaction in eOriginal.
Solution: This behavior has been resolved; Document Management now uses the DGS `TransactionID` in the incoming request to create a transaction for use with eOriginal.
Implementation Notes: This defect correction is available in the December release of Hosted Expere / Expere Document ServicesDocument Management.

Ability to perform a Select / Generate
Type: Enhancement Reference: PBI 698507 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: In addition to a Select and Generate API call, Document Management can now facilitate a Select / Generate API call when using sending a transaction to eOriginal. With this API call, users first select a specific set of documents to be generated (using a Select API call) then generate that document set (using a Generate API call).
Implementation Notes: This enhancement is available in the December release of Document ManagementHosted Expere / Expere Document Services.

eOriginal: Upload Validation
Type: Enhancement Reference: PBI 698504 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: eOriginal upload validation logic has been updated so that only eNotes are validated. Previously, all documents were validated, causing a transaction to fail. In the transaction, if `EOriginalUploadInd element` = 0, only eNotes are uploaded to eOriginal. As a result, no other documents are sent to eOriginal.
Implementation Notes: This enhancement is available in the December release of Hosted Expere / Expere Document ServicesDocument Management.

October - 2021

Validation added when using either SoleProprietorship or Trust entity types when requesting an eNote
Type: Enhancement Reference: PBI 690489 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: EntityTypes
Summary: We have added validation to the `entityType` schema so that only a SoleProprietorship or Trust options can be passed in when requesting an eNote.
Technical Notes: This validation applies to both V1 and V2 Document Management API's.
Implementation Notes: This enhancement is available in the October release of Document Management.

TestOnDemand (TOD) / PreviewOnDemand (POD) enhanced to include environmental enumeration
Type: Feature Reference: PBI 686966 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Document Generation Services Installation / OD Guide: Appendix: Document Generation Services Sample Transforms.xml file
Summary: As part of our eOriginal integration, we enhanced Document Management logic to determine which environment (TOD or POD) is used based on the transaction data indicators and Document Generation Services transforms.xml file property values below: If the TODPODCredentialsVisible flag in the DGS transforms.xml file is set to true and the value of /Txn/EOriginalPreviewOnDemandEnvironmentInd is equal to '1' (Preview On Demand) then DGS passes the Environment Property with a value of 1 If the TODPODCredentialsVisible flag in the DGS transforms.xml file is set to true and the value of /Txn/EOriginalPreviewOnDemandEnvironmentInd is equal to '0' OR is Blank (Test On Demand) then DGS passes the Environment Param with a value of 0 If the TODPODCredentialsVisible flag in the DGS transforms.xml file is set to false DGS passes either '0', '1' or '2' based on the existing code and the single set of credentials that are stored when the flag is set to false
Technical Notes: This enhancement is only supported in our Customer Test (CT) environment.
Implementation Notes: This feature is available in the October release of Document Management.

Logic provided when passing in eOriginal credentials
Type: Enhancement Reference: PBI 687250 / 690563 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Document Management Integration Guide > EOCredentials
Summary: As part of our eOriginal integration, we support the use of both PreviewOnDemand (POD) and TestOnDemand testing environments through the list below. Through the eOLogin method call, we pass the correct credentials based on the following request information: When passing in an Enum of "1" (PreviewOnDemand), EOriginalUploadTypes is analyzed to determined if the MERS or NonMERS credentials are appropriate for the corresponding environment. When passing in an Enum of "0" (TestOnDemand), EOriginalUploadTypes is analyzed to determined if the MERS or NonMERS credentials are appropriate for the corresponding environment.
Technical Notes: This enhancement is only supported in our Customer Test (CT) environment.
Implementation Notes: This enhancement is available in the October release of Document Management.