Release Notes July 2023

REPORTS: Show linked entities in calendar detail within the report

You are able to create a report based on calendar items. If you use the column layout, you can click further to see all the items for that month, for instance. We added a new column called 'Linked entities,' which shows the entities that are linked to the calendar item. We support candidates, relation contacts, relations, tasks, and vacancies. Multiple entities can show, and when you click on one, it opens the detail view of that entity.

WORKFLOWS: 'Preview document'-button in Standard document functionality

Within OTYS, we implemented a month ago that you can preview your document prior to generating it by a workflow. This is now also possible by the normal standard document functionality.

DASHBOARDS: Option to show/hide 'Entry date' in candidate widget

We have made it possible to show/hide the entry date on the candidate widget so you can create more action-driven widgets on the dashboard.

Job API: Add Consultant phone number

When you request the detail of a vacancy, you also get some information about the owner(s) of the vacancy. The mobile phone number was missing, and this has been added.

SETTINGS: Hidden procedure statuses not shown in settings GE103, GE203 & GE303 anymore

Some time ago, we created the possibility to hide procedure status 2 & 3 (client settings SE3289 & SE3290), so that clients are, for example, able to use only one status. The client settings 'CRM - Relation Contact Permission templates' (GE103), 'Online CV Presentation - Status configuration' (GE302), & 'Online Job Presentation - Status configuration' (GE303) however, still always showed all three procedure statuses. Now the statuses are also shown/hidden based on the client settings.

REMINDERS: Standardize layout of reminders module to be the same as other modules

Most modules in the OTYS system (like Candidates, Vacancies, CRM, Procedures, Tasks, etc.) have a similar 'basic set up.' Our Reminders-module had an 'alternative layout.' There is really no good reason for it, so we changed this module to have the basic set up like most modules in the OTYS system.

VACANCIES: Hide slug field behind client/user setting

If you use the custom URL functionality, then you can change the slug for a vacancy. This is not always desired, so we created a client/user setting that hides the slug field. This is a key-user setting. The setting is called 'Vacancies - Enable slug field' (SE3488).

PARTNER FRAMEWORK: Logic to enable, disable, or hide a custom action

In OTYS Go!, we can create custom actions via our Partner Framework. There are different types of custom actions. Currently, when a custom action is created, this will be available for all users within the client. You can block users from interacting with them, but you cannot hide the custom action, and therefore, if they do not have permissions, they will see an option the user cannot use. We have created an additional field 'Endpoint visibility check' when configuring a custom action (client setting GE288). In this field, you can fill in an endpoint URL which will be triggered in the same way as the actual endpoint for the partner action (for example, posting OTYS SSO data of the user), however OTYS will expect JSON back to define the visibility of the custom action (show it like it currently does, show it 'disabled' so the user cannot use it or hide it). The expected returned JSON is a simple JSON with six key/value pairs: 'visible' (set to 'true' if the user should see the option or 'false' if it should be hidden), 'enabled' (set to 'true' if the option should be enabled or 'false' if it should be disabled), 'URL' with the URL that should be used, 'text' with the text of the button, 'tooltip' with the text of the tooltip in case of a disabled option, and 'info' which you can use for internal debugging purposes). In some cases, some fields will not apply (for example, if 'visible' is set to 'false,' then 'text' will not be shown); however, please make sure to always provide all fields and for example set values to 'null.' Additionally, if no specific information is available, we will fallback to the original behavior (so if you, for example, do not provide this new 'Endpoint visibility check,' we will still show the option to all users).

GENERAL: Daily history feature to view previously opened and changed entities

As you are working a full day in OTYS, you make a lot of small changes and open a lot of entity details or add notes and documents. But there is no way to quickly see what you have done earlier today or to quickly go back to a previous action. We now have a new feature called 'Daily History.' It shows you the items you have opened and certain changes that you have made. You can now quickly go back to, for example, a candidate you opened previously. You can access the history by clicking on the button at the top, left from your profile picture anywhere in the OTYS system.

GENERAL: Create specific detail page titles for browser tabs

When you have multiple OTYS Go! browser tabs open, you do not know exactly which tab has what open based on the tab name. We changed this to be more clear and show the name of the entity, for instance, the candidate name and id.