Jump to main content

# Changelog Entries - 2021

This help topic encompasses new features, enhancements, and defect corrections covering all aspects of your hosted environment, including Expere Document Services and the Expere Engine.

Note: The Hosted Expere Changelog uses a dynamic URL to display the changelogs relevant to your version of the program, and as a result, the URL changes from release to release. For best results, always access the Changelog by clicking the hyperlink from the Expere Document Services landing page. If your desire is to bookmark the changelogs, we recommend bookmarking the landing page rather than the Changelog.

Supplemental December release

Note: The supplemental December release will be deployed to the CT and Production environments on December 20.

Expere Engine: Log4j updated
Type: Enhancement Reference: PBI 706658 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: We previously informed you that the Expere Engine was using a vulnerable version of Log4j that was determined to have a security risk. As a result, we upgraded the Expere Engine to Log4j version 2.15.0. On December 14th, Apache confirmed another medium vulnerability that required an update to Log4j version 2.16.0. They have since confirmed an additional critical vulnerability on December 20th that requires an update to version 2.17.0. As a result, we have upgraded the Expere Engine to use Log4j version 2.17.0. No user action is required.
Implementation Notes: This enhancement is available in the supplemental December release of Hosted Expere / Expere Document Services.

EZ Transform: Log4j updated
Type: Enhancement Reference: PBI 706667 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: It was identified that EZ Transform was using a second vulnerable version of Log4j that was determined to have a critical security risk. We have corrected the security finding by upgrading EZ Transform to use Log4j 2.17.0. No user action is required.
Implementation Notes: This enhancement is available in the supplemental December release of Hosted Expere / Expere Document Services.

Supplemental December release

Note: The supplemental December release will be deployed to the CT and Production environments on December 11.

Expere Engine: Log4j updated
Type: Enhancement Reference: PBI 706305 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: It was identified that the Expere Engine was using a vulnerable version of Log4j that was determined to have a security risk (2.14.0 then 2.15.0). We have corrected the security finding and created an Expere release containing an updated Expere Engine which includes the security remediation. No user action is required.
Implementation Notes: This enhancement is available in the supplemental December release of Hosted Expere / Expere Document Services.

EZ Transform: Log4j updated
Type: Enhancement Reference: PBI 705774 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: It was identified that EZ Transform was using a vulnerable version of Log4j that was determined to have a security risk. We have corrected the security finding by deploying a fix through emergency maintenance. No user action is required
Implementation Notes: This enhancement is available in the supplemental December release of Hosted Expere / Expere Document Services.

December

Expere Engine enhanced to use FOP 2.6
Type: Feature Reference: PBI 696660, 696662, 701342 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: As a part of our continued effort to create WCAG 2.0 compatible documents we have updated the Expere Engine to now use FOP 2.6 when generating TaggedPDF documents. We will continue making enhancements to FOP 2.6 for TaggedPDF support, so check back for items being identified and corrected. Please note, WCAG support requires special content authoring and is not currently supported ‘out of the box’. As part of our feature to update the Expere Engine to use FOP 2.6, we made the following WCAG 2.0-related changes in the December release: PBI 696660: during the course of reporting an issue related to our WCAG 2.0 feature work, an internal user reported that the Adobe Acrobat Accessibility checker was failing. This PBI resolved that issue so that running the Accessibility checker now completes successfully. PBI 696662: we addressed three issues for this particular work item: An internal user reported that our authoring tool timed out when attempting to generate the Uniform Residential Loan Application (URLA) as a TaggedPDF document type. This issue has been resolved. An italicized word, Texas Constitution, was tagged incorrectly and was being read out of order. This issue has been resolved. A URL, www.oregonlawhelp.com, appeared in a separate section within the Adobe tag tree rather than within the tagging for the paragraph where it resided. This issue has been resolved. PBI 701342: an internal user reported that when clicking a Form tag within the Adobe tag tree, it resulted in the the entire form being highlighted, rather than a particular word or phrase. It was discovered that checkboxes associated with this Form tag were being removed, resulting in an empty form tag and the entire form being highlighted. This issue has been resolved.
Implementation Notes: This feature / enhancement work is available in the December release of Hosted Expere / Expere Document Services.

TaggedPDF behavior enhanced
Type: Defect Reference: PBI 704153 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: A user reported during preliminary testing that multiple loans failed when attempting to output them using the TaggedPDF document format.
Solution: This issue has been resolved; users may now resume testing using a TaggedPDF document format.
Implementation Notes: This defect correction is available in the December release of Hosted Expere / Expere Document Services.

PdfMerge and linked option (radio) button field behavior enhanced
Type: Defect Reference: PBI 703835 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: A user reported that when testing Wolters Kluwer E-Sign (WKES) linked fillable field functionality, they discovered that the enumerated values for field names in a mergedPDF did not match that of the corresponding JSON file. For example: PDF: WKES_RadioButton_username@email.com_20_M JSON: WKES_RadioButton_username@email.com_19_M This resulted in receiving errors in WKES when trying to complete the eSign process.
Solution: This issue has been resolved; WKES fillable field enumerated values in a merged PDF now match that of the corresponding JSON file and the package of documents can now be eSigned through WKES.
Implementation Notes: This defect correction is available in the December release of Hosted Expere / Expere Document Services.

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 Services.

Engine: multiple accounts now allowed in a single transaction with the same product
Type: Enhancement Reference: PBI 701178 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: A user reported that an error occurred when opening multiple accounts in a single transaction when where the same EZ Config (or OPPSA) Product name was used for more than one account in the request. Internal analysis determined that this error occurred because Expere previously only allowed multiple accounts in a single transaction when the product name was different for each account. As a result, this behavior has been enhanced: Expere now supports multiple accounts in a single transaction with the same product name.
Implementation Notes: This enhancement is available in the December release of Hosted Expere / Expere Document Services.

RTF output: signature line behavior enhanced
Type: Enhancement Reference: PBI 703264 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: Users reported signature line inconsistencies that necessitated addressing; instead of being a starndard, uniform width, the length of the signature line directly corresponded to the number of the characters in the value of the `SignerName` element. As a result, the signature line would span across the entire width of the page. This behavior has been enhanced so that the signature line for both RTF and PDF outputs are 3.5" wide.
Implementation Notes: This enhancement is available in the December release of Hosted Expere / Expere Document Services.

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 Hosted 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 Services.

November

ESignatureAndFieldSupport XY Coordinates Only behavior enhanced
Type: Defect Reference: PBI 698521 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: Users reported that when passing in an `ESignatureAndFieldSupport` ancillary option with Coordinates only set to "true," transaction data was not printed on the document for those fields which would normally contain data.
Solution: This behavior has been enhanced after internal analysis; transaction data now appears and prints as expected expected when ESignatureAndFieldSupport with Coordinates Only = ‘true’ is set.
Implementation Notes: This defect correction is available in the November release of Hosted Expere / Expere Document Services.

DGS Core DocViewer API: v2 added for `BeginSession` and `updateTransaction`
Type: Enhancement Reference: PBI 694061 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: BeginSession - POST; UpdateTransaction - POST
Summary: DGSCoreDocViewer has been updated with V2 REST methods for the BeginSession and UpdateTransaction API calls. These were updated in an effort to be more consistent with preliminary REST API calls in this service that were previously created. The updated "v2" methods, noted in the URL's, now utilize JSON data rather than form data.
Implementation Notes: This enhancement is available in the November release of Hosted Expere / Expere Document Services.

Expere Engine enhanced to use FOP 2.6
Type: Feature Reference: PBI 696660, 686589 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: As a part of our continued effort to create WCAG 2.0 compatible documents we have updated the Expere Engine to now use FOP 2.6 when generating TaggedPDF documents. We will continue making enhancements to FOP 2.6 for TaggedPDF support, so check back for items being identified and corrected. Please note, WCAG support requires special content authoring and is not currently supported ‘out of the box’. As part of our feature to update the Expere Engine to use FOP 2.6, we made the following WCAG 2.0-related changes in the November release: PBI 686589: It was reported that in a TaggedPDF document, tables that were split between pages resulted in the corresponding Adobe tag tree displaying the tables separately. A TaggedPDF document with tables that split between pages are now combined into one table in the Adobe tag tree.
Implementation Notes: This enhancement is available in the November release of Hosted Expere / Expere Document Services.

DocViewer Embedded PDF
Type: Feature Reference: PBI 696788 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: As part of our overall effort to convert static to dynamic documents, DocViewer has been enhanced to allow viewing the new an embedded .PDF document type. DocViewer can now view and extract an embedded .PDF file. Typical DocViewer functionality is also supported through the documents, such as data entry and field interaction.
Implementation Notes: This feature is available in the November release of Hosted Expere / Expere Document Services.

New AnchorText ancillary output type added
Type: Feature Reference: PBI 678700 / 678702 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Web Services Guide (SOAP): AncillaryOutputTypeEnum; Expere Document Services Web Services Guide (REST): AncillaryOutputTypeEnum; Expere Document Services Tool Suite User Guide: Select & Generate, Select / Generate
Summary: We have implemented a new feature where users can now author documents that contain text anchors for signature and date fields. Through this new feature, we have added a new ancillary output type called "AnchorText" that, when selected, allows third party eSiging applications to add initial, signature, and date fields to a document.
Implementation Notes: This feature is available in the enhanced November release of Hosted Expere / Expere Document Services.

October release

Note: All Hosted Expere / Expere Document Services changes were released in the Early October release; there are no additional customer-facing changes that will be included in the regularly-scheduled October deployment.

Early October release

Note: The early October release will be deployed to the CT environment on 10/7 and the Production environment on 10/14.

eOriginal: ability to support testing between Preview on Demand / Test on Demand environments
Type: Feature Reference: PBI 694049 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: eOriginal Quick Guide: Expere Transaction XPaths for eOriginal
Summary: Users may now indicate to which eOriginal environment they want to their transaction: Test On Demand (TOD) or Preview on Demand (POD) through the `EOriginalPreviewOnDemandEnvironmentInd` data point. This indicator accepts the following values: 0 = TestOnDemand 1 = PreviewOnDemand 2 = Production
Implementation Notes: This feature is available in the October release of Hosted Expere / Expere Document Services.

