Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Import Link Fixer

Table of Contents
maxLevel1
indent1px
stylenone

...

DateVersionType

 

8.68.0Release

 

8.69.0Release


Bug Fixes

  • Corrected the refund to prevent modifying the transaction if there is an associated check.  Refunds with checks are not modifiable.
    • If the refund/check need to be updated, instead the check can be void and a correct refund reissued. 
  • Improved the Appropriation Resolution report "zero balance" option to ensure that accounts that sum or balance to zero are not being excluded.  Only those accounts that have zero amounts for all fields are excluded.  The FYTD Appropriation Carryover and Totals report was not properly applying the "Include Accounts with Zero Balances" option as accounts that summed to zero were also being excluded.
    • Periodic > Appropriation Resolution Report
  • Corrected a bug that allowed the July 1 cash balance to display as 0.00 in the specific case where June is closed and the system creates July (July doesn't exist before closing June).
  • Corrected a bug on Proposed Amounts grid when attempting to Apply as Temporary or Permanent budgets for the next fiscal year. Error message indicated that it required the effective date on the initial transaction to be in the current fiscal year. That is not the case - Temporary or Permanent budget amounts can be posted for the next fiscal year while still in the current fiscal year. If July of the next fiscal year posting period does not exist, it will be created.
    • When Applying proposed amounts as Adjustment type, the date IS required to be in the current fiscal year. This is intended to prevent issues with mis-keyed dates that we've had reported previously.

Improvements

  • Improved the message displayed when scenarios are promoted to proposed amounts to include "ALL existing proposed amounts, both Expenditure and Revenue," for clarity.

...

We will be removing the obsolete "SSDT Auditor Report Bundle" in an upcoming release.  The report bundle was replaced last year with jobs, the District Audit Job and SOC1 Audit Job.  Details on how to use the audit jobs can be found in the Job Scheduler user documentation.


OLD: Reports > Report Bundles

...

DateVersionType

 

6.87.0Regular

 

6.88.0Regular

Bug Fixes

  • An issue with the Compensation Print Screen Report failing was corrected. 
  • Corrected a 'zero exception' error with the Afford Report.  If the Afford Report is run for a specific month and an employee is only part of one payroll in that month, the Compensation Calendar Start Date is after the payroll Stop Date,  and the report is calculated based on months a divide by zero exception was occurring.  This is a result of the Calendar Start Date being used as the starting point for counting months - along with the payroll Stop Date as the stopping point.  The result of this is 0 months.  This is then used to determine hours per month by dividing hours by months, resulting in the divide by zero exception.  This has been updated so that if the months are 0, the result will be zero - and no division takes place.
  • Updates were made to the stream progress indicator to prevent it from spinning indefinitely.  
  • When creating Custom Field Definitions with the Type of 'Code,' the sort order has been corrected to be sorted in alphabetical order by Code. 
  • The Quarter Report has been updated to include board pickup adjustments when calculating information in the Form 941 section.
  • Leave Projection Report has been updated to handle fully docked employees with absences.  The system tries to determine the amount to charge the leave accounts.  Part of this calculation divides by total charged to the Pay Accounts in the payroll associated with the absence.  In this case, the total amount charged is zero.  In these cases, the report will now included an information message.
    • Info - Total account charges is zero for MM/DD/YYYY payroll, could not calculate charge amount for Leave Projection. No action required.
  • The total gross for the 400 and 450 Payroll Items on the Payroll Item Detail Report pre-posting the payroll verse after posting the payroll will now match for employees that have increased compensation.  
  • Payroll Items where active date ranges (end dates are blank) will no longer cause issues.

Improvements

  • Salary Notice Notices - add the following new properties are now available and can be added to custom forms:
    • salaryScheduleId
    • salaryScheduleColumn
    • salaryScheduleStep
    • rate
    • rateType
    • districtExperience
    • buildingExperience
    • accredDistrictExperience
    • militaryExperience
    • tradeExperience
    • retireSystemExperience
    • ohioPublicExperience
    • ohioPrivateExperience
    • nonOhioPublicExperience
    • nonOhioPrivateExperience
    • purchasedExperience
    • authorizedExperience
    • totalExperience
    • principalExperience
    • degreeType
    • degreeTypeDescription
  • On the Pay Report, any Payroll Item Configuration with an 'abbreviation' longer than 8 characters will not be truncated to 8 characters followed by '...'.  
  • With the SERS other email requirement, there is a chance the Employee>Other Email Address could be the same as the Employee>Primary Email Address and/or Secondary Email Address.  If the System>Configuration>Email Direct Deposit Notice Configuration>Send Notification To All Addresses is checked, duplicate email addresses for the same employee will not receive their notifications twice.  Please note, while it is not recommend to use case sensitive emails, it is allowed.  If a user were to enter two emails and the only difference is the case, two email notifications will be sent.
  • The email address will now print on the SERS New Hire Report and be included in the SERS New Hire grid.
  • Users can now add a Payables Adjustments by typing in the Payroll Item Code or select from a drop-down menu.  Prior to the update, the user could only select from the drop down.

...

Bug Fixes

  • Corrected an error when from a change made on the 1.33.0 release.   When deleting transactions or splitting items related to constraints recently added to the audit table.  This caused an error to occur when deleting an acquisition, disposition or transfer transaction.  It also caused an error when attempting to split an item.  (where original tag is deleted) it generated an error message.  This was fixed on the 1.33.1 hotfix.
  • System>Configuration>Migration Import - Corrected the Migration Importer for Acquisitions to allow importing multiple acquisitions for an item.

Improvements

  • Internal: Implemented intrusion detection in Inventory like it exists in USAS and USPS.  If an intruder is detected, the login attempt fails and this results in a generic "Bad credentials" response being returned to the user. 

  • Audit Reports>Audit Report performance improvements have been were made, which will also positively impact impacted the report bundle generation.  Any district that migrated prior to April 2022 will see the most benefit (75-80%) as we are now excluding the initial migration audit entries for everyone.  Additional improvements are underway on subsequent JIRA issues (INV-460 and INV-439).

New Features

N/A

Patches

N/A

...