What’s New – Commercial Valuation^® R1.16.2

Introduction

The latest release of Commercial Valuation^® (CV) includes new functionality along with updates to current functionality. This document serves as a high-level guide to the changes that have been made as part of the Commercial Valuation 1.16.2 release.

New Functionality

Rebranding to Cotality

CoreLogic has officially rebranded as Cotality. This change represents our strategic progress in recent years and is intentionally designed to bring clients more value. As a result of this rebrand the Commercial Valuation User Interface has been updated with new logos and links that reflect Cotality rather than CoreLogic.

Updates to Existing Functionality

Several updates to existing Commercial Valuation functionality have been addressed in the Commercial Valuation R1.16.2 release.

User Interface Error when Restoring a Historical Iteration on a Locked Valuation

The Commercial Valuation User Interface would show an error message if a user tried to restore an historical iteration to be the current iteration if the valuation was locked. This has been addressed with version 1.16.2.

User Interface Error Shows on Manual Entry of Contents Data

The Commercial Valuation User Interface would show an error message if a user tried manually entered data in the Contents area of the Property Valuation Summary page and did not include the Note field. The error was non-specific to the actual error. A change has been made so that the user knows the Note field cannot be blank when entering Contents data.

User Interface Manage My Account Page

The Commercial Valuation User Interface Manage My Account page would prompt the user “Are you sure you want to leave this page? Changes will not be saved.” when no changes were made. This has been corrected to only prompt if there are unsaved changes on the page.

Web Methods not Creating Historical Iterations

In the past, there have been two (2) web methods (UpdateAddition & UpdateCustomAddition) that when called have not created historical iterations for the valuation record. This has been addressed with version 1.16.2.

Web Method Integration Guide Update

Currently the Web Services API Integration Guide states on page 98 that the ValuationReport object returned from the GetValuationReport web method will be returned as a byte array. This is incorrect. The API returns a base64 encoded string. The guide has been updated to reflect the correct field type.

 

If there is a specific reported defect or issue that you wish to understand or need more information, please contact your client services representative.