Jump to main content

# 2024 Release One (1) Expere Engine and Tools Changelog

Expere Engine Release: 2024 Release One (1)External release date is April 2024. Expere Engine build number is: 24.1.0.5558.

Engine: FOP 2.8 upgrade
Type: Feature Reference: PBI 807402, 807403 Documentation Impacts: Expere Implementation Guide > BSI Properties comprehensive overview; Expere Developer Guide > SelectAndGenerateRequest and GenerateRequest
Summary: the Expere Engine has been updated to use FOP 2.8 exclusively when generating documents; users will no longer need to pass in a `FOP26=true` element and value in transaction when generating documents. Note: As part of this upgrade, Expere will no longer generate documents using FOP 1.1. The `bsi.properties` file, used to control certain properties, has been updated to remove the `com.bankerssystems.expere.render.FOP26` property. SelectAndGenerate and Generate requests have removed references to the `FOP26` element. As a result, the Expere Engine will disregard any attempt to pass this element in with a value of "false".

OPPSA components removed from Expere Engine
Type: Feature Reference: PBI 788036
Summary: Previously, we informed you (here) that OPPSA references had been removed from our user documentation. We have now removed actual OPPSA references in our software code from our Expere On-Prem products, consisting of the following methods: CreateOppsaPhaseRequest CreateOppsaPolicyOrganizationRequest CreateOppsaPolicyUserRequest DeleteOppsaBarcodeRequest DeleteOppsaPackageRequest DeleteOppsaPacketRequest DeleteOppsaPhaseRequest DeleteOppsaPolicyOrganizationRequest DeleteOppsaPolicyRequest DeleteOppsaPolicyUserRequest DeleteOppsaProductRequest GetOppsaBarcodeRequest GetOppsaPackageRequest GetOppsaPacketRequest GetOppsaPolicyOrganizationsRequest GetOppsaPolicyRequest GetOppsaPolicyUsersRequest GetOppsaProductsRequest PublishOppsaBarcodesRequest PublishOppsaPackagesRequest PublishOppsaPacketsRequest PublishOppsaPhasesRequest PublishOppsaPoliciesRequest PublishOppsaProductsRequest SaveOppsaBarcodeRequest SaveOppsaPackageRequest SaveOppsaPacketRequest SaveOppsaProductRequest UpdateOppsaPolicyOrganizationRequest UpdateOppsaPolicyUserRequest UploadOppsaPolicyRequest VerifyOppsaLoginRequest Additionally, we have removed OPPSA related parameters from the following methods: CreateTransactionRequest GenerateRequest GetPackageDataRequirementsRequest ListDocumentsRequest ListPackagesRequest ListPhasesRequest SelectAndGenerateRequest SelectAndGenerateTestDocumentsRequest SelectRequest

Support enhanced for HELOC vaulting
Type: Feature Reference: PBI 797989
Summary: in order to support vaulting of the HELOC note, Expere has been updated to return values in the response for `<Vault/>` and `<FinancialAsset/>` elements if present within a document that is part of a document package. The response file will resemble the following:
    <r:PackageDoc PackageDocID="PKGD.AffidavitOfMortgagorNJ_Copy">
        <r:DocDescriptor>
                         <r:DocID>PKGD.AffidavitOfMortgagorNJ_Copy</r:DocID>
                         <r:DocType>Dynamic</r:DocType>
                         <r:DocDisplayName>Affidavit of Mortgagor-NJ</r:DocDisplayName>
                         <r:DocRootEntityName>INS.AffidavitOfMortgagorNJ_Copy</r:DocRootEntityName>
                         <r:ESignatureDocument>true</r:ESignatureDocument>
                         <r:Vault>true</r:Vault>
                         <r:FinancialAsset>true</r:FinancialAsset>
        </r:DocDescriptor>
        <r:DocWorkOrder>
                         <r:DocPrepare>true</r:DocPrepare>
                         <r:DocAutoselected>false</r:DocAutoselected>
                         <r:DocSuggested>false</r:DocSuggested>
                         <r:DocFormat>TaggedPDF</r:DocFormat>
                         <r:DocStyle>WKFS_StyleGuide</r:DocStyle>
        </r:DocWorkOrder>
    </r:PackageDoc>
