Release Notes - 6153.0


Release Notes for XDOC 6153.0

Overview 

This document provides an in-depth summary of enhancements that feature new functionality and general changes to improve on the existing functionality of your XDOC environment.  

Use the following release notes topics to review information related to this release to production. 

Note: Depending on the permissions granted in the system some of the changes described in this release notes might not be available. 

Enhancements and Improvements 

Axacore is pleased to announce several enhancements to your XDOC environment. 

AIVA Documents Integration

The XDOC for Loan and Servicing Documents is now integrated with the AIVA's intelligent document management solution. It is recommended to reach out to your AIVA Account Rep to obtain your unique AIVA Docs ID, URLs and Customer information. These configurations are setup on the Admin > System > AIVA Info > Settings. Additional AIVA Document configurations are setup on the Admin > Projects > AIVA Info > Settings (Settings, Document Types and Document Mapping Recognition).

Installation Note: It is recommended that a single Axacore OCR Service (Axacore.XDoc.Service.OCR.exe) be installed only once per XDoc installation. Multiple instances on the same installation are not supported and may cause errors.

Conditions Management API 

The conditions management API includes new options to add and/or update multiple conditions in XDOC eliminating the need for multiple sequential API calls on a single loan. 

New API Calls 

API Call 

Description 

Link to Documentation 

Condition.ADDXML 

Enables multiple conditions to be added to XDOC in a single API Call. 

Condition Add

Condition.UpdateXML 

Enables multiple existing conditions to be updated in XDOC in a single API Call. 

Condition Update

Create Loan API 

A new API call is available enabling containers/loans to be created in XDOC via an API call. This API call enables container creation in XDOC simultaneously with the creation of the loan in XDOC. 

API Call 

Description 

Link to Documentation 

Container.Create 

Enables a container/loan to be created in XDOC via an API call. 

Container Create

Azure Active Directory B2C Support 

XDOC supports a new Azure Active Directory B2C authentication method that leverages a customer identity access management solution for user sign in. Azure Active Directory B2C authentication provides integrators with various authentication tools including social media platform authentication options, multifactor authentication, and local account authentication. 

Login with Azure B2C 

A new dropdown, titled Logon Using, is available on the XDOC login page. When “Enable B2C User Authentication” is set to “Yes” an option for “Azure AD B2C Authorization” will be available for selection. If “Enable B2C User Authentication is set to “No”, then the field will be defaulted to “XDOC Authorization”. 

When Azure AD B2C Authorization is selected and a user hits “Logon”, they will be directed to the Azure B2C URL configured in the XDOC administrative setting. If users entered their XDOC username on the XDOC login page, it will be automatically defaulted in the email address field of the Azure AD B2C login page. Please note that Azure AD B2C authentication options will vary based on the individual Azure configuration.  

Bypassing XDOC login page 

XDOC offers configuration settings, located in Admin > System > System Security > User Authentication, to bypass the XDOC login page and redirects users automatically to the Azure AD B2C login page.  

Configuration 

New Azure Active Directory B2C configuration options are available in Admin > System > System Security > User Authentication. Please refer to the configuration settings here.  

Logging in with Azure AD B2C 

A new dropdown, titled "Logon Using” enables users to select if they are logging in via Azure AD B2C Authorization or XDOC Authentication. When the field Enable B2C User Authentication, located in Admin > System > System Security>User Authentication, is set to “Yes”, an option for Azure AD B2C authentication will be available in the dropdown menu. If Enable B2C User Authentication is set to “No”, the menu option will be limited to XDOC Authorization and users will be required to enter their username and password. 

Launching into XDOC from a third party application 

If you are currently launching into XDOC from a third party application using the UI launch service, the Azure AD B2C service will not be referenced during login. 

Maintenance updates 

Axacore strives to improve customer experience through regular maintenance updates focused on resolving unintended defects or product issues. The following maintenance items are addressed in this release. 

  1. Error received when copying between containers/loans in in XDOC is resolved. Users will be able to copy documents between containers/loans as designed.
  2. Errors experienced when splitting or merging a large document (1000+ pages) in XDOC are corrected.
  3. The CaptureDate handling when adding documents with DocumentAdd API has been corrected.
  4. Error when deleting a signature annotation file in Admin and Viwer has been corrected.
  5. Issue not being able to delete a condition field definition fron the UI has been corrected.
  6. The Save/Revert/Cancel options on the XDOC Viewer has been corrected. 
  7. Transparent GIF and PNG signature files printing with a black background has been corrected.
  8. When launching print client, the document type field is not blank has been corrected.
  9. The BaseException Error while uploading a documents on the Admin→Utils→Barcode Reader-Copy screen has been corrected.
  10. Corrected a typo on the Document Definitions for the HazardInsuranceAuthorizationandRequrements to HazardInsuranceAuthorizationandRequirements label.
  11. Corrected the update of the Bucket of a document definition automatically when a document definition is marked as Verified.
  12. Updated definition on which bucket Verified content shall be moved to automatically, without manual intervention.
  13. The Secondary sort order when primary is label ascending has been corrected.