Serviceware Resources version 8.0 is a fact!

The biggest change in this version is the introduction of the ‘Serviceware Authenticator’, our new identity provider and broker at the same time. With this, it is now also possible to log in with an ADFS or Azure AD account, or with an account of another linked provider such as Google. Of course, the mobile applications have also been adapted to work with this new authenticator, resulting in “Serviceware Resources for iPhone 8.0” and “Serviceware Resources for Android 8.0”.

With the Serviceware Authenticator we are now also prepared for the connection to the Serviceware Portal, with which we want to serve both clients and employees in the near future with widgets that support their most common use cases. For the same reason, we’ve been converting our appointment widget to a portal-ready version 4.0. We have also been working on a new widget, which will allow clients to register themselves as ‘arrived’ once they have arrived at the location where their appointment will take place.

More preparations for the future, but in the area of integration with external systems, has led to the new ‘Webhooks’ functionality. Serviceware Resources is increasingly part of a complex architectural landscape at our customers, where it is no longer just about importing data from supplying systems, but also about sharing our output – such as appointments, registrations and orders – with receiving systems. With Webhooks, we have built the foundation for this.

Of course, improvements have also been made to existing functionalities. For example, the SRO and Map pop-ups have been sped up, following the MRO pop-up in version 7.14. On the session planning board, the performance of the client picker has been significantly improved and new filter options have been added. And the ‘appointments to be scheduled’ list has been revamped to better support the more common use cases.

Test and acceptance environments can be visually marked to better distinguish them from production. And for sharing appointments via Exchange, support for Office 365 has been added. Also, a number of bugs have been fixed again.

Finally, we have replaced the term ‘service schedule’ throughout with the now more common ‘order’. Also, in terms of terminology, we no longer make a distinction between the healthcare market and the service market. A client, a “recipient of a service”, is now called a client everywhere. Even where in Classic the term ‘customer’ was still used in some cases.