Changelog Entries - 2018

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.

New Features

Enhancements

Defect Corrections

December

The effective date for all products within the scope of this document for this release is December 12 for the CT environment and December 21 for the Production environment.

ID and Email added to WSDL file for FillableFields
  • Type: Enhancement
  • Reference: PBI
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts:
Summary: We have updated the to include the customer ID and SignerEmail for fillable fields. In a future release, these values will be returned in the Expere response when using fillable fields. These values are currently returned when using Wolters Kluwer E-Sign.
Technical Notes: The follwing is an example of the fillable field in the response file: 
<r:FillableText>
	    <r:Id>123456</r:Id>
        <r:EmailAddress>attest@email.com</r:EmailAddress>    
        <r:FieldName>Sara</r:FieldName>
</r:FillableText>
Implementation Notes:

This enhancement is available in the .

Changelog Release Schedule updated
Summary: The wording of the release schedule has been updated to specify the following:

The Customer Test (CT) environment is updated on the first or second Tuesday of the month at 9:00 PM Central Time.
Implementation Notes: This enhancement is available in the December release of Expere Document Services.
Response to return DocumentType updated
Summary: It was previously reported that the DocType (DocumentType) was displaying as "Dynamic" in the Expere Document Services and Document Generation Services response, even if the actual DocType is static (officially known as "Template").
Technical Notes: This behavior has been corrected. The Expere Document Services and Document Generation Services response now accurately reflects the DocType.
Implementation Notes: This defect correction is available in the October release of Expere Document Services.

November

The effective date for all products within the scope of this document for this release is November 13 for the CT environment and November 22 for the Production environment.

Workflow outline and sequence diagram added to web services user guide
Summary: In a continued effort to improve our user documentation, we have enhanced the Expere Document Services Web Services to include a comprehensive sequence diagram and corresponding workflow outline. The detailed workflow outline provides to our more technical API information.
Implementation Notes: This enhancement is available in the November release of Expere Document Services.

October

The effective date for all products within the scope of this document for this release is October 9 for the CT environment and October 18 for the Production environment.

Expere Document Services web services request and response samples updated in webhelp
Summary: We have updated the request and response samples in the Expere Document Services Web Services Guide for the following methods:
  • Generate
  • GetGenerateResults
  • GetRequestStatus
  • GetSelectResults
  • ListAliases
  • ListDocuments
  • ListPNPPackages
  • Select
  • SelectAndGenerate
  • SelectSynchronous

A deeper analysis has concluded that the aforementioned methods are the most common utilized by Expere Document Services users.
Implementation Notes: This enhancement is available in the October release of Expere Document Services.

September

The effective date for all products within the scope of this document for this release is September 11 for the CT environment and September 20 for the Production environment.

Expanded eSign Document Detection
Summary: Expere now accepts eSignable documents when submitted through a new ESignature Document setting in the Document Properties dialog within the Requirements and Content Editor.

