Recently, Dennis has published a huge list of changes introduced in XAF documentation in the previous major update (16.2). In this post, I would like to overview another set of changes in XAF documentation introduced with the 16.2.4 minor update of XAF.
Dashboards
This new topic lists tips and tricks you can use to improve performance and reduce memory consumption in cases when a dashboard is bound to a large collection of objects.
This new topic describes how to specify the maximum number of records to be retrieved from a data store in the Dashboard Designer.
This new topic describes how to customize the DashboardDesigner control used to create and modify dashboards in WinForms XAF applications.
This attribute specifies whether end-users can create dashboards for objects of the attribute's target type.
Reports
In this new tutorial, you will learn how to add the Reports V2 Module for your mobile application using the Application Designer and allow users to download reports.
This new example demonstrates a platform-agnostic approach to accessing the ExportOptions object, which stores the document export options for different formats.
A code snippet demonstrating how to implement the CustomPreviewForm.ShowReport method is added.
Web UI
This topic now mentions that it is possible to customize the new web UI using the ASP.NET Theme Tools (ASP.NET Theme Deployer and ASP.NET Theme Builder),
This new topic details the approach of customizing the default theme mentioned in the previous topic.
This new topic describes the abstract base class for Controllers that create custom Action items, and links an example on how to create a custom Action with a custom control in an XAF ASP.NET application.
This class provides extension methods for Actions in ASP.NET applications. These methods introduce client script support.
Miscellaneous
The recommended approach to accessing the Property Editor's control has been changed, since we have detected issues with the previous approach when using the Reset View Settings Action.
The code snippet in this topic now demonstrates that it is possible to bind an enumeration property to a database directly, without the use of intermediate hidden integer property.
A recommendation to ensure that the EntityFramework.dll assembly is available is added.
A table providing the default values and descriptions of the time periods specifying how frequently the service checks the database is added.
Validation may take significant time when an object to be saved exposes a large collection of aggregated objects. This topic now provides an example on how to cancel validating the aggregated objects that are not updated in the current transaction.
The complete list of changes is available at
No comments:
Post a Comment