1.8.1.31.0016 New Features #

New Features

Released to Clients on 02/09/2017.

This release includes the following additions and modifications to functionality:

1.1 Comparables

  • Grid Display
    • Current settings only allow for up to three comparables to be shown per page when grids are printed. The multiple pages make it difficult to read the grids and to summarize the data with Taxpayers and ARB members. The ability to have multiple comparable properties on one page in landscape format would make it easier to display and read evidence.
    • The grid can now display the subject and up to five sales or equity comparables on one page. The font size is adjusted to make the columns fit the page.
      • The number of comparables to print per page is not configurable.
      • If there are less than 5 then the font size will adjust to display those on a single page. More than five will roll to another page.
    • A database setting is required for the modified version (if you want to use this new option contact Client Services).

R31-1.1

1.2 Images

  • Delete Multiple Images
    • Currently, there is no way to delete multiple images from PACS in one action. The ability to delete multiple images at once would help the CAD User when it is discovered that a property contains images that do not correspond to that property.
    • In this release, the image view is modified to display the existing ‘Tree View’ with an additional ‘Thumbnail’ tab.

R31-1.2a

  • The ‘Tree View’ retains all existing functions, multi-selection is not supported.
  • The ‘Thumbnail’ tab displays the available thumbnail size image for visual reference and also allows a User to select multiple images to Remove.
    • The image date, type, record and sub type display in full once the image is selected.
    • The ‘View User Right Photo Image’ and ‘View User Right Scanned Images’ control display of the new thumbnail view like the tree view
    • The thumbnail view is sorted by Image Date then grouped by image types like the tree view .
    • Since PACS now allows multiple file types to be stored as images, the thumbnail will indicate the file type. The ability to view Word, Excel and PDF remains through the separate file type viewer.

R31-1.2b

1.3 Income

  • General Income Valuation fields
    • When creating an income valuation in PACS, the year built should auto-populate into the Income Valuation based on the year built from the property. The User can change as necessary within the Income Valuation without affecting the property.
    • The following fields cannot be populated from the property:
      • NBHD/Econ – populates from Code File> Income Approach > Economic Area and so has no correlation to the Property Neighborhood Code file.
      • Income Property Type – populates from Code File> Income Approach > Property Type and so has no correlation to the Property Type Code file.
  • Reimbursed Expenses and GPI
    • Travis CAD uses the existing Income Schedule Secondary Income field for multiple purposes, one of them being reimbursed expenses.
    • Previously, when you applied the income schedule in PACS the default was to populate the secondary income below the vacancy and collection line in the income approach. The appraisal staff had to manually move the reimbursements above the line on every parcel. This leads to lost time and increases the chance of additional errors.
    • In this release, adding a new setting to separate the reimbursed expenses from secondary income will assist Travis in using the income schedules with less data entry errors.

OLD: NEW:

R31-1.3a R31-1.3b

  • During the upgrade, the existing single setting will be converted to the new separate settings, where if single is selected then both new separate settings are selected. Users can modify after receiving the release, as needed.
  • Prior year schedules should not be affected, unless the property is supplemented (as existing behavior with the system settings).
  • A new field on the Income Schedule is also added:

R31-1.3c

  • Direct Cap loaded schedule:

R31-1.3d2

  • Setting unchecked:

R31-1.3e2

1.4 Property

  • Condition Review
    • The current condition review process for remodeled property is manual and forces residential appraisers to create building permits 5 years out from the date the condition is changed to Average+ or higher. The intent is to review the condition assigned as a result of the remodel for current conditions every five years following the completed remodel.
      • This enhancement would allow for a process in PACS to reset the condition every certain number of years. The specific numbers of years and condition schedule will be configured by the client. The client will control which improvement details have the condition re-set by the Review process based on a new field on the detail dialog.

NOTE: Existing remodels will need to be maintained through the current work process (using building permits) or manually entered into PACS once the new function is available (changing condition in PACS to trigger the remodel year capture/override).

  • The NEW process requires:
    • Database setting (contact Client Services)
    • Assignment of the NEW User Right ‘Set Condition Review Order’
    • Utilization of Condition Codes
    • Setting Condition Review Order (Tools> Systems Settings> Set Condition Review Order) – when set, the process will subtract the Remodel/Change year from the system year and if it is equal to the max years, then it will match the detail’s condition to the set condition order and change it down one step at the max year interval (every 5 years in the example below) until it reaches the bottom of the list. If the detail’s condition is already at the bottom or not in the list then no action is taken.
  1. Maximum Years
  2. Conditions

R31-1.4a

  • A new improvement detail field is needed to store the ‘Year’ to which the current year should be compared for the Review process. This field will display on all details but will be effective only for improvements where ‘This is the base UP’ is selected.

R31-1.4b

  • Set the condition code = PACS will auto-populate the Remodel/Change Year with the current appraisal year, the User can override as needed:

R31-1.4c

  • To initiate the Review process, Activities> Condition Review

R31-1.4d

EXAMPLE

(Using set order above):

Remodel/Change Year = 2000

Condition set to = Excellent

Review Condition process in 2001-2004 = no change to condition

Review Condition process in 2005 = condition set to Good+ (one step down)

Review Condition process in 2006-2009 = no change to condition

Review Condition process in 2015 = condition set to Good (one step down)

Review Condition process in 2015-2019 = no change to condition

Review Condition process in 2020 = condition set to Average+ (one step down)

Review Condition process in 2021-2024 = no change to condition

Review Condition process in 2025 = condition set to Average (one step down)

