...
You may notice a new Security Role called Default Umbrella Company Role for an Umbrella Company User. This role has been automatically created in case an agency decides to utlise our /wiki/spaces/FV1OH/pages/2558263468 feature. An umbrella company is a company that employs a temporary worker (an agency worker or contractor), on behalf of an agency. The agency then provides the services of the worker to their clients. Umbrella companies typically do not find work for the workers they employ. This feature has been developed for can currently only be used by the United Kingdom.
The User Type ‘Umbrella Company User’ is not available as an entity to use within Security Role configuration. Please DO NOT delete this security role.
...
Custom Field
...
Changes
Search Issue
Currently where you create a new custom field with a default value, and then search for the default via the related search screen, 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 screen or API call, the system will find these results. Please be aware that any reports will need to be re-factored to support where a Custom Field’s default value is used as a criterion.
Consolidation of configuration in Front Office
In Version 12 the configuration of all Custom Field elements, both front and back office, have been centralised and now reside in front office tables. As such Custom Fields that were in back office for Billing Company, Debtor, Pay Company and Payee, have been moved and eh old tables will no longer be updated or maintained. This change may cause downstream impacts for reporting where the report is querying the old tables:
Old Tables for Back Office Custom Fields | New Tables in V12 for all Custom Fields |
Generic | FO.CustomFields |
Generic Link | FO.Customfieldmappings |
If any of your reports are using the old tables to query Custom Fields, please refactor to the new tables. If you have any questions on this change, please log a Support Ticket.”
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:
...