9.0.35 Release Notes

ID

Description of Update

23133/
HS 120757

Users could not print inquiry and protest letters for a specific year by Case ID because the Year drop-down list menu had been removed (in BOE role, choose Activities > BOE > Individual Letter, choose Case IDs method, set Mailing Date and Print). When printing, the system was automatically assuming the current assessment year (2013-2014), but the protests were typically recorded for previous years and Case IDs are reset each year, causing problems for users. The Year menu option had been removed to make the Print BOE Letters dialog box consistent with other letter printing dialogs. This option has now been restored. Also, any letter printing dialog which had the Year menu option prior to release 9.0.35.2000 now has it again, including the dialog for printing property letters.

23023/
HS 119953

Penalty and interest on delinquent taxes did not calculate using the expected posting date until you changed the posting date with the property record open (Penalty and Interest values are displayed in the Tax Due panel; change the posting date by double-clicking the time/date stamp displayed at the bottom right of the PACS application window). The system was basing calculations on today’s date rather than the payment cart’s posting date. The calculation has been modified to calculate P&I using the posting date set in the payment cart, resolving the issue.

23013/
HS 119946

The payout agreement statement included payout agreements in defaulted status (Activities > Payout Agreements > Generate Special Assessment Payout Statement). At the time this issue was recorded, the stored procedure allowed inactive and defaulted payout agreements to be included in the printed statement. Moreover, a single statement could include the same property more than once. The stored procedure has been slightly modified to prevent these unexpected results.

23007/
HS 119922

When issuing refunds, the taxpayer account for bills was the bill.owner_id and the taxpayer account for fees was the fee.owner_id (open a property, expand the Tax Due panel; in the Statement Amounts section, select an item and click Refund). Property overpayment credits were issued to [owner.owner_id] for the property, and account overpayment credits were issued to [overpayment_credit.acct_id]. This was not what was expected. So, now refunds are issued to the property collections owner [property.col_owner_id] instead (except for refundable items with no associated property). Account overpayment credits continue to use their account ID, and non-property fees will use fee.owner_id.

23037/
HS 120017

An unexpected error occurred when trying to print the Outstanding Balances Report (Reports > Outstanding Balance Report). A syntax error in the report’s SQL query has been corrected, resolving this issue.

ID

Description of Update

23000/
HS 119852

While updating a commercial property using Marshall & Swift, value from Additions on Improvements did not calculate as expected (from Property view, expand Improvements panel, open M&S Improvement Detail (the Marshall & Swift option is selected in the Values section of the dialog box), add an entry with units and unit cost to the Additions grid in the Marshall & Swift Commercial Details Dialog box, click Recalculate). Changes to the Marshall & Swift engine prevented communication with PACS regarding Additions. Setting the fields AdditionCostSpecified and QuantitySpecified to True has resolved this issue.

ID

Description of Update

22984/
HS 119717

The This is the base UP option was automatically deselected on Main Area Improvements after recalculating, causing all other Improvements on the property to have zero value (from Property view, open Improvements panel and click Details on MA Improvement and note This is the base UP option selected in General section; reopen the dialog, change the Class/Sub option, save and then recalculate). This issue, which existed in releases prior to 9.0.35.2000, has been resolved.

ID

Description of Update

22841

Attempting to close out a revenue account that had a long account description caused an unexpected error (Activities > Accounting > Close Out Revenue Accounts). Descriptions longer than 100 characters are now truncated, resolving the issue. (This was discovered during beta testing but was an existing issue.)

21225/
HS 108867

When adjustment credits were applied to bills, credit amounts unexpectedly included amount for delinquent P&I (on a property with a paid up prior-year statement, supplement the property in that year, lower the property’s value, accept the supplement and create and activate bills, applying the newly-created credit to the remaining bills due on the statement). The coded calculations for delinquent penalty, delinquent interest, and bond interest on adjustment credit bills and fees has been modified to correct the issue.

