The lowest supported version is now SQL Server 2016.
Login with BankID now uses animated QR codes instead of requiring users to enter their personal identity number. The login now also supports both Mobile BankID and BankID for personal computers, where previously it only supported Mobile BankID.
The BankID login in older versions of Softadmin® will stop working in 2024.
Calendar: Weekdays mode has received a new design.
Users can choose to temporarily hide the calendar item description to fit more appointments on-screen.
Resources have been moved from the top to the side:
The new design also provides optional support for showing start time by using the CalendarDateTime colum instead of the CalendarDate column.
The various textbox with... controls and listboxes have received a new design.
The custom top border has been removed. In many systems the top border was white so you may not notice the change.
There is now support for disabling top links. Normal top links are disabled with their Conditional visibility SQL and top links from Info SQL are disabled by the InfoSQL procedure.
If a top link uses selecteditems then you can choose to have it disabled until the end user selects at least one item.
Controls that have a button in the interface to open a "picker", for example the DateTime control with its date picker, the Colorpicker control with its color picker and the Textbox with dropdown control with its dropdown, have received the new shortcut
alt-down to open the picker with the keyboard.
The Email component now supports sending mail as urgent/high importance/high priority by using the IsHighPriority column. Email clients are not required to respect this: Gmail, most notably, does not.
The Image Process component has gained a new Log error call that it performs when it encounters an unreadable image (usually because it is damaged or an unsupported format.)
File extensions are not always reliable. We have introduced the helper functions SoftadminUtil.Image_IsJpeg and SoftadminUtil.Image_IsPng that you can use as an extra safety net to enforce rules like "Profile pictures must be JPEG" and "Company logotypes must be PNG".
We have added the ability to inactivate individual Azure Service Busses. Inactivation is done on an instance-basis: that is, if you inactivate a bus in development and then deploy to stage then the stage bus will still be activated.
Inactivating a bus for too long may lead to the loss of incoming messages as they exceed their time to live while waiting for a listener to receive them.
You can now generate login links to help pages in the system.