Sequencing behavior enhanced for Option (radio) buttons
Type: Defect Reference: PBI 693352 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: It was discovered that when testing the Wolters Kluwer E-Sign (WKES) additional field support feature, the sequence number assigned to the fillable field on the document differed from that of the JSON relationships file. As a result, WKES could not display the .PDF document because the fields referenced in the JSON did not match that of the document.
Solution: This behavior has been enhanced; the fields in both the .PDF and .JSON files are identical, and the .PDF document now displays properly in WKES.
Implementation Notes: This defect correction is available in the October release of Hosted Expere / Expere Document Services.

RTF Alignment behavior corrected
Type: Defect Reference: PBI 696612 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: A user reported an issue with the alignment of text on documents issues after the Expere release to the Customer Test (CT) environment on September 21. The issue impacted documents generated with an RTF output. All text on the documents was left-justified, when some should have been centered-justified, right-justified, or even slightly indented.
Solution: This behavior has been corrected; documents generated with the RTF output are now created with the expected text alignment.
Implementation Notes: This defect correction is available in the early October release of Hosted Expere / Expere Document Services.

NotaryBlock behavior when used with Wolters Kluwer E-Sign ancillary option enhanced
Type: Enhancement Reference: PBI 693657 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: Users reported that when using the `WKES_ESignatureAndFieldSupport` ancillary output with an authored `NotaryBlock` element, the generated notary section was not present for a notary to hand write any information. Research determined that this behavior occurred when `FillableField` elements were authored inside the `NotaryBlock` element. This behavior has been enhanced so that when `WKES_ESignatureAndFieldSupport` is specified as an ancillary output in the request, the notary section of the document allows for a notary to hand write in the details.
Implementation Notes: This enhancement is available in the early October release of Hosted Expere / Expere Document Services.

Supplemental September release

Note: The supplemental September release will be deployed to the CT environment on 9/21 and the Production environment on 9/28.

