User Interface

A new Report action must be configured in the Orders data controller. The action will produce a PDF output using the custom report template from the “order details” data set filtered by a selected order ID.

Start the Project Designer. In the Project Explorer, switch to the Controllers tab. Right-click on Orders / Actions / ag2 (Form) and press New Action.

Assign the following values:

Press OK to save.

The highlighted parameters will instruct the reporting engine of application framework to use a specific data controller and report template.

The last expression is the filter that will limit  OrderDetails data set by the order ID that was selected on the client in the data view of Orders when action has been activated.

In the Project Explorer, drop Orders / Actions / ag2 (Form) / a100 – Report | Order Report to the left side of a1 – Edit action node to place it first in the action group.

On the toolbar, press Browse. Navigate to the Order Form page, and select an order. Click on Order Report button to see the printable report with a content formatted according to the template.

If you were to click on the Print icon in the top or bottom row of action buttons, then a standard report with a list of order fields will be produced on the server.

Click on the Edit button. Notice that the Order Report button disappears.

Let’s make sure that a click on the Print icon will yield the customized Order Report, and that the same report is also accessible in edit mode.

Configuring “Print” Icon

The Print icon always activates the first “Report” action in any group with “Action Bar” scope.

In the Project Explorer, hold down Ctrl key and drop a100 – Report | Order Report node onto Orders / Actions / ag7 (ActionBar) – Report action group node.

Next, drop a100 – Report | Order Report node on the left side of a1 – ReportAsPdf action node to place it first.

The Print icon will now trigger Orders / Actions / ag7 (ActionBar) – Report / a100 – Report | Order Report action.

Order Report Action in Edit Mode

While holding Ctrl key, drop Orders / Actions / ag2 (Form) / a100 – Report | Order Report onto ag2 (Form) action group node to duplicate the action.

Drag a101 – Report | Order Report on the left side of a4 – Update when Edit to place it before the target.

Double-click on a101 – Report | Order Report node, and make the following change:

Press OK to save. This action button Order Report will now appear when the form is in edit mode.

Let’s add a “Roles” tab on the Users page to allow management of roles. When a role is selected, users corresponding to the role will be displayed below. In order to create this “implied” master-detail relationship, a “UsersInRole” view must be created that will use a custom command to extract the RoleID.

Creating “Users In Role” View

Right-click on Users / Views / grid1 view node, and press Copy.

Right-click on Users / Views node, and press Paste. A duplicate of the view will be created.

Double-click on Users / Views / v100 node. Next to the Command property, select the New Command icon.

Assign these values.

select
    "Users"."UserID" "UserID"
    ,"Users"."UserName" "UserName"
    ,"Users"."Password" "Password"
    ,"Users"."Email" "Email"
    ,"Users"."Comment" "Comment"
    ,"Users"."PasswordQuestion" "PasswordQuestion"
    ,"Users"."PasswordAnswer" "PasswordAnswer"
    ,"Users"."IsApproved" "IsApproved"
    ,"Users"."LastActivityDate" "LastActivityDate"
    ,"Users"."LastLoginDate" "LastLoginDate"
    ,"Users"."LastPasswordChangedDate" "LastPasswordChangedDate"
    ,"Users"."CreationDate" "CreationDate"
    ,"Users"."IsLockedOut" "IsLockedOut"
    ,"Users"."LastLockedOutDate" "LastLockedOutDate"
    ,"Users"."FailedPasswordAttemptCount" "FailedPasswordAttemptCount"
    ,"Users"."FailedPasswordAttemptWindowStart" 
        "FailedPasswordAttemptWindowStart"
    ,"Users"."FailedPasswordAnswerAttemptCount" 
        "FailedPasswordAnswerAttemptCount"
    ,"Users"."FailedPasswordAnswerAttemptWindowStart" 
        "FailedPasswordAnswerAttemptWindowStart"
    ,UserRoles.RoleID RoleID
from "dbo"."Users" "Users"
left join UserRoles on Users.UserID = UserRoles.UserID

Press OK to create the command and insert it into the property. Also make the following changes:

Press OK to save. In the Project Explorer, right-click on Users / Views / v100 and press Rename.

Change the name to “UsersInRole” and press Enter on your keyboard to save.

Adding “RoleID” Field

Right-click on Users / Fields node, and press New Field.

Assign the following properties:

Press OK to save the field. Drop Users / Fields / RoleID field node onto Users / Views / UsersInRole to create a data field and append it to the view.

Adding Roles Tab to Users Page

Switch to the Controllers tab in the Project Explorer. While holding Ctrl key, click on Roles and Users controller nodes in that order. Right-click and press Copy.

Switch back to the Pages tab. Right-click on Users / container1 node, and press Paste. The controllers will be instantiated as views in the container.

Double-click on Users / container1 / view1 (Users) data view node.

Change the following properties.

Press OK to save. Double-click on Users / container1 / view2 (Roles) node.

Make the following changes.

Save the data view. Double-click on Users / container1 / view3 (Users) node.

Make these changes:

Save the data view. Expand Users / container1 / view3 (Users, UsersInRole) / UsersInRole node. Drop RoleID data field node onto Users / container1 / view2 (Roles) to establish a master-detail relationship.