Application Builder

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
Application Builder
Wednesday, February 27, 2013PrintSubscribe
Configuring Hierarchy

The “hierarchy-parent” tag can be used to present a hierarchical view of information.

Note that hierarchy is only available in the second generation data sheet view.

First, create the HR sample web application using Oracle Database Engine.

Adding a New Page

When generation is complete, activate the Project Designer. On the Project Explorer toolbar, click on the New Page icon.

Creating a new page.

Assign a name to the page:

Property Value
Name Hierarchy

Press OK to save. Drop the new Hierarchy page node on the right side of Home page to place it second in the menu.

Dropping Hierarchy page onto Home page.     Hierarchy page is second in the menu.

Switch to the Controllers tab. Right-click on EMPLOYEES data controller and press Copy.

Copying EMPLOYEES controller.

Switch back to the Pages tab. Right-click on Hierarchy page and press Paste. The data controller will be instantiated as a data view.

Pasting onto Hierarchy page.     The data view has been instantiated as a data view in a container on the page.

Configuring Hierarchy in Data Sheet

Double-click on Hierarchy / c101 / view1 (EMPLOYEES) / grid1 view node.

View 'grid1' of EMPLOYEES controller.

Change the view type.

Property New Value
Type Data Sheet

Press OK to save. Double-click on Hierarchy / c101 / view1 (EMPLOYEES) / grid1 / MANAGER_ID –> MANAGER_LAST_NAME data field node.

Data field 'MANAGER_ID' of view 'grid1'.

Tag the data field as the hierarchy parent.

Property New Value
Tags hierarchy-parent

Press OK to save.

Viewing the Results

On the toolbar, press Browse. The data sheet will now be organized according to the hierarchy.

Hierarchy in the Oracle sample database.

Wednesday, February 27, 2013PrintSubscribe
Enabling Second Generation Data Sheet Preview

Starting with release 7.0.7.0, web applications created with Premium or Unlimited edition include a preview of the second generation data sheet view. The new implementation supports horizontal and vertical scrolling, column resizing, and freezing. In addition, applications based on Microsoft SQL Server or Oracle also support hierarchical presentation of data.

The preview does not yet support all capabilities available in the original data sheet. The missing features will be released as soon as they become production-ready. Therefore, the second generation data sheet is disabled by default. If you would like to take it for a spin, make sure to regenerate your web app and follow the instructions below.

Start the web application generator. Create a sample Northwind web app. When generation is complete, click on the project name in the start page of the generator. Then, click Develop to open the project in Visual Studio.

In the Solution Explorer, right-click on ~\App_Code folder, and press Add | Add New Item…

image

Select Class from the list, and assign a name. Press Add to create the file.

image

Replace the existing code base with the following:

C#:

namespace MyCompany.Data
{
    public partial class ControllerUtilities
    {
        public override bool SupportsScrollingInDataSheet
        {
            get { return true; }
        }
    }
}

Visual Basic:

Namespace MyCompany.Data
    Partial Public Class ControllerUtilities
        Public Overrides ReadOnly Property SupportsScrollingInDataSheet As Boolean
            Get
                Return True
            End Get
        End Property
    End Class
End Namespace

Save the file and run the web app. Navigate to the Customers page. On the action bar, press Action | Show in Data Sheet.

image

The grid view will render the second generation data sheet.

image

The second generation data sheet will be enabled by default when the feature set of the previous implementation is replicated.

To use the original data sheet view implementation, make sure that the SupportsScrollingInDataSheet property of class ControllerUtilities returns false.

Wednesday, February 27, 2013PrintSubscribe
EASE Geo Tagging

Some projects require that a location must be recorded when a new order is made or whenever a record is modified. Code On Time client library will automatically request the latitude and longitude from the browset with the use of tags on the data field level.

For example, let’s consider the Northwind sample database. When a new order is created, we would like to save the location. Let’s add two pairs columns to the Orders database table, refresh the Orders controller, and tag these fields as coordinates.

Adding Latitude and Longitude to Orders Table

Start SQL Server Management Studio. In the Object Explorer, right-click on Databases / Northwind / Tables / dbo.Orders node, and press Design.

Designing the Orders table of the Northwind database.

Add four more columns with the following values:

Column Name Data Type Allow Nulls
CreatedLatitude nvarchar(50) yes
CreatedLongitude nvarchar(50) yes
ModifiedLatitude nvarchar(50) yes
ModifiedLongitude nvarchar(50) yes

Save the design to add the columns to the table.

Refreshing Orders Controller

Start the web app generator. Click on the project name, and press Refresh. Check the box next to Orders controller, and click Refresh.

Refreshing the Orders controller.

Tagging the Data Fields

Press Design to activate the Project Designer. In the Project Explorer,  switch to the Controllers tab. Double-click on Orders / Views / editForm1 / c1- Orders / CreatedLatitude (String(50)) data field node.

'CreatedLatitude' data field of view 'editForm1' in the Orders controller.

Add a tag to the data field:

Property New Value
Tags created-latitude

Press OK to save. Double-click on Orders / Views / editForm1 / c1- Orders / CreatedLongitude (String(50)) data field node.

'CreatedLongitude' data field of view 'editForm1' in the Orders controller.

Add the following tag:

Property New Value
Tags created-longitude

Save the data field. Double-click on Orders / Views / editForm1 / c1- Orders / CreatedLongitude (String(50)) data field node.

'ModifiedLatitude' data field of view 'editForm1' in the Orders controller.

Use this tag:

Property New Value
Tags modified-latitude

Save the item. Double-click on Orders / Views / editForm1 / c1- Orders / ModifiedLongitude (String(50)) data field node.

'ModifiedLongitude' data field of view 'editForm1' in the Orders controller.

Use this tag:

Property New Value
Tags modified-longitude

Save the data field.

Now, repeat the steps above to assign the correct tags to the relevant data fields in createForm1 view.

It is also possible to store latitude and longitude in the same field in the form “[latitude],[longitude]” by using the tags “created-coords” and “modified-coords.”

Viewing the Results

On the toolbar, press Browse. Navigate to the Orders page. Create a new record. A request for permission will be triggered – every browser will display it differently.

Internet Explorer 9 requesting permission for the site to track physical location.

Allow the website location request for the session or site. Press Cancel and open the create form again. Both sets of coordinates will be updated. Note that the data fields are read-only.

All coordinate fields are updated with the values supplied by the browser.

Save the record and edit the record again. Note that only Modified Latitude and Longitude values are changed.

"Modified" coordinates updated with the values supplied by the browser.