Concerning adjustment credits, delinquent P&I applies when a taxpayer pays toward the base due and delinquent P&I, but adjustments have eliminated or reduced the delinquent amount. In this instance, some or all of the delinquent P&I is refunded to the taxpayer with the base amount.

22760

The change log now records when and who made changes to the chg_log_columns table (Tools > Change Log > Administration). This data can be viewed in the database. (Tracking this data cannot be turned on/off through the user interface.)

20595*

The Property Type drop-down list in the Property Sub Type code file dialog box now displays the Mobile Home type as Real/Mobile Home (in PACS.ADMIN, choose Tools > Code File Maintenance > Property). Also, Sub Type code files with the Real / Mobile Home Property Type selection are now available when editing MH type property records (the Property Sub-Type option on the record can be found on the Identification panel).

22434/
HS 116137

The design and function of the code chooser used for adding and removing property group codes to properties has been modified (click Add in the Property Group Codes section of the Property Codes panel of the Property view). Previously, using the code chooser to change codes resulted in the removal of any codes previously assigned to the property; users can now choose to add codes by selecting the List selection appends items option in the Property Group Codes Selection dialog box/code chooser.

22494/
HS 116726

The user had to assign a letter type when creating Inquiry Status and BOE Inquiry Additional Status code files (Tools > Code File Maintenance > BOE Maintenance). Doing so is no longer required.

21239/
HS 111539

The Residential Time Adj PCT/MO, Commercial Time Adj PCT/MO, and Land Time Adj PCT/MO fields now accommodate up to four decimal places. These fields are displayed in the Miscellaneous section of System Wide Configuration in PACS.ADMIN (Tools > Comparable Property > System Wide Configuration).

11753

The following functionality has been added to PACS Current Use module:

• Current Use Code files now include the attribute option Public Benefit Rating System. (Tools > Code File Maintenance > Current Use)
• The Land Detail dialog now includes the Public Benefit Rating System % field in the Productivity Valuation panel. This field is set to 100% by default, and is enabled for land details that have a Current Use Code file with the Public Benefit Rating System attribute selected in the Use Code field

When a Land Detail is assigned a Current Use Code file with the Public Benefit Rating System attribute selected,

• In the Land Detail dialog box’s Productivity Valuation panel, the Calculated Value option is selected and its value = [Market Value * PBRS Percent]
• The user can modify the Public Benefit Rating System %, which causes the Calculated Value to change
• The Appraisal Method field, Table field, Unit Price field and Show Schedule button are all disabled

Note The Change Log records the code selection, and the PBRS % value is copied to new year layers.

22125/
HS 115392

An unexpected error occurred when modifying an event object (in property Events panel, select event and click Details, click Open in Event Objects panel). The system now handles instances when no date is entered, resolving the issue.

20999/
HS 109725

After a change to the dialog box type, the Permit # field in the Permit Information section of the Remodel Information Detail Dialog box now accommodates both numeric and letter entries (from the Property view, expand the Values panel and click Remodels).

21376

Opening an existing total exemption detail through the Property view Tax Area, Exemptions & Special Assessments panel and then cancelling out of the detail dialog resulted in the user being prompted to save, though no actual changes had been made. This occurred because PACS tried to write a default income record (which only senior/disabled exemptions should have), leaving an indicator that a change had been made. (This did not cause any data errors.) The exemption Income Information grid in the Property Exemption Details dialog box no longer attempts to write a default record unless the grid is displayed, as is the case for senior/disabled exemptions.

19580/
HS 103940

After deselecting Exact Match in the User Settings dialog box, the option was automatically selected again on reopening the dialog box (Settings > User Settings). The controls for the menu options in this dialog have been modified, correcting the issue.

22346/
HS 115033, 22302/
HS 116214

The GISUpdatePACSImage stored procedure, which adds images to properties, did not include imprv_id as expected. This stored procedure did not call the Middle Tier. Now it has been modified to look and work as expected. Also, an inconsistency in how images are stored has been reconciled. Additionally, Ref IDs are now set to 0 as follows: (a) for Property-level Images, Ref ID# is 1, 2 and 3; (b) for Improvement-level Images, Ref ID# is 2 and 3 (Ref ID 1 is used for the Improvement ID).