See Expere Developer Guide > DocDescriptor for more information.

WCAG: Expere Engine enhanced to support embedded and Tagged .PDF's
Type: Enhancement Reference: PBI 801184, 797053, 810310, 812027, 805562, 799649, 803558, 802124, 724801, 797504, 797968, 791476, 791351, 792908, 693326, 791635, 791882, 772123 Documentation Impacts: See below for any pertinent links.
- Summary: As a part of our continued effort to create WCAG compatible documents we have updated the Expere Engine to now support the generation of Tagged .PDF documents. We will continue making enhancements to the Expere Engine for Tagged .PDF support, so check back for items being identified and corrected. As part of our continued work to support Tagged .PDF's, we have implemented enhancements to resolve the following WCAG-related changes in Expere 2024 Release One: Signature and Date order behavior enhanced (PBI 801184): it was reported that the eSignature and Date fillable fields were displayed out of order in the Adobe Acrobat tag tree, resulting in synthentic screen readers to read tags in an incorrect order. Expere has been enhanced to display the eSignature and Date fillable fields in the correct order in the Adobe Acrobat tag tree. Multiple column list behavior enhanced when split across pages (PBI 797053): it was reported that when lists were present in multiple columns and spanned two pages, the lists were incorrectly tagged in the Adobe Acrobat tag tree as two lists. The expected behavior was despite the lists spanning two pages, the lists should have been tagged as one list. This behavior has been enhanced, lists that exist within multiple columns and span two pages are now tagged as one list in the Adobe Acrobat tag tree. Character Encoding behavior enhanced (PBI 810310): it was reported that Tagged PDFs were producing a "Character Encoding Failed" exception in Adobe Acrobat when running its Accessibility Checker. Internal analysis determined that generating a Tagged PDF with an <ESignatureAndFieldSupport/> ancillary output with <eSignatureCoordinatesOnly/> and <NonSignatureFieldCoordinatesOnly/> coordinates set to "true" in the request were causing this exception. See below for code sample:
      <AncillaryOutputsDoc>
      	<AncillaryOutput>
      		<OutputType>ESignatureAndFieldSupport</OutputType>
      		<ESignatureAndFieldSupport>
      			<!-- A boolean value to determine if eSignatures should be repressed in favor of X/Y coordinates. -->
      			<!-- Values: true, false -->
      			<eSignatureCoordinatesOnly>true</eSignatureCoordinatesOnly>
      			<!-- A boolean value to determine if eSignature date is supported. -->
      			<eSignatureDateSupport>true</eSignatureDateSupport>
      			<!-- The text that will be used for the eSignature tooltip -->
      			<eSignatureTooltip>ESignature ToolTip</eSignatureTooltip>
      			<!-- The text that will be used for the eSignature initials tooltip -->
      			<eSignatureInitialsTooltip>ESignature Initials ToolTip</eSignatureInitialsTooltip>
      			<!-- A boolean value to determine if all acroform fields that are not eSignature should be repressed in favor of X/Y coordinates. -->
      			<!-- Values: true, false -->
      			<NonSignatureFieldCoordinatesOnly>true</NonSignatureFieldCoordinatesOnly>
      			<!-- A boolean value to determine if eSignatures initial fields should render as Text fields -->
      			<!-- Values: true, false -->
      			<eSignatureWKES>false</eSignatureWKES>
      		</ESignatureAndFieldSupport>
      	</AncillaryOutput>
      </AncillaryOutputsDoc>
