...
| Note |
|---|
Please be aware of the following important points about upgrading to v12.10:
|
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.
...
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.
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.
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:
...