Features

What is a "feature?"A feature is a new function or series of functions within an application which did not previously exist. On this page you will find changelogs associated to features being delivered in incremental pieces. Each changelog describes a small function delivered to support the larger feature function as a whole. Below you will find a list of features, with their respective changes, associated to the Expere Document Services version the feature is or will be delivered.

eNotary

Wolters Kluwer has added the ability for a Notary Public to notarize documents electronically.

eOriginal

In this iteration of eOriginal-related functionality, we have implemented the ability to electronically sign the eNote using the eOriginal application.

Note: As of the eOriginal feature, all Feature-related changelog entries will now reside on the Changelog Entries - 2020 page.

Default Data - Logos

Wolters Kluwer has added the ability to include logos in Default Data content for use with the EZConfig application.

Ability to include logo in Default Data content for EZConfig
  • Type: Feature
  • Reference: PBI
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts:
Summary: We have updated the API request calls with a new EZConfig parameter, which can be used to apply Logos from EZ Config Default Data. This parameter can be used to pass in specific organization ID, name, alias, and line of business information when using logos. When the <OrgId>, OR the <OrgName>, <OrgAlias>, and <OrgLOB> (Line Of Business) are included in the SelectAndGenerate or Generate request, the Logo setup for the given Organization within EZ Config is applied.
Note:
  • If a logo has not been setup for the specified Organization within EZ Config, logos will not be applied.
  • If an Ancillary Output Logo is included in the request, and EZ Config parameters are included for logo use, the Ancillary Output logo will be applied.

Refer to the on how to set up the logo functionality for your organization.

Technical Notes: Sample request snippet below: 
<data:EZConfig>
                  <data:OrgName>Organization 3</data:OrgName>
                  <data:OrgAlias>FixedLibrary\.(.*)</data:OrgAlias>
                  <data:OrgLOB>Commercial Lending</data:OrgLOB>
   </data:EZConfig>
Implementation Notes: This feature is available in the .
Tool Suite updated with ability to apply Default Data logo
  • Type: Enhancement
  • Reference: PBI
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: Expere Document Services Tool Suite Guide: Select Generate Deliver; Select and Generate
Summary: As part of the feature work to apply a logo from EZ Config Default Data content, the pages within the Tool Suite have been updated with a new Default Data section here Apply Logo from Default Data can be selected. The Tool Suite User Guide contains detailed information on using this new functionality.
Implementation Notes: This feature is available in

Standard eSignature and Field Level fillable fields

This feature allows authors enter field level logic into a standard eSignature and field level support fillable field for dynamic documents by enhancing mutually exclusive checkboxes and credit card fields. What are mutually exclusive checkboxes? For example, if presented with two checkboxes or option buttons (commonly referred to as "radio buttons"), you may only select one. Checkboxes are mutually exclusive in that if one box is checked the borrower cannot check another related check box.

Mandatory/Optional fillable field function added
  • Type: Feature
  • Reference: PBI 571757 / 571756
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: When a request includes a "true" value indicator for <eSignatureAndFieldSupport> for either a dynamic or static document, our eSignature and Field Support functionality has been updated with the following:
  • The Expere response file returns a <SignatureRequired> element with either a "true" or "false" value.
  • The <FieldType> returns any of the following enumeration values:
    • Initials
    • Name
    • Numeric
    • Alphanum
    • CCName
    • CCNumber
    • CCExpiryDate
    • CCBillingAddr
    • Date
  • <FillableText> / <FillableCheckbox> elements are flagged with either a "true" or "false" value for those fields and checkboxes that require mandatory data completion (noted as <Mandatory>).
Note: These elements are all optional.
Technical Notes: Sample request code below:
<Document>
			<DocumentID>PKGD.testsignature</DocumentID>
				<AncillaryOutput>
					<OutputType>ESignatureAndFieldSupport</OutputType>
					<ESignatureAndFieldSupport>
						<eSignatureCoordinatesOnly>false</eSignatureCoordinatesOnly>
					</ESignatureAndFieldSupport>
				</AncillaryOutput>
	     </Document>
