Changelog Entries - 2020

• Type: Feature
• Reference: PBI 626572
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: eOriginal Quick Guide: eNote Destruction Workflow Outline (eOriginal Quick Guide available by request)

The possible enumerated values for Txn/EOriginalDestructionType are defined as follows:

• 0 = Do NOT execute
  • Destruction logic within eOriginalwill NOT be run.
• 1 = Destruct managed doc profiles only
  • Documents previously uploaded to eOriginal by Expere, including the eNote, will be destructed.
• 2=Destruct ALL doc Profiles
  • Documents previously uploaded by Expere,including the eNote,as well as any manually uploaded documents through eOriginal Command Centerwill be destructed.
• 3 = Destruct Transaction
  • Removes the entire transaction from eOriginal.Note: If Txn/EOriginalDestructionType is NOT included in the request it is treated the same as a '0'.

• Type: Enhancement
• Reference: PBI 628336
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

We have enhanced this behavior to reflect the following changes:

• The Title name now defaults to the packet, which typically display as Default;
• The language is set to English.

• Type: Enhancement
• Reference: PBI 620019
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts:

Additionally, the Organization dropdown has been updated to include the ID after the ORG name to distinguish between multiple organizations that have the same name.

• Type: Enhancement
• Reference: PBI 626223
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

This behavior has been enhanced: signature line and date fields are sequenced last for the same email address.

• Type: Defect
• Reference: PBI 625632
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

• Type: Defect
• Reference: PBI 624666
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

• Type: Enhancement
• Reference: PBI 625098
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

• Type: Enhancement
• Reference: PBI 623479
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

It was determined that convertToDefaultSchema removed the predicates when white space was present in the transaction .XML file. As a result, we have enhanced convertToDefaultSchema to now return predicates when whitespace is present in the transaction .XML file.

• Type: Feature
• Reference: PBI 617790
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: Expere Developer Guide: FillableText

• Type: Enhancement
• Reference: PBI 616574
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

• <InstancePageCount> did not return a value; it should return any page number value other than "0"
• <InstancePageSize> returned a value; expected values were either "letter" or "legal"

<InstancePageCount> and <InstancePageSize> elements now return expected values for the eNote.

• Type: Enhancement
• Reference: PBI 619087
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: eOriginal Quick Guide available by request

• Type: Feature
• Reference: PBI 560985
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: eOriginal Quick Guide available by request

What is eNote redraw and destruction? After an eNote has been generated, it is determined that a revised version of the eNote is required, or an eNote is no longer applicable. Redraw or Destruction will be executed based on transaction parameters provided in the request. Based on the transaction parameters the eNote will be redrawn, replacing the original eNote previously generated, or the eNote will be removed (destructed), and replaced with a paper note.

• Type: Enhancement
• Reference: PBI 617785
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: eOriginal Quick Guide available by request

• Type: Enhancement
• Reference: PBI 617784
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: eOriginal Quick Guide available by request

• Type: Feature
• Reference: PBI 615219
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: eOriginal Quick Guide available by request

The <Txn/EOriginalTransactionTypeName> has been added to the Expere Txn Schema as a new data point for collecting the eOriginal Transaction Type. The transactionTypeName is a parameter used when creating the transaction in eOriginal. It is a ‘string’ value which is preconfigured within eOriginal. Please work with your eOriginal Implementation Consultant if you are unsure what this value is.

In addition to adding the new data point above, we have updated our mapping for <LoanOriginationId>. This data point was already being mapped to the eNote within eOriginal. This has been further enhanced to now set the <LoanOriginationId> as the Loan ID for the eO Transaction within the eOriginal Command Center.

• Type: Enhancement
• Reference: PBI 616466
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

• Type: Enhancement
• Reference: PBI 616051
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

