Appraisal Scope Updates — Week 45

This week we released two updates which included the changes below. See the in-product snapshot here.

New Features

• When an appraisal form fee changes because an order’s details (loan type, property characteristics, etc…) change, and those new details cause the fee to update, you will now be prompted to accept the new fee or retain the current one.
• When an e-mail response to an order is rejected by Appraisal Scope because it doesn’t recognize the sender’s address as a party to that order, the original sender will now receive a message telling them this.  You may edit this template under your SETTINGS / EMAILS tab.
• Payment information is now visible to an appraiser in their accounting tab.
• CU score is now an available column to configure in the Revision Sent tab.

Integrations

• Appraisal Scope now uses the latest Bing mapping control from Microsoft to validate order addresses.
• The ability to set the rush order flag via our client API is now available to integrated partners.

Maintenance

• Management Fees once again calculate on invoices when they are configured.
• “File number” is now an available field in the appraiser and client scorecard report categories.
• “Borrower name” is now an available field in the appraisal payment history report category.
• The “Due” tab can now be sorted by the “Assigned to” column.
• When a document is e-mailed in response to an order notification, it is correctly attached to the order and marked as type “Other” again.
• Carriage returns in the “Additional Comments” field are now preserved when the field is edited.
• An issue was resolved that incorrectly showed some appraisers to be within 1 mile of the subject property when assigning, even though they were not.
• We optimized the performance of the Rule Profiles feature.