Sample response code below:
<r:FillableFieldSet>
                     <r:FillableText>
                        <r:FieldName>This is a fillable field.</r:FieldName>
                        <r:ToolTip>This is a fillable field.</r:ToolTip>
                        <r:Width>216.00002</r:Width>
                        <r:Height>14.0</r:Height>
                        <r:XCoordinate>133.01</r:XCoordinate>
                        <r:YCoordinate>511.93</r:YCoordinate>
                        <r:FontName>Arial-ItalicMT</r:FontName>
                        <r:FontSize>10.0</r:FontSize>
                        <r:NumberOfCharacters>0</r:NumberOfCharacters>
                        <r:FieldText>default value</r:FieldText>
                        <r:HorizontalAlignment>Left</r:HorizontalAlignment>
                        <r:Underline>false</r:Underline>
                        <r:PageNumber>1</r:PageNumber>
                        <r:FieldType>Alphanum</r:FieldType>
                        <r:Mandatory>Yes</r:Mandatory>
                     </r:FillableText>
                     <r:FillableCheckbox>
                        <r:FieldName>This is a fillable checkbox.</r:FieldName>
                        <r:ToolTip>Click the box to select and deselect.</r:ToolTip>
                        <r:Checked>false</r:Checked>
                        <r:PageNumber>1</r:PageNumber>
                        <r:XCoordinate>154.9</r:XCoordinate>
                        <r:YCoordinate>491.45</r:YCoordinate>
                        <r:Mandatory>Yes</r:Mandatory>
             </r:FillableCheckbox>
Implementation Notes: This new feature requires you to install the Expere 2019 Release Twois available in the October release of Hosted Expere / Expere Document Services. .
Support expanded for mutually exclusive checkboxes - dynamic and static documents
Summary: We have enhanced Expere to support mutually exclusive checkboxes with our standard eSignatureAndFieldSupport.

When mutually exclusive checkboxes have been authored in content using GroupID, and if the request submitted includes eSignatureAndFieldSupport as "true," the resulting PDF is generated with mutually exclusive checkboxes.
Technical Notes: Expere now includes a GroupID element that aggregates related checkboxes and option buttons together.
Implementation Notes: This new feature requires you to install the Expere 2019 Release Twois available in the October release of Hosted Expere / Expere Document Services.

Support for Wolters Kluwer E-Sign Field Level Logic

This feature allows authors enter field level logic into an Wolters Kluwer eSignature field for dynamic documents by enhancing mutually exclusive checkboxes and credit card fields. What are mutually exclusive checkboxes? For example, if presented with two checkboxes or option buttons (commonly referred to as "radio buttons"), you may only select one. Checkboxes are mutually exclusive in that if one box is checked the borrower cannot check another related check box.

Mutually Exclusive Checkboxes
Summary: Expere has been enhanced to generate mutually exclusive checkboxes (or option buttons) for documents where Wolters Kluwer E-Sign is being used. When an .REQ file is submitted with a <GroupID/> element set to "True" and letters and numbers are strung together to group two fields, Expere interrogates the .REQ file to locate the <GroupID/> and create the corresponding checkboxes and option buttons.
Technical Notes: Expere now includes a GroupID element that aggregates related checkboxes and option buttons together.
Implementation Notes: This feature is available in the 2019 Release Two (2) of the Expere Engine.

Token Authentication

Users can now add a token when authenticating to the Callback API instead of a traditional username and password. This new token feature works exclusively with REST API callbacks.

Tool Suite updated to use token authentication
Summary: Users can now specify a token or username/password when authenticating a transaction in the following API calls:
Note: The Callback URL must be specified either in the database or request; if not specified, no callbacks are sent. Any login information specified in the request overrides login information that exists in the database.
Implementation Notes: This enhancement is available in the September release of Expere Document Services.
New Token option for callback authorization
Summary:

We have extended our callback functionality to include the ability to call a REST callback service with a token.

The callback functionality that utilizes either a username and password or no authentication will continue to call a SOAP callback service. Using a token is the only scenario where a REST callback service is utilized.

The DocumentServicesAPI WSDL has been updated to contain a new optional field under "Authorization" called "Token" for use with Select & Generate and Generate API calls.

Note: if the callback information is provided with the request, it takes precedence over what is stored in the database CallbackAuthentication below
Implementation Notes: This new feature enhancement is available in the September deployment of Expere Document Services; no user action is required.
Note: You will need to create your own REST endpoint when using a token with callback authentication; future documentation will be authored to aid you in this process. Contact your Professional Services liaison for further information on implementing this new REST callback service.

Logos

Wolters Kluwer has added the ability to apply logos to the header of each Expere-generated document.

Ability to apply a logo
Summary: Users can now add a unique logo per transaction or document, through a SelectAndGenerate or Generate call, respectively. This is accomplished through a new Logo ancillary output option. See Technical Notes below for code samples.

For Ancillary Output Logos, note the following considerations:

  • The logo height and width can be specified by the user in the Expere request through the <HeightInInches/> and <WidthInInches/> elements. The required unit of measurement is inches (for example. 1.5). Users must pass in either the <HeightInInches/> or <WidthInInches/> element. If only passing in one of the above elements, Expere will auto-scale the logo.
    Note: While users are not restricted to the size of the image (in terms of height or width), a recommended size is 1.5 inches.
  • The logo can be placed either in the left, center, or right portion of the header through the <Justification/> element.
  • The logo can be applied to first page only, all pages, or all page except for the first page through the <Placement/> element.
  • Users can provide tool tip information through an optional <AlternateText/> element.
  • Logos are supported on all non-recordable dynamic documents where an integrated disclosure (TRID) style guide is not used.
  • Supported logo types consist of the following:
    • PDF: .jpeg, .bmp, .gif, .png, .tif
    • RTF: .jpeg, .bmp, .gif, .png

When using custom logos: Custom logos where the logo image is passed in the transaction, using one of the xpaths below, will continue to be honored. The Ancillary Logo will be ignored for documents using the transaction logo:

  • /Txn/LogoDesc
  • /Txn/LogoLeftDesc
  • /Txn/LogoCenterDesc
  • /Txn/LogoRightDesc

Custom logos where the logo image is within the custom content (embedded in the REQ), will print both the Ancillary logo and the logo embedded in the REQ. Users can adjust for this by using the Generate API and specify which documents the Ancillary logo should be applied to, or, remove the custom logo from custom content.

Technical Notes: Sample code below for an ancillary logo:
<doc:AncillaryOutput>
                <doc:AncillaryOutputOption>
                    <doc:OutputType>Barcode</doc:OutputType>
                    <doc:Barcode>
                        <doc:Type>barcode39</doc:Type>
                        <doc:Pattern>Static Text</doc:Pattern>
                        <doc:UseCoverPage>false</doc:UseCoverPage>
                        <doc:FirstPageOnly>false</doc:FirstPageOnly>
                        <doc:HorizontalAlignment>Center</doc:HorizontalAlignment>
                    </doc:Barcode>
                </doc:AncillaryOutputOption>
                <doc:AncillaryOutputOption>
                    <doc:OutputType>Logo</doc:OutputType>
                    <doc:Logo>
                        <doc:HeightInInches>1.1</doc:HeightInInches>
                        <doc:WidthInInches>1.5</doc:WidthInInches>
                        <doc:Placement>AllPages</doc:Placement>
                        <doc:Justification>Left</doc:Justification>
                    </doc:Logo>
                </doc:AncillaryOutputOption>
            </doc:AncillaryOutput>
Implementation Notes: This feature is available in the 2019 Release Two (2) of the Expere Engine.