This behavior has been updated so that Tagged PDFs using eSignatureAndFieldSupport ancillary output with <eSignatureCoordinatesOnly/> and <NonSignatureFieldCoordinatesOnly/> coordinates set to "true" in the request now pass an Adobe Acrobat Accessibility Check. Path Object Not Tagged behavior enhanced (PBI 812027): it was reported that Tagged PDFs were producing a "Path Object Not Tagged" exception in the PAC 2021 Accessibility Checker. Internal analysis determined that this error occurred when using the <ESignatureAndFieldSupport/> ancillary output. This behavior has been enhanced so that using an <ESignatureAndFieldSupport/> ancillary output when generating a Tagged PDF document no longer results in a "Path Object Not Tagged" exception in the PAC 2021 Accessibility Checker. "Text with insufficient contrast" behavior enhanced with multiple LinkText elements (PBI 805562): It was reported that Tagged PDFs were producing a "Text with insufficient contrast" exception in the PAC Accessibility Checker when multiple `LinkText` references (which are authored in the native .REQ file) are present in the the footer of a document. This behavior has been updated so that TaggedPDF documents (individual / merged PDF documents) containing multiple links related to a specific `LinkText` element do not result in a "Text with insufficient contrast" exception in the PAC Accessibility Checker. Ancillary process flows updated (PBI 799649): updates were made to our ancillary process flows. No customer facing changes. Embedded PDF logging functionality enhanced (PBI 802124): logging has been enhanced when an Embedded PDF contains improperly labeled fillable fields so that an entry normally marked as an ERROR is now marked as a WARN. If the list of fillable fields is blank, no WARN entry will be logged. Note: When a signature field is improperly labeled, the system will continue to throw an ERROR level message. Watermarks supported in dynamic documents (PBI 724801): dynamic documents have been updated to support the use of watermarks in Tagged PDF outputs. In order to pass accessibility checks, the watermark now contains an alternate text value that is defined when generating an individual tagged or merged tagged PDF. See ADA Implementation Guide > Working with Watermarks for more information. Watermark functionality added with Embedded PDF files (PBI 803558): users can now use a Watermark ancillary output with an Embedded PDF file. Additionally, internal analysis determined that the presence of an Embedded PDF Barcode Cover Page was included in the page count of the entire document. As a result, Expere has been enhanced so that the cover page was not included in the page count when generating an Embedded PDF with a Barcode Cover Page. For more information, see ADA Implementation Strategies Guide > Working with Watermarks and Expere Developers Guide > Watermarks (Self-hosted users) / Implementation Strategies > Watermarks (Hosted users). Tag tree behavior enhanced for fillable fields in an individual PDF document (PBI 797504): It was reported that certain Tagged PDFs' tag tree order was incorrect when including a value for a field that was authored as a fillable field, specifically a Signature or Acknowledgement section within a document. When the document utilized an `eSignatureAndFieldSupport` ancillary output and when the document was not eSignable, the tag tree displayed tags in the wrong order and with incorrect Form values in some cases. This issue has been resolved so that when generating a Tagged PDf with `eSignatureAndFieldSupport` ancillary output, the resulting tag tree displays tags in the correct order and with the correct values. Tag Tree modified for fillable fields in merged PDF (PBI 797968): It was reported that certain Tagged and merged PDFs' tag tree displayed a value for a field that was authored as a fillable field in a document that was not eSignable, specifically a Signature or Acknowledgement section. When the document utilized an `eSignatureAndFieldSupport` and either a `PdfMerge` or `MergedCopyPdf` ancillary output and when the document was not eSignable, the tag tree displayed Form values in some cases. This issue has been resolved so that when generating a Tagged and merged PDF with `eSignatureAndFieldSupport` ancillary output, the resulting tag tree will NOT display values for fillable fields. Signature fields now include alternate text tooltips in Tagged PDF (PBI 791476): It was identified that eSignature fields in a Tagged PDF should have included a tooltip in order to pass an accessibility check. As a result, Expere has been updated so that by default, an eSignature field will have a default tooltip value of "Unsigned Signature Field". Additionally, all fillable initial fields will contain a default value of "Unsigned Initial Field". Users may override these values and their own custom values through the following means: eSignature tooltip: pass in an `eSignatureAndFieldSupport` ancillary output in the transaction with the <eSignatureTooltip/> element containing the desired string value. Initial field tooltip: pass in an `eSignatureAndFieldSupport` ancillary output in the transaction with the <eSignatureInitialsTooltip/> element containing the desired string value. See Expere Developer Guide > Using eSignature and Acroform fields > Setting a tooltip value and ADA Implementation Guide > Customizing Electronic Signature Tooltip for more information. Figure element on single page with no bounding box accessibility error resolved (PBI 791351): It was reported that Tagged PDFs were producing a "Figure element on single page with no bounding box" in the PAC Accessibility Checker; checkboxes and images were flagged for not containing a defined bounding box. A fully accessible document will have figures with a defined bounding box indicating the position of the figure on the page. This behavior has been enhanced so that checkboxes and images contain defined bounding boxes and pass the PAC 2021 Accessibility Checker. Path elements marked as Artifacts (PBI 792908): It was identified that Path elements are required to be marked as artifacts. Path elements are underlines that appear in the document (for example: lines that appeared under headings and in the tagline). This behavior has been enhanced so that these path elements are now tagged as artifacts. LinkText tagging behavior enhanced when LinkReference and LinkText appear on separate pages (PBI 693326): It was reported for some Tagged PDF documents where a superscript (`LinkReference` in the native .REQ file) and the corresponding linked text (`Linktext` in the native .REQ file) were present on separate pages, the <Span> tag for the superscript was incorrect in the tag tree. This behavior has been resolved so when the superscript and corresponding linked text appear on separate pages, the <Span> tag appears with the appropriate linked text. <Span> tag contained incorrect information in tag tree (PBI 791635): it was reported that certain <Span> tags in the Adobe Acrobat tag tree were incorrectly placed in locations that were reserved for superscripts for linked text and the corresponding linked text. This behavior has been enhanced so that the superscript used for linked text only contains the corresponding linked text. Tag tree behavior enhanced for fillable fields (PBI 791882): It was reported that Tagged PDF’s tag tree order is incorrect when including a value for a field that was authored as a fillable field but for the given scenario, the Tagged PDF does not include fillable fields. For example, an REQ file is authored using a common file for notaries, but the REQ itself is not an eSignable document. In this scenario, some of the values in the signature and notary sections were out of order in the tag tree. This behavior has been addressed so that the tag tree displays values in the correct order. Tag tree behavior enhanced with tables embedded into bulleted lists (unsequenced lists) (PBI 772123): it was reported that the tag tree in Adobe Acrobat was incorrect with respect to the following issues: When a table was present within a sequenced list that contained a heading with a superscript. That tag tree did not correctly tag the superscript. When multiple unsequenced lists were present in the same row of a table. The separate unsquenced lists were being placed into the same list in the tag tree. The Engine has been updated to addressed the above scenarios so that the tag tree flows through the document in the correct order.

