The February release has been one that the team has been working on since December and we haven't been able to say much about it and that has been so tough but we are finally ready to announce the release of our version one of service desk to paid customers first.
Help Desk (To many features to list them all)
The help desk brings with it so many new features that its hard to list them all, so we will just go over some of the high level features that we are excited about below...
- Allow view only users to put in a customizable help desk ticket, this is currently limited to two categories "General", "Assigned Asset" but in a future release the categories will be customizable by your team as well.
- Custom help desk ticket builder, this is a custom form builder tool that allows for conditional questions to be put in place, we spent almost the past month alone working on just this feature to ensure that it was going to meet all the needs of a demanding user such as yourself.
- Custom ticket status, so you can build out the perfect service desk.
- Adding in help desk fines, for when you you need to charge a fine to an end user on a help desk ticket.
- Help desk reports so you can stay on top of your service desk.
Our custom form builder shown below...
New Fines Filter By Location
Fines are a touchy subject, but based on customer feedback we learned that user of the software needed to be able to run reports for fines based on users locations, and this wasn't possible. Well now it is!
SQL Loader Improvements
Over the months of December & January we made huge strides in decreasing load times of our application by improving our SQL queries to be more performant. We recently learned that this had a small bug for API users where deeply nested data was not returned. This fix allows our SQL to include data no matter how deeply nested and will still be just as performant.
To give you some ideas on the strides that we have made in this area, our p50 response time is now around 500ms for cold response data and when data is in our cache, we are constantly seeing sub 100ms response times for end users across the US.
Improved Developer Efficiency & Dropped Support For IE 11
As an application grows in size keeping developers productive becomes difficult, and our application had become extremely bloated and slow for our development team. We currently use Vue2, and custom class components to run our frontend application and found that we had no migration path to Vue3. With this in mind we decided that the best course of action would be to introduce Vite into our developer and build tooling. This has the upside of saving our developers each around 30min of compile time a day, the downside of this move is that we are dropping support for IE11 in our application. We currently do not see any paid members using IE11 so we do not anticipate this being a problem moving forward but we just wanted to share.