A new SuppressESignature element can be added to the REQ as a child of Document\Condition. If this element is present then eSignatures are disabled for the entire document. A typical use case is to have a condition to check if the document has any Notary signatures and add this element if it does since documents with Notary signatures are currently never eSignable.
Technical Notes: Refer to the Requirements and Content Editor User Guide for usage.
Implementation Notes: This enhancement is available in the September release of the Expere Engine.
Feature flag functionality activated
  • Type: Enhancement
  • Reference: PBI 511784
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: Previously in PBI 504715 (New <ESignatureDocument/> element added), we updated the Expere Document Services WSDL with a new <ESignatureDocument/> element. This feature functionality was disabled, pending document content to be updated with the new <ESignatureDoucmnet/> element. With the September release this functionality has been activated in our CT environment, as of 09/11/18. This will be released to the production environment in October, on 10/18/18.
Implementation Notes: This enhancement is available in the September release of Expere Document Services.
WKES signature enumeration enhanced
  • Type: Enhancement
  • Reference: PBI 520468
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: Previously, Wolters Kluwer E-Sign signature fields were being enumerated incorrectly when a single document contained multiple signature sections for one or more recipients. This resulted in the same signing enumeration being used in both signature areas of the document. This behavior has been enhanced; each recipient signature line, within a single document, is now enumerated as its own signing field.
Implementation Notes: This enhancement is available in the September Release of Expere Document Services.
Ability to generate transaction barcodes on RTF documents restored
  • Type: Enhancement
  • Reference: PBI 498686
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: You can now generate transaction barcodes on RTF-generated documents through the use of the <TaglineBarcodeDesc> element in your transaction .XML. The value within this element should represent the barcode pattern to appear on the RTF document. This enhancement modifies previous behavior where the presence of the <TaglineBarcodeDesc> element within the transaction caused it to fail.
Technical Notes: A sample request with the <TaglineBarcodeDesc> element could resemble the following:
<TaglineBarcodeDesc>Bar Code 1</TaglineBarcodeDesc>
Implementation Notes: This enhancement is available in the 2018 Release Three (3) of the Expere Engine.
Configurations type for BeginSession
  • Type: Enhancement
  • Reference: PBI 511720
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: Configuration; BeginSession
Summary: In an ongoing effort to enhance our user documentation, we have incorporated additional detail surrounding the Configuration type in the BeginSession request topic in the Expere Document Services web services documentation.
Implementation Notes: This enhancement is available in the September release of Expere Document Services.

August

The effective date for all products within the scope of this document for this release is August 7 for the CT environment and August 16 for the Production environment.

ESign/InkSign/NoSignatures now returned in InstanceSigningInstructions
  • Type: Enhancement
  • Reference: PBI 517516
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: We had recently updated the InstanceSigningInstructionsTypeEnum within the Expere Document Services WSDL to remove unused values (PBI 506119 - Instance Signing enumerations updated). In the August release, the enumeration values that remain will now be used to populate the instance signing instructions within the response through the use of ESign, InkSign, or NoSignatures.
Implementation Notes: This enhancement is available in the August release of Expere Document Services.
Checkboxes rendered when XY coordinates are requested
  • Type: Enhancement
  • Reference: PBI 506732
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: It was reported that documents were not rendering check boxes when XY coordinates were being requested and being merged by an institution's third-party vendor. We have enhanced how Expere renders check boxes on documents; when they are merged by a third-party vendor, check boxes are not removed or missing.
Implementation Notes: This enhancement requires the 2018 Release Three (3) Expere Engine.
Document white-space reservation enhanced when using barcodes
  • Type: Feature
  • Reference: PBI 512325
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: Previously users of barcodes found extra white-space above the tag-line was being saved when additional document text could fit on the page. Unfortunately this caused documents to print additional pages, sometimes causing increased recording costs when the documents impacted were recordable. In an effort to reduce excess white-space on documents when using barcodes, Expere now reads the barcode type being used and reserves only the space necessary to print the requested barcode.
Implementation Notes: This enhancement requires the 2018 Release Three (3) Expere Engine.

July

The effective date for all products within the scope of this document for this release is July 10 for the CT environment and July 19 for the Production environment.

Ability to pass in a request with multiple OPPSA products
Summary: Users can now pass requests to Expere Document Services containing multiple OPPSA products using the OPPSA Merge Product Data page and the following API requests:
  • Select Generate and Deliver
  • Select and Generate
  • Generate

Tool Suite users : use the Oppsa Required checkbox and follow the instructions using the Select Generate and Deliver, Select and Generate, Select / Generate, and OPPSA Merge Product Data.
Technical Notes: Integrators - the EDS Web Services: Oppsa data type now allows for multiple ProductName elements.
Implementation Notes: This feature is available in the July release of release of Expere Document Services.
Expere EZ Config Packages and Packets Application and Web Services Available
Summary:Wolters Kluwer introduces a new application, Expere EZ Config Packages and Packets. This application allows users to organize and manage documents and configure packages that align to your financial institution’s workflow phases. Expere EZ Config Packages and Packets integrates with Expere Document Services, which is leveraged to process requests for document generation.
Implementation Notes: This feature is available in the July release of Expere Document Services.

