In this release, an additional column is added to the appraisal export layout that contains the actual assessed value. This column can be referenced as needed without altering the existing format and calculation in the export.
Existing column modified description:
New column description:
This change should be published to any third party vendors who utilize the Appraisal Data Export. The updated layout file will be provided as soon as available.
1.2 Comparable Search
Deleted Properties option
Client request to be able to use or change the comparable system setting ‘Include deleted properties’ for each comparable search
Add the option to change the comparable system setting ‘Include deleted properties’ from comparables for each search. For:
The system setting should be used as the default. The user can change when performing the comparable search.
The user selection in a search will not replace or be saved as the system default.
NOTE: Equity grids DO NOT use include deleted properties.
Comp Grid Adjustments for Flat Valued Improvements
We are running a comp grid for a property which has a $7,500 flat valued pool. When comparing this property to a sold property, the comp grid is adjusting the comparable property $15,900 for the pool. It appears the comp grid is adjusting the flat value of $7,500 by the Neighborhood factor of 212%.
There are multiple settings affecting the grid calculations. The setting in Tools->System Settings->Set System Display Options titled ‘Apply Mass Adjustment Factor to Flat Valued Improvements’ was not taken into account on the grids. The grid was calculating the value of the imprv detail * the adjustment * the mass adjustment (given that certain settings are in place).
If an improvement is set to Flat value then->
If the System setting is set (Apply Mass Adjustments to flat valued improvements) then the comp grid adjustment will be the value of the improvement detail times the mass adjustment.
If the setting is off then the value will be the value of the improvement detail.
If the improvement is not flat valued, then the comp adjustment will be the value of the detail * the detail adjustment. The product of that will have any amount adjustment added to it proportionally, and the sum of that will be multiplied times the mass adjustment.
The value of the detail is divided by the Calculated Improvement value. This will provide a % of the detail to the improvement as a whole (Total Detail Value on the improvement screen). Then that % is applied to the amount adjustment and added to the value.
The intent is to have the comp grid calculation line up with the value in PACS. Based on how PACS calculates and the multiple settings allowed, it is possible that the ending comp grid adjustment does not match PACS at the improvement level. We advise that flat valued improvements have their flat value match the sum of the imprv detail values.
This only applies to Residential grids. Commercial grids do not have corresponding adjustments.
Delete Multiple Images
The function to delete multiple images has been re-worked due to the reports of performance issues.
A new separate dialog is implemented for deleting multiple images. This dialog is available from the Images tab for the following:
The dialog is launched from a new button ‘Remove Multiple Images’
Selection of multiple images is allowed
The User will be prompted to confirm before deletion is successful. The dialog remains open until closed by the User.
Mobile System Identifier
The PACS system needs to identify whether the client is PACS Mobile client or not.
This will be used in the New Year layer process to determine if additional warning should be displayed to the user [below].
The indicator will also be used for the assignment group functionality described below.
New Year Layer Warning
Mobile processes prior to New Year layer creation still involve manual coordination with support, dev and DCS. At this point the process cannot be automated but a warning for Mobile clients only will help prevent errors or process issues.
When the User selects to Create the New Year Layer, a dialog will display for Mobile clients ONLY:
Assignment Group Maintenance
This incorporates the function from Mobile Manager, to create and associate mobile assignment groups, into PACS. There are no new functions or selections related to this project.
NOTE: The separate Mobile Manager website will still be available and will allow processing. The intent is to transition away from the separate site but there is currently no ETA .
For the mobile device, there is a configuration to prevent additional properties from being added to the mobile workflow. This is most likely not a concern for production environments but is included for reference purposes .
For associating assignment groups in PACS, the process needs to recognize this setting.
A ‘new property’ for the mobile device means the property ID does not exist in ccProperty.
When a user attempts to select an assignment group code for a property which does not exist in ccProperty, check whether:
If “N”, notify and prevent user from assigning the code.
Warning message displays
User is expected to wait until PACS Mobile is ready or adjust the setting before editing the group.
If “Y”, allow user to set the assignment group code.
Assignment Group will be stored as a NEW code file:
Tools>Code File Maintenance> General> Mobile Assignment Groups…
Code – up to 10 characters (existing field is 10, varchar)
Description – up to 100 variable characters(existing field is 50, varchar)
Inactive flag – to control display in the drop down
Delete – verify on delete if code is assigned. Do not allow delete if the code is in use.
Existing codes (from mobile_assignment_group) should be incorporated in new code file UI when the release is deployed. These codes should display and be available to assign to properties as if the codes had been created through the UI. As a default, the codes will be active rather than ‘inactive’.
A NEW User Right will allow a user to maintain (add, change, remove) the Mobile Assignment Group for a property. [Edit Mobile Assignment Group ]
A NEW User Right will allow a user to manage the Mobile Application Code File, add, delete, edit consistent with PACS code file structure. [Codefile Maint: Mobile Assignment Groups ]
A new PACS UI field is added to track mobile device property assignment:
The association between a property and an assignment group code is currently stored in the table “ccProperty” (PACS database). After the changes in this document are made to PACS, the existing associations should display in the new UI field as if the selection had been made through the UI.
New UI field is enabled ONLY IF:
PACS Mobile flag is set to True
Property is in uncertified year layer (PACS Mobile only handles property in uncertified year layer with sup_num = 0)
NEW User right indicated below is assigned
On certain property types:
Currently, only Real, Mobile Home and UDI Parent properties are accessible through the Mobile device
Hide new assignment group field for properties not accessible by mobile: Personal, Mineral, Auto
At the property level Prop Codes tab under the Group Codes paragraph
With the label ‘Mobile Assignment Group’
To populate as a drop down selection from NEW code file
Where CANNOT be Null or blank
The field may be blank for properties not in ccproperty, i.e. new properties
Selection drop down will not allow a blank
Where only one assignment group can be selected per property
The new field will be added as a search criterion on Property Search Secondary tab and as a column in the results.
A NEW process is implemented to allow association of assignment group codes for multiple properties.
Activities> Mass Maintenance> Mobile Assignment Groups…
The user will be able to search for properties with the following criteria:
Mobile Assignment Group – existing code assigned
Abstract/Subdivision – multiple selection
Neighborhood – multiple selection
Region – multiple selection
Map ID – multiple selection
Group Code – multiple selection
Entities – multiple selection
Subset – multiple selection
Use Code – multiple selection
State Code – multiple selection
The user will be able to search by a list of property ID’s. The selection will accept a carriage return list of IDs .
The user will be able to select by SQL Query . This option should be used to find any property not having an assignment group, similar to the Mobile Manager process to ‘Detect New Properties’.
The user will select to Update/Insert an assignment group from the properties meeting search criteria.
The user will see a count of records before modifying the assignment group
PACS Processes impacted:
New Year Layer – currently this is a manual process run by support for each client. The manual steps will be retained as coordination with DCS is needed.
Future Year Layer – the current design of ccproperty supports only a single row for property. The future year will not be affected by assignment groups associated in PACS, i.e. groups will not copy to the Future Year.
Split – retain assignment code in a property split, copy to new properties created
Merge – retain assignment code in a property merge, where the selection to merge to is used. The ‘merge to’ property assignment group will be retained. When a new property is created from a merge, the assignment group from the base property will be retained. [The Prop Codes tab is retained currently for a Merge, so this will be consistent.]
Copy Property to another Year – the current design of ccproperty supports only a single row for property. The copy to year will not be affected by assignment groups associated in PACS, i.e. groups will not copy to another Year.
Mass Create – retain assignment code for original property and copy to created properties when property is used to mass create properties
Create Property – The New Property wizard will not be modified for the new assignment group field(s). The user will be expected to update the assignment group after property creation.
Delete Property – When a property is deleted (inactivated) via PACS, the property will be removed from ccProperty table.
For UDI properties:
The current design of ccproperty supports only UDI parent properties. Assignment Group maintenance will not be possible for UDI child properties .
When a UDI property is suspended, it effectively becomes its own property. The assignment group should be editable in this case.
1.5 Online Appeals – Scheduling
Online Scheduling Configuration
When implemented, it was determined that Online Scheduling would need to directly access the PACS database. We have since learned that this may put our clients at risk for SQL License violations.
In order to mitigate that risk, we have disabled the “Enable Online Scheduling” checkbox on the Website Configuration dialog in PACS Appraisal.
The checkbox will still be displayed, indicating whether or not Online Scheduling is enabled, but the client user will not be able to change that checkbox.
Clients wishing to use Online Scheduling should contact Harris Govern in order to enable the Online Scheduling capability. This will allow us to verify that the client has adequate SQL Server licensing prior to turning on the functionality.
Plat Map Image Type Available
Client request to use PDF files for the abstract / subdivision plat maps linked to the “View Plat Map” aka face map on real property.
Since some image types are not supported through the existing PACS image viewer, we will be launching the native file type viewer available.
File types have been expanded to include JPEG, PDF, TXT, PNG, XLSX, DOCX:
PID 15742, ref_id1: 001000-0007-11-00
If multiple images exist for a reference ID, an image viewer will open for the user to select the image to view .
Upload Protest File Layout modified for New Reason
The Comptroller’s office modified the ARB protest reasons which we need to handle with the new option to upload protests by excel.
Modify reason one text to ‘Incorrect appraised (market) value’
For the new Notice of Protest reason code –
‘Incorrect appraised or market value of land under special appraisal for ag-use, open-space or other special appraisal.’
Add this as the last reason code before ‘Evidence Requested’ column
Evidence Display by Protester Type
PACS will no longer limit the evidence in that window to evidence submitted by the current protester, it will show all evidence tied to this protest.
There is also a new column that will show the protester type code (“OW” for owner, “AG” for agent etc…). The new column will need to be added to the grid display after receiving the release.
This column will only populate for newly created evidence after the upgrade. The data is not available for existing evidence on a protest
Configurable Warning for Import Characteristics
There are several situations that will affect the user expected calculations with regard to profiles, etc. If the sale information was captured in previous years and subsequent schedule or matrix changes have occurred for the current year, the data will not produce the expected result because the sale information is tied to previous year’s data. This is also true with depreciation if an improvement has not reached a point at which it no longer depreciates. The indicated NBHD adj would be a couple of points off potentially.
After changes in R28, client request is display a NEW configurable warning in the UI which directs the user to import ‘current appraisal data’ if they uncheck the ‘Characteristics of Involved property at the time of this sale reflect current property characteristics’ box.
Please contact client services if your office would like this message TO DISPLAY.
Business Practice offered as a guideline:
Go to the ‘Sale Information’ tab in the appropriate sale record and uncheck the ‘Characteristics of Involved property at the time of this sale reflect current property characteristics’ box. (New PACS warning box should appear)
Go to ‘Sale Improvement’ tab and click the ‘Import’ button.
Choose the ‘Current Appraisal Data’ button and check the ‘Import land and improvement Segments’ checkbox. Click OK.
Modify the improvement or land characteristics to account for how the property looked at the time of sale. (For example, if the property currently includes a $50,000 pool but sold before the pool was added, remove the pool from the ‘sale improvement’ tab.) It is always best practice to recalculate the sale record after making any modifications to the sale data.
Export-Appraisal Info-AG Values. Instead of the assessed value=to the market value on properties with ag, in PACS the assessed value shows to be in the productivity value. This was corrected; new column added- ‘assessed_val’ at the end of the export file Appraisal_info file
8.0 Enhancement – (The appraiser table is not being updated with the user_id from the pacs_user table, this results in the new Appraiser unable to log into iPad. There should be an option to associate appraiser_id with the corresponding pacs_user_id)
MAP audit issue-PACS SqFt Matrix segment issue on appraisal cards; not printing. This issue resolved by updating appraisal card to handle land method SQMTX. This will now produce square feet as the value.
When a parcel layer is pulled up in GIS 2.0 and then select a parcel; the info button will not display the information.
PTD EARS: LIH needs to be reported as XA.
BETA-R32-Efile Form Customization Issue, coding error; a release build was dropped on one of the PC’s in Bexar’s training environment to verify that the fix resolved the problem
2017 Roll History does not match 2017 Value, occurs when accounts are done on a UDI Split. This issue has been fixed.
When copying property to Future Year Layer, the entities are not being copied, too. Issue fixed.
GIS view (view property button) grayed out. An issue where the modal check on the viewer was incorrect. This has been fixed.
PACS GIS Advanced NBHD search errors; PID 425110 causing issue. Fixed a null reference exception where incorrect GIS data is encountered for a service layer.
Online Appeals-cannot save a customized email. This has been fixed.
Errors-Mass Updated then recalculated all props and all are showing errors. Issue corrected.
Evidence is gone; when evidence was created and published then add an Agent to the account. and then the agent was made the Primary Protester, the Evidence in PACS is gone. Issue corrected, all evidence tied to the protest will show.
Import agent protests, UDI Parent accounts; user unable to import spreadsheet containing UDI parent accounts. This has been resolved. Now able to import UDI parent accounts using import agent protest process.
Copy to Excel from lawsuit list not working properly. Issue fixed in copy to Excel functionality; columns and row widths verified.
Comp Grid adjusting the comparable property for this pool (flat value) to Neighborhood adjusted. Residential comp grid-calculate for improvement detail adjustments modify
Mineral import entity prop percentage issue. Resolved. Modified Mineral Import Merge step to create rows on pers_prop_entity_assoc for any Personal properties that have an entity_prop_prop_pct of less than 100%
Need help to import supplement 10.
Ready to do mineral import. Configuration needed to correctly create geo_id in the mineral import process. Substring (account_number, 2,11) not currently available. This has been resolved.
MH Listing report issue
Appeals staging job hangs, will not start manually
ALCOA values, total of the market value does not match the total at the bottom of the screen
Image rec type change not changed in associated prop
BPP Field card printing issue
Homestead IA mismatch on Total Due shown in system
Mineral Supplement-if there is a ‘S’ type bill and the due date has been shifted, it is not calculating correctly. Resolved, functioning as expected.
Improvement New Value Complete not calculating correctly. This has been resolved. User can select the Imprv Detail radio button to drive off the % complete.
Income Values Distributed not used with Special Exemptions. This issue has been fixed
Sales submission will not complete due to bad data in the database, arithmetic overflow converting numeric to data type variable character.
BETA R33-Fields missing on Prop Codes tab. Fixed.
BETA R33-Mobile Assignment Group-Mass Update enhancement, list of “Available Assignment Groups” is not a current list. Possible that the live database and not the test database was updated. Either a fresh backup or clean out the old groups in this database will resolve issue.
Request BETA R33- Mobile Assignment Groups-Mass Update (2017/2018 issue)- Unable to test new Mobile Assignment Groups-Mass Update enhancement. Resolved; ran the NYL process which updated the ccProperty data to 2018.
BETA R33-New search by Assignment Group enhancement, search time is slow for displaying the results. Issue resolved; an index was added to the mobile_assignment_group_id column in ccProperty to increase search time.
PACS.Online Client, LaSalle TAX, the 2017 Certified Appraisal Data Import is failing with the following error: Bulk load data conversion error (type mismatch or invalid character for the specified codepage) for row 94, column 106 (solar_exemption_amount). P&A changed their layout; a patch was created through HS 171423. Patch applied, import still failing. Resolved; agent format file adjusted; file import successful.
BETA 126.96.36.199-ARB CAD Evidence Protester Type
BETA R33-GIS view property option
BETA R33- Include Deleted Properties issue-results do not display. Issue has been resolved.
PACS does not support TLS 1.2 in PACS GIS 2.0. Clients should be able to access this data so they can pull flood and census data directly and use within PACS when configured in a service layer. Many of these sites are from the Federal Government. All Federal websites are required to use HTTPS. This form of transport layer appears to be what FEMA is using. Development corrected this issue.
Receive an error on the file when importing a Pritchard and Abbott certified mineral information using the supplement. This has been corrected.
Unable to do a mass recalculation for Marshall & Swift in the 2018 year, the option is grayed out. This has been fixed, the Marshall & Swift option has been enabled.
When attempting to import an ownership import, receive an error “Import file is not a supported version. Support version: 188.8.131.52”. The version string needed updating. Issue resolved by Development.