Web Application Generator

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
Web Application Generator
Tuesday, August 14, 2012PrintSubscribe
Overview of Data Fields

A data field is a binding of a field to a data controller view. Only one binding of a field can exist in each view. Data fields in form views are organized in categories. The data controller will automatically bind primary key fields and alias fields to a data view if the corresponding data fields are not explicitly defined.

If the value of a field is required for a business rule implementation but should not be displayed to the user, then the data field binding must be created and marked as hidden.

If the field has read roles specified and the user is not matched to the roles, then the data field will become invisible. If the field has write roles specified and the user is not matched to the roles, then the data field will be rendered as read-only.

Data fields can be dynamically rearranged with the help of data controller virtualization.

Data Field Properties:

Property Description
Aggregate Function Specifies a function that will be performed on the rows in grid view. The value will be displayed at the bottom of the grid.
Alias Specifies an alias for the field. The alias will be used to display values. The header text of the alias will be used.
Auto Complete Minimum Prefix Length Specifies the number of letters required for auto-complete to be displayed. If less than 1, auto-complete will be disabled.
Category Displays the category Id that the data field belongs to.
Chart Specifies the role the data field will play in the chart.
Code Filter Specifies the behavior of the filter expression.
Columns Specifies the width of the data field.
Controller Displays the controller that the data field belongs to.
Data Format String Specifies a string that will be used to format the field before presentation.
Data Type Displays the type of the field.
Field Name Specifies the field that the data field will reflect.
Filter Expression Specifies when records will be displayed based on field values.
Footer Text Specifies the text displayed under the field in the user interface.
Format On Client When disabled, the server will format the field using the specified data format string.
Header Text Specifies the text displayed as a label in the user interface.
Hyperlink Format String Specifies a format string that will be rendered as a link. Field names surrounded by brackets can be used to dynamically populate values.
Read Only When enabled, users will not be able to edit the value. The value will not be passed to the server.
Read-Only When Specifies a JavaScript expression that will allow editing on the field when the expression evaluates to true.
Rows Specifies the height of the data field.
Search Mode Specifies the behavior in the advanced search bar.
Search Options Specifies the options available in the advanced search bar. From here, you can also Disable Auto Complete, Disable Multiple Values, Disable Samples, Enable Auto Complete Anywhere.
Text Mode Specifies the method used to display text values. Available options are: Password, Rich Text, Note, Static.
The field is hidden When enabled, the data field will not be displayed in the user interface.
Tool Tip Specifies text to display when the user mouses over the field.
View Displays the view that the data field belongs to.
Visible When Specifies a JavaScript expression that will display the field when the expression evaluates to true.

Learn how to work with data fields in the Designer.

Learn to drag and drop data fields in the Project Explorer.

Common Tasks:

Task Description
Configure a Password Field Learn how to configure a password data field.
Enable Rich Text Editor Learn how to enable rich text editing on a data field.
Monday, August 13, 2012PrintSubscribe
Working with Fields

A field represents a column of a data row. There are physical and virtual fields. Virtual fields are not derived from a physical column of a data table – their values are computed at runtime. Bindings of fields to views are called data fields.

In the Project Explorer, fields are contained under the Fields node of a controller. If an asterisk (*) is present after the name of the field, the field is required. The field type and length are displayed in parentheses. Some fields fields may display “read-only” label.

Fields under the Fields node of a controller in the Project Explorer.

Creating a Field

A field can be created by using the New Field context menu option on the Fields node.

New Field context menu option in the Project Explorer.

Moving Fields

Fields can be moved using drag and drop operations.

Dropping a field node onto another field node will place the field after the target field.

CategoryID field dropped on CategoryName field in the Project Explorer.     CategoryID field moved after CategoryName in the Project Explorer.

Dropping a field node on the right side of another field node will place it after the target field.

CategoryName dropped on the right side of CategoryID field.     CategoryName field moved after CategoryID field in the Project Explorer.

Dropping a field node on the left side of another field node will place it before the target field.

Picture field dropped on the left side of Description field.     Picture field node placed after Description in the Project Explorer.

Fields can be copied to a different controller by dragging onto the controller or Fields node. The original field will not be deleted.

Description field dropped on CategorySalesfor1997 controller node.     Description field placed at the bottom of Fields node of CategorySalesfor1997 controller in the Project Explorer.

Creating Data Fields

When fields are dropped onto a view or category, they will be instantiated as data fields in the target view. When the field is dropped onto a form view, the data fields will be appended to the last category.

Dropping two fields onto a view node.     Two data fields created in view1.

Cloning a Field

A field can be copied by dropping onto the controller or Fields node while holding Ctrl key. The name of the clone will be appended with a number, and the new field will be configured as a calculated field that reflects the physical column in the database. Use context menu option Copy on the field and use Paste on the controller or Fields node to create a clone.

Description field dropped on Categories controller node while holding Ctrl key on the keyboard.     Description field duplicated as 'Description_1' in the Categories controller.

Create Standard Validator and Converter

Validation and conversion business rules can be quickly created using the Add Validator and Add Converter context menu options. Code, SQL, and JavaScript options are available.

Add SQL Validator context menu option for a field in the Project Explorer.

When an option is selected, the field is configured as calculated, and a business rule will be created.

Validator for CategoryName field automatically created in the Project Explorer.

Deleting a Field

Fields can be deleted using the context menu option Delete. This will also remove all data fields, items, and field outputs.

Delete context menu option in the Project Explorer.

Monday, August 13, 2012PrintSubscribe
Working with Fields in Designer

Fields represent properties of business objects. These properties are reflecting physical columns of a data row or a computed value based on other columns.

A complete list of data controller fields can be seen by switching to the All Fields tab on the Home page of the Project Browser.

All Fields tab on the Home page of the Project Browser displays all fields in the web application

The Fields tab on a controller page will display all fields of that specific controller.

Fields tab on a controller page displays the fields of a controller.

Clicking on the name of a field or the Open context menu option will display the details of the field.

Open context menu option in the Project Browser.     Field detail form in the Project Browser.

The Sync context menu option will select the relevant node in the Project Explorer.

Sync context menu option in the Project Browser.     CategoryName field node synchronized in the Project Explorer.

If the field is configured as a static item lookup, the items are specified under the Items tab on the Fields page.

List of static field items on the Items tab of the Fields page.

Binding of fields to data controller views are called data fields. They can be accessed via the Data Fields tab.

Data fields for a field are accessible via the Data Fields tab on the Field page.

Fields can be dragged to the views to create a binding (data field). When dropped on a form view, the data fields will be appended to the last category of the view. When dropped on any other type of view, the data field is created under the view node itself.

Dropping two fields onto a view node.     Two data fields created in view1.

Fields names can be changed using the Rename context menu option in the Project Explorer. The Rename operation will also update all references to the field, including the alias in the command text.

Rename context menu option in the Project Explorer.     CategoryName field in Rename mode in the Project Explorer.

Fields can be deleted using the Project Explorer context menu option Delete.

Delete context menu option in the Project Explorer.

Fields can be quickly found by their property values using Navigate To window.

LastName field found in Navigate To using the search terms 'lastname employees'.

Continue to Overview of Fields