July - ExpeditedThe effective date for all products within the scope of this document for this release is June 26 for the CT environment and July 19 for the Production environment.

ApplyPoliciesAndReturnTransaction API updated to retain empty elements
  • Type: Defect
  • Reference: PBI 511700
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: It was reported that empty elements were removed from the request .xml file when using the ApplyPoliciesAndReturnTransaction API. As a result, when utilizing DocViewer, users were not prompted to collect those additional data items that were missing from the original request .xml file.
Solution: When using the ApplyPoliciesAndReturnTransaction API, empty data points and collections are retained in the request .xml file.
Implementation Notes: .
OppsaId no longer required
  • Type: Defect
  • Reference: PBI 511365
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: It was reported that the OppsaId was required in an OPPSA request, according to the Expere Document Services WSDL. However, when the OppsaId is included in the request it causes the transaction to fail.  
Solution: The Expere Document Services WSDL has been updated to remove the OppsaId, and therefore is no longer required.
Implementation Notes: This defect correction is available in the July release of Expere Document Services.
Additional DocData element now populated
  • Type: Enhancement
  • Reference: PBI 500629
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: With the June release of Expere Document Services we updated the WSDL with a new DocData element for <InstanceRecordableFlag/> (See previous WSDL change log here.) This new element is now included in the response and populated with a value of 'True' when the document is recordable, or a value of 'False' when the document is not recordable.
Implementation Notes: This feature is available in the July release of Expere Document Services.
AssembleDocumentsService updated to create document list
  • Type: New Feature
  • Reference: PBI 501804
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: PackageDoc
Summary: Expere now has the ability to create a Document List for a SelectAndGenerate or Generate request. The Document List provides the list of documents created for a request and returns the list in the response, under <DocumentList/>, as well as a Document List PDF. To take advantage of this behavior a Document List Document needs to be authored within in the package of documents being requested.
Technical Notes: Sample response below:
<r:DocumentList>
            <r:DocumentID>PKGD.TitleGuarantyApplication-IA</r:DocumentID>
            <r:DocumentID>PKGD.ChangedCircumstances</r:DocumentID>
        </r:DocumentList>
Implementation Notes: This feature is available in the July release of Expere Document Services.

June

The effective date for all products within the scope of this document for this release is June 12 for the CT environment and June 21 for the Production environment.

New <ESignatureDocument/> element added
  • Type: New Feature
  • Reference: PBI 504715
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: DocDescriptor
Summary: We have updated the Expere Document Services WSDL to contain a new <ESignatureDocument> element in the DocDescriptor data type. This new optional element will allow for either a "true" or "false" value to determine whether to incorporate signature fields and to indicate if the document is esignable.

By default, this element is set to "false," disabling this feature until a future date.
Technical Notes: Sample response below:
<r:PackageDoc PackageDocID="PKGD.BalloonPaymentMortgageDisclosure_initials_ff">
             <r:DocDescriptor>
                    <r:DocID>PKGD.BalloonPaymentMortgageDisclosure_initials_ff</r:DocID>
                    <r:DocType>Dynamic</r:DocType>
                    <r:DocDisplayName>Balloon Payment Mortgage Disclosure with initiails and fillable</r:DocDisplayName>
                    <r:DocRootEntityName>INS.BalloonPaymentMortgageDisclosure_initials_ff</r:DocRootEntityName>
                    <r:ESignatureDocument>false</r:ESignatureDocument>
             </r:DocDescriptor>
             <r:DocWorkOrder>
                    <r:DocPrepare>true</r:DocPrepare>
                    <r:DocAutoselected>true</r:DocAutoselected>
                    <r:DocSuggested>false</r:DocSuggested>
                    <r:DocFormat>PDF</r:DocFormat>
                    <r:DocStyle>WKFS_StyleGuide</r:DocStyle>
             </r:DocWorkOrder>
       </r:PackageDoc>
