# Expere Engine and Tools Change Log Entries

June - Expere 2017.2External release date is TBD.

New color element added
Type: New Feature Reference: PBI 445200 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: A new child element, `<ColoredPaper/>` has been added to the `<DocInstance/>` element of the Expere Response. The new element `<ColoredPaper/>` will be included in the Expere response and set to True when a selected form is authored with a color paper attribute. If the form(s) are not authored with the color paper attribute, the `<ColoredPaper/>` element will not be included in the Expere response.
Technical Notes: A sample response consists of the following:
    <r:DocInstance DocIDRef="PKGD.AuthorizationDocumentAccounts_Copy">
    						<r:SignaturePointSet>
    							<r:Signer>
    								<r:Id>S3</r:Id>
    								<r:Description>Account Holder, Account Holder, Account Holder, Account Holder</r:Description>
    								<r:SignaturePoints>
    									<r:SignaturePoint>
    										<r:IncludeDate>false</r:IncludeDate>
    										<r:PageNumber>2</r:PageNumber>
    										<r:PageOrder>2</r:PageOrder>
    										<r:Height>36.0</r:Height>
    										<r:Width>198.0</r:Width>
    										<r:SignatureText>S3</r:SignatureText>
    										<r:XCoordinate>37.0</r:XCoordinate>
    										<r:YCoordinate>341.5</r:YCoordinate>
    										<r:Type>Signature</r:Type>
    										<r:FieldName>SIG_Account Holder_S1_S3_true_2</r:FieldName>
    									</r:SignaturePoint>
    								</r:SignaturePoints>
    							</r:Signer>
    						</r:SignaturePointSet>
    						<r:ColoredPaper>True</r:ColoredPaper>
    					</r:DocInstance>
Implementation Notes: This feature requires a 2017.2 Expere Engine update.

Expere now updated to support latest versions of Microsoft Windows and SQL
Type: Enhancement Reference: PBI 451614 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere System Requirements guide: Windows Environment Software Requirements
Summary: The Expere Engine has been tested to validate that it functions properly with Windows Server 2016 and SQL 2016.
Implementation Notes: This feature requires a 2017.2 Expere Engine update. For more information, consult the Expere System Requirements guide: Windows Environment Software Requirements.

PDF bookmark / eSignature behavior enhanced
Type: Defect Reference: PBI 444844 Compliance Impacts: This item is/is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: It was previously reported that bookmarks were appearing in PDF documents despite the eSignature Support option set to "false" in the `bsi.properties` file (`com.bankerssystems.expere.render.eSignatureSupport=false`). Expected behavior is that bookmarks should not appear in the PDF document when the eSignature option is disabled.
Solution: This issue has been resolved; bookmarks no longer appear when the eSignature Support option is set to "false" in the `bsi.properties` file.
Implementation Notes: This feature requires a 2017.2 Expere Engine update.

Barcode enhancement: additional location options
Type: Enhancement Reference: PBI 443543 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Barcodes
Summary: Expere Engine users may now select their barcode location in their request by selecting one of the following justification options using the `HorizontalAlignment` parameter: Left Right Center These barcode adjustment options affect the following API's: Select and Generate Select Generate
Technical Notes: Sample request consists of the following:
    <xs:element name="HorizontalAlignment" minOccurs="0">
              <xs:annotation>
                <xs:documentation>Identifies how the barcode aligns within the form.  Possible values are "Left", "Right", or "Center".</xs:documentation>
              </xs:annotation>
              <xs:simpleType>
                <xs:restriction base="xs:string">
                  <xs:enumeration value="Left">
                  </xs:enumeration>
                  <xs:enumeration value="Center">
                  </xs:enumeration>
                  <xs:enumeration value="Right">
                  </xs:enumeration>
                </xs:restriction>
              </xs:simpleType>
            </xs:element>
Implementation Notes: This feature requires a 2017.2 Expere Engine update. For more information, see Barcodes.

Extra underscore added when email address is not present for WKES naming
Type: Enhancement Reference: PBI 450656 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Sequencing: WKES email address sequencing and naming behavior
Summary: We have enhanced WKES naming functionality to now include a two underscore placeholder if the signer does not have an email address.
Technical Notes: Note the following: When an email is present: `WKES_<Type>_<email>_<Sequence number>` When an email is not present: `WKES_<Type>__<Sequence number>` with two underscores between `<Type>` and `<Sequence>`
Implementation Notes: This enhancement requires a 2017.2 Expere Engine update. See Sequencing: WKES email address sequencing and naming behavior for more information.

