The grid control now supports a new "list view mode" that supports mobile devices.
The grid control will render both table views and list views of the same data. Using CSS media queries, only one of the views is displayed at any given time, depending on the display size.
The list view mode can work in different ways, which can be defined on every grid.
If you need to disable list view mode globally for all grids, you can set the VI_Common_GridListViewDisabled configuration setting to "true".
If you have defined any grid controls in custom code, or if you have made any modifications to existing grid controls, it is strongly recommended that you test the affected forms on mobile devices.
This version of Secure Token Server (STS) is a rebrand and is not backwards compatible. It contains breaking changes for any integrators.
The following is an overview of changed settings.
Base type for Provider Configurations:
Built-in Provider Configuration types:
Base type for Claim Definitions:
Built-in Claim Definition types:
OData Configuration setting annotations:
Login page CSS class name change to .defenderCloudDiv.
Days until password expires claim type changed to urn:rsts/daysUntilPasswordExpires.
Encrypted password claim type changed to urn:rsts/encryptedPassword.
The Windows Service name changed to RedistributableSecureTokenServer.
The Windows Event Log name changed to Secure Token Server.
The Event Log Source names are RSTS and RSTS Audit. If you had written an RSts.exe.config file with TraceListeners in it, you would change to:
<source name="RSTS" switchValue="All">
<source name="RSTS Audit" switchValue="All">
The Windows Performance Counter application category name changed to STS. And the providers category is just STS Providers.
The default value of the STS Issuer Name setting is urn:RSTS/identity.
The default SSL certificate (if one doesn't already exist) and Signing certificate is now CN=Redistributable STS Demo.
The file Default.aspx is no longer being installed. Any bookmarks that directly point to this file are no longer valid.
This change has been made because the software updating mechanism cannot manage updates for this file.
The Web SQL sqlsearch functions are used to build WHERE clauses to filter a table by a search query. In the past, these filters were always evaluated by the database server. These functions now use the external search index where available.
The search results may be slightly different due to syntax differences between SQL and Lucene. The database filter functionality is only provided as a fallback and should be considered deprecated.
It is recommended to index all columns that were previously used in sqlsearch functions. To do this, set the "Index weighting" property on the column using the Designer tool.
If at least one column of the specified table is indexed, then the search index is queried. Otherwise, the table is filtered on the database server using a LIKE query, using the columns that are part of the table’s display pattern. (The search column configuration in Web Designer is not used anymore.)
If the column is indexed, then the search index is queried. Otherwise, the SQL Server will filter the database using a LIKE query.
It is advised to test any usages of the sqlsearch functions in custom code after migration