Reports as Email Attachments, Data Views without Extenders, Azure SDK 2.4

Monday, August 18, 2014PrintSubscribe
Reports as Email Attachments, Data Views without Extenders, Azure SDK 2.4

Code On Time release introduces the following features and fixes.

  • Implemented support for attachments in Email Business Rules. Multiple xml tags <attachment/> can be specified in the body of the email template.
  • Added SMTP settings to Features page of Project Wizard
  • Report handler now supports static method Report.Execute to enable generation of report data on the server. The method accepts filter, sort expression, controller, view, template name, and output format as parameters.
  • SQL business rules can generate emails. This allows creating multiple complex emails with optional attachments using the full power of SQL dialect of the database engine.
    1) First, a business rule must set EnableEmailMessages property of the business rules class.
    2) Next, another business rule executing in the same sequence will return a list of data rows with columns titled as "To", "Subject", "Body", etc. to produce a list of outgoing emails.
  • Desktop and Touch UI now support parsing of "data-" attributes to enable initialization of data views from user controls without using server-side tags. This feature will be the core capability in virtual pages. We are also considering replacing DataViewExtender references with the new “data-” attributes in the generated pages. For example, a master detail relationship between Categories and Products can be declared with this snippet of XML:
    <div id="categories" data-controller="Categories" data-show-in-summary="true"></div>
    <div id="products" data-controller="Products" 
        data-filter-fields="CategoryID" data-filter-source="categories"></div>
  • Generate from SQL will include byte fields if "base Table Name" is specified. Base table name will be used to create the controller to ensure the labels make sense.
  • Updated "Generate From SQL..." function to add up to 1000 data fields to grid1.
  • Added ability to "not create controllers automatically" when creating a new project. This will create a database object filter of "__none" and will not create any controllers.
  • If multiple views are available, then page header is not displayed in grid/list below the tabs representing view names in Touch UI apps.
  • Touch UI recognizes data-content-framework attribute on custom pages to enable upcoming support for built-in CMS (content management system). The future supported values are "bootstrap" and "" (empty string).
  • Custom pages do not fire appscroll events to improve performance of long “bootstrap” pages.
  • Wide and Tall pages will disabled sidebar and page header in Touch UI applications.
  • First virtual page of the data app will not display  a page header
  • Custom controls can use data-page-header attribute to set up the text of the page header in Touch UI apps. The page header is inherited from activator label (if any) and will not be displayed if it matches the first page.
  • Azure SDK 2.4 is now supported in Azure Factory project type.
  • Implemented enhanced processing of Azure SDK references to prevent duplicates created after Azure SDK upgrade. Azure Factory project do not include a reference to Azure Storage for Azure SDK 2.4. It must be added manually when needed.
  • Negative search with quick find now requires a space in front of the sample. So the search sample "to-do" will not be treated as "positive 'to' and negative 'do'".
  • Moved resetting of Result.Canceled to beginning of SelectedValue loop to allow PreventDefault on each individual selected row in business rules executed for data view with multiple row selection.
  • Report handler uses a more robust method of figuring the base URL of application to ensure correct image URLs in reports.
  • Application framework adds "order by row_number__" to "SELECT" requests to ensure consistent results on multi-processor machines running SQL Server. Thank you Patrick Saunders and fgary6861!
  • The contents of "virtual" pages marked as data-app-role="page" is wrapped in a div with class app-page-content. This significantly improves the rendering of Bootstrap content pages in CMS.
  • Touch UI: Settings menu displays "Settings" label.
  • Touch UI: Action Group menus of actions display header text of action group as a header for the panel.
  • Touch UI: Method $ navigates to a virtual page. The method must be used when programming custom virtual pages to complete navigation.
  • Touch UI: The framework will not auto-enhance virtual pages marked as data-enhance="false".
  • Touch UI: Custom user controls can implement "delayed" transitions to pages if remote data is required to display the page. The tutorials are coming up this week.
  • Touch UI: Action groups with child items are displayed on the sidebar.
  • Property "field" can be used to reference field names when configuring filters for and $app.execute methods.
  • Method $app.execute will execute "Select" command if a command is not specified. It will also use "grid1" as the default view Id.
  • Data controllers based on Result Sets produced by business rules will work correctly with field names that contain non-alphanumeric characters or starting with numbers.
  • Touch UI: User controls without activators do not have an empty link on the "main" user interface page.
  • Added null field check for negative quick find searches.
  • Generate button in Project Designer will always be shown if "Browse" is hidden.
  • Fixed DotNetNuke project file to create Web.*.config files in /WebApp, not /Sandbox folder.
  • Project Designer's "Generate" button will be hidden if User Interface = Touch UI.
  • Touch UI: View selector options in context menu will synchronize with the view selection tabs of grid/list.
  • Modified "Data Controller" construction selectors on "Database Connection" page.
  • Fix the bug causing Quick Find to fail if "," without a following query sample are entered.
  • Select "includes" / "does not include" filter in advanced search bar if another search criteria is present will not throw an exception in Desktop UI.
  • Fixed the spelling with incorrect processing of map-latitude and map-longitude tags in Touch UI apps.
  • Included new translated resources in hr locale. Thank you uremovic!
  • Updated lookups to use sort expression of view.
  • Moved execution of ControllerAction methods into "InternalExecuteBusinessRules" method to ensure parity between those methods and business rules.
  • Minimized simultaneous appearance of multiple progress indicators in Touch UI apps.
  • Enhanced visual appearance of Dedicated Login in Touch UI.
  • Touch UI:  Summary views are refreshed only if they are visible on the page and are in the direct sight of a user.
  • Negative search uses NULL value check on fields to ensure correct output. Previously presence of NULL values in a data row was causing exclusion of correct “negative” data rows from the output.