Implementation Notes: This enhancement is available in the June release of Expere Document Services.
Instance Signing enumerations updated
Summary: We have added the enumeration values around the instance signing data type to consist of the following:
  • NoSignatures
  • InkSign
  • ESign

Additionally, we have removed the following enumerations:

  • NoSignaturesAndPrint
  • ESignAndPrint
  • InkSignOrEsign
  • InkOrEsignAndPrint

We have updated the WSDL and the corresponding Web Services help topic here: InstanceSigningInstructionsTypeEnum.
Implementation Notes: This enhancement is available in the June release of Expere Document Services.
Change Log webhelp restructured
Summary: To improve consistency with other product change logs, we have restructured the Wolters Kluwer Hosted Expere Change log to include the following enhancements:
  • The main Change Log Overview and Important Notifications page now consists of individul product change log sections: Expere Document Services/Expere Engine; OPPSA; EZConfig Packages and Packets.
  • The monthly list of Expere Document Services/Expere Engine new features, enhancements, and defect corrections has been moved to the top of this topic.
Implementation Notes: This change log restructure is available in the June release of Expere Document Services.
Additional DocData element (<InstanceRecordableFlag/>) added
  • Type: Enhancement
  • Reference: PBI 500627
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: Web Services: DocInstance
Summary: The <InstanceRecordableFlag>false</InstanceRecordableFlag> schema point is now supported in the Expere Document Services WSDL. The value will be populated in the response with the July release.
Technical Notes: Sample response snippet (<InstanceRecordableFlag>false</InstanceRecordableFlag> highlighted) below:
</DocData>
         <InstanceDisplayName>Errors and Omissions Agreement</InstanceDisplayName>
         <InstanceFileName>Default-Errors_and_Omissions_Agreement.pdf</InstanceFileName>
         <InstanceFormattingMetadata/>
         <InstanceSequence>999</InstanceSequence>
         <b:InstanceBarcodeValue>Tag Line 1</b:InstanceBarcodeValue>
         <InstancePageCount>1</InstancePageCount>
         <InstanceRecordableFlag>false</InstanceRecordableFlag>
         <DocFormat>PDF</DocFormat
Implementation Notes: This feature is available in the June release of Expere Document Services.

May

The effective date for all products within the scope of this document for this release is May 8 for the CT environment and May 22 for the Production environment.

Response data updated
  • Type: Enhancement
  • Reference: PBI 500623
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: We have updated the Expere Document Services response to include additional <DocData> values, consisting of the following:
  • <InstanceFormattingMetadata>
  • <InstanceBarcodeValue />
  • <InstancePageCount>
  • <DocFormat>

These elements existed within Expere Document Services; however they were previously not supported.
Technical Notes: Sample Expere Document Services response:
</DocData>
               <InstanceDisplayName>Errors and Omissions Agreement</InstanceDisplayName>
               <InstanceFileName>Default-Errors_and_Omissions_Agreement.pdf</InstanceFileName>
               <InstanceFormattingMetadata/>
               <InstanceSequence>999</InstanceSequence>
<b:InstanceBarcodeValue>Tag Line 1</b:InstanceBarcodeValue>
               <InstancePageCount>1</InstancePageCount>
               <InstanceRecordableFlag>false</InstanceRecordableFlag>
               <InstancePageSize>Letter</InstancePageSize>
               <DocFormat>PDF</DocFormat>
