Designer

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.

Creating a Business Rule

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

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 a business rule on the right side of a business rule will also place it after the target rule.

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

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

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

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

Renaming Business Rules

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

Editing Business Rules

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

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

Deleting Business Rules

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

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.

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

Change the Code Default:

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

Change the Code Default:

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.

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.

Clear the Code Default:

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

Change the following properties:

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

Use the following configuration:

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.

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.