23-05-044
Release notes - Selfpoint3 - stable-23-05-044
Bug fixes
Unable to use the name of a deleted process when creating a new one
New processes could not be given names that belonged to a process that had been deleted. This was caused by processes not being properly unpublished when they were deleted. This issue has now been fixed.
Removed request body limits on emails sent via Microsoft Graph API
Emails with files attached in the email request body often threw a max body limit error. This was caused by a limit on how large the request body was allowed to be. This only affected emails that were sent using the Microsoft Graph API. This limit has now been removed with the recommendation to instead limit the amount of files and size of the files that users can upload inside of a form. This can be done in the FileUpload components setting.
Error when accessing mail logs in system center
When trying to access mail logs in the system center tab the user was some time met with an error saying something similar to âCannot destructure property âfromâ of tâ. This bug that was causing that error to be thrown has now been adressed and fixed.
Labels of empty checkboxes showing in summary and PDF
Labels of Checkbox component showed up in summaries and PDF files even do no value were selected in component. This happened when values had been selected and then deselected and was caused by a bug in how the component value was interpreted in summary and PDF files after values had been deselected. This bug has now been corrected.
Component name no longer default for missing label
In the Checkbox, Radio, Dropdown and Input components when a label was missing the component name was displayed instead in PDF files. This has been changed so that no label is displayed when no label is set.
New & Improved
Generate PDF/A-1B compliant PDF files
There has been a new setting added in the effect âDocument/generatePDFâ labeled âPDF/Aâ. When this is enabled the effect will generate PDF files that fullfil the PDF/A-1B requirements for long term preservation.
GrandID - removed personal number input
In the latest release build the GrandID integration for login and signing were updated to conform with the âsĂ€ker startâ changes that were made by BankID. These changes removed reliance on personal number for user authentication. To be able to make the transition as smoothly as possible the old GrandID integrations were still supported in the previous release which meant that the personal number input remained in the login component by default, with the option in the component settings to remove it. Now the personal number input has been permanently removed since the old GrandID integrations will no longer be functional and therefore not be supported.
The requirement on having a view with a âcloseTabâ component for the GrandId integration to redirect to has also been removed. That view is now built into the platform itself.
InputTable sum displayed in PDF files
When the âsumâ option is enabled for a column in the InputTable component the sum of the entered values in that column will now be displayed in PDF files as well.
Removed change user button from GrandID component
The button âchange userâ has been removed from the GrandID component since this functionality is no longer supported.
Inline CSS added to more components
We have done an overhaul of the inline CSS functionality in our form and view components to make sure that the function works in the components that has the setting. As part of this the inline CSS setting was temporarily removed from some components. We have now re-added the setting to multiple components and added it to a few new ones.
Last updated