Residential Property Summary

  • The residential property summary (RPS) is currently an excel spreadsheet that lists all of the characteristics of a particular property for the current tax year for easy viewing during an informal or formal hearing. The RPS will also display the prior tax year’s characteristics so the appraiser can easily determine if there was any year over year changes.
    • The RPS is an extremely helpful time saving tool for appraisers during the appeals season. A few examples of what appraisers look for during an informal or formal hearing include changes in land value, changes in condition and class due to a remodel, or changes in the percent complete due to new construction.
    • If there were no changes from the prior tax year in land value, class, condition, effective year of construction, or physical, functional, or economic obsolescence, the RPS will tell the appraiser the last year a change was made to one of these characteristics.
    • In order to integrate the Summary into PACS, the custom client queries are used. It is possible for a client to update the ‘functions’ called to display certain data but if not, then the fields will be blank for those fields where values are not retrievable. Example: Improvement grade – acquired via a function that Travis wrote. That functions looks at specific imprv / imprv detail type codes and a specific improvement attribute code that brings back the improvement grade. If those values are left coded into the function then fields referencing improvement grade will come back null. There also exists the slight chance that a client has their code-file defined in a way that the function brings back a value but that value is not anything to do with improvement grade.
  • With this change, the Property menu has also been redesigned for a more compact display:

R31-1.4e

  • Open Previous Year
  • Display [also see b]
    • Next Property
    • Previous Property
    • Residential Property Summary (NEW)
  • Supplement
    • Add Property to Supplement
    • Move Property to Supplement
    • Remove Property from Supplement
  • Copy Property
    • Copy Property Information to Another Year
    • Copy Property to Future Year
  • Delete Property
  • Recover Property
  • Split Property
  • UDI
    • Create Property Group
    • Associate a Non-UDI Property with the Current Property
    • Remove UDI status from the Current Property
    • Remove Child From Parent
    • Restore Deleted Child to Parent
    • Suspend Child From Parent
    • Restore Suspended Child to Parent
  • Change Log
    • Open Change Log
    • Open Change Log History
  • Comparables
    • Sales Default Grid
    • Equity Default Grid
    • Manage Comparables
    • Print Grids
  • Recalculate with Trace
  • List related Land DCF Analyses
  • ARB Submission
    • Capture Values
    • Undo Capture
  • Online Applications
  • Print
    • Appraisal Card
    • Calculation Worksheet
    • Sales Ratio Report
    • Comparable Grids
    • Property Letters
    • Labels
    • Property Applications
    • Value Certification Notice
    • Tax Ceiling Certificate
    • Transfer Certificate
      • DVHSS
      • DVCHS
      • MASS

The new option under the Property menu will launch a read-only Summary grid. The grid can then be printed or exported to excel.

  • Columns of main report:
    • Property ID
    • Current Uncertified Year
    • Prior Year
    • % Change – calculate for fields in RED below
    • Last Year Changed – calculate for fields with [*]
  • Rows
    • Land Value *
    • Improvement Value
    • Market Value
    • Ag Use Value
    • Appraised Value
    • HS Cap
    • Assessed Value
    • Appraisal Method
    • Exemptions
    • NBHD Code
    • NBHD Imp Market Adj
    • NBHD Profile Analysis
      • Sample Size
      • Population
      • Sample Size Percentage
      • Beginning Profile Median
      • Ending Profile Median
  • Land Sqft
  • Land Adjs (adjustments)
  • Number of Imps
  • Living Area
    • Sub-report grid needed ‘Area Range’
    • Rows:
      • 75% of subject current year living area
      • 1.25% of subject current year living area
    • Class *
    • CDU * – condition code
    • AYOC – actual year of construction
    • EYOC * – effective year of construction
    • Percent Complete
    • Physical Percent *
    • Functional Percent *
    • Economic Percent *
    • Columns of sub-report grid ’Recent Sales’
      • Date (sale_date)
      • Sale Type
      • Sale Price

R31-1.4f

1.5 New Year Layer

  • Previously, the New Year creation was not retaining the following Comparable Property Configurations. These will now be copied up in NYL creation:
    • Use Adj Sales Instead of Actual
    • Use Neighborhood Adj
    • Ma Adj to comp
    • Include Confidential Sales

R31-1.5

1.6 Sales

  • Sale Ratio on Residential Sales Grid
    • When in the process of informal & formal hearings, it would be very beneficial to have the sales ratios of the comparables to automatically populate on the Residential Sales grids. This would increase the efficiency of a hearing, also allowing for shorter hearings.
    • The grid formula will match the Sale Ratio report calculation (total market value of all properties on a sale/adjusted sale price).

R31-1.6

1.7 Mass Update

  • The framework supporting Mass Update has been modified in order to allow fields to be added without requiring a full PACS release build.
    • This should allow for quicker turnaround on co-dev requests to add fields.
    • As part of this project, the field sub-market was added to Mass Update.

2.8.1.31.0023 Release Notes (Limited) #

HelpStar ID Description of Update

167475

BETA-TCAD Notice, not printing some of the Appraisal Notice Configuration and also Notice of Protest not printing the “TDD”. Field too short. This was corrected, increased character limit and reduced font size.

167486

PACS Collections is crashing. One of the new variables in the modified Property menu was not being initialized causing memory issues. This was corrected.

167536

Mass Maintenance randomly crashes since upgrade. Corrected.

167513

Image copy function inactive after 8.1.31.16 upgrade. This has been corrected.

167045

Recalculating all values with the M&S props and receiving error. This has been corrected.

166410

Upgrade to MVP; receive error when attempting Mass Recalu all properties including M&S; this was corrected

167591

Comp grids; still only printing 3 comps per page. This was corrected.

167615

167485

Mass Maintenance quick entry is not functioning, kicked out of PACS when entering information. This issue has been corrected.

Help Guide Powered by Documentor
Suggest Edit
%d bloggers like this: