The enhancements described in the related pages below represent significant functional changes that you must be aware of prior to upgrading to this release. Some of these enhancements require specific actions before or immediately after upgrading and are therefore highlighted here for your reference. Please refer to the relevant sections of this What’s New Guide, as identified below, for detailed information about each enhancement and any configuration that is required.
Please be aware of the following important points about upgrading to v12.10:
Before upgrading, please ensure that no pay batches are being processed in the Payroll module. All pay batches must be closed before attempting to proceed with the upgrade.
Leave Taken Deduction Rule Entitlement Balance Condition Change
The behaviour of the Sufficient Entitlement Balance condition on leave deduction rules for leave taken has changed whereby on upgrading to v12 the condition will partially pay leave taken if a payee has an insufficient entitlement balance to cover the entire duration of leave taken. Read more here.
Security Role Changes
We have split out some of the security permissions that impact the Candidate Portal, to provide you with the ability to determine if some of the sections display in the record. We have also added a new item to display your Privacy URL in Candidate and or Client Portal. To maintain your Candidate Portal Users existing experience, on upgrade we will automatically tick any additional permission items to sustain their current view and edit abilities. Read more here.
Custom Field Change
Currently where you create a new custom field with a default value, and then search for the default via the UI, or run a call via an API, the system will not pick up results that match the default value. In the v12.10 release, we have made a change to remedy this issue to ensure that where default values are applied in a search or API call, the system will find these results. Please be aware that any reports will need to be re-factored to support where the default value is used as a criterion.
Phone Number Change
Currently where a number is entered via the UI, we apply validations to check that the values entered are numeric, and the number of values meets the criteria for a phone number. We then cleanse to remove spaces and store it ready to support SMS services. As phone numbers can also be imported (for example via an API) in this release we have introduced logic to validate, cleanse and store the number. Where we are unable to validate, for example the number contains a non numeric character, the value will be stored and displayed, however it will be prepended by the double quote symbol as shown below:
“0403t88236
Where you see this in the system, you can either edit and add the correct number, leave it as it is, or remove where it is not a mandatory field. Please note as advised in the past BPME masking on phone numbers (where configured), will not apply as we need to store the values without spaces to support SMS services. We are aware that users would prefer to see numbers masked, and we are looking for a solution that will support this in the future.