AprilExternal release date is TBD.

Package functionality added to Select, SelectAndGenerate, and Generate API's
Type: Enhancement Reference: PBI 444150 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: SelectRequest, SelectAndGenerateRequest; GenerateRequest; InlinePackage.
Summary: We have enhanced the `Select`, `SelectAndGenerate`, and `Generate` API's to accept custom packages through a new `<InlinePackage/>` parameter within each of these API's. This allows users to create or modify one or multiple custom packages for a particular line of business or precedence unit by selecting documents from one or more package or autoselection rules.
Implementation Notes: Consider the following: This enhancement requires picking up the Expere Engine 2017.1 release. Users must select one of the following: PackageID LOBPhase InlinePackage See SelectRequest, SelectAndGenerateRequest; GenerateRequest; InlinePackage for more information.

eSignature Field Order enhancement
Type: Enhancement Reference: PBI 444854 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: We modified the method for applying enumerated values to the `<eSignature/>` fields so that the sequencing method always assigns the highest value in the sequence of each signer to their respective `<Type>Signature</Type>` fields, hence making the Signature field the last field in the order.
Technical Notes: Here is an example response:
    -<r:SignaturePointSet>
      -<r:Signer>
        <r:Id>null</r:Id>
        <r:SignerEmail>firstlast@test.com</r:SignerEmail>
        <r:Description>null</r:Description>
        -<r:SignaturePoints>
          -<r:SignaturePoint>
            <r:IncludeDate>true</r:IncludeDate>
            <r:PageNumber>1</r:PageNumber>
            <r:PageOrder>null</r:PageOrder>
            <r:Height>36.0</r:Height>
            <r:Width>198.0</r:Width>
            <r:SignatureText>null</r:SignatureText>
            <r:XCoordinate>36.0</r:XCoordinate>
            <r:YCoordinate>566.84</r:YCoordinate>
            <r:Type>Signature</r:Type>
            <r:FieldName>WKES_Signaturefirstlast@test.com_2</r:FieldName>
            <r:Sequencing>2</r:Sequencing>
          </r:SignaturePoint>
          -<r:SignaturePoint>
            <r:IncludeDate>false</r:IncludeDate>
            <r:PageNumber>1</r:PageNumber>
            <r:PageOrder>null</r:PageOrder>
            <r:Height>36.0</r:Height>
            <r:Width>50.0</r:Width>
            <r:SignatureText>null</r:SignatureText>
            <r:XCoordinate>238.0</r:XCoordinate>
            <r:YCoordinate>566.84</r:YCoordinate>
            <r:Type>Date</r:Type>
            <r:FieldName>WKES_Datefirstlast@test.com_1</r:FieldName>
            <r:Sequencing>1</r:Sequencing>
          </r:SignaturePoint>
        </r:SignaturePoints>
      </r:Signer>
      -<r:Signer>
        <r:Id>null</r:Id>
        <r:SignerEmail>_first_last@test.com</r:SignerEmail>
        <r:Description>null</r:Description>
        -<r:SignaturePoints>
          -<r:SignaturePoint>
            <r:IncludeDate>true</r:IncludeDate>
            <r:PageNumber>1</r:PageNumber>
            <r:PageOrder>null</r:PageOrder>
            <r:Height>36.0</r:Height>
            <r:Width>198.0</r:Width>
            <r:SignatureText>null</r:SignatureText>
            <r:XCoordinate>309.6</r:XCoordinate>
            <r:YCoordinate>566.84</r:YCoordinate>
            <r:Type>Signature</r:Type>
            <r:FieldName>WKES_Signature_first_last@test.com_2</r:FieldName>
            <r:Sequencing>2</r:Sequencing>
          </r:SignaturePoint>
          -<r:SignaturePoint>
            <r:IncludeDate>false</r:IncludeDate>
            <r:PageNumber>1</r:PageNumber>
            <r:PageOrder>null</r:PageOrder>
            <r:Height>36.0</r:Height>
            <r:Width>49.99997</r:Width>
            <r:SignatureText>null</r:SignatureText>
            <r:XCoordinate>511.6</r:XCoordinate>
            <r:YCoordinate>566.84</r:YCoordinate>
            <r:Type>Date</r:Type>
            <r:FieldName>WKES_Date__first_last@test.com_1</r:FieldName>
            <r:Sequencing>1</r:Sequencing>
          </r:SignaturePoint>
        </r:SignaturePoints>
      </r:Signer>
    </r:SignaturePointSet>
