(Turn on subtitles in YouTube for English translation)
TABLE OF CONTENTS
- Brief Overview
- 1. General
- 2. Product Life Cycle Management
- 3. XS Core
- 4. XS Modules
Brief Overview
In this summary, you can quickly review all the new functionalities.
Part | Explanation |
XS CORE | |
Organizations | |
Location page in employer management | To make better use of the screen width in employer management, we have replaced the split page for branches with only an overview page. |
Unique employees in a database | The moment you add or change an employee, it is checked whether that employee already exists within the same employer file. If that's the case, you'll see a warning. |
Secure Messaging | |
Feature Authorization "Add New Participant" | A new feature authorization has been added, "Add New Participants to Dialogue". |
Workflows | |
Ad-hoc trigger execution | A new event has been added within trigger management: "Employers Run Directly (Batch)". |
New trigger condition: Task executed present in workflow | We now also have a trigger condition that checks if the task executed is present in a workflow. |
To have a task event occur in the past or not | We've added an option to make task events expire and not occur in the past. |
Mail for open tasks is manageable | We've removed the template from email templates and added it as a message template. This allows the e-mail that the users receive about the outstanding urgent tasks to be adjusted. |
Renewal of the task execution screen of the renewed file | The visual layout of the page is now made clearer with a more compact view. |
Dashboards & Reports | |
Anonymous invoicing of financial reports | In invoice export reports, no data is shown in the columns employee and file number, if the transaction in question is set up as 'Anonymous invoicing'. |
Report overview organizational, customer and absenteeism teams | The report now shows all members within an absence team role on a node (below each other in a cell), if several are provisioned. |
CAS code reporting expanded to include age category and function group | In order to be able to manage absenteeism in a more targeted way, the report has been clarified in various ways. |
Exact_exportabonnementen extended with organizational structure filter | The report has been expanded with the 'Levels to show' filter. This can make the organization part selection within the report easier. |
API's & Webhooks | |
API's campaigns | Data can be retrieved for campaign types, campaigns, and assignments. In addition, it is possible to add campaigns and assignments. |
XS MODULES | |
Forms | |
Questionnaire management in a new style | Questionnaire management has been adapted to the new style, so that the appearance of the system remain as consistent as possible. |
1. General
Thursday January 23, 2025 we will take another release of Xpert Suite into production with a number of bug fixes and functional changes. If you have any questions after reading this release note, please contact the Xpert Desk. Enjoy reading!
Next planned release: for fast-track customers Wednesday 19 February (release 'Achilles'), for slow-track customers Thursday 27 March 2025 (release 'Aspidochelone'). This schedule is subject to change. The full release schedule 2025 can be found here.
1.1 Abaia
Release Name | Abaia |
 |
