In this week's release, we are bringing the following changes and updates to our SaaS customers:
What have we added?
- Reservations can now include accessories.
- Invoices (both final and pro-forma) can be exported to PDF.
- Forms from both the portal and automations now also have a 'date' and a 'date/time' field.
- It is now also possible to delete fields/questions from a form.
- The search pages now also accept the asterisk as a wildcard (in addition to the already existing %).
- Emails sent from actions (e.g. a ticket unsubscribe email) now also show any images. These are embed in the mail.
- Tickets now also show the rating (if available) within the practitioner section.
- You can now use variables within form fields. This allows you to use the value of field in, for example, the title of the created ticket. (Example: ${form.title}).
- Neo4Z now offers brute-force detection against possible attacks. This can be set via management.
- We have started work on the 'automations' module. This allows tasks to be performed automatically by Neo4Z. Think of the automatic creation of new accounts (within Active Directory, for example) from a Ticket.
- Quite a few database optimisations related to sorting, filtering and searching have been added to all tables of the application.
- Objects within application management can now have the same relationship multiple times.
- Actions (management) is split into 'Actions and Triggers'. This allows you to link an action to multiple triggers which also allows you to use OR conditions to trigger something. In addition, you can, for example, reuse emails by linking them to multiple actions.
What did we change or fix?
- Within the admin options, it was already possible to manage all values of selectboxes, for example. This option was called "Lists". From customers, we got the tip to rename it to "Look-up lists". We have done so!
- Several minor spelling mistakes (Dutch)
- Several module options still appeared, and sometimes caused error messages, when the module was switched off.
- Images uploaded via modal (from the WYSIWYG editor) were not always usable.
- Tickets created through a form on the portal did not have a start date