PackageInformation element added to request & response
Type: Enhancement Reference: PBI 805559, 814058, 802775, 803062, 799271 Documentation Impacts: Expere Developer Guide > PackageInformation
Summary: the Generate and SelectAndGenerate requests have been updated to pass in package information (`<PackageInformation/>`) as part of the `<InlinePackage/>` element, Additionally, the `<DocSet/>` element returns this `<PackageInformation/>` element and values in the Expere response file. The Expere Developer Guide > PackageInformation and related sections (accessible through links within the PackageInformation topic contain detailed information. Note: The `PackageInformation` and its child elements are optional elements and unlikely to be used by self-hosted users.

Radio button behavior enhanced with Embedded PDF documents
Type: Enhancement Reference: PBI 813395
Summary: it was determined that radio buttons did not function as expected on Embedded PDF documents; for example, users could select both options if two radio buttons were present. The expected behavior was that only one option could be selected; selecting an option would deselect the other option. This behavior has been enhanced, so that radio buttons are generated correctly on Embedded PDF documents.

Expere: Partial Document list functionality updated to support Embedded PDF documents
Type: Enhancement Reference: PBI 800537 Documentation Impacts: (Self-hosted users) Expere Developer Guide > Document List and Partial Document List functionality; (Hosted Expere users) Expere Document Services Implementation Strategies Guide > Document List and Partial Document List functionality
Summary: in March 2023 (PBI 744444), we informed you that the Expere Engine was enhanced support the selection of either a full or partial document list. As part of this overall effort, Partial Document List functionality has been updated to include EmbeddedPDFs in the Partial Document List.

Engine: Java 17 enhancement with .NET - user action required
Type: Enhancement Reference: PBI 806554 Documentation Impacts: Expere Implementation Guide > .NET Users: Expere .NET Installation
Summary: Expere on-prem users must install Java 17 when installing the Expere .NET Runtime Engine. Users must perform the following: change `replace_with_full_path\bin\server\jvm.dll` to include the actual path to the Java 17 JDK, for example `C:\Program Files\Amazon Corretto\jdk17.0.8_7\bin\server\jvm.dll`.

Expere: Engine updated to use Amazon Corretto Java 17 for use with WildFly
Type: Enhancement Reference: PBI 784744, 818222 User documentation: Expere System Requirements: Java Environment Software Requirements
Summary: The Expere Engine has been updated to use Amazon Coretto Java 17 when using Wildfly.

Expere: SMART Doc PDF copy updated to return `SignaturePointSet`
Type: Enhancement Reference: PBI 803141 Documentation Impacts: (Hosted Expere users) Expere Document Services Implementation Strategies > Using SMART Doc functionality / dynamic Expere eNotes; (Expere on-prem users) Expere Developer Guide > Using SMART Doc functionality / dynamic Expere eNotes
Summary: Expere SMART Doc functionality has been enhanced to include a `<SignaturePointSet/>` container and corresponding information in the Expere response for the PDF Copy of an eNote when the eNote has been specified to be eSignable in the REQ's Properties. Typical behavior for an eSignable document is to also have esignature fields and be fillable and also be identified as eSign in the response for `<InstanceSigningInstructions/>`. The PDF Copy for an eNote will not have esignable fields and will have a designation of NoSignatures for `<InstanceSigningInstructions/>`.

Engine: Document assembly behavior updated when using images with a Tagged PDF
Type: Enhancement Reference: PBI 799727
Summary: It was reported that images failed to display on some generated Tagged PDF documents. After internal analysis was conducted, it was determined that Expere should be updated to fail transactions and not generate documents when images are not located and cannot be printed on the document. Note: This enhancement will only affect those documents assembled with FOP 2.8.

Expere: Notary and Recordable document behavior enhanced when using namespace prefixes
Type: Enhancement Reference: PBI 805425
Summary: It was reported that recordable and notary documents were being returned as "ESign" instead of "InkSign" when `/Txn/ExcludeESignatureAndENotaryInd=1` was passed in the transaction .XML and when a namespace prefix was defined. This behavior has been modified so that Expere now supports namespace prefixes when `/Txn/ExcludeESignatureAndENotaryInd` is specified.

Expere: new Expere Workflow Guide available
Type: Enhancement Reference: PBI 805957 Documentation Impacts: Expere Workflow Guide
Summary: A new Expere Workflow Guide has been created that provides detailed information on various common workflows when using Expere. Additionally, this guide contains information about key Expere-related concepts, such as Autoselection and Callbacks. Note: This guide will be periodically updated with additional workflows, key concepts, and other pertinent information.

Expere: Implementation Guide updated with new Java/WildFly/Expere combined installer
Type: Enhancement Reference: PBI 812608 Documentation Impacts: Expere Implementation Guide: Combined Java/WildFly/Expere installation procedure
Summary: The Expere Implementation Guide has been updated with a new topic explaining how to install the combined Java/WildFly/Expere installer.

SMARTDoc address logic updated
Type: Enhancement Reference: PBI 801206
Summary: Previously when Expere parsed SMARTDocs mailing addresses, it also converted the mailing addresses to comply with that of the USPS (United States Postal Service) mailing address convention. After further analysis, it was determined that Expere will now only parse the mailing addresses as the mailing addresses do not need to adhere to USPS mailing address conventions.

Engine: Watermark processing flow updated for upcoming iText upgrade
Type: Enhancement Reference: PBI 762647
Summary: Internal analysis has determined that an upcoming iText upgrade would impact the way watermarks function within the Expere Engine. As a result, watermark processing has been updated within Expere to accommodate an upcoming iText upgrade. Note: This upgrade will not affect integrations or generated documents.

Engine: response updated to return SmartDoc element
Type: Enhancement Reference: PBI 791619
Summary: As part of our overall work to support SmartDoc functionality, the Expere Engine has been updated to return the `SmartDoc` element within the `DocDescriptor` container if specified in the transaction request for the PDF copy, in addition to being returned for the SmartDoc. For more information, see Expere Developer Guide > DocDescriptor.

Engine: AnchorText behavior enhanced
Type: Enhancement Reference: PBI 799068 Documentation Impacts: (Expere self-hosted users): Expere Developer Guide > AnchorText; (Expere Hosted users): Hosted Expere Implementation Strategies Guide > AnchorText
Summary: The `AnchorText` ancillary output functionality has been enhanced based on user feedback. As a result, the AnchorText document included in a document package when the `AnchorText` ancillary output is selected and lists each document that contains anchors by providing the `InstanceDisplayName`, the `SignerRole`, and `SignerName` values; for example:
    Application Disclosure-WI | Borrower | John Doe

Engine: Ancillary Barcode Height option honored
Type: Enhancement Reference: PBI 798000 Documentation Impacts: (Expere self-hosted users:) Expere Developer Guide > Implementing Barcodes as an Ancillary Output Option; (Expere Hosted users): Expere Document Services Implementation Strategies Guide > Implementing Barcodes as an Ancillary Output Option; Requirements Editor User Guide: Implementing Barcodes as an Ancillary Output Option
Summary: Expere now supports specifying per-document ancillary barcode height. The barcode height authored in the native REQ file will be applied to that document's ancillary barcode. Note: Consider the following: Barcode height can be specified for all Expere-supported ancillary barcode types. If no value is specified, then apply the default height value. In scenarios where the barcode type is authored in the REQ while the ancillary specifies a different barcode type, the ancillary barcode type will take precedence. If a document has a footer and a barcode height defined, it is possible the amount of space defined for the footer will need to be adjusted to get the desired output. The maximum barcode height is 44 points / .61 inches. If a larger space is specified when authoring the barcode, additional white space will be reserved, but the barcode height will be 44 points/.61 inches.

Expere: Landscape orientation behavior enhanced for static documents
Type: Enhancement Reference: PBI 759968
Summary: Users reported that certain static documents that consisted of both portrait and landscape page orientation did not display the landscape-oriented pages correctly. For example, one document contained portrait orientation all but the last page of the document, which contained a landscape orientation. This last page was inadvertently display the page in portrait orientation and was truncating some of the information. As a result, Expere has been enhanced so that landscape page orientation is now preserved in static documents.

Expere: Engine updated to used Wildfly 30.0
Type: Enhancement Reference: PBI 801294
Summary: The Expere Engine has been updated to use WIldfly 30.0.

Engine: fillable date field behavior identified in Embedded PDF; additional logging functionality added
Type: Enhancement Reference: PBI 795571 Documentation Impacts: ADA Implementation Guide > Troubleshooting
Summary: During internal testing for a separate work item, it was identified that one of the date fields did not generate as a fillable field when eSignatureAndFieldSupport was specified for a specific Embedded PDF REQ file. Analysis revealed that the specific Embedded PDF REQ file required an additional content update, and thus, no coding changes were implemented. However, additional logging functionality was added in order to identify this issue if it occurs by providing a list of fields that need to be removed and re-added so the document generates with the correct fillable fields.

Engine: log4j and wildly logging updates
Type: Enhancement Reference: PBI 796918
Summary: The default logging configuration has been adjusted to remove excess and unnecessary log entries from the log file.

Expere Test Service Pool updates
Type: Enhancement Reference: PBI 797396
Summary: The Service and Endpoint fields have been removed from the Test Service Pool due to an internal static code analysis.

DocViewer: Mortgage acknowledgement section and Authority document updated
Type: Defect Correction Reference: PBI 820322
Summary: DocViewer has been updated to ensure that the values for by, of, and of in the Acknowledgement section of the Mortgage document now populate with data when both collateral owners are individuals. Additionally, the Note Information Inclusion dropdown field now correctly displays on the Authority document. Previously, these values were blank.

DocViewer: US Territories supported
Type: Enhancement Reference: PBI 811107
Summary: DocViewer has been updated to support the following US Territories: American Samoa (AS) Guam (GU) Commonwealth of Northern Mariana Islands (MP) Commonwealth of Puerto Rico (PR) U.S. Virgin Islands (VI)

DocViewer: Sorting behavior enhanced
Type: Enhancement Reference: PBI 779680
Summary: DocViewer has been enhanced so that fees are sorted for any document that contains a `SortByValue`, including the Loan Estimate Addendum.

DocViewer: additional output format supported
Type: Feature Reference: PBI 796964
Summary: As part of our support of additional output formats, DocViewer has been enhanced to support a new date output of "MM/YYYY" and "M/YYYY." Note: Example displays consist of the following: MM/YYYY: 01/2024 M/YYYY: 1/2024; 10/2024

DocViewer: new Support Required Data parameter added
Type: Enhancement Reference: PBI 711363, 795682, 795683, 795684 Documentation Impacts: DocViewer Web Services Guide > DocViewer API > BeginSession DGS Core DocViewer REST API (V2) > DocViewerOptions; (Wolters Kluwer users) DocViewer Test Web App User Guide > Using the Test Web App interface - Create Session using transaction data
Summary: DocViewer has been enhanced to determine if required documents should be available for viewing in the Document Drawer. This functionality is enabled when passing in a `SupportRequiredData=yes` parameter through `BeginSessionRequest`. When this parameter is passed in the request, only those documents that are considered "Required" are available for viewing in the Document Drawer.

DocViewer: Track Changes enhancement
Type: Enhancement Reference: PBI 797711, 797851, 797852, 797853 Documentation Impacts: DocViewer Web Services Guide > BeginSession (Input) and CreateDocViewerSessionRequest; (Internal users) TestWebApp User Guide > Using the Test Web App interface - Create Session using transaction data
Summary: DocViewer has been enhanced so that changes can be saved and accessed during a later session. Users may now pass in a `changedDataPoints` flag during a `BeginSession`, so that additional modifications may be applied to a new session. Note: The record of changes appears after submitting documents or ending a current session on the End Session page within the Changed Transaction Data section. Users can continue to apply these same changes by selecting the Transfer changes to new session button on the End Session page then submitting a `changedDataPoints` flag during subsequent sessions.

DocViewer: PKGPKT.PackageName behavior enhanced with `BeginSession`
Type: Defect Reference: PBI 800848
Issue: Users reported 404 issues when attempting to launch a `BeginSession` using an EZ Config PKGPKT.PackageName content URI. Internal analysis determined that the alias was not being passed when retrieving the package from EZ Config Packages and Packets when using a `BeginSession`.
Solution: This behavior has been enhanced so that a DocViewer `BeginSession` can be started using PKGPKT.PackageName.

DocViewer: expected language not appearing
Type: Enhancement Reference: PBI 808874
Summary: On the Note Commercial Line of Credit Non Revolving, there is certain language which was not appearing in DocViewer. This language should appear, depending upon whether an element exists in the XML. DocViewer has been enhanced to accommodate if the element exists or does not exist and to display the proper language.