Blog: Posts from July, 2012

Labels
AJAX(112) App Studio(7) 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(177) 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(183) 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(2) 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
Posts from July, 2012
Tuesday, July 17, 2012PrintSubscribe
Read-Only Data Fields

Data fields can be rendered as read-only if a field-level JavaScript expression evaluates as true for a given data row.

For example, the Customers edit form has a Region data field. Let’s configure this data field to only be editable when the Country is “USA”.

Region data field is editable by default in the Customers edit form.

Start the Project Designer. In the Project Explorer, double-click on Customers / container1 / view1 / editForm1 / c1 – Customers / Region data field node.

Region data field in editForm1 of Customers controller.

Change the Read-Only When property:

Property New Value
Read-Only When [Country] != 'USA'

Press OK to save the data field. On the toolbar, press Browse.

When the application loads in your browser, select a customer that is not from the USA. The Region data field will not be editable.

Customer not from USA does not have an editable Region data field.

Select a customer that is from the USA. The Region data field will be editable.

Customer from USA does have an editable Region data field.

Tuesday, July 17, 2012PrintSubscribe
Hyperlink Format String

The Hyperlink Format String property allows formatting fields as hyperlinks that can use the field values as parameters.

Start SQL Server Management Studio. Right-click on Databases node, and select New Database.

Create New Database in SQL Server Management Studio.

Assign the database the name of FormatString, and press OK to create the server.

Right-click on Databases / FormatString / Tables node, and select Add New Table.

Add New Table to FormatString database.

Add the following columns:

Column Name Data Type Allow Nulls
ProductID int False
ProductName nvarchar(50) False
Price money True
PictureUrl nvarchar(100) True

Right-click on ProductID column and select Set Primary Key.

Set ProductID as Primary Key.

Highlight ProductID column. Under Column Properties, specify the column as an identity.

Property Value
(Is Identity) Yes

Save the table as “Products”.

Switch to the web application generator. Create a new Web Site Factory project from the FormatString database. When the project configuration is complete, activate the Project Designer.

In the Project Explorer, double-click on Products / container1 / view1 / grid1 / Price data field node.

Price data field of grid1 on the Products page.

Change the Hyperlink Format String:

Property New Value
Hyperlink Format String _blank:{PictureUrl}

Press OK to save the data field. Double-click on Products / container1 / view1 / grid1 / PictureUrl data field node.

PictureUrl data field of grid1 on the Products page.

Mark the data field as hidden:

Property New Value
The field is hidden True

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

When the web application is loaded, create three new records on the Products page with the following values:

Product Name Price Picture Url
Standard 349 /images/Buy_CodeOnTimeStandard.gif
Premium 899 /images/Buy_CodeOnTimePremium.gif
Unlimited 2499 /images/Buy_CodeOnTimeUnlimited.gif

The value of Price field in the grid view is rendered as a clickable link.

Value in Price data field rendered as a link.

When you click on the link in the Price column, you will navigate to the PictureUrl.

Clicking on the Price data field link will navigate to the specified PictureUrl.

Tuesday, July 17, 2012PrintSubscribe
Status Bars

The state of real world business objects modeled in the application database is frequently determined by the values of multiple object attributes.

For example, an order status may depend on the Order Date and Shipped Date. It would take some time for an end user to analyze the values to understand the status of an order. It would be beneficial for an application to provide a graphical representation of the order status.

Let’s implement a graphical representation of the internal object state using the Orders table of the Northwind sample. Most records have Shipped Date before Required Date. Some records do not have a value in the Shipped Date column. Other records have a Shipped Date past the Required Date.

List of orders in various states.

It would be reasonable to assume that records without a Shipped Date have not been shipped yet, records that have a Shipped Date past the Required Date have been shipped late, and that the order is on time when the Shipped Date is before Required Date.

Start the Project Designer. In the Project Explorer, switch to the Controllers tab. Right-click on Orders / Fields node, and select New Field option.

Create new field in the Orders controller.

Give this field the following settings:

Property Value
Name Status
Type String
Length 50
The value of this field is computed at run-time by SQL expression. True
SQL Formula
case
    when ShippedDate is null
        then 'Waiting To Ship'
    when ShippedDate < RequiredDate
        then 'Shipped'
    when ShippedDate > RequiredDate
        then 'Shipped Late'
end
Label Status
Values of this field cannot be edited True

Press OK to save the field. Right-click on Orders / Views / editForm1 / c1 – Orders node, and select New Data Field.

New Data Field in editForm1 view.

Give this data field the following settings:

Property Value
Field Name Status
The field is hidden True

Double-click on Orders controller node.

Orders controller node in the Project Explorer.

Change the Status Bar property:

Property New Value
Status Bar

Orders.editForm1.Status: Shipped
Order Placed > Preparing your shipment > Shipped > [You should receive your item soon] >

Orders.editForm1.Status: Waiting To Ship
Order Placed > [We are preparing the order for shipment] > Shipped >

Orders.editForm1.Status: Shipped Late
Order Placed > [Oops, your order has been delayed] > We are trying to obtain your items >

Press OK to save the controller. On the toolbar, press Browse.

Navigate to the Orders page. Select an order in which the Shipped Date is before the Required Date. A status bar above the form provides a quick status update on the status of the order.

Status bar for an order that has been shipped on time.

Select an order where Shipped Date is after Required Date. The status bar shows that the order has been delayed.

Status bar for an order that shipped late.

Finally, select an order without a value in Shipped Date field. The status bar will show that the order has not yet been shipped.

Status bar for an order that has not been shipped yet.

Status can be figured with complex calculations. For example, we configured the following SQL Formula for a new Status field in Products controller:

case
    when Discontinued = 1
        then 'Discontinued'
    when UnitsInStock + UnitsOnOrder < ReorderLevel
        then 'Low On Stock'
    when UnitsOnOrder > 0
        then 'On Order'
    when UnitsOnOrder = 0
        then 'In Stock'
end

The Status Bar configuration for Products controller looks like this:

Products.Status: Discontinued
Flagged for Review > [ The production of the product has been discontinued] >
 
Products.Status: Low On Stock
High Demand > [The product will be out of stock soon] > Place an order >
 
Products.Status: On Order
Product stock low > [An order has been placed] > Restocking >
 
Products.Status: In Stock
Recently restocked > [Plenty of stock] >

A product that has a large amount of Units In Stock will display the following status bar.

Status bar for a product that is fully stocked.

When there are a large amount of Units On Order, the status bar will notify that there is sufficient items ordered.

Status bar for a product that is being restocked.

Discontinued products will be displayed like the picture below.

Status bar for a product that has been discontinued.

When the stock is low, the status bar will warn the user.

Status bar for a product that is low on stock.