Monday, July 17, 2017PrintSubscribe
July 2017 Hotfixes 2

Code On Time release introduces the second collection of July hotfixes described below:

  • Added support for ReportViewer 2016.
  • Trust Origin URI specified for Report Viewer 2016 to ensure reporting DLLs loading correctly after being copied to another machine.
  • Windows Live OAuth Handler wrong redirect URI fixed.
  • App generator “User Interface” option now has "Touch UI + Classic" option. When "Touch UI" is set, no Desktop themes will be generated.
  • URL Hashing in HTML implementation is now fixed.
  • New projects will not permit “space” characters in the name.
  • Reports Viewer version is now a variable stored in the project file.
  • Fixed issues with Report Viewer version not detecting when generating from Project Designer.
  • Home page of the app generator displays the descending order of projects
  • Older ReportViewer references are removed from the VS project file.
  • ReportViewer DLL files are copied to the “bin” folder only when v14 is used.
  • Added MSGraphOAuthHandler implementation.
  • "Login with Microsoft" button appears on login page when MSGraph config entry is present in the site content.
  • Fixed exception in BusinessRules.UserId implementation raised when user is not logged in.
  • Added "IsEmpty" and "IsNotEmpty" to row filter operations. New options can be used in “soft” filters set on the server.
  • Fixed DotNetNuke Factory project compilation issues.
  • Touch UI: Fixed. Multi-select checkboxes are not cleared after Batch Edit.
  • Touch UI: New “Select All” option is displayed when more than one option is available for selection in a basket.
  • Touch UI: Keyboard navigation in the list scrolls the page when item is not visible.
  • Touch UI: Key “Right” goes to the lookup page after selecting “See All”.
  • Touch UI: Last focused field is recorded in the touch.lookup() method to correctly restore input focus when the lookup view is canceled.
  • Touch UI: Blank lookup field shows a popup when scrolled into view.
  • Touch UI: Removed excessive blank space in front of Add Item in empty basket.
  • Touch UI: Calendar is opened in correct position if the date input field has been scrolled into view in IE.
  • Updated app generator to use correct version of MSBuild for VS 2017, 2015, 2013, with MSBuild4.0 as fallback.
  • Touch UI: Command separator is displayed in popup with items for AutoComplete/Lookup.
  • Action with command name Select works correctly after command Update.
  • Fixed issue with Active Directory loading ASP.NET membership provider with no connection string.
  • Dropping/pasting controller view onto page will set the view as well.
  • Ensure "standalone database" checkbox is checked when membership dialog is loaded.
  • Fix for "asp_CheckSchema" exception with custom membership.
Monday, October 27, 2014PrintSubscribe
Prerequisite Verification and Report Viewer Publishing

Code On Time release includes a new feature and two enhancements. 

  • Publishing of Mobile Factory, Web App Factory, and Web Site Factory will also include all required DLLs from Microsoft Report Viewer if reporting has been enabled in a project. Previously this capability has been available only in Azure Factory projects. There is no need to install Report Viewer on the server machines anymore.
  • The new update implements enhancements to the process of prerequisite verification that was introduced in the last update. The app generator detects if IIS Express or Report Viewer are missing on the computer and suggest to download them. The enhancements were made to address issues related to this feature that were reported by several users.
  • We have also enhanced the process of inclusion of combined script file. This feature is available only in Unlimited edition and significantly speeds up the initial download of application pages. All required scripts are combined into one file and compressed. The downloaded file is cached by web browsers for a year. The name of the combined script changes with every release of the app generator and with every instance of publishing. There were several reports indicating that the file name includes incorrect “culture” component in some configurations. We believe we were able to address the issues. If the new release does not correct the issue, then please open a support ticket and we will arrange for a troubleshooting session as soon as possible.

ATTENTION: DotNetNuke and SharePoint developers must request a hot fix that will correct the compilation error present in both and releases. The fix incudes two files:

  1. PageBase.codedom.xslt – copy the file to [Documents]\Code OnTime\Library\Data Aquarium\_App_Code\Web folder.
  2. DataControllerService.codedom.xml – copy the file to [Documents]\CodeOnTime\Library\Data Aquarium\_App_Code\Services folder.

See complete release notes for version to learn about the features that have become available over the weekend.

Saturday, August 16, 2014PrintSubscribe
Reports at Attachments in Email Business Rules

Application framework allows generating reports on the server. This capability makes it possible to produce reports as attachments of email business rules.

Consider the following Email Business Rules implementing a simple notification executed in response to Update command in Categories data controller.

Property Value
Command Name Update
Type Email
Phase After
Port: 587
Password: PASSWORD
EnableSSL: true

From: "Sales Admin" <>
Subject: Category "{CategoryName}" has changed!

Dear Admin,

This product category has been changed.
See attachment for category product details.

System Monitor

<attachment type="report">
<attachment type="report">
    <name>{CategoryName} Products</name>
    <sortExpression>UnitPrice desc</sortExpression>
            <value type="Int32">{CategoryID}</value>

Note the two attachment elements embedded directly in the email message. Each element defines a snippet of XML markup describing the report execution arguments.

The first attachment is produced for Categories data controller. Data is filtered by CategoryID of the modified record. The report is produced for editForm1 view.

The second attachment is produced for Products data controller. Data is filtered by CategoryID and sorted in descending order of Unit Price. The report is produced for grid1 view.

Note the field names of the updated data record referenced in curly braces. Expressions {CategoryName} and {CategoryID} are replaced with the actual values during processing.

Attachment definitions are removed from the email body by application framework. The framework will generate each report using specified arguments and attach the report to the email before it is sent out to the recipient.

Run the application and edit any category. Click OK button to save the changes.

An email business rule will trigger an email notification with two report attachments produced in a Touch UI app created with Code On Time application generator.

The data will be saved after a slight delay.

Check your smart phone device for messages.

An email notification on an Android device generated by an Email Business Rule of an app produced with Code On Time.

This is how the email message may look.

The text of the email notification produced by an Email Business Rule in an app created with Code On Time applicaition generator.

Click on an attachment to see the report data in a PDF reader installed on your device.

An attachment report with Category details displayed in Adobe Reader on an Android device.

An attachment report with a list of Products in changed category displayed in Adobe Reader on an Android device.