Release Notes March 2023

DOCUMENTS: Search and replace functionality in OTYS Go!

We have added a functionality in OTYS Go! to create & implement 'search & replace'-rules for Documents. This can be useful in specific situations when for example you merge an extra field that indicates the transport method of a candidate (for example 'train') and want to replace it by some text about travelling by train. By enabling client setting 'Go! Documents - Enable search and replace rules' (SE1290) will enable this behavior and using client setting 'Go! Documents - Search & Replace rules' (GE316) will then enable you to manage the rules. Then when processing a standard document at the very end the search & replace rules can be applied.

INTERACTIONS: Match criteria within Interaction form widget can be updated via window

It is possible to use an interaction form as a widget. One of the fields you can add are the match criteria's. Adding match criteria in the interaction form widget works different compared to the original match criteria widget. We made an update to the match criteria field in an interaction widget. Now you have a + button when the widget. This can at all times be used. In the window that opens, you see a list of the match criteria that is available and selected, same as the original match criteria widget.

PARTNER FRAMEWORK: Improved handling of webhooks

Some time ago we launched 'OWS webhooks' (see https://www.otys.com/partners/docs/Manual-OTYS-Go!-Partner-OWS-webhooks.pdf) which allows external parties to get an 'active signal' if a user executes a specific action. These webhooks are connected to the underlaying OWS requests. These OWS requests can however be sent in different ways (only the request, one or multiple requests in a 'MultiService.execute' & one or multiple requests in a 'LanguageService.wrapRequest'). However, not all these requests resulted in a webhook and did not always include the method triggering the webhook. We have made various changes to make this work more consistent.

CANDIDATES: Possible to change owner 2 and 3 in batch

With client setting 'Candidates - Two additional owners' (SE3336) you can enable the option to add a second and third owner to the candidate. You can now add the second and third owner also in batch from the candidate list.

SMS: Delivery reports for SMS text messages

It is possible to send SMS messages from your OTYS system. For this we are using Spryng as a provider. We always used to show a status of the SMS message in OTYS Go!. However this status only indicated if Spryng correctly received the SMS messages and send it to the mobile network. If someone for example had his phone turned off, OTYS would show status 'Send'. We have now implemented 'delivery reports' for these SMS messages. SMS messages send from OTYS will now by default get the status 'Pending' and once the SMS is actually received (or if there is some kind of error) the status will change (to 'Received' or a specific error). Please note that this will only indicate if the SMS was delivered to a mobile phone, it does NOT necessarily mean the SMS is actually read by the recipient (unlike for example WhatsApp, the SMS protocol does not support these kinds of read indicators). Please note that if you do NOT use the SMS messages from an OTYS bundle but from your own Spryng account, some additional configuration is needed in your Spryng account.

ASSIGNMENTS: Extra fields in list veiw

For many entities we have an 'extra fields' functionality, which allows you to add custom fields for which OTYS does not have standardized fields. This way if you for example want to register a candidates shoe size (for which OTYS does not have a standardized field), you are able to add extra field 'shoe size

' in a candidate detail. For assignments we already had this extra fields functionality, but it was not yet possible to add these extra fields in the list view of the assignments module. Now this is possible. This is globally available for all clients which use assignments extra fields, however the configuration of the list view of course needs to be changed to show the desired extra fields.

ASSIGNMENTS: Hide 'Stop'-button in assignment detail

In an assignment detail of an active assignment, we by default show a 'Stop'-button to stop the assignment. It was not possible to hide this button for all or for specific users (for example because an integration with an external tool is 'stopping' the assignments). We have created client-user setting 'Assignments - Hide 'Stop'-option in assignment detail' (SE3460) that will hide the 'Stop'-option in the assignment detail. It is a client/user setting so that you can for example enable it for the client (to by default hide the option for all users) and then to disable it for specific users (so that the option will be visible for these users) OR so that you can disable it for the client (to by default show the option for all users) and then enable it for specific users (so that the option will be hidden for these users). Please note that if you do not have access to setting SE3460, Customer Service can enable it for you (please mention 'SE3406' in your request).

PROJECTS: Change status through status label in header

In most details the 'status' of the record shows in the header and you are able to change it by clicking on it (so the candidate detail will for example show the candidate status in the header and clicking on it allows you to change it). The project detail already showed the project status, but did not allow you to change it by clicking on it. Now it is possible to change the project status by clicking on it.

PLANNING BOARD: Show/hide job type in request view

In the Planning board-module it is possible to get an overview of candidates & requests. In both views it is possible to limit the fields shown, similar in the way you configure a list view in for example Candidates. In the request view it however was not possible to hide the job type (it would always show). We have now added this field to the list view configuration so that you are able to show/hide it.

PROJECTS: Clickable contact person in project detail header

In the headers of details, we show the most important information about that record. This can also include 'related' records, which we normally make 'clickable'. In a project detail we already showed the (clickable) linked customer, but not the contact person linked to the project yet. Now we do show a clickable contact person in the header of a project detail if the project is linked to a (main) contact person. Clicking on the contact person's name will open the contact person detail on top of the project (so closing the contact person will bring you back to the project).

CANDIDATES: Option to hide field 'Copy to Cards and licences widget'

In a dossier it is possible to upload all kinds of documents. When uploading a document, you can define a dossier type to distinguish the documents (for example 'CV', 'Contract' & 'ID card'). For the candidate dossier it is possible to give the dossier types a marking so that if you select that specific dossier type, it is also possible to fill in a document number, issue date and/or expiration date. Since we also have a widget to fill in this data; we will currently always also include an additional select to copy this data to the relevant widget. It was not possible to hide this option. Now it is. By disabling client setting 'Dossier - Show option 'Copy to Cards and licences-widget' when uploading document' (SE3459) this option is not shown anymore.