Web App Generator

The Advanced Search Bar allows the user to combine specific search parameters in order to find data. When the search bar is first opened, the first three data fields in the grid view are displayed.

The end user can change the filter field using the field name dropdown. By default, all data fields that exist in the grid view are searchable. The user can be forced to enter a value in some search fields, while other fields may be suggested as additional options when the search bar opens for the first time. Users can also be prevented from searching by specific fields.

Start the Project Designer. Right-click on Customers / container1 / view1 / grid1 view node, and click Show All Data Fields option.

Make the following changes to the list of data fields:

Save the data fields, and select Browse on the tool bar to regenerate the web application.

When the browser window opens, navigate to the Customers page and open the advanced search bar. The data fields with Search Mode of “Required” or “Suggested” will be displayed initially.

The first field is required, and cannot be changed.

If a search is performed without entering a parameter into required Company Name field, the user will be informed that the field is required.

Fields marked as “Forbidden” are not displayed on the list of fields available for search.

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