Designer

Labels
AJAX(112) App Studio(9) 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(178) 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(184) 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(3) 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
Designer
Tuesday, July 17, 2012PrintSubscribe
Working with Business Rules

Business rules extend the functionality of a web application through custom code.

Business rules are located under the Business Rules node of a controller. The icon of a business rule is different for each business rule type: SQL, JavaScript, C#/Visual Basic, or Email.

Business rules that belong to Orders controller in the Project Explorer.

Creating a Business Rule

A business rule can be created by using the context menu option New Business Rule on the Business Rules node.

New Business Rule context menu option in the Project Explorer

Enter a Command Name, Type, Phase, and Script if necessary. Press OK to save, and the business rule will be added to the list.

Reordering Business Rules

The order of business rules reflect the execution sequence.

Dropping a business rule onto another business rule will place it after the target rule.

Dropping r100 business rule onto r101 business rule.     Business rule r100 placed after r101.

Dropping a business rule on the right side of a business rule will also place it after the target rule.

Dropping business rule r101 on the right side of r100.     Business rule r101 is placed after r100.

Dropping a business rule on the left side of a business rule will place it before the target rule.

Dropping business rule r101 on the left side of r100.     Business rule r101 placed before r100.

The context menu commands Cut/Copy and Paste will also move business rules.

Cut context menu option on a business rule node.

Business rules can be moved to another controller by dragging onto another controller node.

Dropping r100 business rule on Order Details controller. Business Rule r100 placed under Business Rules node of OrderDetails controller.

Dropping onto another Business Rules node will place the business rule at the bottom of the list.

Dropping r101 business rule onto the Business Rules node of Order Details controller. Business rule r101 placed at the bottom of Business Rules node in OrderDetails controller.

Renaming Business Rules

The ID of a business rule can be changed using the context menu option Rename.

Rename context menu option for business rule in the Project Explorer.     Business rule r101 in Rename mode.

Editing Business Rules

For SQL, JavaScript, and Email business rules, the script can be changed by opening the business rule in the Project Browser.

Open context menu option in the Project Explorer.

Code business rule files can be opened by using the context menu option Edit in Visual Studio.

Edit in Visual Studio context menu option in the Project Explorer.

Deleting Business Rules

Business rules can be deleted by using the context menu option Delete, or the Delete keyboard shortcut.

Delete context menu option in the Project Explorer.

Monday, July 9, 2012PrintSubscribe
Code Default

The Code Default property provides an expression written in C#/Visual Basic that evaluates to an initial field value of a new data row. Database tables frequently define default column expressions that will be evaluated by the database engine when a new record is persisted. From the user perspective, it is beneficial to see what exactly will be inserted in the column at the time when the user enters the field values instead of leaving the fields blank and relying on the database to fill in the blanks. The Code Default may provide a duplicate calculation that fulfills this need.

Default Values with C# / Visual Basic

The New Orders form has two date fields, Order Date and Required Date, that should have defaults when the form is first initialized.

New Orders form without any default values.

Start the Project Designer. In the Project Explorer, switch to the Controllers tab, and double-click on Orders / Fields / OrderDate node.

OrderDate field of Orders controller.

Change the Code Default:

Property New Value
Code Default DateTime.Now

Press OK to save. Double-click on Orders / Fields / RequiredDate node.

RequiredDate field of Orders controller.

Change the Code Default:

Property New Value
Code Default DateTime.Now.AddDays(7)

Press OK to save. On the Project Browser toolbar, press Browse button.

Navigate to the Orders page, and create a new record. The Order Date field will be populated with the current date. The Required Date field will be populated with the date seven days in the future.

New Orders form with default values for Order Date and Required Date fields.

This is how the code generator incorporates the code expression in the C#/Visual Basic business rules.

C#:

using System;
using MyCompany.Data;

namespace MyCompany.Rules
{
    public partial class OrdersBusinessRules : MyCompany.Data.BusinessRules
    {
        
        [RowBuilder("Orders", RowKind.New)]
        public void BuildNewOrders()
        {
            UpdateFieldValue("OrderDate", DateTime.Now);
            UpdateFieldValue("RequiredDate", DateTime.Now.AddDays(7));
        }
    }
}
Visual Basic:
Imports MyCompany.Data

Namespace MyCompany.Rules
    
    Partial Public Class OrdersBusinessRules
        Inherits MyCompany.Data.BusinessRules
        
        <RowBuilder("Orders", RowKind.New)>  _
        Public Sub BuildNewOrders()
            UpdateFieldValue("OrderDate", DateTime.Now)
            UpdateFieldValue("RequiredDate", DateTime.Now.AddDays(7))
        End Sub
    End Class
End Namespace

A custom utility class can be implemented for complex calculations. A static or shared property or method of the class can be used in Code Default expressions similar to how System.DateTime class is used in the example.

Default Values with SQL Business Rules

Code Default permits simple default values. For a majority of situations or when a more complex default value calculation involving interactions with the database is required, SQL Business Rules provide a great alternative.

Switch back to the Project Designer. Double-click on Orders / Fields / OrderDate field node.

OrderDate field of Orders controller.

Clear the Code Default:

Property New Value
Code Default N/A

Save the field. Double-click on Orders / Fields / RequiredDate field node.

RequiredDate field of Orders controller.

Change the following properties:

Property New Value
Code Default N/A

Press OK to save the field. Right-click on Orders / Business Rules node, and select New Business Rule option.

image

Use the following configuration:

Property Value
Command Name New
Type SQL
Phase Execute
Script
set @OrderDate = GETDATE()
set @RequiredDate = DATEADD("d", 7, getdate())

Press OK to save the business rule. On the toolbar, press Browse.

Navigate to the Orders page, and create a new order. The correct date values will be presented as default values.

New Orders form with default values for Order Date and Required Date fields.

The business rule matching New command is automatically executed on the server and the values of parameters OrderDate and RequiredDate are transferred to the fields with the same name in a new row.

Monday, July 9, 2012PrintSubscribe
Overview of Commands

A command provides a developer-friendly dictionary of SQL expressions that correspond to the individual fields and also define the base table and joined tables. The application framework uses the command text elements to compose Select, Update, Insert, and Delete statements at run-time.

Command Properties:

Property Description
Controller Specifies the controller that the command belongs to.
Event Specifies which event that causes the command to execute.
Id Specifies the unique identifier for the command.
Table Name Specifies the table name to be used in automatically constructed Insert, Update, and Delete operations.
Text Specifies the text of the command.
Type Specifies the type of the command.

Learn how to work with commands in the Project Designer.

Learn to drag and drop commands in the Project Explorer.