March 2025
Candidates
Upgrade 'Document Type & Expiration'-filter
In the Candidates module we updates the filter for Document types. So far it was only possible to use this filter when looking for document types with an expiration date. You can now search for document types without expiration date, exclude document types and use a flex-filter for the expiration date. This makes it possible to search for example 'all candidates without a document with type x', or 'all candidates with a document type y that will expire next month'. Document types can be configured by a key user in setting 'Dossier types configuration' (GE91)
'Last login history' available for exports
The 'last logged in date' registers the date the candidate was last logged in to the Candidate portal. This date is now available to use in export profiles (setting 'Candidates - Export profiles candidates' (GE138)). Note: to use this, setting 'Candidates - History widget of candidate information in Candidate Portal' (SE3505) needs to be enabled by OTYS.
CRM
'New password' email for contacts and candidates generates in recipients language
When generating a new password for a webuser with a language selected, the e-mail will now generate in this language if a template for this language is available. If the webuser does not have a set language, the e-mail will generate in the language of the OTYS user that is generating the password.
Batch action 'change owner' available for contacts
We've added the 'Change owner' batch action to the contacts module.
By default the owner of the relation is the owner of the contact person. To make it possible to specifically select an owner for contact persons, activate client setting 'Customer Manager - Contact person owner' (SE1726)
Settings
Assign Customer level to CV document based on level in questionset
For documents in candidate dossiers you can use acces levels to indicate which contact persons should be able to see them in a portal. Some time ago we made it possible to configure which level a document should get via the questionset. This way a document automatically gets the correct level when a candidate uploads it during application. Since CV's are a special type of documents, this was not yet working for those. This will now also work for CV's. To work with these levels, and automatically assign them to the documents and CV's some configuration is needed.
General
What's new - shortcut to release notes
In the menu behind the 'information'("?") button, top right of your screen, you will now find 'what's new'. This is a shortcut to our release notes.
Interactions
Error when adding unlinked fields to form with action set
Using our Interactions-module it is possible to create forms that can be used for all kinds of purposes. This can be something very simple (for example a contact form which can be published on a website) or more advanced (for example creating your own OTYS Go! widgets that update data in your OTYS system). For the advanced options it is important to assign the correct 'action' to the form (for example 'Update candidate') and to connect each field to a database field (for example 'Candidate first name'). However, it was possible to add fields to such a form without selecting a database field. To avoid this we will now show an error if you add or update a field which does not have a linked database field in a form with such an action set. Please note this check will only take place when adding/updating the field, it will for example not adjust current data or do a check if you set an action for a form that already has lots of fields added to it.
Fields 'Remove application button' and 'Searchable in Actonomy' available in Interaction form
The fields 'Remove application button' and 'Searchable in Actonomy' are used by some customers to keep vacancies online, without the option to apply. We have made these fields available in Interaction forms.
'Internal remark' available for use in Interaction forms
In vacancies you find a field called 'Internal remarks'. This field is now also available to use in interaction forms for the actions 'create vacancy' and 'update vacancy'.
KANBAN
Make collapsed columns with entities in Kanban easier to find
If you have a kanban board with a larger number of columns, there's a big chance you might have some of these columns collapsed. We already had a number behind the title of the collapsed column to show you that this hidden column had entities in it. Based on the idea of a customer we've now also made this title appear in the same font colour as the 'non collapsed columns' to make sure you never miss hidden entities again.
Timesheets
Show hover for notes
In the Timesheets there in an option to add notes per day, for example for a short explanation by the candidate. Based on feedback from customers we now added a hover, so you can see the note without clicking it open.
Vacancies
Block/unblock as batch action for vacancies
In vacancies you find a checkbox to 'block' the vacancy, usually in the Publication widget. When this is active, the vacancy will not be included in jobfeeds to for example Indeed. We have added 'Mark block/unblocked' as a batch action, to make it easier to block / unblock multiple vacancies at the same time. In setting 'Vacancies - Enabled batch actions' (SE3413) you can configure what batch actions should be active. This is a client/user setting: you can configure the default values for all users, and make exceptions on a user level.
Improved copy address from relation functionality
There is an option to automatically copy address details from a relation when you relate a vacancy to that relation. We now copy two more fields: 'state'(NL: provincie) is now also copied, and we fill 'location' with the 'City' field. If you want to show different information for 'location' - for example 'Utrecht region' instead of 'Houten', you can change the information and it will stay that way. To use this functionality a setting needs to be activated by OTYS. Reach out to our Support team to have this activated for you.
Sort on vacancy status
In the listview of the vacancies module it is now possible to sort on status.
Sort on location in vacancies listview
In the listview of the vacancies module it is now possible to sort on location.
Setting to disable 'Duplicate vacancy' option
In the vacancy detail, in the 'more' menu, you find an option to duplicate the vacancy. We have added a setting to make it possible to enable and disable this option. The new setting is 'GO! Vacancies - Enable duplication' (SE3577). This is a 'client/user' setting; you can configure the default on client level, and make exceptions on user level. If you don't make a change, the setting will be enabled and the duplicate option will be available for all users, as it was before we added the setting.
Postal code and City available to use in listview
In the Vacancies module you can now use the fields 'Postal code' and / or 'City' in your listview.
Additional fields copied when creating new version of job
In vacancies we have an option to create multiple 'versions'. This way you can for example create multiple versions of the job text to attract more candidates. When you create a new version, a lot of information in copied to that new version. We have added some fields to include a.o. Extra Fields, additional info from widgets 'location', 'Publication' and 'Application options'.
Previous/next buttons when navigating from applicants widget
When candidates are connected to a job, you can view them via the 'Joined candidates' button and the 'applicants' widget. When you use the 'joined candidates' route and open a candidate, you are able to navigate the candidates that are connected to the job with the 'next' and 'previous' buttons. These previous/next buttons are now also available when you open the candidates via the applicants widget.
Country field is now searchable
For our users that have vacancies available for more than one country, we've now added the ability to filter on the 'country' field.
Filter on Status in Instant Match
In addition to Match Criteria and (optional) Matching Templates, you will now be able to use a Status filter. This way you can specify to, for example, only look for candidates with status 'Talentpool' or vacancies with status 'Open'.