The semantics of the write protection functionality has been modified.
When defining a write protection on a property, the write protection will affect all controls bound to that property. Previously, only controls defined in the sub tree of the "write protection" node were affected. This change was made to reduce ambiguity in some situations, and to allow for cleaner separation of UI and permission-related code.
If you have both read-only and read-write use cases in a component, you can define a so-called proxy property to build a read-only proxy property.
In versions up to 6.1, the internal data storage allowed for Boolean-typed values to be NULL. This is no longer the case, and the C# non-nullable type System.Boolean is now used.
WebSQL expressions such as IsNull(BooleanFunction(), true) are now considered invalid and will generate the following compiler error:
"The expression is of type System.Boolean and is never NULL."
Previous versions included a "heartbeat" functionality to keep a user’s session open as long as the browser window was open. This was implemented by sending a “ping” from the browser to the server. As this may cause heavy server load in certain scenarios, this feature has been removed.
As a consequence, the session timeout configured for the web application will now cause inactive sessions to time out, even if the user’s browser window is still open.