In line with the regular schedule, this version will be released on Wednesday 14 December be made available to all test environments. 2 weeks after that, on 28 December, this version will become available in production.
What have we added?
- You can from now on import mails from Office 365 mailboxes! This allows an email to be automatically converted to a ticket, or if it is a response to an existing ticket, added to the ticket. You can also choose which folder to import from. Currently, there can be a delay of up to 5 minutes between the mail coming in and the actual import.
Neoforce looks at the subject of the email to determine whether it is a response or not. If an existing ticket number is in the subject, then it is a response.
Note: The option is available from a new admin page, so you need to give yourself permissions to use it. - We now offer out-of-the-box support for Single Sign On based on Microsoft accounts! We had been doing this for a while, but that required the help of support, and work in Azure Active Directory.
So from now on, this will be a thing of the past and you will be able to work from Administration > General/App > Security settings > Login settings Activate Single Sign On.
Note: This also means that we will soon say goodbye to the current method of Single Sign On. We will talk to customers who use it and pick a date together. - Time registration for tickets has been improved! You can now set that you want to make time registration mandatory for new tickets or changing tickets, for example when changing the status or adding a comment.
- You can now delete ticket templates. Of course, you need to have authorisations to do so.
- For datasets, you can hide the contents of a field by default.
- You can now also number the ticket number of subtickets based on the number of the main ticket. This way, you can immediately see which main ticket a subticket belongs to.
- Datasets tabs may have a different layout. If not set specifically for a tab, the schema setting will be used.
- You can now automatically create a ticket about the asset from an asset (datasets). You can find the link under the triangle next to [New].
- Subtickets and main tickets can now share files with each other. This way, you maintain overview and thus see files linked to other subtickets or the main ticket everywhere in the tickets. (This is an optional setting).
- If you are using buckets, you will see that the subtickets are now visible there as well and can also be edited from the main ticket.
What did we change or fix?
- The user experience of buckets within tickets and datasets (if enabled).
- Various minor changes to the user interface.
- Some spelling errors in translations.
- Improvements related to system speed.
From 2023, a different update strategy.
As you could read in our previous article, from next year we will be using a different method of releases. You can read all about it in this article.
Thank you very much for the pleasant cooperation.
To conclude, it remains for us to thank all our customers for the pleasant cooperation in 2022.
We would like to thank you for all the feedback, ideas and all the contributions. We would also like to thank you very much for trusting us.
On behalf of the entire Neoforce team; happy holidays and a happy new year!