22666/
HS 117607

Scripts that run during PACS’s installation have been updated to ensure nothing is missing.

16749/
HS 93505

Users can now redo a REET export (Export > Export REET Recorded Information). After initially performing an export for a given date and being notified of errors, the user can rerun the export for the same date after correcting the errors. Attempting to do so causes a confirmation message to display, asking if the user would like to redo the export.

21998/
HS 114263

An unexpected error was produced while performing the NCOA Import (Imports > NCOA). The error was the result of the system being unprepared for parts of the import file’s formatting and content. The fix required a few changes: the import process now (1) discards lines that do not have a numeric owner ID or year, such as the header row, (2) handles instances where the address is an exception instead of a real address (exceptions are still listed in the import), and (3) discards records with duplicate owner IDs. These fixes resolve the issue.

22208/
HS 115705

Importing a payment file caused an unexpected error (Import > Import Payment Run). The import file included at least two property IDs that were recorded as the number 0, which is invalid. The database to which this data was being imported had bad data issues as well, which affected the import performance. As a resolution, the system’s payment import code has been modified to prevent issues like this by rejecting the import with an error message when they contain zero or negative number statement IDs. Additionally, the system displays a specific error message when a user attempts to import and process an unassociated fee.

22636/
HS 117535

Income information displayed in the Income Information grid of the Land Segment detail whether or not the Include option was selected on the same Land Detail displayed in the Land Details grid of the Improvement & Land Designations panel of the Income Detail view (open the Income Detail view by choosing the Details button of an Income Valuation record in the Property view Income Valuations & Characteristics panel). This issue has been resolved by fixing the way Land Details are filtered for display.

22807/
HS 118235

Adding a Land segment from a different PID to an income valuation generated an unexpected exception error (from Property view, expand Income Valuations and Characteristics panel, go to Improvement and Land Designations panel, click Add in the Land Details grid). The grid toolstrip has been fixed, correcting the issue.

21360/
HS 109266

Property-type letter details such as the letter’s Name and Description could not be edited when Enable Event was selected (create new letter from Word Letter Processing Maintenance menu). The details dialog is now enabled as expected regardless of event status.

21006/
HS 110900

During Levy Certification, as evident from the Levy Calculation Summary Report, New Construction Values were excluded for properties that were involved in an active Tax Area annexation in the current year (Activities > Levy > Levy Certification, select a levy certification run and click Details, then expand the Tax District Summary panel; from there, select a levy or levies in the grid and click Print). This issue has been corrected.

22899/
HS 119111

An unexpected error occurred when removing a property from a litigation record (from the Litigation view Properties panel, Properties grid). This error was not reproduced internally. However, a related error that occurred while using the arrow key to navigate through properties in this grid was discovered and corrected.

21307/
HS 111674

The default Base Date for commercial M&S is 01/01 in the property’s year. A validation error displayed unexpectedly when the current date (according to the system clock–not the PACS posting date) was earlier than the default base date. Now, when this occurs, the default base date is set to the current posting date.

22901

Various issues tied to Marshall & Swift have been resolved. Development made changes allowing support for the .NET framework 4.0 with the Marshall & Swift engine, and they addressed a number of other conflicts.

22537/
HS 117157

When mass updating Land new construction values, PACS did not retain the value because the New Construction Value Override was not being automatically selected in the process (Activities > Mass Maintenance (Property) > Mass Maintenance > Mass Update). This issue has been corrected.

22446

The appraiser name displayed on personal and master lease account property appraisal notices is now the name of the Review Appraiser listed on the Personal Property panel instead of the Last Appraiser from the Appraiser Info panel. This is partially a change from functionality in 9.0.34.2109 (and prior).

22756

The Filing Status was not retained on Appraisal Notice runs (Activities > Appraisal Notices > Appraisal Notices Maintenance, perform the notice selection process with a Filing Status selection, then close out and return to Appraisal Notice Maintenance and view details of same run). This issue has been resolved.

