Release notes - 5 July 2023

HR

Enhancements

  • Screen Designer: Any calculated or page join fields are now read only by default. This has been done to prevent fields that get data from another part of the system from being editable.

  • Logged in user: When accessing the top right-hand user menu, the logged in user's name now shows Known As and Surname.

Fixes

  • Cost of Absence: The cost of absence field on the query builder only screen Absence (Dates) has been enhanced to include any salary changes within the period being queried.

  • Workflow: Asks were being duplicated if roles from HR and Payroll had the same name, this has been fixed.

  • Dashboard: The enhanced dashboard chart My Task List Summary had an error when a workflow task owner was Page-Field Lookup, this has been fixed.

  • Bank Holidays: The AM and PM options have been removed. If you used Bank Holidays to give employees half a day off, this is now only possible using Allocate a Holiday/Absence.

Help centre updates

New

Updated

Payroll

Enhancements

  • Pay Elements Export: User Items will now show the Display Value on the Payroll > Application Data > Pay Elements > Excel Export.

Fixes

  • Planner: Maternity showing incorrectly on the Employee Planner, this has been fixed.

  • Holiday Advance: Incorrect employee NI value when using holiday advance function, this has been fixed.

Stability and Infrastructure

We've been tuning background jobs to free up the resource for our database servers to process the things you want to do.

  • Email queue: We've tuned queries that relate to the processing of Cascade's email queue. Our recently improved monitoring and analysis highlighted that the queries running in the background every 2-3 minutes to manage this processing were using high amounts of resource on the server. We've tuned these queries now so they run much faster and use a lot less resource to do the same processing

  • Errors in automated jobs: We've tuned queries that run whenever the system detects an error in any automated background jobs, these background queries were using an excessive amount of server resource which has now been reduced by up to 80% on some of our larger customer databases.