24-04-002

Release notes - Selfpoint3 - rc-24-04-002

Bug fixes

Footer and header parsed incorrectly when generating empty PDF

The function for generating empty PDF files for a given form often failed and resulted in just an empty object literal being returned. This was adressed in a previous release but the problem still remained. The problem had to do with the new header and footer function that was introduced in rc-23-10-001 not being parsed correctly when generating empty PDF-files That problem has now been corrected and the function should now work as intended again.

Links forces line break in mail body

Adding a link to the body in a mail template forced a line break. Which made it impossible to have links embedded inside of regular text. This bug has now been fixed.

Microsoft Graph emails not working with new effect Mail/SendToGroup

There was issues with sending emails via Microsoft Graph using the new effect "Mail/SendToGroup" that was introduced in the previous release. Those issues has now been addressed and corrected and the effect should now work with emails sent via Microsoft Graph as well.

New & Improved

Copy registers

Registers can now be copied. The function can be found in the admin plattform on the register page.

When copying a register it is possible to choose between copying it with or without register data.

Summary component in views

The component “Summary” has been added to views. This means that a summary of a formData object (ticket) can be displayed in views, which can be useful for example on signature views to let users view a summary of what they are signing. The component can be found in the component selector inside of the view builder.

Created and updated readable in formData

When building a form the properties “created” and “updated” can now be read from formData. This means that using “formData.created” or “formData.updated” inside of handlebars will now retrieve those values dynamically from the tickets formData. For example an “Input” component can be configured to have the default value {{formData.created}}. That input will then display the date the ticket was created inside of the ticket itself.