22848/
HS 118535

An unexpected error was generated after entering an invalid property ID in the quick post dialog boxes, receiving an invalid ID warning, and then entering a valid Property ID (Activities > Posting > Quick Post: Single Payment). An issue with the search text box retaining info incorrectly has been resolved.

22110/
HS 111804

An unexpected error occurred when generating payout statements because defaulted agreements were included, causing the system to count properties twice when collecting data for the statement (Activities > Payout Agreements > Generate Special Assessment Payout Statement). Payout agreement statement runs now include only Active payout agreements.

21540*

Existing depreciation schedules were not available for selection in the New Property Wizard (import schedule in PACS.ADMIN through Tools > Schedule Maintenance > Depreciation Schedule Maintenance; File > New > Property, select Personal property type, navigate through the Wizard and then, after adding sub-segments, click Depreciation). The issue preventing schedules from populating the grid has been resolved.

21324*

An Asset ID column now displays in the Sub Segments grid in the Personal Property panel of the Property view, and on the Sub Segments panel in the Segment Detail dialog.

21308/
HS 111831

Non-mailing address types did not display in the Property Search Results list because the system sought main addresses only. Now the mailing address is sought out first, and any secondary address is displayed when no mailing address can be identified. Note that the property search results display the collections owner’s address when performed by a user in the Treasurer role, and the property owner’s address when performed in the Assessor role.

22704

Using the Recheck Date option in the Property Search view Other Search Criteria extended panel did not return the expected results. Though it had not been previously, this field criterion is now included in the query.

20965/
HS 110858

Overpayment credit receipts did not display the account to which the payment was posted (from Property view, expand Payment History panel, select refund payment and click Details, then click Reprint Receipt in the Refund Detail dialog box). This issue has been corrected.

21436/
HS 112338

When Require Ref. Number for Check or MO Tendered was set to False in PACS.ADMIN System Configuration, not all expected checks displayed on receipts (Tools > System Configuration > Post Payment > Require Ref. Number for Check or MO Tendered). Without the reference number, the query that gathers receipts pared down results by ignoring results with identical values. This query has been modified to include all checks.

19814/
HS 105267

Entering a future Date of Sale (later than the current date) is now permitted when creating a new REET record (File > New > REET). When doing so, a warning is displayed. Note that entering a future date of sale can potentially cause issues with the REET export (Export > Export REET Recorded Information).

21178/
HS 110398

The Electronic REET Import failed because the process was not correctly assigning the REET IDs from the import file (Activities > REET > Electronic REET Processing). This issue has been resolved.

22106/
HS 115327

The REET import via Electronic REET Processing failed unexpectedly (Activities > REET > Electronic REET Processing, choose Import File). Part of the issue was that the import brought a decimal value to a field the system had formatted for integers; also, the import file included a date foreign to SQL. The system field is now prepared for decimal values; and a graceful error will be issued when an incoming year value is unreadable (i.e., prior to 1900). In case of the second event, import files must be corrected before processing successfully.

21658*

When moving from the Payout Agreement Wizard to the Payment Cart, the payoff amount displayed in the cart was incorrect (Activities > Payout Agreements > New Payout Agreement). This amount calculated based on the schedule, and included bond interest accrued on payments with due dates after the payment date. The Payoff Statement Report also displayed the unexpected values (from the Payout Agreement view, choose Commands > Print Payoff). This calculation issue has been resolved.

21282*

A user opened multiple copies of the Rendition Penalty Dialog box (expand Rendition panel in Property view and click Penalty). This issue has been resolved by disabling the Penalty button when the Rendition Penalty Dialog box is open.

21313*, 21995*

In 9.0.34.2108, ticket 21313 developed functionality allowing users to automatically set a penalty fee on Properties for which taxpayers did not return a rendition. However, the expected penalty info was not being displayed in the Rendition Penalty Dialog on the property (from the Property view Rendition panel, in the Rendition section, select the rendition and click Penalty).

