Release Notes

Code On Time release 6.0.0.29 includes enhancements to both code generation library and application design environment.

Generated web applications now support JavaScript Business Rules and Automatic Tracking of Selected Record. The Project Designer has been enhanced with drag & drop and cut/copy/paste  capabilities and offers “Navigate To” window that allows quickly locating project configuration elements.

The following features, enhancements, and bug fixes are included in this release:

• Drag & drop and cut/copy/paste are support for pages, containers, data views, controls, user controls, controllers, and commands. Other project configuration elements will also be enhanced in the coming weeks.
   
• The entire data controller can now be cloned.
   
• Project Designer properties of menu configuration elements can be easily synchronized with Project Explorer.
   
• Navigate To window allows quickly finding project configuration elements.
    
• Code generator automatically combines all JavaScript files found in [Documents]\Code OnTime\Library\_Client\Scripts folder in a single _System.js file. The file is included in the generated web applications of all types.
   
• Automatic Tracking of Selected Record is supported by the client library. Developers can take advantage of selected record synchronization.
   
• New search option $autocompleteanywhere will cause the auto-complete to search anywhere in the field values. By default, the framework searches using "Begins With" operation, which generally performs better, but will not yield partial matches.
   
• Data field property "Search Options" supports $disableautocomplete, $disablesamples, and $disablemultiplevalues options.
   
• Modal form views now support dragging of the header.
   
• View Details shows a modal view that will refresh the original source if changes are made.
   
• "Hidden" fields will be displayed in summary if marked as "Show In Summary".
   
• Master data sheet views automatically set focus on the first cell of the first row.
   
• "Flat" actions will display the action description as a tooltip.
   
• Implemented a fix for Import Processor to ensure that field values that are missing in import file are created to simulate as if the values were entered in the user interface form. Previous implementation has passed the non-blank values only. This makes it possible to implement UPSERT when importing data records.
   
• Code On Time will now pre-process the designer logs before navigating to the data controller summary.
   
• Localizer now takes into account the name of the module/webpart when caching the resource strings.
   
• Project Explorer tab now feature "Home" button that shows List of Pages, List of Controllers, or List of User Controls.
   
• The issue with the left border in AjaxControlToolkit tabs is fixed in all themes.
   
• Sorting on fields with Format On Client = false will not cause a runtime exception.
   
• Method Controller.UserInInRole is now creating an instance of ControllerUtility class to verify the user identity. This allows implementing custom role validation against SharePoint or DotNetNuke user groups.
   
• ControllerDataSource will correctly perform Update/Insert/Delete operations when C#/VB business rules are associated with the data controller.
   
• Component ControllerDataSource will use "=" filter operation if FilterParameter instance has its DBType property set to any value other than Object or String.
   
• Aggregate fields are correctly formatted on the server when "Format On Client" property of a data field is set to "false".
   
• It is possible to specify "about:blank" as the URL of top level pages without breaking the rendering of Advanced Menus.
   
• Context Field Filters now support static filters in the both formats:
  FieldName = 12345 and FieldName='12345'
    
• Decimal parameters are automatically initialized as Decimal(38,10) in SQL Business Rules and SQL action.
   

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".