Implementation Notes: This feature is available in the June release of Expere Document Services.
Ability to generate document list now available
  • Type: New Feature
  • Reference: PBI 500258
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: PackageDoc
Summary: Users can now generate a list of all documents included in a package through a new <DocumentList/> element within the PackageDoc data type.
Technical Notes: <DocumentList/> is an optional element; the available values are either "true" or "false."
Implementation Notes: This feature is available in the May release of Expere Document Services.
Callback delivery behavior enhanced
Summary: Users reported not receiving callbacks for certain Deliver requests. We determined that new errors were occurring, which were not accounted for with our existing retry logic. As a result, Expere Document Services would provide a Failed callback message but would not attempt a retry on the transaction.

We have updated our logic to perform retries when a delivery callback returns an exception for any errors that may occur.

Implementation Notes: This enhancement is available in the May release of Expere Document Services.

April

The effective date for all products within the scope of this document for this release is April 10 for the CT environment and April 19 for the Production environment.

Ability to resend callback status for a single transaction
  • Type: Enhancement
  • Reference: PBI 439636
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: SUPPORT page: Delivery Audit Log
Summary: It was determined that in some instances, Mailed callback statuses were not received for some transactions; as a result, users do not know if a transaction package was mailed.

Within the Tool Suite, you can now resend the following callbacks for a single transaction using the SEND button in the Delivery Audit Log:

  • Mailed
  • Canceled
  • Error
  • Tracking Number
Implementation Notes: This feature is available in the April release of Expere Document Services.
Rich Text Format (RTF) document format issue corrected
  • Type: Defect
  • Reference: PBI 494606
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: It was previously reported that when submitting a Select and Generate request with an RTF document output format, in some transaction instances no response was returned and the transaction remained in an Incomplete state.
Solution: We have implemented internal code enhancements to resolve this issue; submitting a Select and Generate request with an RTF document format output type now returns a successful response.
Implementation Notes: This defect correction is available in the April release of Expere Document Services.

February Out of band CT release

The effective date for this release is February 21 for the CT environment and March 15 for the Production environment.

ApplyPoliciesAndReturnTransaction behavior enhanced
  • Type: Defect
  • Reference: PBI 492706
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: It was reported that the ApplyPoliciesAndReturnTransaction API was not functioning correctly; while it returned incoming transaction data, it did not apply the policy data to the transaction. This API should generate a merged .XML file with both transaction and policy data.
Solution: This issue has been resolved; the ApplyPoliciesAndReturnTransaction API now functions as expected.
Implementation Notes: This feature is available in the March release of Expere Document Services.

February

The effective date for all products within the scope of this document for this release is February 6 for the CT environment and February 15 for the Production environment.

Ancillary barcodes now honor bottom margins for recordable documents
  • Type: Enhancement
  • Reference: PBI 490310
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: We have adjusted the static placement of the ancillary barcode for documents where margin requirements have been authored. It was determined that certain documents contained barcodes; in some cases, those documents are recordable which causes issues when formally recording with the county or state. This behavior has been enhanced: the ancillary barcode now honors the bottom and side margins so users can record their documents with any county or state. Note the following:
  • If a dynamic .REQ file is authored with bottom, left, or right margins and contains selected justification, the margin is then honored when applying an ancillary barcode.
  • If a dynamic .REQ file is not authored with margin requirements, then the default of .5" margin is honored when applying an ancillary barcode.
Implementation Notes: This feature is available in the February release of Expere Document Services. No user action is required.
Update Maximum Days to Expire (90 days)
  • Type: Enhancement
  • Reference: PBI 486653
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: Expere Document Services Tool Suite: Select Generate Deliver; Select And Generate
Summary: In a previous release (via PBI 422732) we added the ability for users to identify the number of days for Wolters Kluwer to retain their transaction data, by using the <DaysToPersistInLongTermStorage/> element. This element could be used on a transaction by transaction basis, or be set at the Account level, by contacting SupportLine . With the original implementation we defaulted the DaysToPersistInLongTermStorage value to 7 days, but allowed a maximum of 60 days to be submitted. Based on customer feedback, the maximum number of days has now been expanded to 90 day while the default remains at 7 days.