Further development to correct these issues and meet user expectations has resulted in the following changes to the Rendition Penalty Dialog (when a penalty is applicable):

• For properties whose owners have filed, but filed late, when opened, the Rendition Penalty Dialog now updates and displays the appropriate rendition penalty according to the scheduled if there is no override.
• If the user chooses to undo a previous override, and the scheduled penalty is different from the penalty previously set via the override, a message is displayed.
• For properties whose owners have not filed, no penalty is selected or displayed (until the set rendition penalty process is run).

Note the following:

• Events for rendition penalties and waivers are now more detailed. Events are generated for adding or changing the penalty (with the penalty value included), or for removing the penalty, and for adding or removing waivers. These events are Assessor system-type events, and the responsible user is recorded and displayed instead of System. No event is generated simply because the Rendition Penalty Dialog was opened and closed.
• The mass functions for setting and clearing rendition penalties also generate the revised events.
• The user can no longer open two copies of the Rendition Penalty Dialog.
• A different, earlier version of the Rendition Penalty Dialog is shown for years 2004 and earlier, and it displays the expected data.
• Choosing Override allows the penalty to be freely changed, regardless of waivers or schedules.
• Absent an override, choosing a Waiver that grants a waiver clears and disables the rendition Penalty field.
• Absent an override, waiver, or scheduled penalty percentage value, the user can freely impose, change, or remove a penalty.

21339*

The Notice Penalty field displayed in the Personal Property Rendition Maintenance Penalties dialog box has been removed (Tools > Personal Property Rendition Maintenance > Configure Penalties). The value entered/recorded in this field played no role in calculating and assigning penalties.

21351*

The Print Duplex option displayed in the Print Personal Property Rendition Application dialog box was selected by default (from Property view, Commands Menu > Print Personal Property Rendition Application). This would cause two copies of each rendition to print. Print Duplex is now unselected by default.

21375*

The Both Non-Farm and Farm option in the Print Personal Property Rendition Application dialog box was selected by default (Commands > Print Personal Property Rendition Application). For convenience, the Non-farm option is now the default print option.

21428*

The user was unable to add Group Codes while navigating the Personal Property Rendition Wizard (Activities > Rendition Processing > Personal Property Rendition). The toolstrip’s association with the Group Codes grid has been restored, resolving the issue.

21542*

Attempting to save a depreciation table without choosing a DOR Schedule code file caused an exception error (Tools > Schedule Maintenance > Depreciation Schedule Maintenance, click Add). A more graceful error is now displayed in this instance.

22017*

When printing rendition penalty letters, using the Query option did not produce the expected results because the dialog box checked for specific syntax in the query and often did not find it. This overly sensitive syntax check has been corrected in the following functional locations: (1) Print Rendition Penalty Letters (Activities > Rendition Processing > Print Rendition Penalty Letters); (2) print BPP Penalty Waiver Letter (Activities > Rendition Processing > Penalty Waiver Letter); (3) Print Property Rendition Applications (Activities > Rendition Processing > Print Personal Property Rendition Applications); (4) Print Request for Supporting Documentation (Activities > Rendition Processing > Request for Supporting Documents Letter).

22062*

Personal Property Rendition Applications printed with a single line of text on one page (Commands > Print Personal Property Rendition Application; Activities > Rendition Processing > Print Personal Property Rendition Applications). The text has been rearranged to correct this issue. Note that, due to pagination issues, choosing Print Duplex may result in a blank page printing out at the end of the application.

22079*

When printing BPP rendition penalty letters, the Skip Letters Already Printed option failed (Activities > Rendition Processing > Print Rendition Penalty Letters). On initial printings, the system did not update itself properly. The updating mechanism has been corrected.

22081*, 22548

Users can now generate a preview from the Print Rendition Penalty Letters dialog box (Activities > Rendition Processing > Print Rendition Penalty Letters). Additionally, when printing, users can select their printer.

22659/
HS 117460

The barcode on the Personal Property Rendition Application has been suppressed, and will no longer display (open property, choose Commands > Print Personal Property Rendition Application).

19615