Implementation Notes: This enhancement requires picking up the Expere Engine 2017.1 release. and setting the `<eSignatureWKES/>` option to "true."

WKES Sign Date Naming Convention
Type: Enhancement Reference: PBI 442435 Compliance Impacts: This item iis not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: The WKES Sign Date fillable field naming convention has been updated from WKES_date to WKES_signdate.
Implementation Notes:No user action is required.

eSignature Enhancements
Type: Defect Reference: PBI 440808 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: We have updated the field name elements for the eSignature and eSignatureDate within the PDF and ExpereResponse file as part of the SignaturePointSet element. The eSignature field name has been updated to no longer include the borrower name, additionally, the eSignatureDate field name for Static content has been updated to be consistent with Dynamic content.
Solution: The specific changes to the eSignature and eSignatureDate field names are captured below. Before: eSignature Field Name: SIG_Borrower_1_1_true_1_BobbyBorrower_BW1Name.eSig eSignatureDate Field Name: BW1Name.eSig.eSigDate After: eSignature Field Name: SIG_Borrower-1_1_true_1_BW1Name.eSig eSignatureDate Field Name: SIG_Borrower_1_1_true_1_BW1Name.eSig.eSigDate
Implementation Notes:No user action is required.

EnableEsignatureManifest Added to BSI.Properties
Type: Enhancement Reference: PBI 440811 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: As a means to enable or disable the esignature manifest file we have added a flag, EnableEsignatureManifest, to BSI.Properties. With the default of FALSE, Expere does not look for the esigmanifest file as part of the content. When set to TRUE, the esigmanifest file is expected to be in the content repository.
Implementation Notes:No user action is required.

Version Number Added to Schemas
Type: Enhancement Reference: PBI 442215 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary:A version number attribute has been added to the root of all Expere Request and Response schemas to aid in troubleshooting.
Implementation Notes: No user action is required.

New ApplyPoliciesAndReturnTransaction API introduced
Type: New Feature Reference: PBI 432140 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: ApplyPoliciesAndReturnTransaction
Summary: The `ApplyPoliciesAndReturnTransaction` API has been implemented to update the provided transaction with the provided Product information. This allows users to pass the updated returned transaction (which includes the Product information) into our DocViewer application, as well as the ability to use `Select`, `SelectAndGenerate`, or `Generate` API's to generate documents with product data.
Implementation Notes: See ApplyPoliciesAndReturnTransaction for detailed information on using this new API.

Ancillary Barcodes Not Rendering on Dynamic Documents
Type: Defect Reference: PBI 443195 Compliance Impacts: This item is not not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: Ancillary barcodes contained in a request would not render on dynamic documents.
Solution: This did not impact static documents. This has been repaired so requests with ancillary barcodes will render as expected on dynamic documents.
Implementation Notes: No user action is required.

Expere Engine: Pinyon Script added to JetFonts.xml
Type: Enhancement Reference: PBI 437588 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: We have added Pinyon Font to the `jetfonts.xml` file within our Expere Engine. This will allow users to generate a static document with a script font.
Implementation Notes: No user action is required.

Text string area message enhanced
Type: Enhancement Reference: PBI 406465 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: Previously if a `<Text/>` element's text string contained more characters than what was allowed, an error message was logged. We have updated the logging level for this message to be WARN instead of ERROR.
Implementation Notes: No user action is required.

Logging levels updated
Type: Enhancement Reference: PBI 432256 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: Previously, all exceptions that appeared in our log files were reported as errors. This did not reflect the nature nor severity of the exception being logged.
Technical Notes: We have modified our level of logging to consist of the following: Fatal: major system outage or SQL exception Error: system error that does not set off an alert; retries; ongoing system issue Warning: transactions with invalid GUID format, permissions issues, invalid characters being passed in, invalid transaction xml, etc
Implementation Notes: No user action is required.