OPPSA Conversion: enhancements and behavior/functionality modifications
Type: Enhancement Reference: PBI 687430, 687789, 687668, 687377, 687780, 687803, 688296, 693325 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: Enhancement (PBI 693325): the DocViewer UpdateTransaction API has been updated to handle KeyCollections changes, eliminating the need for users to set up KeyCollections in the OPPSA conversion output file.. Enhancement (PBI 687430): due to lack of consistency in OPPSA, the conversion sets the /Txn/OrgJurisdiction as the default value for the KeyPathValue. Enhancement (PBI 687668): previously in the OPPSA export two xpath values which gathered the same value were sent in the transaction; one Xpath was correct, while the second Xpath was incorrect. Now, only the correct Xpath is used in one key collection. Enhancement (PBI 687789 / 688296): there are EZ Config specific Xpaths that correspond to checkboxes in OPPSA that were not tied to an Xpath, this enhancement maps the OPPSA checkbox value to the corresponding EZ Config Xpaths. Enhancement (PBI 687780: the OPPSA conversion previously did not account for policies that contained a `nodeName`. These does not account for Oppsa policies that have a nodeName within them. The xpaths that exist with a nodeName value are converted like seen in description Enhancement (PBI 687803): when converting the truth in savings Oppsa policy we are now setting the /Txn/Deposit/Accounts/Account/TruthInSavingsPolicyName xpath with the value in the export file Defect (PBI 687377): the `TransferOrPaymentType` value was missing from the `DataItem>Xpath` after the conversion process occurred. This behavior has been enhanced to preserve this Xpath value. Enhancement (PBI 688316): the following Xpaths are now being converted from Oppsa. Previously the corresponding OPPSA checkboxes were not mapped to an Xpath: /Txn/Deposit/EZConfigNightDepositAgreementInd /Txn/Deposit/ElectronicProcedureDisclosures/ElectronicProcedureDisclosure/ElectronicProcedureType /Txn/Deposit/EZConfigSecondMobileBankingAccessMethodInd /Txn/Deposit/RegEPolicies/RegEPolicy/MinimumBalanceCheckingInd /Txn/Deposit/RegEPolicies/RegEPolicy/MinimumBalanceSavingsInd /Txn/Deposit/EZConfigEarlyWithdrawalPenaltyReducedRateBasisType
Implementation Notes: These enhancements and defects are available in the enhanced September release of Hosted Expere / Expere Document Services.

September

Support for embedded PDF's
Type: Enhancement Reference: PBI 678008 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: We have introduced a new authoring format that inserts an embedded .PDF file into the content file (.REQ file). This new .REQ type will allow users to enter data into fillable fields and electronically sign a document within this embedded PDF.
Implementation Notes: This feature is available in the September release of Hosted Expere / Expere Document Services.

Tool Suite: UCD Functionality removed
Type: Enhancement Reference: PBI 689284 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Tool Suite User Guide: Select Generate Deliver; Select & Generate.
Summary: Due to deprecated functionality, we have removed the UCD section and Request UCD checkbox within the Expere Document Services Tool Suite. We have renamed this section to TRID Merge and have preserved the checkbox of the same name.
Implementation Notes: This enhancement is available in the September release of Hosted Expere / Expere Document Services.

Barcodes: barcodeInter25 format enhanced
Type: Enhancement Reference: PBI 681620 / 690908 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Implementation Strategies Guide: Barcode Types (Fonts) and Patterns
Summary: It was discovered that barcodeInter25 requires an even number of characters in the barcode pattern in order to function properly; as a result, when an odd number of characters is provided for a barcodeInter25 barcode type, we are prepending a 0 to the barcode. Note: as a reminder, BarcodeInter25 is a numeric-only barcode type.
Implementation Notes: This enhancement is available in the September release of Hosted Expere / Expere Document Services.

WSDL and Tool Suite: TaggedPDFEmbeddedFont document format no longer supported
Type: Enhancement Reference: PBI 684964 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Tool Suite User Guide: Select & Generate; Select / Generate; Expere Document Services Web Services Guide: DocumentFormatTypeEnum
Summary: TaggedPDFEmbeddedFonts is no longer supported as a document format. The TaggedPDFEmbeddedFonts has been removed as a DocumentFormatTypeEnum from the WSDL. Additionally, Tagged PDF Embedded Fonts is no longer available as a Document Format option within the Expere Document Services Tool Suite.
Implementation Notes: This enhancement is available in the September release of Hosted Expere / Expere Document Services.

Supplemental August release

Document Format enhanced with EZ Config Packages and Packets
Type: Enhancement Reference: PBI 636172 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Tool Suite User Guide: Select and Generate; Select / Generate
Summary: Previously, the Expere Document Services (EDS) Tool Suite required users to select the Document Format. By requiring the Document Format to be selected it would override the value set within EZ Config Packages and Packets when Merge EZ Config data was used. . As a result, this behavior has been enhanced: we are no longer requiring that users select the Document Format in the EDS tool suite. If no value is provided in either EDS or EZ Config Packages and Packets, the default format will be PDF.
Implementation Notes: This enhancement is available in the Enhanced August release of Hosted Expere / Expere Document Services.

Expere Engine: SignatureField formatting/spacing behavior resolved
Type: Enhancement Reference: PBI 681392 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: Users reported that a `SignatureField` element authored outside of a `Table` element was being placed over the signature line and any text directly below It (see below): We have enhanced this behavior so that the `SignatureField` can be authored outside of a `Table` element without forcing the field to obscure the signature line and text. The updated behavior appears as follows:
Implementation Notes: This enhancement is available n the Enhanced August release of Hosted Expere / Expere Document Services .

DocViewer: Phase dropdown functionality unavailable when using EZ Config Packages and Packets
Type: Enhancement Reference: PBI 683811 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: We had an enhancement request to remove the Phase dropdown from the Document Options or Document View page in DocViewer when using EZ Config Packages and Packets. Users may now view documents from the Forms to View First dropdown, essentially bypassing the Phase dropdown.
Implementation Notes: This enhancement is available in the Enhanced August release of Hosted Expere / Expere Document Services.

Early August Release

Note: The early August release will be deployed to the CT environment on 7/29 and production environment on 8/5. The regularly scheduled CT release on 8/10 and Production release on 8/19 will still occur for product maintenance but will not include application enhancements.

DocumentService REST API: BRE to be specified on Generate and Deliver Requests
Type: Enhancement Reference: PBI 684946 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Hosted Expere > Wolters Kluwer E-Sign Feature Guide: Deliver > Special Considerations
Summary: Users may now specify BRE (Business Return Envelope) information in `Generate`, `Generate-Synchronous` and `Deliver` requests. The BRE can specified at either the request level, resulting in the same BRE being used for all delivery groups created from the request, or within the `Recipient` container to override what was specified on the request. BRE can also be specified at there Recipient level only, allowing only some recipients to receive BREs. Note: `BRE` is an optional parameter on the request, and must be configured on your account within Print Fulfillment. Please work with your Professional Services contact for setup/configuration questions.
Technical Notes: Consult the Hosted Expere > Wolters Kluwer E-Sign Feature Guide: Deliver > Special Considerations on detailed information when using the BRE parameter
Implementation Notes: This enhancement is available in the early August release of Hosted Expere / Expere Document Services.

Instance Display Name and Embedded PDF behavior enhanced
Type: Defect Reference: PBI 684468 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: Users noted that in the response file, the Instance Display Name (`InstanceDisplayName`) appeared incorrectly. The `InstanceDisplayName` element should have displayed the static text consisting of the document display name and the DTA value, for example: `<r:InstanceDisplayName>Tax Escrow Account Receiving Tax Bills NY - C1StAddr, C1City, NY C1PC</r:InstanceDisplayName>` Instead. only the DTA value appeared: `<r:InstanceDisplayName>C1StAddr, C1City, NY C1PC</r:InstanceDisplayName>`.
Solution: `InstanceDisplayName` now display the static text consisting of the document display name and the DTA value.
Implementation Notes: This defect correction is available in the early August release of Hosted Expere / Expere Document Services.

Entity signatures missing space issue corrected
Type: Defect Reference: PBI 686843 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: A user reported an issue where the signature line under the phrase "A(n) Limited Liability Company did not allow enough space for the party to sign.
Solution: This issue has been resolved; the Expere Engine has been updated to provide enough space under the phrase "A(n) Limited Liability Company for a party to sign a signature.
Implementation Notes: This defect correction is available in the early August release of Hosted Expere / Expere Document Services.

Tool Suite: EZ Config support options updated
Type: Defect Reference: PBI 682957 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere DocumentServices Tool Suite User Guide: Select Generate Deliver, Select and Generate, Select / Generate
Issue: Previously, we had updated the Expere Document Services Tool Suite with a new EZ Config Merge Options section (see PBI 675396). Further analysis determined that we needed to implement additional enhancements to this section.
Solution: The EZ Config Merge Options section has been updated to the following: The Product Only option has been updated to Default Data Only. Functionality has been updated so that the product and organization data are merged with the request transaction. The Logo and Product option has been renamed to Logo and Default Data.
Implementation Notes: This defect correction is available in the early August release of Hosted Expere / Expere Document Services.

DocumentService REST API: Delivery response updated to return the Delivery request ID first
Type: Enhancement Reference: PBI 683581 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Web Services Guide: Appendix: REST API Request and Response Samples > Deliver Request / Response Samples
Summary: The DocumentService REST API Delivery method has been enhanced to immediately return the request ID and delivery groups before calling Wolters Kluwer E-Sign to return ID's for each document package. This enhancement is intended to alleviate timeouts that may occur within the calling application while waiting for a response from DocumentServce.
Implementation Notes: This enhancement is available in the early August release of Hosted Expere / Expere Document Services.

DocumentService REST API: new ListDocuments-synchronous method created
Type: Feature Reference: PBI 670690 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Web Services Guide: ListDocuments-synchronous
Summary: `ListDocuments-synchronous` has been added as a Document Service REST API method and is used to list documents for a given document package.
Implementation Notes: This feature is available in the early August release of Hosted Expere / Expere Document Services.

Supplemental July release

Note: The supplemental July release will be deployed to the CT environment on 7/15 and production environment on 7/22.

Bug found in enhanced July release
Type: Defect Reference: PBI 686724 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: After our supplemental July release we found that a bug existed in DocumentService/EDS. As a result, we have rolled back the changes in those components and removed the Change Logs. We will be releasing those changes at a future date; new date is yet to be determined. All other changes still outlined in the Change Log are available on the respective release dates (outlined above) for each environment.
Implementation Notes: This defect correction has resulted in a rollback of previously-released changes as part of the Hosted Expere / Expere Document Services.

Fee Merging behavior enhanced
Type: Defect Reference: PBI 684633 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: A user reported that Default Data for Late Fee and Prepayment Penalty information resulted in duplicate Late Fee information when merging Default Data with the request transaction. Subsequently, this duplicate information resulted in an error in DocViewer.
Solution: This issue has been addressed: policies containing Late Charges and Prepayment Penalties exist now merge correctly into the request transaction.
Implementation Notes: This defect correction is available in the supplemental July release of Hosted Expere / Expere Document Services.

New Environment and Connectivity Details section added to Web Services Guide
Type: Enhancement Reference: PBI 681311 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Web Services Guide: Environment and Connectivity Details - Customer Test (CT), Environment and Connectivity Details - Production Environment
Summary: We have added new Environment and Connectivity Details pages to our Web Services Guide; each topic is specific to our CT or production environments and lists SOAP / REST important endpoints, application URL's, IP addresses, and Swagger pages .
Implementation Notes: This enhancement is available in the supplemental July release of Hosted Expere / Expere Document Services.

System Requirements enhanced for Tool Suite user guide
Type: Enhancement Reference: PBI 681833 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Tool Suite User Guide: System Requirements
Summary: As we enhance consistency for all our end user documentation deliverables, we are ensuring that system requirements information is present in the appropriate artifacts, specifically the Expere Document Services Tool Suite User Guide: System Requirements
Implementation Notes: This enhancement is available in the supplemental July release of Hosted Expere / Expere Document Services.

WCAG 2.0: Empty figure tags / blank paragraph behavior enhanced
Type: Enhancement Reference: PBI 684124 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: Users reported an issue with empty Paragraph and Figure tags when running a full accessibility check in Adobe Acrobat. It was determined that the stylesheet used when generating the document inserted duplicate blocks that did not contain any content. This behavior has been enhanced: empty Paragraph and Figure tags are no longer created in the tag tree and will not cause a full accessibility check to fail.
Implementation Notes: This enhancement is available in the supplemental July release of Hosted Expere / Expere Document Services.

July

Integrators / Hosted Expere Integration to Wolters Kluwer E-Sign: Invitation to register for electronic package delivery
Type: Feature Reference: PBI 650345 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Feature Guide: Register; Expere Document Services Tool Suite User Guide: SETUP Page
Summary: As part of the Hosted Expere to Wolters Kluwer E-Sign (WKES) feature, the WKES Register method was created to support registering users for electronic delivery of document packages. When the WKES SmartContentStatus returned to Hosted Expere for a given address is either "NoContentStatus" or if the user does not exist, users will now receive an invitation from WKES to register for electronic package delivery. Additionally, we have introduced the following statuses: InvalidEmailAddress: indicates the user email address is not valid. UserContainerDoesNotExist: Indicates that the User Container has not been entered for the account in the Tool Suite > SETUP Page. Finally, we have updated the Expere Document Services Tool Suite > SETUP page to include a new System Admin (Invite User) Username, updated Username to Compliance Officer Username, and added a User Container field.
Implementation Notes: This feature is available in the July release of Hosted Expere / Expere Document Services .

WCAG 2.0: Waiver of Grantors Rights-GA tagging and screen reading enhanced
Type: Enhancement Reference: PBI 680864 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: The following WCAG 2.0-related items have been addressed regarding the Waiver of Grantors Rights-GA document: Tagging was incorrect: the tag for Notary Commission Expiration Date - OBJR should have appeared after the tags for Date and Seal. The Adobe Acrobat screen reader read sections in the wrong order: the screen reader read the field for Grantor on page one, then began reading the field next to My Commission expires and then read page one items four and five. This issues have been resolved; tagging and screen reading behaviors have been enhanced to act as expected.
Implementation Notes: This enhancement is available in the July release of Hosted Expere / Expere Document Services.

GenerateUpdate callback behavior enhanced - REST Deliver method
Type: Defect Reference: PBI 680150 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: Users reported receiving a `GenerateUpdate` callback when calling the `DocumentService` REST API `Deliver` method. This is incorrect behavior; a `GenerateUpdate` callback should not be sent when making a `Deliver` call.
Solution: This behavior has been enhanced; users will not receive a `GenerateUpdate` callback when making a `Deliver` REST call.
Implementation Notes: This defect correction is available in the July release of Hosted Expere / Expere Document Services.

ConfigureRoles behavior enhancement
Type: Enhancement Reference: PBI 680967 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: Based on user feedback, we updated `ConfigureRole` so the roles are not sequenced when we send them to eOriginal. By not sequencing the roles the email invitations will not be automatically sent out by eOriginal.
Implementation Notes: This enhancement is available in the July release of Hosted Expere / Expere Document Services.

June

Field linking now supported for use with Wolters Kluwer E-Sign
Type: Feature Reference: PBI 674227 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: Expere now supports linking fillable fields with option (radio) buttons and checkboxes for use with Wolters Kluwer E-Sign (WKES). This enhancement allows better representation of fillable field relationships on the document within WKES, ensuring end users completing the documents are only completing the fields necessary. If you are interested in using this feature, please contact your Professional Services representatitve for more information.
Implementation Notes: This feature is available in the June release of Hosted Expere / Expere Document Services.

Tool Suite: OPPSA Conversion to EZ Config - Support for EZ Config Product and Organization for Select Generate Deliver / Select and Generate / Generate functions
Type: Enhancement Reference: PBI 675396 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere DocumentServices Tool Suite User Guide: Select Generate Deliver, Select and Generate, Select / Generate
Summary: As part of the OPPSA conversion project to EZ Config, the Tool Suite has been updated to allow users to pass in an EZ Config Product and/or Organization into either a Select Generate Deliver, Select and Generate, and Select / Generate method. This allows users to merge logo and product information into an Expere transaction without utilizing EZ Config's UpdateTransaction API. The Tool Suite functionality for each of the aforementioned pages has been updated to include a new EZ Merge Options dropdown; this replaces the Default Data > Apply Logo from Default Data checkbox. For more information, consult the Tool Suite User Guide: Select Generate Deliver, Select and Generate, Select / Generate pages.
Implementation Notes: This feature is available in the June release of Hosted Expere / Expere Document Services.

ListDocuments - PackageID added to result
Type: Enhancement Reference: PBI 546262 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services WebServices Guide: Documents
Summary: Previously in PBI 671445, a new `PackageID` parameter was added to the `Documents` data type in the Expere Document Services `DocServices` WSDL. As part of this PBI, the package ID for each document will now be returned in the `ListDocumentsResponse`.
Technical Notes: Sample response snippet:
    <r:DocumentSet>
                <r:Document>
                   <r:DocumentID>PKGD.AuthorizationDocumentAccounts</r:DocumentID>
                   <r:StoredDocID>PKGD.AuthorizationDocumentAccounts</r:StoredDocID>
                   <r:DisplayName>Authorization Accounts</r:DisplayName>
                   <r:Type>Dynamic</r:Type>
                   <r:Phase>DepositAccountOpening</r:Phase>
                   <r:PackageID>PKG.DepositAccountOpening</r:PackageID>
                </r:Document>
Implementation Notes: This feature is available in the June release of Hosted Expere / Expere Document Services.

Support for Embedded PDF
Type: Feature Reference: PBI 677951 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: Wolters Kluwer has introduced a new authoring format as part of WCAG 2.0 compliance initiative. When authored as a "PDF." (PDF prefix), the Expere Engine now generates documents with an embedded .PDF file of an image. For more information, see the following Expere Authoring and Tools changelog.
Implementation Notes: This feature is available in the June release of Hosted Expere / Expere Document Services.

DocumentService: OPPSA Conversion to EZ Config - Support for EZ Config Product and Organization for Generate / Generate-Synchronous methods
Type: Feature Reference: PBI 678710 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: As part of the OPPSA conversion project to EZ Config, Document Services has been updated to allow users to pass in an EZ Config Product and/or Organization into either a Generate or Generate-Synchronous API method. This allows users to merge logo and product information into an Expere transaction without utilizing EZ Config's UpdateTransaction API. Document Services has been updated to pass in a new `<MergeEZConfig>` element with enumerated values of `LogoOnly`, `DefaultDataOnly`, or `LogoAndDefaultData` within the `<EZConfig>` element for a request first.
Technical Notes: Sample request:
    <EZConfig>
                   <OrgName>OrgBaseLibrary - CDL</OrgName>
                   <OrgAlias>BaseLibrary\.(.*)</OrgAlias>
                   <OrgLOB>Consumer Direct Lending</OrgLOB>
                   <MergeEZConfig>
                      <Enum>DefaultDataOnly</Enum>
                   <MergeEZConfig>
                   <ProductNames>
                      <string>Product - CDL BaseLibrary</string>
                   </ProductNames>
                </EZConfig>
Implementation Notes: This feature is available in the June release of Hosted Expere / Expere Document Services.

eOriginal: Instance Display Name added when creating Doc Profile
Type: Enhancement Reference: PBI 677125 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: Document Generation Services has been updated to display the document name when a user is logged into Command Center and Closing Center. Instead of all documents showing as 'Closing Document' you will now see the actual instance display name. This functionality was enhanced for the closing documents but the eNote will still appear as such since it is already unique in the naming convention.
Implementation Notes: This enhancement is available in the June release of Hosted Expere / Expere Document Services.

eOriginal: Addition of Execution Type To Uploaded Documents
Type: Enhancement Reference: PBI 677580 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: Document Generation Services has been updated to allow the eOriginal Closing Center the ability to determine the execution type for each closing document that is uploaded.
Implementation Notes: This enhancement is available in the June release of Hosted Expere / Expere Document Services.

User documentation navigation enhancements: new Getting Started guide / Expere Document Services Web Services Guide API restructure
Type: Enhancement Reference: PBI 677461 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Hosted Expere Landing Page; Expere Document Services Web Services Guide
Summary: We made the following user documentation changes: Hosted Expere Landing Page: we have added a new Getting Started section and guide to the landing page; this provides a high-level overview of which documents you will use during and after your implementation Expere Document Services Web Services Guide: we have reformatted the web services guide to allow for better ease of navigation when examining SOAP and REST API information.
Implementation Notes: This enhancement is available in the June release of Hosted Expere / Expere Document Services .

Hosted Expere to WKES Integration Feature Guide: callback routing expanded
Type: Enhancement Reference: PBI 677738 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Feature Guide: Using Callbacks > Callback Routes
Summary: We have enhanced the Feature Guide > Using Callbacks section to include additional information about the following callback routes: generate delivery delivery setup
Implementation Notes: This enhancement is available in the June release of Hosted Expere / Expere Document Services.

eOriginal Reverse Registration
Type: Feature Reference: PBI 676849 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: eOriginal Quick Guide: eNote MERS Reverse Registration Workflow
Summary: The feature allows a user to reverse a MERS registration for the eNote that is generated in the transaction. When the `/Txn/EOriginalMERSReverseRegistrationInd` is passed as true in the transaction .XML file, we call for the reverse registration of the eNote.
Implementation Notes: This feature is available in the June release of Hosted Expere / Expere Document Services.

WCAG 2.0: DocumentReference / hyperlink tagging and screen reader behavior enhanced
Type: Enhancement Reference: PBI 678807 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: The following WCAG 2.0-related items have been addressed (applicable document appears in bold next to the bulleted issue): Credit Agreement HE Variable Draw Repay-TX document: the Adobe screen reader read the italicized TexasConstitution out of order; the tag for TexasConstitution was incorrect in the tag tree. These items have been resolved: TexasConstitution is now read in the correct by the screen order and appears correctly in the tag tree. Welcome Approved Notice document: the tag for "www.oregonlawhelp.com" was out of position and in its own `Section` within the tag tree; it appeared after the tagging for the paragraph where it resided. This item has been updated; www.oregonlawhelp.com now appears in the same section with its surrounding paragraph information.
Implementation Notes: This enhancement is available in the June release of Hosted Expere / Expere Document Services.

Integrators: OPPSA Conversion to EZ Config - Support for EZ Config Product and Organization for SelectGenerateDeliver / SelectAndGenerate / Generate methods
Type: Feature Reference: PBI 676380 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services: MergeEZConfig; MergeEZConfigEnum
Summary: As part of the OPPSA conversion project to EZ Config, Expere Document Services has been updated to allow users to pass in an EZ Config Product and/or Organization into either a SelectGenerateDeliver, SelectAndGenerate, and Generate API method. This allows users to merge logo and product information into an Expere transaction without utilizing EZ Config's UpdateTransaction API. Expere Document Services has been updated to pass in a new `<MergeEZConfig>` element with enumerated values of `LogoOnly`, `DefaultDataOnly`, or `LogoAndDefaultData` within the `<EZConfig>` element for a request first.
Technical Notes: Sample request:
    <EZConfig>
                   <OrgName>OrgBaseLibrary - CDL</OrgName>
                   <OrgAlias>BaseLibrary\.(.*)</OrgAlias>
                   <OrgLOB>Consumer Direct Lending</OrgLOB>
                   <MergeEZConfig>
                      <Enum>DefaultDataOnly</Enum>
                   <MergeEZConfig>
                   <ProductNames>
                      <string>Product - CDL BaseLibrary</string>
                   </ProductNames>
                </EZConfig>
Implementation Notes: This feature is available in the June release of Hosted Expere / Expere Document Services.

May

Engine: URLA address field behavior enhanced (Salesforce case # 00774441)
Type: Defect Reference: PBI 669577 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
UPDATE: Recently we made a development change to address Salesforce case # 00774441 where two initial fields that should have been present adjacent to Your Initials in the middle of the page were superimposed over Additional Borrowers at the bottom of the page. This change has been backed out of an enhanced CT deployment scheduled to occur on 4/16. This change will be re-released in a near future release. Issue: Similarly to PBI 669576, a related initial issue was reported when generating the URLA for transaction using the DC version of the form: two initial fields that should have been present next to Your Initials on the middle of the page were superimposed over the words Additional Borrower Names on the footer of the page (see example below).
Solution: Initial fields, previously hovering over footer text, are now appropriately placed under the Your Initials field in the middle of the page
Implementation Notes: This defect correction is available in the May release of Hosted Expere / Expere Document Services.

eOriginal: Borrower/Cosigner/Power-of-Attorney behavior enhanced
Type: Enhancement Reference: PBI 669619 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: We have added an error message for when a user tries to send an eNote transaction to eOriginal with unsupported party types. If the borrower or cosigner in a transaction is not an individual or a sole proprietorship, or if there is not an individual power of attorney passed for the borrower or cosigner the transaction will fail. eOriginal does not support any other party types for the eNote signers.
Implementation Notes: This enhancement is available in the May release of Hosted Expere / Expere Document Services.

eOriginal > Upload feature: support uploading documents to Non-MERS eVault
Type: Feature Reference: PBI 668967 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: eOriginal Quick Guide: eNote Upload Workflow Outline; Document Generation Services: SETUP page
Summary: Previous work was completed to allow the collection of non-MERS eVault credentials. This PBI is using those credentials to send the appropriate transaction data to the correct eVault, based on the type of upload the user has specified. (`/Txn/EOriginalUploadTransactionType`)
Implementation Notes: This feature is available in the May release of Hosted Expere / Expere Document Services.

Transaction merging behavior enhanced (Salesforce case # 00793373)
Type: Defect Reference: PBI 672854 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: Users reported that when attempting to merge an EZ Config Default Data organization into the transaction .XML, the resulting .XML file displayed only a single "undefined" line. This behavior occurred when attempting to merge organization data without any product information.
Solution: This issue has been resolved; users may now merge Default Data organzation information with the request transaction.
Implementation Notes: This defect correction is available in the May release of Hosted Expere / Expere Document Services.

DocumentService: default enum values verified for parameters
Type: Defect Reference: PBI 672665 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: DocumentService users reported transaction failures when passing in a request with a barcode ancillary output without a value in the `horizontalAlignment` parameter.
Solution: This issue has been resolved: if no value is specified for `horizontalAlignment`, the value defaults to "Right"
Implementation Notes: This defect correction is available in the May release of Hosted Expere / Expere Document Services.

eOriginal > Upload feature: supported expanded for non-eNote transactions
Type: Feature Reference: PBI 668967 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: eOriginal Quick Guide: Upload Workflow Outline > How do we identify when documents should be uploaded to eOriginal?; Expere Transaction XPaths for eOriginal
Summary: Updates have been made to collect the credentials for eOriginal that are tied to the non MERS eVault. This eVault is used when uploading transactions that do not generate a eNote. This functionality does require proper setup with eOriginal to provision a non MERS eVault for an organization.
Implementation Notes: This feature is available in the May release of Hosted Expere / Expere Document Services.

WCAG 2.0: Reading order behavior enhanced
Type: Enhancement Reference: PBI 669277 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: As part of our continued effort to ensure WCAG 2.0 compliance, we have updated read order functionality. Users originally reported that the Adobe Acrobat screen reader was reading sections of pages in the wrong order within the FHA Mortgage document.
Implementation Notes: This enhancement is available in the May release of Hosted Expere / Expere Document Services.

Supplemental April release

Note: Additional changes were deployed to the CT environment on 4/15 and 4/16 and will be included in the production release on 4/21.

Callback to Salesforce feature
Type: Feature Reference: PBI 669932 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Web Services Guide: Callback; Callback Authentication > AuthorizationHeaderOverride
Summary: As part of the Callback to Salesforce feature, a new optional string parameter for `<AuthorizationHeaderOverride/>` has been added to the `<callback/>` element of the request. The value is passed in the AuthorizationHeaderOverride will be used as the key for the authorization header for the token returned in the response. This allows headers to be ‘customizable’ and support callbacks to systems which can only receive tokens under certain header types.
Technical Notes: Sample request snippet below:
    	"generate": {
    		"request": {
    			"daysToExpire": 0,
    			"documentFormat": "PDF",
    			"transactionData":<base64datahere>",
    			"contentIdentifier": "BaseLibrary.PKG.Default",
    			"callback": {
    				"AuthorizationHeaderOverride": "TestHeader"
    			},
Implementation Notes: This feature is available in the supplemental April release of Hosted Expere / Expere Document Services.

Integrators: `DocServices` WSDL updated to include PackageID in ListDocumentsResponse
Type: Feature Reference: PBI 671445 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Web Services Guide: Documents
Summary: A new `PackageID` parameter has been added to the `Documents` data type in the Expere Document Services `DocServices` WSDL. The package ID for each document will be returned in the `ListDocumentsResponse` in a future release.
Implementation Notes: This enhancement is available in the supplemental April release of Hosted Expere / Expere Document Services .

WK Hosted > WKES Integration: ElectronicOnly and ElectronicWithESign behavior updated
Type: Enhancement Reference: PBI 670712 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Feature Guide: Deliver > Special Considerations
Summary: We have modified the functionality for the `ElectronicOnly` and `ElectronicWithEsign` delivery options to use mailing information from the `Recipient` element when parties have not consented to electronic delivery. The Recipient information will be used as the ‘backup’ information for paper delivery when either electronic method cannot be used. If Recipient information is not provided, DiscreteParties for Paper Delivery will be used. parties have not consented to electronic delivery. The parties represented within the `Recipient` element would receive a physical, paper mailing.
Implementation Notes: This enhancement is available in the supplemental April release of Hosted Expere / Expere Document Services.

eOriginal: Namespace functionality enhanced
Type: Defect Reference: PBI 674121 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: An issue was reported when sending an eNote to eOriginal. It was determined that the transation failed due the addition of a namespace.
Solution: Document Generation Services was updated to support the namespace in the transaction and will successfully pass the required data to eOriginal.
Implementation Notes: This defect is available in the supplemental April release of Hosted Expere / Expere Document Services.

April

Note: The April release was deployed to the CT environment on 4/6 and will be included in the production release on 4/21.

eOriginal > Upload feature: eNote option usage behavior enhanced
Type: Feature Reference: PBI 645942 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: eOriginal Quick Guide: Expere Transaction XPaths for eOriginal and eNote Upload Workflow Outline
Summary: Current support of the upload feature is limited to transactions where the eNote is generated. The user must pass the /Txn/EOriginalUploadTransactionType to indicate that their transaction generates an eNote. The user does still need to pass the /Txn/EOriginalUploadInd along with the new type in order to get the documents to upload successfully.
Implementation Notes: This feature is available in the April release of Hosted Expere / Expere Document Services.

eOriginal > Upload feature: document viewing limit added
Type: Feature Reference: PBI 663313 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: We have limited the number of documents each signer sees when they are logged into eOriginal. The signers will only have visibility into the list of documents that they are eSigning and the documents that do not support eSignatures or do not have signatures.
Implementation Notes: This feature is available in the April release of Hosted Expere / Expere Document Services.

eOriginal > Upload feature: AutoDate field added to signatures
Type: Feature Reference: PBI 665323 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: eOriginal Quick Guide: Upload Workflow Outline > Signing the document
Summary: With this release, the signature lines have been updated to automatically populate the date when the eSignature is completed. This applies to the closing documents only and not the eNote. The EsignatureDateSupport attribute needs to be passed as true in the request for the date to be added to the documents correctly.
Implementation Notes: This feature is available in the April release of Hosted Expere / Expere Document Services.

eOriginal > Upload feature: FillableFieldSet enhanced to support mutually exclusive checkboxes
Type: Feature Reference: PBI 623980 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: eOriginal Quick Guide: Upload Workflow Outline > Enhanced Support
Summary: Support has been added to account for documents that contain mutually exclusive checkboxes. The field will be available for the first party listed in the Expere response that is signing the document if there is only one set of checkboxes.
Implementation Notes: This feature is available in the April release of Hosted Expere / Expere Document Services.

WCAG 2.0: Split tables producing error in Initial Disclosure Package transaction (Salesforce case # 00748724)
Type: Defect Reference: PBI 660304 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: A user reported that their transactions for the Initial Disclosure Package repeatedly failed when attempting to generate documents using the output type of TaggedPDF's. The result consisted of a NullPointerException in the error message and log file. Additionally with this PBI, development reviewed the following issues: Tables which spanned across more than one page resulted in table headers not appearing, and Adobe Acrobat Accessibility Checker producing an error and being unable to read the table headings. Signatures in the footer were not read in the correct order by the Adobe Acrobat Accessibility Checker.
Solution: We have enhanced this behavior; as a result: Initial Disclosure Packages now generate successfully for an output type of TaggedPDF. Table headings and signatures in the footer of the document are read in the correct order by the Adobe Acrobat Accessibility Checker.
Implementation Notes: This defect correction is available in the April release of Hosted Expere / Expere Document Services.

eOriginal OrgAdditionalAddress Mapping updated to use 'type'
Type: Defect Reference: PBI 671198 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: We made a change so the Payment Center address prints in the Payments section of the eNote instead of the first address the organization passes.
Implementation Notes: This defect correction is available in the April release of Hosted Expere / Expere Document Services.

Barcode 128 behavior enhanced (Salesforce case # 00625326)
Type: Defect Reference: PBI 634764 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Implementation Strategies: Barcode Types (Fonts) and Patterns
Issue: Users reported barcodes did not appear on RTF documents when using a Barcode128 type with documents containing EZ Config Packages and Packets setup information. Internal analysis determined that the presence of %Page% and / or %TotalPages% when using Barcode128 and generating RTF outputs resulted in the barcode not appearing.
Solution: When either %Page% or %TotalPage% is included in the barcode pattern for RTF output and barcode type of 128, the page or totalpage is removed from the barcode; all other barcode data will be used for generating the barcode.
Implementation Notes: This defect correction is available in the April release of Hosted Expere / Expere Document Services.

Engine: URLA initial field behavior enhanced (Salesforce case # 00761731)
Type: Defect Reference: PBI 669576 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: A user reported that the eSignable portion of the second initial field on page three (3) of the URLA was floating above the lower right footer area where the initial field should have been placed. Internal analysis determined that an issue existed with how middle pages of generated documents handled intials with DC loans for married couples (see example below).
Solution: This issue has been resolved; the fillable field for the second initial field now apperas as expected in the bottom right footer of the document.
Implementation Notes: This defect correction is available in the April release of Hosted Expere / Expere Document Services.

Integrators / Hosted Expere Integration to Wolters Kluwer E-Sign: GetRecipientDeliveryActionItems REST API method created
Type: Enhancement Reference: PBI 668310 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Web Services Guide: GetRecipientDeliveryActionItem
Summary: As an enhancement to the Hosted Expere Integration to Wolters Kluwer E-Sign feature, we have added a new `GetRecipientDeliveryActionItem` REST API method that when called, provides a response with information on open or actionable package statuses in Wolters Kluwer E-Sign for a given recipient; see below: for those recipients that have an `ElectronicWithEsign` package that has not been signed. for those recipients that have an `ElectronicOnly` package that has not been viewed. The `GetRecipientDeliveryActionItem` call must contain two required parameters; the `accountId` and `RecipientEmailAddress`. The response message will consist of the following, specifically an action that the recipient needs to perform (ESIGN if `ElectronicWithEsign` or REVIEW if `ElectronicOnly`): PassthroughIdentifier TransationIdentifier Action (either ESIGN or REVIEW depending on the delivery format) Loan number PackageId WKESId GroupId Documents (DocID's of the documents associated to the open WKES package)
Technical Notes: Sample response below:
    {
        "packages": [
            {
                "transactionIdentifier": "475095",
                "passthroughIdentifier": "123465er3234",
                "groupId": "6161d8c9-cd69-443a-9b3a-ae004ccb8b28",
                "wkesId": "4560083",
                "packageId": "4559657",
                "action": "REVIEW",
                "documents": [
                    {
                        "docID": "PKGD.NoticeOfHomeownershipCounseling-DEF",
                        "instanceDisplayName": "Notice of Homeownership Counseling - B2_FName B2_MName B2_LName"
                    },
                    {
                        "docID": "PKGD.HUDForm92070ServicemembersCivilReliefAct-RS",
                        "instanceDisplayName": "HUD Form 92070 Servicemembers Civil Relief Act"
                    }
                ]
            },
            {
                "transactionIdentifier": "475095",
                "passthroughIdentifier": "123465er3234",
                "groupId": "e6ec311a-c1f3-458a-87a7-a560a2305f32",
                "wkesId": "4560082",
                "packageId": "4559656",
                "action": "REVIEW",
                "documents": [
                    {
                        "docID": "PKGD.NoticeOfHomeownershipCounseling-DEF",
                        "instanceDisplayName": "Notice of Homeownership Counseling - B1_FName B1_MName B1_LName"
                    },
                    {
                        "docID": "PKGD.HUDForm92070ServicemembersCivilReliefAct-RS",
                        "instanceDisplayName": "HUD Form 92070 Servicemembers Civil Relief Act"
                    }
                ]
            }
        ]
    }
Implementation Notes: This enhancement is available in the April release of Hosted Expere / Expere Document Services.

eOriginal > Upload feature: Wildcard initial support added when initializing
Type: Feature Reference: PBI 667032 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: eOriginal Quick Guide: Upload Workflow Outline
Summary: Support has been added for documents that contain initial fields where the content does not specify the party that should complete the initials. The fields will be available for the first party that is signing the document. Note: This PBI is part of the Upload feature that is currently work-in-progress and will be available in a near-future sprint.
Implementation Notes: This enhancement is available in the April release of Hosted Expere / Expere Document Services.

eOriginal > Upload feature: FillableFieldSet enhanced to support multi-line text fields
Type: Feature Reference: PBI 623977 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: eOriginal Quick Guide: Upload Workflow Outline
Summary: Support has been added to account for documents that contain multiline text fields. The field will be available for the first party listed in the Expere response that is signing the document if there is only one set of text fields.
Implementation Notes: This feature is available in the April release of Hosted Expere / Expere Document Services.

eOriginal > Upload feature: FillableFieldSet enhanced to support single line text fields
Type: Feature Reference: PBI 623976 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: eOriginal Quick Guide: Upload Workflow Outline
Summary: Support has been added to account for documents that contain single line text fields. The field will be available for the first party listed in the expere response that is signing the document if there is only one set of text fields.
Implementation Notes: This feature is available in the April release of Hosted Expere / Expere Document Services.

eOriginal: role name changed for parties not signing eNote
Type: Feature Reference: PBI 659108 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: eOriginal Quick Guide: Upload Workflow Outline > Signer Roles
Summary: All parties who are signing documents that do not include the eNote will have a role of 'Signer' to be more generic and to allow for more than 8 total parties signing documents in a single transaction within eOriginal. The parties who sign the eNote will still have the 'Borrower' role and is still limited to 8 parties with the 'Borrower' role.
Implementation Notes: This feature is available in the April release of Hosted Expere / Expere Document Services.

eOriginal: support for Power of Attorney enhanced
Type: Enhancement Reference: PBI 658678 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: eOriginal Quick Guide: Expere Transaction XPaths for eOriginal > Signer Types
Summary: With this release, we have added support for a power of attorney to sign the eNote for the borrowers and cosigners.
Implementation Notes: This enhancement is available in the April release of Hosted Expere / Expere Document Services.

Hosted Expere to WKES Integration Feature Guide now available
Type: Enhancement Reference: PBI 658996 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Feature Guide or through the Hosted Expere landing page.
Summary: Hosted Expere users working through the Hosted Expere to WKES Integration can now consult the Feature Guide created specifically for this feature workflow. The new Expere Document Services Feature Guide area is intended to provide a more comprehensive look at each feature available and various integration strategies, which may help with user implementation. Each feature guide will consist of its own set of help topics, with links to request/response samples (where applicable), the methods which can be used (REST or SOAP), and other critical information.
Implementation Notes: This enhancement is available in the April release of Hosted Expere / Expere Document Services.

Read order and signature bookmark behavior enhanced
Type: Enhancement Reference: PBI 634558 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: Users reported the following issues: The Adobe Acrobat screen reader read the Confirm Receipt section, located at the bottom of the page, before items on the same page that preceded it. Signatures appeared out of order in the Bookmark navigation pane in a tagged PDF. Instead of appearing after specific heading bookmarks, they appeared before them (see screen shot below). This behavior has been enhanced: for non-merged, single documents, the screen reader reads the items in the correct order while bookmarks appear in the correct order.
Implementation Notes: This enhancement is available in the April release of Hosted Expere / Expere Document Services.

Integrators: response now returns SignatureUniqueIdentifier for fillable checkbox
Type: Enhancement Reference: PBI 649949 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: Previously, in PBI 656099, we updated the EDS (DocumentService) WSDL to include a `SignatureUniqueIdentifier` element for each fillable checkbox in a Notary Block; the `SignatureUniqueIdentifier` element connects the fields within the Notary Block to the notary signature so the electronic delivery platform knows which fields are associated with each specific notary block. For this PBI, Expere now returns the `SignatureUniqueIdentifier` for fillable checkboxes in the response file.
Implementation Notes: This enhancement is available in the April release of Hosted Expere / Expere Document Services.

March

Note: PBI 661929 will appear in the CT environment on 3/11 and in the production environment on 3/18.

Expere Engine: DefaultData fees behavior enhanced
Type: Enhancement Reference: PBI 661929 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: Users reported that Default Data policy fees did not merge with request transaction fees; instead, they appeared after the existing fees. This behavior has been enhanced so that Default Data fees are merged with existing fees under the same fee name. Response sample before enhancement: Response sample after enhancement: Note: if no fees exist on the transaction, all fees from default data are appended to the transaction; additionally, deposit fees with the same name that have fee details present will have any matching detail nodes merged.
Implementation Notes: This enhancement is available in the March release of Hosted Expere / Expere Document Services.

Note: The March release will occur in the CT environment on 3/5 and in the production environment on 3/18. .

Integrators / Hosted Expere Integration to Wolters Kluwer E-Sign: SmartConsentStatus descriptions enhanced
Type: Enhancement Reference: PBI 666082 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Feature Guide: Register
Summary: As part of our Hosted Expere Integration to Wolters Kluwer E-Sign feature, we have updated the SmartConsentStatus responses to contain more descriptive information. For more information, see the Register topic within the Feature Guide for more information.
Implementation Notes: This feature is available in the March release of Hosted Expere / Expere Document Services.

PostProcess call updated to include DiscreteParty information
Type: Defect Reference: PBI 665530 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: A user reported an issue where DiscretePartyID values were not included in the response file when selecting the eNote option with MergedCopyPDF as an ancillary option. Additionally, it was discovered that the InstanceProperties, DiscreteParties, and InstancePageSize containers were also not being returned.
Solution: This behavior has been enhanced so that the Expere response now includes the DiscretePartyID value(s) as well as InstanceProperties, DiscreteParties, and InstancePageSize containers when generating an eNote with MergedCopyPDF as an ancilary option.
Implementation Notes: This defect correction is available in the March release of Hosted Expere / Expere Document Services.

eOriginal > Upload feature: FillableFieldSet enhanced to support checkboxes
Type: Feature Reference: PBI 623979 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: eOriginal Quick Guide: Upload Workflow Outline
Summary: Support has been added to account for documents that contain checkbox fields. The field will be available for the first party listed in the expere response that is signing the document if there is only one set of checkboxes.
Implementation Notes: This feature is available in the March release of Hosted Expere / Expere Document Services.

eOriginal > Upload feature: FillableFieldSet enhanced to support initial fields
Type: Feature Reference: PBI 623578 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: eOriginal Quick Guide: Upload Workflow Outline
Summary: Support has been added to account for documents that contain initial fields. The fields will be available for the parties that are signing the document.
Implementation Notes: This feature is available in the March release of Hosted Expere / Expere Document Services.

eOriginal: `transactionBusinessProcessName` supported
Type: Enhancement Reference: PBI 662149 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts:eOriginal Quick Guide: Expere Transaction XPaths for eOriginal
Summary: In order to accommodate the filtering of transactions within the eOriginal vault we have added the ability to pass the transactionBusinessProcessName to eOriginal. Users should pass this business process name in their transaction xml as`/Txn/EOriginalTransactionBusinessProcessName`. There are steps that need to be completed in eOriginal for the enhancement to full function.
Implementation Notes: This enhancement is available in the March release of Hosted Expere / Expere Document Services.

Integrators / Hosted Expere Integration to Wolters Kluwer E-Sign: Tool Suite > SETUP Page updated to selected callback information
Type: Feature Reference: PBI 651577 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Tool Suite User Guide: SETUP Page > Enable Callbacks sub-section
Summary: As part of our Hosted Expere Integration to Wolters Kluwer E-Sign feature, we have updated the REST Credentials section on the Tool Suite SETUP page to include three new checkboxes: Generate Delivery Setup Delivery Status Selecting a particular checkbox(es) sends callbackes to the user for the particular REST API method.
Implementation Notes: This feature is available in the March release of Hosted Expere / Expere Document Services.

eNotary / Integrators: SignatureUniqueIdentifier added to FillableCheckbox and FillableText in EDS WSDL
Type: Enhancement Reference: PBI 656099 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Web Services Guide: FillableCheckbox; FillableText
Summary: To support eNotary functionality within Hosted Expere, we updated the DocumentServices WSDL to now include a `SignatureUniqueIdentifier` element for `FillableCheckbox` and `FillableText` data types. We will be updating functionality in a near-future sprint to return this element and value in the response file. Note: This is an optional parameter.
Technical Notes: Sample WSDL code snippets: FillableCheckbox
    <xs:complexType name="FillableCheckbox">
    				<xs:complexContent mixed="false">
    					<xs:extension base="tns:FillableField">
    						<xs:sequence>
    							<xs:element minOccurs="0" maxOccurs="1" name="Checked" nillable="true" type="tns:ExpereBoolean"/>
    							<xs:element minOccurs="0" maxOccurs="1" name="GroupID" nillable="true" type="xs:string"/>
    							<xs:element minOccurs="0" maxOccurs="1" name="SignatureUniqueIdentifier" nillable="true" type="xs:string"/>
    						</xs:sequence>
    					</xs:extension>
    				</xs:complexContent>
    			</xs:complexType>
FillableText
    <xs:complexType name="FillableText">
    				<xs:complexContent mixed="false">
    					<xs:extension base="tns:FillableField">
    						<xs:sequence>
    							<xs:element minOccurs="0" maxOccurs="1" name="Width" nillable="true" type="tns:ExpereFloat"/>
    							<xs:element minOccurs="0" maxOccurs="1" name="Height" nillable="true" type="tns:ExpereFloat"/>
    							<xs:element minOccurs="0" maxOccurs="1" name="FontSize" nillable="true" type="xs:float"/>
    							<xs:element minOccurs="0" maxOccurs="1" name="NumberOfCharacters" nillable="true" type="xs:int"/>
    							<xs:element minOccurs="0" maxOccurs="1" name="FontName" nillable="true" type="xs:string"/>
    							<xs:element minOccurs="0" maxOccurs="1" name="FieldType" nillable="true" type="tns:FillableFieldTypeEnum"/>
    							<xs:element minOccurs="0" maxOccurs="1" name="FieldText" nillable="true" type="xs:string"/>
    							<xs:element minOccurs="0" maxOccurs="1" name="HorizontalAlignment" nillable="true" type="tns:HorizontalAlignmentEnum"/>
    							<xs:element minOccurs="0" maxOccurs="1" name="Underline" nillable="true" type="xs:boolean"/>
    							<xs:element minOccurs="0" maxOccurs="1" name="MultiLine" nillable="true" type="xs:boolean"/>
    							<xs:element minOccurs="0" maxOccurs="1" name="SignatureUniqueIdentifier" nillable="true" type="xs:string"/>
    						</xs:sequence>
    					</xs:extension>
    				</xs:complexContent>
    			</xs:complexType>
Implementation Notes: This enhancement is available in the March release of Hosted Expere / Expere Document Services.

Supplemental February release

Note: The supplemental February release will occur in the CT environment on 2/18 and in the production environment on 3/18.

eOriginal: transaction destruction behavior enhanced
Type: Enhancement Reference: PBI 658736 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: eOriginal Quick Guide: eNote Destruction Workflow Outline
Summary: A user can now destroy a transaction in eOriginal (destruction workflow) if the required data is missing. Previously the user would get an error before the destruction was done.
Implementation Notes: This enhancement is available in the February Out of Band release of Hosted Expere / Expere Document Services.

eOriginal: Mappings updated
Type: Enhancement Reference: PBI 647253 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: eOriginal data points used for a fixed or ARM loan
Summary: With this release, additional mappings were added for further support of fixed and ARM loans for eOriginal.
Implementation Notes: This enhancement is available in the February Out of Band release of Hosted Expere / Expere Document Services.

Integrators / Hosted Expere Integration to Wolters Kluwer E-Sign: Delivery Groupings logic updated for SuppressPaperDelivery
Type: Feature Reference: PBI 654114 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Feature Guide: Deliver method > Special Considerations
Summary: As part of our Hosted Expere Integration to Wolters Kluwer E-Sign feature, Delivery Groupings have been updated for use with SuppressPaperDelivery: Expere returns a `SuppressPaperDelivery` element and value in the `DiscreteParty` section of the response. If this value is set to "true," a paper delivery group is not created for the particular discrete party containing the "true" value. :
Implementation Notes: This feature is available in the February Out of Band release for Hosted Expere / Expere Document Services.

Integrators / Hosted Expere Integration to Wolters Kluwer E-Sign: Delivery Groupings logic updated for SmartConsentStatus
Type: Enhancement Reference: PBI 658570 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: As part of our Hosted Expere Integration to Wolters Kluwer E-Sign feature, Delivery Groupings have been updated for use with SmartConsentStatus: Delivery Groupings logic has been added to include a "SmartConsentStatus" when `Delivery Mode = "ElectronicOnly"` or `"ElectronicWithESign"`. When `Delivery Mode = "ElectronicOnly"` or `"ElectronicWithESign"` delivery groupings are created for each unique recipient. Emails returned for each discrete party are analyzed to verify a smart consent status is present within Wolters Kluwer E-Sign to ensure they are registered (or "consented") to receive electronic packages. If any of the recipient emails are not consented, a DirectToPaper delivery mode it utilized, and delivery groupings are created based on that delivery mode.
Implementation Notes: This feature is available in the February Out of Band release for Hosted Expere / Expere Document Services.

Integrators / Hosted Expere Integration to Wolters Kluwer E-Sign: Deliver method enhanced for ElectronicOnly and ElectronicWithEsign option
Type: Feature Reference: PBI 644747 / 649874 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Feature Guide: GetDeliveredImages > Delivery Modes
Summary: As part of our Hosted Expere Integration to Wolters Kluwer E-Sign feature, we have updated our `Delivery` method to now support `ElectronicOnly` and `ElectronicWithEsign` delivery modes. This means that document packages created through the Generate method can be delivered to WKES using either the `ElectronicOnly` or `ElectronicWithEsign` delivery method.
Implementation Notes: This feature is available in the February Out of Band release for Hosted Expere / Expere Document Services.

Integrators / Hosted Expere Integration to Wolters Kluwer E-Sign: GetDeliveredImages method updated to support ElectronicWithESign and ElectronicOnly
Type: Feature Reference: PBI 661128 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Feature Guide: GetDeliveredImages > Delivery Modes
Summary: As part of our Hosted Expere Integration to Wolters Kluwer E-Sign feature, we have updated the `GetDeliveredImages` method to now support `ElectronicWithEsign` and `ElectronicOnly` delivery modes. When either of these options are selected, using the `GetDeliveredImages` method retrieves and returns a merged PDF of the images that were provided to the recipients. Note: For ElectronicWithESign, the image returned will be the signed document package.
Implementation Notes: This feature is available in the February Out of Band release for Hosted Expere / Expere Document Services.

Integrators / Hosted Expere Integration to Wolters Kluwer E-Sign: Callbacks returned
Type: Feature Reference: PBI 650149 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: As part of our Hosted Expere Integration to Wolters Kluwer E-Sign feature, we now return status updates from WKES via the DocumentService callback service. The status are returned in a .JSON format with the following information: TransactionID (transactionIdentifier): the ID returned from the Generate (when DeliveryHold = No) or Deliver request. PassthroughID (passthroughIdentifier): the external identifier provided by the customers calling system on the Generate or Deliver request. DeliveryGroupID (groupId): the ID provided for each unique delivery group created on the request. Wolters Kluwer Package status: all information from Wolters Kluwer E-Sing on the status of the given package. The user will receive a callback message that could resemble the following where bullets above are highlighted:
    {"deliveryResponse":{"transactionIdentifier":"459771","passthroughIdentifier":null,"groupId":"403eab3c-752f-4212-a901-2dca58ff7776",
    "Package":{"PackageDetail":{"Id":"4543067","Status":"DirectToPaper","PushEvent":"CREATED","ReturnedReceivedMsgId":"","LoanNumber":"999888777","Comment":""},
    "PackageAttachments":{"Attachments":{"Attachment":[{"Name":"HUD Approved Counseling Agencies-NV - Oscar James Obligor, Jr..pdf","Number":"0"},{"Name":"HUD Approved Counseling Agencies-NV - Betty Lou Smith.pdf","Number":"1"},
    {"Name":"Notice of Intent to Foreclose-NV - Oscar James Obligor, Jr..pdf","Number":"2"},{"Name":"Notice of Intent to Foreclose-NV - Betty Lou Smith.pdf","Number":"3"}]},"PackageStatuses":{"PackageStatus":{"Action":"REVIEW","Recipient":"paperout@wolterskluwer.com","Received":"Thu, Feb 04, 2021 14:54:55","Viewed":"","Purged":"","Recalled":"","Signed":"","Rejected":"","PaperRequested":"","DirectToPaper":"Thu, Feb 04, 2021 14:54:55","PaperCompleted":"","PaperNote":"","Label":"","PackageError":"","Consented":"","PushedToVault":"","PushedToVaultNote":"","AdditionalData":"","UserTag":"","TRIDUndeliverable":"","ReceivedMsgId":"4542447"}}}
    2021-02-04 14:57:37.203 -06:00 [INF] Executing HttpStatusCodeResult, setting HTTP status code 200
Technical Notes: To add callbacks to a request, the following elements must be passed:
    "callback": {},
                "delivery": {
                    "deliveryHold": false,
                    "deliveryMode": "DirectToPaper",
Implementation Notes: This feature is available in the February Out of Band release for Hosted Expere / Expere Document Services.

February

eOriginal: Password Override
Type: Enhancement Reference: PBI 658575 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: eOriginal Quick Guide: Password Override
Summary: In order for end users to log into eOriginal users will need to provide a password in the transaction xml. For parties that sign the eNote the last 4 digits of the SSN will be used, unless a unique passcode is passed in the transaction xml. For all other parties the unique passcode is required. This passcode is used for the end users log in with and must be provided to the end user.
Implementation Notes: This enhancement is available in the February release of Hosted Expere / Expere Document Services.

Integrators / Hosted Expere Integration to Wolters Kluwer E-Sign REST API methods added
Type: Feature Reference: See Summary for each item Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: see Summary for each item.
Summary: We have created the following REST methods for the Hosted Expere integration to Wolters Kluwer E-Sign feature: WKESRegister: this method can be used to register users to authorize electronic delivery of documents PBI: 642878 Feature Guide: WKESRegister Expere Document Services Web Services Guide: WKESRegister GetDeliverySetup: this method can be used to retrieve the delivery setup information for a transaction PBI: 649879 Feature Guide: GetDeliverySetup Expere Document Services Web Services Guide: GetDeliverySetup Deliver: this method can be used to Deliver document packages to delivery group(s) originally created through the Generate request, or to send the Generated document package to specified recipients in the Deliver request. PBI: 650116 Feature Guide: Deliver Expere Document Services Web Services Guide: Deliver Note: Users must pass in the `TransactionId` from the Generate request, in the Deliver request (required parameter); additional optional parameters include `PassthroughId`, `RecipientInfo`, and `ReturnAddress`
Implementation Notes: This feature is available in the February release of Hosted Expere / Expere Document Services.

eOriginal: signers now passed as part of Upload feature
Type: Feature Reference: PBI 658150 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: eOriginal Quick Guide: Expere Transaction XPaths for eOriginal
Summary: Previously, only eNote signers were passed to eOriginal. As part of our feature work related to uploading documents from a transaction to eOriginal, all signers included in the Expere response are now passed to eOriginal. Note: in the `Txn/EOriginalUploadType` XPath value, users may specify either "0" (never upload documents to eOriginal) or "1" (only upload documents to eOriginal if an an eNote is autoselected. Wolters Kluwer does not currently support always uploading documents to eOriginal (specified through a "2" value). Note: This PBI is part of the Upload feature that is currently work-in-progress and will be available in a near-future sprint.
Implementation Notes: This feature is available in the February release of Hosted Expere / Expere Document Services.

Integrators / Hosted Expere Integration to Wolters Kluwer E-Sign: Delivery Groupings created for Electronic with E-Sign delivery
Type: Feature Reference: PBI 644744 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Feature Guide: Deliver
Summary: As part of our Hosted Expere Integration to Wolters Kluwer E-Sign feature, we have updated our delivery grouping logic to now support creating delivery groups when the `DeliveryMode` is set to `ElectronicWithESign`. Now, upon submitting a Generate request where `DeliveryMode` = `ElectronicWithESign`, delivery groups will be created and the DeliveryGroup callback will consist of the following: `Delivery` container Inside the `Delivery`, the following elements are present: `deliveryMode`: `ElectronicWithESign` `deliveryGroups`: `emailAddresses` (values) `discretePartyId` `groupID` `documents` (`docID` and `instanceDisplayName`)
Implementation Notes: This feature is available in the February release of Hosted Expere / Expere Document Services.

Integrators / Hosted Expere Integration to Wolters Kluwer E-Sign: GetGenerateResults updated with delivery group ID
Type: Feature Reference: PBI 649878 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Feature Guide: Generate-Result method; Expere Document Services Web Services Guide: REST API > GetGenerateResults
Summary: As part of our Hosted Expere Integration to Wolters Kluwer E-Sign feature, we have enhanced the `GetGenerateResults` method to allow a Group ID to be submitted in the request. This will allow users to review a document package for a specific delivery group ID for a given request. For more information, see the Feature Guide.
Implementation Notes: This enhancement is available in the February release of Hosted Expere / Expere Document Services.

Integrators / Hosted Expere Integration to Wolters Kluwer E-Sign: email address returned as part of Discrete Party in response file
Type: Enhancement Reference: PBI 651638 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Web Services Guide: DiscreteParty
Summary: Previously in PBI 625511, we added the `EmailAddress` parameter to the `DiscreteParty` data type in the Expere Document Services `DocServices` WSDL. We are now returning an `EmailAddress` value in the response file when an email address has been provided in the request transaction for a `DiscreteParty`.
Implementation Notes: This enhancement is available in the February release of Hosted Expere / Expere Document Services.

Hosted Expere Integration Wolters Kluwer E-Sign: Delivery Groupings created for ElectronicOnly delivery
Type: Feature Reference: PBI 649866 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: As part of our Hosted Expere Integration to Wolters Kluwer E-Sign feature work, we have updated the Delivery Groupings logic to now create delivery groups. The new Expere Document Services Feature Guide contains detailed information regarding Delivery Groupings and how they impact the integration to Wolters Kluwer E-Sign feature.
Implementation Notes: This feature is available in the February release of Hosted Expere / Expere Document Services.

Supplemental January Release

Note: The supplemental January release will occur in the CT environment on 1/15 and in the production environment on 1/21.

PostProcess functionality enhanced with eNote and MergedCopyPdf
Type: Defect Reference: PBI 656164 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: It was reported that when submitting a request where `EClosingType=1` and `MergedCopyPdf=true`, the subsequent Expere response exhibited the following behavior: It did not include the `Id` element and value in the `FillableFieldSet` > `FillableText` container It contained a value of "`alphanum`" in the `FieldType` parameter instead of "`initial`."
Solution: This issue has been resolved; submitting a request where `EClosingType=1` and `MergedCopyPdf=true`, the response file now includes the `Id` in the `FillableFieldSet` > `FillableText` container and "`initial`" value in the `FieldType` parameter. Additionally, we determined that `EmailAddress` was not being returned in the response; as a result, we have updated the response to include this field. See example response below:
    <FillableText>
                      <Id>TestPartyID</Id>
                      <EmailAddress>TestEmail@email.com</EmailAddress>
                      <XCoordinate>544.63</XCoordinate>
                      <YCoordinate>67.16</YCoordinate>
                      <FieldName>Footer Initial_22</FieldName>
                      <ToolTip>Enter your initials.</ToolTip>
                      <PageNumber>92</PageNumber>
                      <Mandatory>No</Mandatory>
                      <Width>28.7999878</Width>
                      <Height>10</Height>
                      <FontSize>10</FontSize>
                      <FontName>ArialMT</FontName>
                      <FieldType>Initials</FieldType>
                      <HorizontalAlignment>Left</HorizontalAlignment>
                      <Underline>true</Underline>
                      <MultiLine>false</MultiLine>
                  </FillableText>
Implementation Notes: This defect correction is available in the January release of Hosted Expere / Expere Document Services.

January

Expere Engine: Support for Font, FontSize, and Underline added for Signatures
Type: Enhancement Reference: PBI 645801 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Web Services Guide: SignaturePoint
Summary: It was determined that Expere needed to support specifying a specific font and its size, and the ability to add an underline to a Signature and Signature Date field. As a result `Font`, `Font Size`, and `Underline` parameters are now supported for the `SignatureField` and `SignatureDateField` elements.
Implementation Notes: This enhancement is available in the January release of Hosted Expere / Expere Document Services.

Integrators: Response file updated to use `DocumentProfileId` in `DocInstances`
Type: Enhancement Reference: PBI 649079 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: Previously in PBI 638364, we updated the Expere Document Services `DocService` WSDL to add a `DocumentProfileId` to the `DocInstances` parameter. We have now updated Expere Document Services to return the `DocumentProfileId` element in the `DocInstances` container in the Expere response file.
Technical Notes: Sample response below (`DocumentProfileId` is bolded at the bottom of the `DocInstances` container):
    <DocInstances>
    			<DocData>
    				<base64>JVBERi0</base64>
    				<text xsi:nil="true"/>
    				<xml>
    					<NotApplicable/>
    				</xml>
    			</DocData>
    			<InstanceDisplayName>Cooperative Fixed Rate Note</InstanceDisplayName>
    			<InstanceFileName>Default-Cooperative_Fixed_Rate_Note.pdf</InstanceFileName>
    			<InstanceFormattingMetadata>
    				<InstanceSigningInstructions>NoSignatures</InstanceSigningInstructions>
    			</InstanceFormattingMetadata>
    			<InstancePacketType xsi:nil="true"/>
    			<InstancePacketName xsi:nil="true"/>
    			<InstanceDocumentRef xsi:nil="true"/>
    			<InstanceSequence xsi:nil="true"/>
    			<InstanceBarcodeValue xsi:nil="true"/>
    			<InstancePageCount>4</InstancePageCount>
    			<DocFormat>PDF</DocFormat>
    			<Copy xsi:nil="true"/>
    			<SignaturePointSet xsi:nil="true"/>
    			<InstancePageSize>Letter</InstancePageSize>
    			<DocIDRef>PKGD.eNotePlaceholderFannieMaeFreddieMac3200</DocIDRef>
    			<InstanceRecordableFlag>false</InstanceRecordableFlag>
    			<DocumentProfileID>10471666</DocumentProfileID>
    		</DocInstances>
Implementation Notes: This enhancement is available in the January release of Hosted Expere / Expere Document Services.

GetDeliveredImages REST API created for use with paper-only delivery - Hosted Expere > Wolters Kluwer ESign feature
Type: Feature Reference: PBI 649845 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: As part of our Hosted Expere to Wolters Kluwer E-Sign feature, we have implemented a new `GetDeliveredImagesOnly` REST API method that allows users to retrieve images of their physical mailings to the recipient.
Implementation Notes: This feature is available in the January release of Hosted Expere / Expere Document Services.

Middle page initial fields not fillable
Type: Defect Reference: PBI 651453 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: A user reported an issue with middle pages of a generated PDF not being fillable. After generating the UniformResidentialLoanAgreement specifying ESignatureAndFieldSupport, the initial fields on each page were only fillable on the first, second, and last page of the PDF. The initial fields on pages three through ten were not fillable.
Solution: This issue has been resolved; initial fields on middle pages are now fillable.
Implementation Notes: This defect correction is available in the January release of Hosted Expere / Expere Document Services.

Delivery Grouping Callback logic implemented - Hosted Expere > Wolters Kluwer ESign feature
Type: New Feature Reference: PBI 647190 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: As part of our Hosted Expere > Wolters Kluwer ESign feature, we have added callback logic for our Delivery Groupings. The callback logic has been enhanced to indicate whether or not delivery groupings have been created successfully. When delivery groupings are successfully created, the callback returns the following: Status = Successful Passthrough ID Transaction ID DeliveryMode Delivery Group Recipient(s) Mailing or email info GroupID DocIDs When delivery groupings are not successfully created, the callback returns the following: Status = Unsuccessful PassthroughID TransactionID Note: The routing URL is: `/api/v1/deliverysetup-callback`. For a successful callback creates the delivery groupings, the message sent back to users in the response file will resemble the following (in JSON format):
    generateResultsResponse": {
            "getGenerateResultsResult": {
                "passthroughIdentifier": "121215",
                "transactionIdentifier": "70369",
                "status": "Sucessful",
                "documents": {
                    "docSetPackageIDRef": "PKG.AncillaryOptions",
                    "packageDocs": [
                        {
                            "docDescriptor": {
                                "docID": "PKGD.BalloonPaymentMortgageDisclosure_esig_ff",
                                "docType": "Dynamic",
                                "docDisplayName": "Balloon Payment Mortgage Disclosure with esig and fillable",
                                "docRootEntityName": "INS.BalloonPaymentMortgageDisclosure_esig_ff",
                                "docRequiresSignature": false,
                                "docCustomDataItems": [],
                                "negotiableInstrumentFlag": false,
                                "recordableFlag": false
                            }
For a callback that does not create the delivery groupings, the message sent back to users in the response file will resemble the following (in JSON format):
    {
        "generateResultsResponse": {
            "getGenerateResultsResult": {
                "transactionIdentifier": "70370",
                "status": "Failed",
                "statusDescription": "Error: MissingField: Discrete Party"
            }
        }
    }
Implementation Notes: This new feature is available in the January release of Hosted Expere / Expere Document Services.