If you had previously identified an Account Level setting for DaysToPersistInLongTermStorage, your account will not be impacted or changed. If you would like to change/update your data retention settings with Wolters Kluwer, please contact SupportLine or your Professional Services consultant.

Implementation Notes: This feature is available in the February release of Expere Document Services.
Generation behavior modified for multiple instances of same document
  • Type: Enhancement
  • Reference: PBI 484981
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: When a request is made to Expere with multiple rule sources in a package, currently Expere will generate the duplicate documents multiple times for each rule source. This is due to Expere's behavior or requiring that PKGD files from different packages be named differently. To mitigate this issue, we have modified Expere's behavior whereby, a Select or SelectAndGenerate request will generate a document only once, even if the request has packages that contain multiple rule sources.
Implementation Notes: This feature is available in the February release of Expere Document Services.
PDFMerge fillable fields behavior modified
  • Type: Defect
  • Reference: PBI 483572
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: Previously in a request containing PDFMerge with eSignatureCoordindatesOnly set to "true," the resulting PDF document displayed the corresponding fields as fillable. This was incorrect behavior.
Solution: This issue has been resolved; PDFMerge with eSignatureCoordindatesOnly set to "true" does not produce fillable fields on the resulting PDF document.
Implementation Notes: This feature is available in the February release of Document Generation Services.
Document Output formats supported
Summary: We have enhanced Expere Document Services' document assembly behavior to support the following document output types:
  • PDF
  • RTF
  • Raw XML
  • Tagged PDF

The Document Output Formats has been added to the WK Hosted webhelp and contains detailed information around document assembly and document formats.

Implementation Notes: This feature is available in the February release of Expere Document Services.
Callback enhancement: new connection failure status
Summary: We added a new callback DeliveryFailed status which is returned in the DeliveryRequestStatus of the DeliveryService callback. You will receive this callback status when the Delivery Service is down.
Implementation Notes: The WK Hosted webhelp has detailed information and screenshots regarding this new error status. This feature is available in the February release of Expere Document Services.
InstanceProperties elements added to response file
  • Type: Enhancement
  • Reference: PBI 472925 / 483305
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: DocInstance; StateSpecificProperties
Summary: Expere Document Services now reads the <InstanceProperties/> element value from the original .REQ file and passes it to Expere Document Services for print fulfillment purposes. As a result, we have added the following child elements to the <InstanceProperties/> element:
  • ColorPaperRequired
  • ColorPaperColor
  • PrintingOption
  • RegistrationRequired
  • RegistrationInstructions
  • RecordingRequired
  • RecordingInstructions
  • CustomerPrintingRequired
  • CustomerPrintingInstructions
  • AttachmentRequired
  • AttachmentInstructions
  • InsertRequired
  • InsertInstructions

