June 2026
You can configure a Grid to keep its first column fixed while the rest of the columns scroll horizontally.
Use this when the first column identifies each row, so that end users can retain context when navigating wider datasets.
The Grid's row link buttons and checkboxes will now stay on screen as the user scrolls horizontally.
This happens regardless of whether the first column is locked or not (see above).
The compute sum setting now also applies to multirow columns. It has been moved from Grid settings to Display settings.
Previously, a multirow always included an "empty" row: a row of controls prefilled with default values. This row became a real entry only after a user edited one of its fields.
This could be confusing. If controls show realistic default values, users may assume the row is already saved as part of the form.
At the same time, having the empty row available allows users to start entering data immediately, without first clicking New row.
The setting Hide row when empty prevents the multirow from adding this "empty" row. The setting Empty state text can optionally display a message when the multirow is empty.
Stored procedures can now be published as MCP Tools. A system can publish multiple MCP servers, each containing multiple tools.
A stored procedure can either work with raw JSON, or have the server handle serialization or deserialization automatically.
The Chat component's Store message call can now act as a mini-Coordinator and call one other menu item - usually a GenAI or a full Coordinator menu item.
This updates the list of chat messages without needing to reload the whole menu item.
The system can be configured to let users stay signed in for extended periods using the LoginKeepUserSignedInDays setting.
There is a balance between convenience and security. We recommend using this feature only in low-risk systems.
You can now configure additional query parameters to be sent with the OpenID Connect authorization request. This is defined per identity provider.
Published web services are typically used for server-to-server integrations.
However, when a web service is intended to be called from a browser, CORS headers are required. These headers inform the browser which origins (websites) are allowed to access the service, helping prevent misuse from malicious sites.
You can now configure allowed CORS origins for published web services.
We've replaced the algorithm that AutoComment uses to determine where a SQL module is called from. The new algorithm is significantly faster. It also detects some calls that the old algorithm did not, and has fewer false positives.
Previously, AutoComment was added directly to the top of each SQL module.
While this ensured the text was always available, it introduced several disadvantages:
dm_exec_sql_text, only the AutoComment block was visible instead of the executing procedure name.modify_date of the procedure changed daily, making investigations more difficult.From this version, comments are stored in a separate database table. When a SQL module is opened with Softadmin® Assistant (for example using the Edit button in the admin interface or the F1 shortcut in SSMS), the comment is retrieved and added above the SQL module definition.
This means that from this version, you need at least SSMS 22 with the latest version of Softadmin® Assistant.
The Database Designer can now create, alter, and drop primary keys.
The Database Designer now has predefined column templates that let you create multiple columns following a common pattern.