"PackageDocs": [
      {
        "DocDescriptor": {
          "DocID": "PKGD.AddendumToLoanApplication-HE",
          "DocType": {
            "Enum": "Dynamic"
          },
          "DocDisplayName": "Addendum to Loan Application",
          "DocRootEntityName": "INS.AddendumToLoanApplication-HE",
          "DocRequiresSignature": false,
          "DocCustomDataItems": [],
          "DocumentClass": null,
          "DocumentTypeDescription": null,
          "NegotiableInstrumentFlag": false,
          "RecordableFlag": false,
          "FormNumber": null
        },
        "DocWorkOrder": null
      },

• Type: Feature
• Reference: PBI 612832
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

eoConfigureSortOder and eoConfigureRoles is called for eOriginal transactions when Txn/EOriginalEsignInd = True

• Type: Defect
• Reference: PBI 607955
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

• Type: Enhancement
• Reference: PBI 606934
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

• Type: Enhancement
• Reference: PBI 612138
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

• Type: Defect
• Reference: PBI 612168
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

• Type: Defect
• Reference: PBI 610128
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

• Type: Enhancement
• Reference: PBI 429547
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

• Type: Defect
• Reference: PBI 607603
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

• Type: Defect
• Reference: PBI 589263
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

• Type: Enhancement
• Reference: PBI 604430
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

• <FieldText> (returns a value if text string is present; if not it will return a "nil" value)
• <HorizontalAlignment> (values are "left," "center," or "right")
• <Underline> (either "true" or "false" value)
• <MultiLine> (either "true" or "false" value)

<r:FillableText>
    <r:FieldName>Lender.FullNameStreetCityStateZip_1</r:FieldName>
    <r:ToolTip>Lender.FullNameStreetCityStateZip_1</r:ToolTip>
    <r:Width>203.22</r:Width>
    <r:Height>40.96997</r:Height>
    <r:XCoordinate>39.98</r:XCoordinate>
    <r:YCoordinate>905.7</r:YCoordinate>
    <r:Sequencing>1</r:Sequencing>
    <r:FontName>Courier</r:FontName>
    <r:FontSize>10.0</r:FontSize>
    <r:NumberOfCharacters>0</r:NumberOfCharacters>
    <r:FieldText>Sample Text</r:FieldText>
    <r:HorizontalAlignment>Left</r:HorizontalAlignment>
    <r:Underline>false</r:Underline>
    <r:PageNumber>1</r:PageNumber>
    <r:MultiLine>true</r:MultiLine>
</r:FillableText>

• Type: Enhancement
• Reference: PBI 612334
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

• Type: Enhancement
• Reference: PBI 592830
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

• Type: Enhancement
• Reference: PBI 604817
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: Expere Document Services Web Services Guide: DocDescriptor; DiscreteParty

• DocDescriptor: the <LogoSupport/>, <DocumentList/>, and <ESignatureDocument/> elements now appear in this exact order at the bottom of the <DocDescriptor/> data type.
• DiscreteParty: the <ForeignAddress/> element now appears before <BusinessName/> in the <DiscreteParty/> data type.

• Type: Enhancement
• Reference: PBI
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts:

• <FieldText>
• <HorizontalAlignment>
• <Underline>
• <MultiLine>

<r:FillableText>
    <r:FieldName>Lender.FullNameStreetCityStateZip_1</r:FieldName>
    <r:ToolTip>Lender.FullNameStreetCityStateZip_1</r:ToolTip>
    <r:Width>203.22</r:Width>
    <r:Height>40.96997</r:Height>
    <r:XCoordinate>39.98</r:XCoordinate>
    <r:YCoordinate>905.7</r:YCoordinate>
    <r:Sequencing>1</r:Sequencing>
    <r:FontName>Courier</r:FontName>
    <r:FontSize>10.0</r:FontSize>
    <r:NumberOfCharacters>0</r:NumberOfCharacters>
    <r:FieldText>Sample Text</r:FieldText>
    <r:HorizontalAlignment>Left</r:HorizontalAlignment>
    <r:Underline>false</r:Underline>
    <r:PageNumber>1</r:PageNumber>
    <r:MultiLine>true</r:MultiLine>
</r:FillableText>

• Type: Enhancement
• Reference: PBI 598270
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

We have enhanced this functionality; eSignatures are properly created on all signature areas of the URLA continuation sheet.

• Type: Enhancement
• Reference: PBI 588517
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

We have updated our functionality to return a ‘nil’ value for the NumberOfCharacters element in the Expere Response, when one is not authored.

Sample reponse before enhancement:

<r:FillableFieldSet>
    <r:FillableText>
        <r:Id>*</r:Id>
        <r:EmailAddress>*</r:EmailAddress>
        <r:FieldName>Field3</r:FieldName>
        <r:ToolTip>Field3</r:ToolTip>
        <r:Width>547.2</r:Width>
        <r:Height>40.0</r:Height>
        <r:XCoordinate>37.0</r:XCoordinate>
        <r:YCoordinate>510.32</r:YCoordinate>
        <r:FontName>ArialMT</r:FontName>
        <r:FontSize>10.0</r:FontSize>
        <r:NumberOfCharacters>0</r:NumberOfCharacters>
        <r:FieldText/>    
        <r:HorizontalAlignment>Left</r:HorizontalAlignment>
        <r:Underline>false</r:Underline>
        <r:PageNumber>1</r:PageNumber>
        <r:MultiLine>true</r:MultiLine>    
    </r:FillableText>
</r:FillableFieldSet>

</r:FillableFieldSet>

We have updated our functionality to enhance thie behavior: if no content is added to either the ToolTip or NumberOfCharacters elements, neither element appears in the response file.

• Type: Enhancement to Standard eSignature and Field Level fillable fields Feature
• Reference: PBI 592305 / 592302
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: Expere Developer Guide: FillableCheckbox

When fillable checkboxes are authored in the REQ with a GroupID, and the request is for eSignature and Field Support with NonSignatureFieldCoordinatesOnly set to ‘True’:

• The Radio button grouping is named using the GroupID
• The response includes ALL radio button options with XY Coordinates for each radio button option, as well as the GroupID.

<r:FillableCheckbox>
                  <r:Id>BorrID</r:Id>
                  <r:EmailAddress>test@email.com</r:EmailAddress>
                  <r:FieldName>yes</r:FieldName>
                  <r:ToolTip>yes</r:ToolTip>
                  <r:Checked>true</r:Checked>
                  <r:PageNumber>1</r:PageNumber>
                  <r:XCoordinate>154.29</r:XCoordinate>
                  <r:YCoordinate>661.22</r:YCoordinate>
                  <r:GroupID>Group1</r:GroupID>
                  <r:Mandatory>No</r:Mandatory>

• Type: Enhancement
• Reference: PBI 605233
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

We have updated Expere to better accommodate utilizing both versions of iText. As a result, until all Expere components using iText are upgraded to version 7, the PDF will indicate an APGL license, but the Wolter Kluwer license still applies.

• Type: Defect
• Reference: PBI 592245
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

• Type: Enhancement
• Reference: PBI 599080
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

This behavior has been enhanced. We have updated Expere to escape the "&" when it is submitted in a request; Expere now serializes this special character and returns it in the response file successfully.

• Type: Enhancement
• Reference: PBI 595023
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

As a result, we have enhanced the size of our fillable fields and checkboxes to match those of their non-fillable counterparts.

• Type: Enhancement
• Reference: PBI 588118 / 592823 / 592830
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

• Barcodes
• Watermarks
• Duplex

• Type: Enhancement
• Reference: PBI 589741
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: Expere Developer Guide: Using mutually exclusive checkboxes

• Type: Enhancement
• Reference: PBI 591870
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

As a result, Expere now uses .5 inch default document margins when they have not been authored in the document and when using either barcodes or logos.

• Type: Enhancement
• Reference: PBI 589821
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

We have updated EDS to implement new retry logic; which will now attempt three retries before failing the EDS response.