Release Notes February 2023
CANDIDATES: Be able to hide & rename 'standard candidate statuses'
We have 3 global statusses for candidates for a long time, these are 'Via VMP', 'Via Website' & 'Via Profiler'. We have created an option to hide them. Keep in mind that hiding one or more global candidate statuses, could cause unwanted results. For instance, by default a new candidate that applied via the website gets the status 'Via website'. If you hide this option, a candidate does not have a status to start with.
MAIL: Allow reply-to email header'
In the BO we had an setting SE1584, 'Mail Manager - Use Reply-To header when replying to emails' to reply to the 'Reply-To' header. This was not working in OTYS Go!, To give you an example the following example can be made. LinkedIn send a email with an apply to your email with in the from field 'noreply@linkedin.com' they have put 'candidateemail@gmail.com' in the 'Reply-To header'. With the setting off you click 'Reply' and it will fill in 'noreply@linkedin.com' in. With setting 'SE1584' on it will fill in 'candidateemail@gmail.com'
CANDIDATES: Manually merge double candidates'
Within OTYS We have a dedouble functionality to merge double candidates within the database of the candidate module. There were rules connected how OTYS sees these double candidates and will mark them. There was no option to dedouble functionality to merge double candidates, we have implemented a batch action where when you mark 2 or more candidates you can trigger the 'Merge candidates' batch action if it was available in SE3407. If you preform this batch action you will be redirected to the original de double functionality with these candidates open.
VACANCIES: Add column for 'Job type code'
You can enable vacancy types for the vacancy module with client setting 'Vacancy Manager - Use job types' (SE761). When enabled, you can add the column ; Job type (name)' to the list view. We added a new column called 'Job type (code)' to show the id of the job type in the list view as well.
GENERAL: Use Smart date filters for all date entities of Vacancies & Candidates (Including extrafields)
Within OTYS we have a lot of datefields, these datefields all mean something special and are filterable. We have moved from a 'DateRangeField' to a 'CustomizedDateRangeField' where we are possible to configure special filters for dates based upon your criteria such as: Customer period, current period, last period, From today & Future period. Besides of this we we also ran a script to covert all the stored queries for all client that had one or more of these fields saved. This was now implemented for the following fields:
Last Contact date
Date available
Extra fields
Last update
Entry date
TASKS: Implement 'Logged in user' option in criterium 'Manager' & 'Assigned to'
In order to create filters for other people for some criteria you should select a specific user, we can imagine this is not really nice if you have 300 users. There for we have added the option to add a 'Logged in user' so you can create 1 filter and based upon that 'logged in user' it will select all the criteria for this filter. This is implemented for 'Manager' & 'Assigned to'
VACANCIES: Filter 'Shortlist' in Vacancies-module
In the Vacancies-module it is possible to mark a vacancy to show on the shortlist (checkbox) and to define the shortlist websites (multi-select, in case of multisite). Using the filter in the Vacancies it was already possible to search for vacancies based upon the selected shortlist websites, but it was not possible to search for the shortlist marker (the checkbox). Now it is possible using the 'Shortlist'-filter.
TASKS: Batch action to update tasks extra fields
In the Tasks-module we have 'extra fields' (like we have in other modules) to create client specific fields for tasks. From now on it is also possible to change these tasks extra fields in batch, similar to how you use other batch actions (right click on selected tasks and choose 'Extra fields'). Please note the extra fields batch action needs to be enabled for the client/user through setting SE3414.
INTERACTIONS: Add vacancy salary fields to interaction forms
Within the Interaction module there was not an option to add the vacancy salary fields, we have added these three fields - Salary currency (Single select), - Salary value (Text field) & - Salary Per (Single Select) to the interaction forms.
INTERACTIONS: Validating interaction form fields based upon regular expressions
Using the Interactions-module you are able to create forms that can for example update an existing candidate or create a new vacancy. For fields of type 'Textfield' & 'Textarea' it is also possible to configure additional checks ('max. digits', 'max. characters', 'postal code', 'e-mail', 'phone number', 'initial letter capital', 'word starts with capital', 'all capitals' & 'letters only'. These checks are fine for most use cases, however there are specific use cases that can not be met with these checks (for example 'exact number of characters', 'whole amount between 10 - 1000' or 'decimal amount'). Since we do not want to create very specific checks for this in interaction forms, we have created a generic solution allowing to configure a check based upon a (user defined) regular expression (which is an 'industry standard' for checking if a string matches a specific pattern). For this we have added a section 'Regular expression' below the current section for the (basic) checks. This section includes three fields: checkbox 'Check based upon regular expression', text input 'Regular expression' and 'Error message'. If the checkbox is checked, we will check if the entered text by the user matches the regular expression and if it does not we will NOT save the form but show the configured error. Please note that regular expressions are for advanced users and that these checks only work when filling in the form using OTYS Go! or our web services.
CANDIDATES: Extra fields in undouble functionality
Two candidates in the OTYS system can be one and the same person (for example because the candidate applied after a year as a new candidate with a different email address). To avoid 'double candidates' we have an undouble functionality (see Doubles), which allows clients to either manually or automatically merge two candidates into one. This functionality has a 'limited scope' for which fields will be moved from one candidate to another candidate. From now we also support candidate extra fields in our dedouble functionality. When dedoubling candidates you will now see all candidate extra fields which are configured to be 'visible' and is filled in for at least one of the two candidated dedoubling (so extra fields which are not filled in for both candidates will not be shown, since there is no data to transfer). The user can then choose which data should be used in the way it already worked. Multi-select candidate extra fields will be 'merged' (so if candidate 1 has options 'Option A' and 'Option B' and candidate 2 has options 'Option B' and 'Option C', merging this field would select options 'Option A', 'Option B' and 'Option C'). The candidate extra fields are also included in the automatica merging of candidates. If candidates are merged automatically the data of the most recent candidate will be used in case of any conflicts (for example if a candidate extra field of type 'textarea' is filled for both candidates).
PLANNING BOARD: Option to set HRM items to passive on planning board
In the Planning board it is possible to add 'HRM items'. These HRM items can be used to indicate if for example a candidate is sick or on holiday. The HRM items use 'HRM categories' (for example 'holiday') and 'HRM types' (for example 'holiday in home country') to specify the HRM items. It was only possible to create HRM categories/types. If you did not need a category/type anymore you could either delete it (which would however also delete historic data) or put a famous 'DO NOT USE ANYMORE' indicator in its name. Since that is not ideal, it is now possible to mark an HRM category/type as 'active'. If it is active it can be used actively (for example when creating new items and when searching). If it is not active it will not show on those places, but HRM items which already have that category/type will be unchanged.