Elements will only be returned in the EDS response if the element is authored in the .REQ. See StateSpecificProperties section of the webhelp for full details on all potential values being returned in the response. This PBI is part of the overall State-Specific Delivery Intelligence feature
Technical Notes: Sample response below:
<xs:element name="InstanceProperties">
             <xs:complexType>
                    <xs:all minOccurs="0">
                           <xs:element name="ColorPaperRequired" type="YesNoEnum" minOccurs="0"/>
                           <xs:element name="ColorPaperColor" type="ColorPaperColorEnum" minOccurs="0"/>
                           <xs:element name="PrintOption" type="PrintOptionEnum" minOccurs="0"/>
                           <xs:element name="RegistrationRequired" type="YesNoEnum" minOccurs="0"/>
                           <xs:element name="RegistrationInstructions" type="xs:string" minOccurs="0"/>
                           <xs:element name="RecordingRequired" type="YesNoEnum" minOccurs="0"/>
                           <xs:element name="RecordingInstructions" type="xs:string" minOccurs="0"/>
                           <xs:element name="CustomerPrintingRequired" type="YesNoEnum" minOccurs="0"/>
                           <xs:element name="CustomerPrintingInstructions" type="xs:string" minOccurs="0"/>
                           <xs:element name="AttachmentRequired" type="YesNoEnum" minOccurs="0"/>
                           <xs:element name="AttachmentInstructions" type="xs:string" minOccurs="0"/>
                           <xs:element name="InsertRequired" type="YesNoEnum" minOccurs="0"/>
                           <xs:element name="InsertInstructions" type="xs:string" minOccurs="0"/>
                    </xs:all>
             </xs:complexType>
       </xs:element>
       <xs:simpleType name="YesNoEnum">
              <xs:restriction base="xs:string">
                    <xs:enumeration value="Yes"/>
                    <xs:enumeration value="No"/>
             </xs:restriction>
       </xs:simpleType>
       <xs:simpleType name="PrintOptionEnum">
             <xs:restriction base="xs:string">
                    <xs:enumeration value="NotSpecified"/>
                    <xs:enumeration value="DuplexLong"/>
                    <xs:enumeration value="DuplexShort"/>
                    <xs:enumeration value="Simplex"/>
             </xs:restriction>
       </xs:simpleType>
       <xs:simpleType name="ColorPaperColorEnum">
             <xs:restriction base="xs:string">
                    <xs:enumeration value="White"/>
                    <xs:enumeration value="Yellow"/>
                    <xs:enumeration value="Red"/>
             </xs:restriction>
       </xs:simpleType>
Implementation Notes: This feature is available in the December release of Expere Document Services.
Discrete Party logic updated
  • Type: Enhancement
  • Reference: PBI 472927
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: DiscreteParties and DiscreteParty
Summary: As part of a continued effort to implement the Single State Delivery feature, we have added a new element called <DiscreteParties/>. Within <DiscreteParties/>, <DiscreteParty/> elements include the following new elements:
  • ID
  • Name
  • BusinessName
  • AddressLine1
  • AddressLine2
  • City
  • State
  • ZipCode
  • CountryCode
  • MailingMethod

This allows those users implementing Wolters Kluwer print fulfillment or other print fulfillment services to track mailings using additional data.

Note: Expere Document Services will continue to accept the <DiscretePartyID/> element when authored on content.
Technical Notes: Sample response below:
<r:DocInstance DocIDRef="PKGD.Preforeclosure">
            <r:DocData>...</r:DocData>
            <r:InstanceDisplayName>Document A - John Doe</r:InstanceDisplayName>
            <r:InstanceFileName>Document A - John Doe.pdf</r:InstanceFileName>
            <r:InstanceFormattingMetadata/>
            <r:InstanceSequence>999</r:InstanceSequence>
            <r:InstancePageCount>2</r:InstancePageCount>
            <r:InstanceRecordableFlag>false</r:InstanceRecordableFlag>
            <r:InstancePageSize>Letter</r:InstancePageSize>
            <r:DocFormat>PDF</r:DocFormat>
            <r:DiscretePartyIDs>
		<r:DiscretePartyID>1425</r:DiscretePartyID>
	    </r:DiscretePartyIDs>
            <r:DiscreteParties>
              <r:DiscreteParty>
                <r:ID>1425</r:ID>
                <r:Name>John Doe</r:Name>
                <r:BusinessName />
                <r:AddressLine1>12345 Main St.</r:AddressLine1>
                <r:AddressLine2></r:AddressLine2>
                <r:City>Anywhere</r:City>
                <r:State>MN</r:State>
                <r:ZipCode>12345</r:ZipCode>
                <r:CountryCode>USA</r:CountryCode>
                <r:MailingMethod>First Class</r:MailingMethod>
              </r:DiscreteParty>
            </r:DiscreteParties>
          </r:DocInstance>
Implementation Notes: This feature is available in the January release of Expere Document Services.