Release notes February 2024

Partners: Universal hashed link system for partners

We have more-and-more partners integrating with OTYS. These partners sometimes send an email, SMS, Whatsapp or other form of communication to a candidate or contact person. These communications can include URL's. In some cases the partner wants to include a hashed URL which will automatically log the person in and redirect the person to a specific OTYS portal page. For this we already had some specific OWS methods that can create these kinds of hashed URLs. Since we were getting more-and-more of these kinds of requests, we preferred not to keep creating specific OWS methods for these kinds of hashed links, but created a 'generic system' for it. New OWS method 'Otys.Services.OCDService.createToken' allows partners to create hashed tokens to automatically login a candidate or contact person and redirect the user to the defined portal page. The method expects four parameters: an OWS session token, an OCD webuser ID, an array with a 'url' key-pair value (with the URL to which the person should be redirected) and the number of days the token should be valid. Reason for adding an array with (currently only) one key-pair value, is that it allows us to amend it in the future with additional fields if needed. If a correct request is send, OWS will return the token in the result. This token can then be added to the URL of the portal in format '[website]/index.php/page/ocdapp/bb/1/command/loginandredirect/token/[token]'. Please note this will only work in combination with native OTYS portals.

INTERACTIONS: Field candidate 'Placement' available for interaction forms

In a candidate detail it is possible to (un)check the checkbox 'Placement' in widget 'Candidate information'. It was not yet possible to add this field to an interaction form. Now it is.

CSM: Source-button in WYSIWYG-editor of search & replace rules

Using our Documents-module it is possible to automatically generate Word/PDF documents an emails based upon fixed text, merge fields and question fields. We have an additional search & replace functionality, which allows you to additionally search for specific words/sentences and replace it by something different. This way you can for example add merge field 'travelexpensesapply' to the standard document and then replace this by a full paragraph about the travel expenses. These search & replace rules can be configured in client setting 'Go! Documents - Search & Replace rules' (GE316). In this setting the 'replace text' is shown in a WYSIWYG-editor. To give (advanced) users more control of the actual replaced text, we have added a 'Source-button' in this WYSIWYG-editor. Hitting this button will show the underlying HTML and allow the user to change this for 'more control' about the actually outputted result.

GENERAL: Changes to filters to make 'current filter' more clear

In most modules it is possible to create filters. If you hover over a filter, the background color of the filter changes (which is normal for websites and web apps). if you click on a filter, the filter becomes 'active' but does did not have any active marking. Most websites and web apps give 'active options' (for example the current menu option) an active marking. We do this for example for modules, but did not do this for filters. Now we do this for filters as well, so it is more clear to user what the 'current filter' is.