Release Notes ✍️ - 10th of November 2020

Modified on Thu, 03 Dec 2020 at 10:21 AM

We are continuously working on improving your experience with Leviy by fixing issues as fast as possible and provide you with new solutions. Here is an overview of all fixes and improvements you can find in our latest releases.

Due to a number of big changes at Apple iOS the version of the App for iOS will be made available a week later on the 17th of November.

What's improved in the Dashboard v9.28?

Fixed choices for creating an issue now also in the Dashboard - To make it easier to create an issue, fixed choices can be set in Leviy for each issue type. With these fixed choices employees spend less time typing, which means issues are created faster and more consistently. This not only saves time but also makes it empowers analysis. These choices are now supported in the Dashboard in addition to the APp. Setting up these fixed choices is an extra service we offer. Do you want to know more about this? Reach out to us for a chat!
From two language settings to one - The language of the App and the Dashboard could both be set for a user. This caused some illogical situations for certain users. We have changed this so that when you set a language preference somewhere, it will be applied in both the Dashboard and App.

Example: An administrator of a Belgian organisation might set Dutch as the language preference when creating a user. This user then sets his language preference in the App to French. This did not change the language in the Dashboard, which meant that this user would for example receive Dutch notification emails from Leviy.

We have changed this so that when you set a language preference somewhere, it will be applied in both the Dashboard and App.
Blocked users removed from the list of a role - In the Dashboard you can see per role which users are linked. Blocked users were also shown in this list. These have been filtered out to provide better insight and to avoid clutter.
Role management simplified - You can set permissions for each role in the Dashboard. Under the Settings permission group, there were permissions called "Roles", "Role - Users" and "Role - Permissions". With these you could define per role if they were allowed to view and manage roles. We have linked this logic to the user types Administrator. hat cleans up nicely!
Organisation settings management simplified - Under the Settings permission group you could also find the permissions for organisation settings, which can be found under Control > Organisation settings. With this you can manage some general settings, such as the name of your organisation, the logo and synchronisation automations. We have linked this logic to the user type Administrator. Want to know more about what each user type can do? Read this article!
Removed view of DKS with most and least errors - The overview page contained a view of the worst and best DKSs. Since the number of errors within a DKS is relative to the number of rooms and elements that have been inspected which this view did not take into account, this did not provide representative insight. For this reason, we decided it was time to say goodbye.
Uniform styling in Files - The styling of some components in Files did not match. We found the problem and fixed it.

What's improved in the App v2.21?

A new font style - We have applied our new standard font style to the whole App to optimise the readability and consistency.
Removed text size - On the Settings screen you could adjust the font size of the App. This was no longer desirable, as an app should now track the text size of the phone settings. From now on, the Leviy App will automatically scale with the desired settings. Want to know more about where to find the text size settings? Read our instructions here.
Incorrect translations - A number of texts on the home screen of the App were sometimes not displayed in the correct language. We found the problem and fixed it.
Support for special characters and emoticons - We have seen that users are increasingly using special characters and emoticons when performing audits. In some cases, this caused problems when sending data. We have made several fixes to fix this and now are able to support these.
Save button disappeared - After adding a photo to an issue or an audit the save button disappeared from the screen. We found the problem and fixed it.

Under the hood

You have probably noticed that this year is all about tidying up. The well-known statement 'A tidy house means a tidy head' is also applicable to software. Although it does not always seem that much has changed from the frontend, in this release we have taken some valuable steps. With these steps, we hope to host you in a tidier, clearer and more user-friendly home in the long term.

Changes for iOS update - Following a required change in Apple iOS, we were forced to make a number of changes to the Leviy App. These changes had a significant impact on the way screens are displayed and data is exchanged between the App and the server.
Multiple email addresses per account completely phased out - Leviy provides functionality to receive email notifications about, for example, for audits or issues. Until about a year ago it was possible to enter multiple email addresses for this. This was hardly used in practice. Since we moved all user management to Accounts, this is no longer possible. However, we still had some tidying up to do for this in the Dashboard.
Cleaned logic around groups - With groups users can be granted access to clients, objects and units. This data is used by many modules of Leviy and that caused a heavy load on our platform. We have improved this step by step and have now realised a more efficient solution.
Cleaned up logic around checklists - For each checklist you can configure who can perform it. This configuration is used in the synchronisation to the App. Some time ago we adjusted the determination of authorisations to make this much faster and more scalable and we have now phased out the database structure of the old setup.
Cleaned up logic around database changes - When making adjustments to the Leviy Dashboard adjustments to the data model also regularly take place. For example to store new data or to speed up the retrieval of data, we use a modern standard method for implementing changes. Until some time ago we also had our own mechanism for this, which we have now completely phased out.
Administration of app versions - In order to improve communication between the App and Dashboard, it is desirable that it is always clear which version of the App is in use. This was not yet the case with various requests from the App to the server. We have not adjusted this to also implement changes and realise optimisations on these points.
Outdated logging solution phased out - In every application something can go wrong from time to time. In order to be able to respond to this correspondingly, it is important to log and monitor properly. An older solution which we used for this was already partially phased out, we have now completely phased it out.
Old data structure cleaned up - When making changes, it is sometimes necessary to keep data in old structures for old App versions or to be able to roll back an update. We came across various data structures that have already been replaced. We have carried out a substantial clearance in this area, so that this no longer gets in our way and that something can no longer be done unintentionally.

What's improved in the API?

Issues API improved - There is increasing interest in integrating Leviy's Issues module with another system where this data is also relevant, or to improve the way people, who use different software packages, work together. For example in a hospital, hotel or school group. Our Issues module already provides a so-called API, which is always written in English. Sometimes the term Notification was used instead of Issue. This caused confusion which is why we resolved this.
Units API improved - More and more integrations are being made between Leviy and other systems to connect the cleaning in real-time to the processes at a location. This usually involves communication at the level of the unit in Leviy. We received a request from a party to provide the (units) API endpoint with a filter option by unit number, to make it easier to check whether a certain unit (hotel room, bed place, soap dispenser, etc.) already exists in Leviy. We have realized this.
Mews <> Leviy integration improved - Our Housekeeping module can synchronise with a hotel using Mews' Property Management System (PMS). This integration works both ways so that 1) the rooms to be cleaned become known in Leviy, and 2) the cleaning statuses of the rooms are communicated back to Mews to provide realtime insight for the hotel employees who work with Mews. Mews informed us of several changes to their APIs, which required a few changes on our side. The integration has been extensively tested by us and by Mews. Ready for the future!

What's going on behind the waves?

First steps in renewing the Units in the App - The Leviy App is increasingly used in the workplace to communicate about the cleaning at locations. Due to this, we see that users are increasingly faced with larger numbers of units. We have also found that in some cases unit-level authorisation is used to filter things out. Instead of such detours, we want the App to solve this itself with filters on assigned units, on unit categories and on layouts (floors, zones, etc.). This requires a thorough renewal of the necessary screens and logic. In recent weeks we have taken the first steps in this.
Restructuring Dashboard - Through a research study, we got a good idea of how we can improve the navigation in the Dashboard to make it more user-friendly. The dot on the horizon is a restructuring of the entire navigation in Leviy, putting all modules together and within reach, enabling us to facilitate common actions with as few clicks as possible. As a first step, we are thinking of an overview/log of all activities that have been carried out (think of issues, audits, tasks, etc.), so that you are immediately informed of the latest information after logging in. We are currently developing various ideas for this.