For each sale listing, a new Document Type column has been added to the DOR Invalid and Valid Sales reports (populated from deed_type.deed_type_desc joined on chg_of_owner.deed_type_cd) (Reports > DOR > Sales > Invalid Sales Report, Reports > DOR > Sales > Valid Sales Report). These reports are now formatted in landscape to best fit in all required info. This change comes in response to a legislative change.

21020/
HS 111004

Properties that were part of multi-property sales displayed more than once in the Valid Sales Report (Reports > DOR > DOR Sales Report). Additional filtering measures for handling multi-property sales have been added to the report’s generation.

21136/
HS 111074

The Certificate of Delinquency displayed the property owner’s name rather than the collections owner’s name (Commands > Generate Certificate of Delinquency). The information is now drawn from the account owner and not the property owner, resolving the issue.

21137/
HS 111098

Formatting on the Certificate of Delinquency has been improved (from Property view, Commands > Generate Certificate of Delinquency).

21272/
HS 111715

Formatting on the Petition for Refund has been improved (from Property view, Commands > Petition for Refund).

21370/
HS 112170

Formatting on the Excise Detail Report has been improved (Reports > Excise Detail Report).

21649*, 21650*

Expected property and tax information did not populate on the Certificate of Delinquency when it was generated from a Personal property (from Property view, Commands > Generate Certificate of Delinquency). Personal properties were previously excluded; this has been corrected. Additionally, the Late Filing column was removed and some formatting enhancements were made.

21685

The Collected Escrow Applied Report was improved; this includes setting the report to generate landscape, adding the county name and version, inserting a box around the header, expanding the Property ID column, modifying Total label to Grand Total, plus remedying other minor issues (Reports > Escrow > Collected Escrow Applied).

21747

The Escrow Value Listing Report was improved; this includes adding the county name to top of page with a full header, sorting on Property ID then tax year then difference, and aligning data carefully (Reports > Escrow > Escrow Value Listing).

22265/
HS 115845

Just prior to release 9.0.34.2108, issue 21744/HS 113719 stated that, on the REET Collections Daily Recap Report, values representing the amounts collected on a given day were inconsistent between reports run per day and reports run for the month (Reports > Daily > Daily Summary). To resolve the issue, values for each day in the report period were set to calculate separately, with daily values summed together at the end.

Subsequently, interest and penalty amounts were reported as no longer being separated out into individual line items on the report anytime Group by Tax District was not selected. To fix this issue, the non-grouped version of the report again shows only base values. Also, for non-Tax Districts, the Amount Collected column is now titled Base Amount Collected, clarifying that P&I are intentionally not included.

22806/
HS 118187

An unexpected error occurred when trying to generate the Annual Financial Report (Reports > Monthly > Annual Financial Report). The report’s unique ID entry has been restored, resolving the issue.

22257/
HS 115911

Users had to take the unexpected step of right-clicking and associating the sketch to an Improvement Detail because, when the sketch drawing was opened from the Improvement Detail, the automatic association was scrapped to allow expansion of Non-Associated areas during the drawing session. Now, the association is restored once the expansions are complete, so users can select any Improvement Detail and associate a sketch with that element.

22487/
HS 116837, 22488/
HS 116846

Instances of creating, modifying, and deleting sketches did not record in the expected PACS database images tables. Changes to the recording of these actions in the database now mean the following: (1) creating a sketch from the Property view (Commands menu) adds the entry to the property_sketch table and the pacs_image table with the pacs_user_id of the updating user; (2) deleting a sketch from the Property view (Commands menu) removes the entry from the property_sketch table and the pacs_image table; (3) creating a sketch from the Improvement dialog (Sketches button) adds the sketch entry to the imprv_sketch table and the pacs_image table with the pacs_user_id of the updating user; (4) deleting the sketch from the Improvement dialog (Sketches button) removes the sketch entry from the imprv_sketch table and the pacs_image table.

Note that the entries in the pacs_image table for both the property and the property improvement have two entries–one for the image itself and one for the thumbnail.

