Blog: Posts from May, 2012

Labels
AJAX(112) App Studio(7) Apple(1) Application Builder(245) Application Factory(207) ASP.NET(95) ASP.NET 3.5(45) ASP.NET Code Generator(72) ASP.NET Membership(28) Azure(18) Barcode(2) Barcodes(3) BLOB(18) Business Rules(1) Business Rules/Logic(140) BYOD(13) Caching(2) Calendar(5) Charts(29) Cloud(14) Cloud On Time(2) Cloud On Time for Windows 7(2) Code Generator(54) Collaboration(11) command line(1) Conflict Detection(1) Content Management System(12) COT Tools for Excel(26) CRUD(1) Custom Actions(1) Data Aquarium Framework(122) Data Sheet(9) Data Sources(22) Database Lookups(50) Deployment(22) Designer(177) Device(1) DotNetNuke(12) EASE(20) Email(6) Features(101) Firebird(1) Form Builder(14) Globalization and Localization(6) How To(1) Hypermedia(2) Inline Editing(1) Installation(5) JavaScript(20) Kiosk(1) Low Code(3) Mac(1) Many-To-Many(4) Maps(6) Master/Detail(36) Microservices(4) Mobile(63) Mode Builder(3) Model Builder(3) MySQL(10) Native Apps(5) News(18) OAuth(9) OAuth Scopes(1) OAuth2(13) Offline(20) Offline Apps(4) Offline Sync(5) Oracle(11) PKCE(2) Postgre SQL(1) PostgreSQL(2) PWA(2) QR codes(2) Rapid Application Development(5) Reading Pane(2) Release Notes(183) Reports(48) REST(29) RESTful(29) RESTful Workshop(15) RFID tags(1) SaaS(7) Security(81) SharePoint(12) SPA(6) SQL Anywhere(3) SQL Server(26) SSO(1) Stored Procedure(4) Teamwork(15) Tips and Tricks(87) Tools for Excel(2) Touch UI(93) Transactions(5) Tutorials(183) Universal Windows Platform(3) User Interface(338) Video Tutorial(37) Web 2.0(100) Web App Generator(101) Web Application Generator(607) Web Form Builder(40) Web.Config(9) Workflow(28)
Archive
Blog
Posts from May, 2012
Wednesday, May 23, 2012PrintSubscribe
Layout: Classic

The Classic layout displays the master data view at the top of the page. The child data views display underneath in their respective tabs.

Customers page with a Classic layout in Code On Time Project Explorer.

When a user first accesses a page with a Classic layout, only the master data view will be visible.

Customers page with only Customers grid visible

If a master record is selected, then a container will appear under the master data view, containing all child data views in their respective tab.

Customers page with 3 child data views each in a tab underneath the master data view with Classic layout.Customers page with 3 child data views each in a tab underneath the master data view with Classic layout.

The child data views display detail records connected to the selected master. If another master record is selected, then the corresponding detail records will be retrieved from the server.

You can control visibility of data views on the page with Visible When and Roles properties.

Wednesday, May 23, 2012PrintSubscribe
Layout: Simple

The simple layout only displays a single data view on each page, with no master-detail relationships.

Customers page with Simple layout displaying only a single data view.

The Customers page from a Northwind web application using Simple layout is displayed below.

Customers page with single data view in a Simple layout.

Wednesday, May 23, 2012PrintSubscribe
Navigation Menus, Role-Specific Data Views

Code On Time release 6.0.0.28 introduces the following features, improvements, and bug fixes:

  • Advanced two-level menus are now available in Premium and Unlimited editions.
     
  • Data views now support "Roles" property to allow additional visibility control. The "Roles" are evaluated on the server and work together with VisibleWhen property.
     
  • Property BusinessRules.UserEmail can be referenced as @BusinessRules_UserEmail in SQL and Email Business Rules.
     
  • Method BusinessRules.AddMailAddresses has been enhanced to accept "loosely" specified list of email addresses separated with comma and semicolon with optional display names.
     
  • jQuery 1.7.2 is now integrated in the client library. The future releases will add support for jQuery UI and JavaScript Business Rules.
     
  • Application framework matches methods with RowBuilder attribute first as an exact controller name match to the requested controller and as a regex match thereafter.
     
  • Page property Title is now optional. If the value is not specified, then the page name is used.
     
  • DotNetNuke Factory will load the projet in correct version of Visual Studio when both VS 2008 and VS 2010 are installed on the same computer when a compilation error has occurred.
     
  • Modal forms will retain scrolling when lookup fields are changed.
     
  • It is possible to reference master views in the visibility expressions attached to all objects.
     
    The implicit master field can be referenced as
     Master.FieldName
  • The explicit alternative is
    view1.FieldName

  • It is now possible to create a soft filter by Null value using SQL Business Rules defined as follows:
     
    if @BusinessRules_Tags is null
    begin
       set @BusinessRules_Tags = 'Tagged'
      set @Region_Filter_Equals = 'null'
    end

    The rule will work with Customers controller in the Northwind sample.
     
  • Method ControllerNodeSet.CreateBusinessRules now support "name" attribute to allow dynamic creation of "named" business rules.
     
  • Removed incorrect reference to aspnet_User controller from the Membership Manager.
     
  • Quick Find will work even if Query by Example is set to "False" on the first field in the data view.
     
  • Fixed the issue with the "soft" filter being require to have a type of "array of objects".