Did you know? |
Abaia is a mythical creature in the folklore of the Ashanti people in Ghana, West Africa. It is often described as a giant, snake-like creature that lives in the region's rivers and lakes, particularly in Lake Bosomtwe.
In Ashanti mythology, Abaia is sometimes associated with water spirits and is seen as a guardian or protector of the aquatic ecosystem. It is also considered a deity by some, and sacrifices and rituals are performed to appease Abaia and ask for favors to ensure safe journeys and a bountiful harvest from its waters.
Abaia is just one of the many mythical creatures and spirits that appear in the rich folklore and mythology of various African cultures. These beings often have symbolic and spiritual significance within their respective traditions. |
2. Product Life Cycle Management
2.1 Introduction
The development of Xpert Suite started in 2003 and since then the platform has been continuously developed and innovated. Due to the modular construction, parts of Xpert Suite can be renewed and improved. Unlike other suppliers, it is therefore never necessary to rebuild the entire platform integrally, which prevents possible transition and migration problems.
Thanks to our active Product Lifecycle Management, Xpert Suite remains a state-of-the-art software platform. We realize that technological advances are essential to remain the most secure platform on the market and to take full advantage of new opportunities.
To ensure that the functionality of Xpert Suite continues to meet your needs, we focus on both technical and functional development. In addition to refreshing the underlying code, we regularly add new options that optimize the use of our platform. These improvements are made available through our regular, nine-weekly releases.
In some cases, it may be necessary to carry out (part of) the transition manually, for example with design aspects, links or updates of underlying technology. We support our customers as much as possible and expect the functional managers to be involved in these processes in a timely and proactive manner.
The phases of an End of Life process indicate how far a transition has progressed and what the requested action is:
Projectfases Xpert Suite | |
Phase 0 – Development | The developers of Otherside are designing and developing new functionality.
There is no schedule yet for when this functionality will be available and the old one will be archived. |
Phase 1 – Available | The new functionality has been tested and is available.
If an automatic transition is possible, it will be performed at release. Otherwise, functional managers can start using the new functionality (in phases). Our advice is not to postpone this. |
Phase 2 – Transition | A hard end date has been set for archiving the old functionality. Functional managers must actively work to complete the transition on time. |
Fase 3 – Archivering | The transition to the new functionality is being completed.
The old functionality will be permanently archived after the deadline and will no longer be available on the set end date. |
At Otherside at Work, we strive for a smooth transition for every change. We understand that clear planning, plenty of time for the transition period and clear instructions are of great importance. We will therefore do everything we can to safeguard these elements and to ensure that the transition process is as smooth as possible.
By means of phasing and well-defined end dates, we provide clarity about the transition phases. We understand that time is a crucial factor in change, which is why we ensure that sufficient time is available for a structured transition.
Our instructions will be clear and understandable, so that the functional managers are well prepared for the changes. Together, we are committed to not only making Xpert Suite a state-of-the-art platform, but also maintaining it.
2.2 End Of Life Projects
2.2.1 Overview of current End Of Life Projects
Look for an overview of ongoing projects here on the XSC.
Please note! Each of the End Of Life projects has an impact.
This includes informing the organization and end users about a different way of working, different appearance or manual management actions that must be carried out to successfully complete the conversion.
Check out these projects and get started with the necessary actions as soon as possible! This gives your organization the opportunity to get used to it in small steps and gives us the opportunity to process any feedback in a timely manner.
2.2.2 New Xpert Suite theme
Like we announced last year, the new theme will be in production from this release. It will be live on the acceptance environments from 20/09 and after collecting feedback it is now suitable for release.
Why this change?
The new theme should ensure that:
- The Xpert Suite looks calmer.
- Information is displayed more clearly.
- There is a better foundation so that we can display future software more consistently.
- The basis of the application becomes much more neutral so that we can apply a better colour and contrast balance.
- There will be less differences between your own corporate styling and the standard application styling, creating a uniform look & feel, and making instructive videos and documentation from Otherside Software more recognizable.
What will be changed?
See video for impact: https://youtu.be/_ZAi5HXV88w
From:
To:
Management before:
Management now:
Future
In the future, we will use this basis to implement several design improvements.
3. XS Core
3.1 Accounts
3.1.1 Information logged-in user
Within the top bar of the Xpert Suite, information is shown from the logged in user.
Why this change?
This makes it clearer which account is logged in. This is useful for users who have multiple accounts, or if you have multiple users working on a single PC.
What will be changed?
The initials of the logged-in user appear in the top bar. The current questions, settings, and logout button are reflected in this menu and are removed from the sidebar.
3.2 Organizations
3.2.1 Location page in employer management
To make better use of the screen width in employer management, we have replaced the split page for branches with only an overview page. In the future, we will also apply this to other tabs in employer management.
3.2.2 Unique employees in a database
Why this change?
It can happen that an employee is created twice, while that was not the intention. This can result in a file being kept in two places or reports being incorrect.
What has changed?
The moment you add or change an employee, it is checked whether that employee already exists within the same employer, based on the BSN (the Netherlands), the RRN and/or the Stamnummer (Belgium) or the SSN (Sweden). If that's the case, you'll see a warning:
Please note: if a user wants to add an employee who already exists and the user does not have an authorization for that existing employee, this message will not appear. For that user, it is as if the employee does not yet exist in the Xpert Suite and the notification is not shown.
3.3 Secure Messaging
3.3.1 Feature Authorization "Add New Participant"
Why this change?
It often happens that external participants are accidentally created while there are also internal participants. The result is that a participant then logs in to see his/her conversation and there is nothing. In addition, this can also cause pollution as external participants are incorrectly created. Therefore, it is now possible not to let users create new participants so that they can only send messages to the participants who are already known.
What has changed?
A new feature authorization has been added, "Select external participants in dialogue". This can be set within the user management for the dialogue authorizations. This is enabled by default for all users. When a user does not have this authorization, they can only select internal users in dialogs and not external users or external collaborators. In addition, the 'Messages only' option will disappear in the dropdown when the user clicks on the 'Add new participants' button. Here are only the other options. Are there no other options? Then the 'Add new participants' button will disappear.
3.4 Workflows
3.4.1 Ad hoc execution of triggers
Why this change?
Sometimes it is useful to be able to perform certain actions that the triggers can perform as a bulk action over a large group. In this case, we were looking for a way to start a process for all employers in an employer group at the employer's file object. Further extensions of these types of events will continue in the future.
What has changed?
A new event has been added within trigger management: "Employers Run Directly (Batch)". Triggers of this type of event have an extra button added: 'Save & Run'.
This allows a trigger to be set up within the context of employers. By clicking on the 'Save & Run' button, the trigger is immediately called. For this functionality, the trigger condition "Employer is in Employer Group X" has also been made suitable for batch events.
3.4.2 New trigger condition: Task executed present in workflow
Why this change?
We already had trigger conditions that check whether a task is present or in progress in a workflow, but no trigger condition yet that checks whether the task is present in a workflow.
What has changed?
We have now added this condition: Task X executed present in workflow.
3.4.3 Whether or not to let a task event occur in the past
Why this change?
This change can best be explained by means of an example. Suppose you have the following setup:
- A task (on day 0 in the process): send questionnaire
- A task event (14 days after the start day of the above task): Send reminder
If you start the process 14 or more days in the past, you will get the situation that both the questionnaire and the reminder are sent immediately when the program starts. After all, the start day of the task is in the past, and the task event looks at the start day of the task. Then someone receives both the questionnaire and the reminder for it at the same time.
What has changed?
To prevent the above situation, we have added an option to make task events expire and therefore not occur in the past. This can be set per task event via Management > Task Libraries > Task > 'Events and Escalation' Panel.
By unchecking this option, you can prevent an event from happening when the start day of the task event is in the past. This can occur when a process is started in the past or when a task comes into the process by means of a trigger with a start day in the past.
By default, the task events do take place in the past, so this option is checked for all existing and new task events. If you don't want the task event to take place in the past, uncheck this.
3.4.4 Mail for open tasks is manageable
Why this change?
Within (currently classic) user management, you can check 'Email user for urgent tasks' for a user and indicate how often this should be done (daily/weekly/monthly/only on working days). This included an email template in the new administration (TaskAlertService), but this template could not be managed.
What has changed?
We've removed the template from email templates and added it as a message template (Manage > Service > Message Templates). This allows the e-mail that the users receive about the outstanding urgent tasks to be adjusted. The message template can be found under the new folder 'Open tasks'.
3.4.5 Renewal of the task execution screen of the updated file
Why this change?
The first version of the screen to perform tasks in the renewed file had been outdated for a while now. The screen did not yet use the optimized components that we developed for the renewed consultation screen. This made the page less easy to use. This page is not yet used by most customers as it is part of the renewed file, but for the few customers who already use it, we have now brought the task execution and consultation hours closer together.
What has changed?
The layout of the page is now made clearer with a more compact view. Also, the list of actions that must or can be performed is clearer:
3.5 Records
3.5.1 Announcement of changes to the transparency of confidential notes
Why this change
At a contact moment, you can record a confidential note. We found that users who have the authorization for 'Confidential notes (contact moments)' can only view these notes if they are on the overview document 'Contact moments overview' (Management > Application settings > Overview documents).
Users who have medical rights in addition to this authorization can see the confidential note on other overview cards, but users without medical rights cannot. That is not consistent, so we want to rectify this.
What will change?
In the next release, 9.4 Aspidochelone on March 27, the confidential notes will always be visible to users with the authorization 'Confidential notes (contact moments)'.
It is important to check how your setup is currently for the confidential notes. Realize that all users without medical rights but with the authorization 'Confidential notes (contact moments)' may be able to see more from the next release than they do now. |
- Verify that the correct users have the confidential notes authorization.
(Classic management > User > Page 2 > Confidential note (contact moments). - Check the various overview cards to see if it is right that the confidential note is checked as a source. (Management > Application Settings > Overview Documents)
- Check who is authorized for the summary documents where the confidential note is checked as a source. (Classic Management > User > Page 2 > 11. Medical Protocol Module > Medical Documents or from the overview document itself: Classic Management > 11. Medical Protocol Module > Medical Documents > Set Authorizations (right mouse click)).
3.6 Dashboards & Reports
3.6.1 Anonymous invoicing of financial reports
Why this change
In financial reports, the 'Anonymous invoicing' checkmark was not always taken into account within the design of the price categories.
What has changed?
In invoice export reports, no data is shown in the columns employee and file number, if the transaction in question is set up as 'Anonymous invoicing'.
3.6.2 Report Overview of organizational, customer and absenteeism teams
Why this change?
When setting up case management teams, it has been possible for some time to assign multiple users to a node within the organizational structure for a certain absenteeism team role. This had not yet been included in the report 'Overview of organizational, customer and absenteeism teams'. This report provides an overview of the organisational structure with the associated absenteeism teams and the number of (in)direct employees per organisational unit.
What has changed?
The report now shows all members within an absence team role on a node (below each other in a cell), if several are provisioned.
3.6.3 CAS code reporting extended to include age category and function group
Why this change
In order to be able to manage absenteeism in a more targeted way, it is desirable to be able to split the diagnoses and causes of absenteeism by age category and job group. In addition, company doctors indicated that the figures were not always clear to interpret.
What has changed
Therefore, the report has been clarified in several ways. For example, by showing results immediately when opening the report, adding an explanation to the report that can be opened from the main screen, and showing the full description of the CAS code by default (and not just the code itself).
In addition, four tables have been added around age group and function group. It is now clear whether certain diseases or complaints are more common in a specific age category or job group. If no CAS or CVO code is registered for an absence process, the number 'not entered' is shown.
In addition, it is shown whether there are many work-related causes of absenteeism in a certain age category or job group.
This report can only be accessed by a user with medical rights. In addition, only the routes of employees for which the logged-in user is authorized are shown. This report is enabled by default in the Statistics folder 'Medical reports'.
3.6.4 Exact_ExportAbonnementen extended with organizational structure filter
Why this change?
The report Exact_ExportAbonnementen had only two of the default organizational structure filters.
What has changed?
The report has been expanded with the 'Levels to show' filter. This can make the organization part selection within the report easier. The report is now more in line with the generic effect of the standard reports.
3.7 API's & Webhooks
3.7.1 API's campaigns
Why this change
To ensure that external parties can also call and create campaigns, a number of new API calls have been made possible within this domain.
What has changed?
Data can be retrieved for campaign types, campaigns, and assignments. In addition, it is possible to add campaigns and assignments.
An overview of all APIs that are currently available can be found via https://api01.xpertsuite.app.
3.7.2 Create an employee API
The employee API only had limited functionality, it is now being expanded to include the creation of Employees, the ability to edit the employee number and external employee ID separately, and the updating of the employee's contact information (email and phone numbers).
3.7.3 Calenders API
It was already possible to retrieve appointments via the call of an API, only you could retrieve the appointments of an entire day. An extension has now been made that specific data can be retrieved based on the appointment id. In addition, all Event APIs also include the call request id.
In addition, two new APIs have been added. One to retrieve appointment options, and one to schedule appointment options. These APIs follow the same behavior as the planning assistant.
Retrieving the appointment options:
Scheduling based on the appointment options:
3.7.4 Calendar appointments webhooks
Within interfaces, there are possibilities to set up webhooks that send a signal to an end point. From now on, it is possible to send a signal via the webhook when creating or editing a calendar appointment. In the case of a create and update, extensive appointment data is sent. In the case of the other statuses, only the appointment id is sent.
3.7.5 Assessment report webhooks extension
The assessment report webhook has been expanded so that it sends more information when an inspection statement is added. This now sends the same data as what can be retrieved via the API. In this case, in addition to the existing data, the code of the inspection declaration type and the consultation type id.
4. XS Modules
4.1 Forms
4.1.1 Questionnaire management in a new style
We have adapted the Survey management to the new style, so that the appearance and appearance of the system remain as consistent as possible. This adjustment has no functional impact.