22349/
HS 115786

Expanding either a Land or Improvement Detail from the Wizard that processes property splits resulted in an expected exception error (Activities > Split Property). This occurred because the split process code was not current and compliant with changes to how the system handles the number of lots values. This issue has been corrected.

22366/
HS 116447

Attempting to perform a property split that included multiple properties with Current Use resulted in an unexpected error (Activities > Split Property). The code for selecting Land details was copying those details too much. Furthermore, in some cases an integer was expected in the Number of Lots field, and decimal values caused errors. These issues have been resolved.

20926

The Exemption Amount field incorrectly displayed as zero (0$) in the General panel of the Special Assessment Bill dialog box (in Tax Due panel of Property view, select a statement in the Special Assessment Bills grid and click Details); this occurred on imported special assessments with exemptions (Import > Special Assessment, process the import, then create and activate bills). A calculation problem with flat fees has been corrected, resolving this issue. (This issue stemmed from project testing for a prior release (33.x) and is included here because it was an existing functionality issue.)

21004/
HS 110586

The user name displayed in the Prepared By field in the Supplement History panel was cleared after a property was moved from a pending supplement group to an active supplement. This info is now preserved when moving a property between non-zero supplements within the same year.

22937

A supplement and change of value were not reflected on the property’s notice. In this instance, the property was put into the pending supplement from a coding supplement group. A subsequent attempt to move the property back into the coding supplement prompted a warning that the property was already in the supplement group, at which point the property appeared to be in both supplement groups. This issue, which was discovered during beta testing but appears to have been pre-existing, was resolved by resorting and prioritizing the multiple threads of property data copying executed during the the supplement process.

21357

The code that generates tax statements has been improved. The time required to generate statements should be down from around 1.5 seconds to less than 1/4 second per statement.

22099/
HS 114961

A property’s prior year levy bill value was missing when the same levy’s current year rate was 0 with no bills created; this error also required the levy’s district to include multiple levies–at least one being a voted levy and another non-voted. The code has been modified to gather the expected values.

22200/
HS 115670

Messaging configurations on corrected tax statements did not work as expected (Commands > Create New Tax Statement). Development has made the following changes to the Important Information section:

• First, the default message has been changed to “If your mortgage company pays your taxes, this statement is only informational. Delinquent payments received without correct interest and penalty will be returned. Postal service cancellation mark by the due date is the only proof of timely payment.” (The issue calling for this change–some of the text was omitted–was a result of a conflict between statement character lengths and Crystal report thresholds.)
• Second, the supplement reason did not display when expected. When gauging whether to show this message, the system now checks if tax_statement_config.supplement_reason is True (a value of 1 in the database) and wa_tax_statement.supp_reason is Not Null.
• Finally the system now gives the message display the following priority: (1) delinquent notice comment, (2) supplement reason, (3) tax statement configuration message, (4) default text. (Previously, it was (1) supplement reason, (2) tax statement configuration message, (3) delinquent notice comment, (4) default text.)

22415/
HS 116319

The second half-payment tax amount due did not display on the second payment coupon when the statement for the second half was generated from the Commands menu and/or taxes were delinquent. An issue with the time stamp complicating matters has been resolved.

22551/
HS 117221

Tax statement 1st half payment coupons printed on a second page, causing the whole statement to require three pages (Commands > Create New Tax Statement). The payment coupon portions of the statement have been reformatted, the primary change being to move white space from the top of the coupon. This resolves this issue.

22767/
HS 117950

The generic Real tax statement message was not displayed on notices as expected (in PACS.ADMIN, choose Tools > Code File Maintenance > General > Tax Statement Messages, give highest priority to a delinquent message code followed by one for owner messages on which the only criteria is that it be for Real property types, then open a property with current year taxes due and none delinquent and choose Commands > Generate Corrected Tax Statement). This issue has been resolved. The default message is: If your mortgage company pays your taxes, this statement is only informational. Delinquent payments received without correct interest and penalty will be returned. Postal service cancellation mark by the due date is the only proof of timely payment.