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, November 27, 2012PrintSubscribe
Advanced User Manager for Custom Membership and Role Provider: Configuring the Views

Let’s customize the Users page and views in order to improve the presentation of the User Management screen.

Moving the Users Page

Start the Project Designer. In the Project Explorer, drag Region / Roles page node onto Region / Users page node to place it underneath Users page.

Dropping Roles page node onto Users page node.      Roles page node has been placed underneath Users page.

Drag Region / Users node on the right side of Reports node to place it at the bottom of the hierarchy.

Dropping Users page node on the right side of Reports page node.      Users page has been placed after Reports.

Right-click on Users / container2 node, and press Delete.

Deleting 'container2' on the Users page.

Configuring grid1

Switch to the Controllers tab and expand to Users / Views / grid1 node. While holding Ctrl key, select the data fields in the following order: UserName, IsApproved, Email, IsLockedOut, CreationDate, LastLoginDate, and Comment. Drop the data fields on Users / Views / grid1 to sort the fields in the selected order.

Dropping several data fields onto 'grid1' view.      The data fields have been rearranged.

Select the data fields LastActivityDate and LastLockedOutDate. Right-click and press Delete.

Deleteing data fields 'LastActivityDate' and 'LastLockedOutDate'.

Configuring editForm1

Double-click on Users / Views / editForm1 / c1 – Users category node.

The category 'c1 - Users' of editForm1 view.

Change the following properties:

Property New Value
Header Text User Information
Description Please select user roles that most closely match user's responsibilities. Roles control access to the areas of this web site. Please contact system administrator if role access restrictions must be changed. Enter any additional comments about this user account. Comment is not visible to the user.

Press OK to save. Right-click on Users / Views / editForm1 node, and press New Category.

New Category context mneu option for editForm1 view.

Assign the following values:

Property New Value
Header Text Password Recovery
Description During the recovery of a forgotten password the user will be asked to enter a user name. If a user account exists then a security question is requested to be answered. A correct answer will trigger an email with a temporary password send to the user. Change locked out flag to 'No' if the user has been locked out after reaching a maximum number of failed login attempts and you want to allow user to login again.

Press OK to save. Expand Users / Views / editForm1 / c1 – User Information category node. While holding Ctrl key, select the following data fields: Email, Password Question, and IsLockedOut. Drop the data fields onto Users / Views / editForm1 / c2 – Password Recovery node.

Dropping several data fields onto category 'c2 - Password Recovery'.      Data fields have been moved to category 'c2 - Password Recovery'.

Press OK to save. Create another category with these properties:

Property New Value
Header Text Activity Statistics
Description Shows statistics of user activity.

Save the category. Drag the data fields CreationDate, LastLoginDate, LastActivityDate, and LastPasswordChangedDate onto Users / Views / editForm1 / c3 – Activity Statistics.

Dropping several data fields onto category 'c3 - Activity Statistics'.      Data fields have been moved to category 'c3 - Activity Statistics'.

Create one more category:

Property New Value
Header Text Login Statistics
Description These are the statistics of failed login attempts by this user. User will be locked out after reaching a maximum number of failed login attempts. Locked out users will be able to login again after the date in Failed Password Attempt Window Start. Users who failed to recover the password will be able to so after the date in Failed Password Answer Attempt Window Start. You can restore user's ability to login by setting Locked Out flag to 'No'.

Save the category. Drag the data fields LastLockedOutDate, FailedPasswordAttemptCount, FailedPasswordAttemptWindowStart, FailedPasswordAnswerAttemptCount, and FailedPasswordAnswerAttemptWindowStart onto Users / Views / editForm1 / c4 – Login Statistics category node.

Dropping several data fields onto category 'c4 - Login Statistics'.      Data fields have been moved to category 'c4 - Login Statistics'.

Select the data fields Password and PasswordAnswer. Right-click, and press Delete.

Deleting the data fields 'Password' and 'PasswordAnswer'.

Configuring createForm1

Double-click on Users / Views / createForm1 / c1 – New Users category node.

Category 'c1 - New Users' of createForm1 view.

Change the following properties:

Property New Value
Header Text New User Information
Description Please enter user name and password. Note that password must be at least 7 characters long and include one non-alphanumeric character. Only approved users will be able to login into the website.

Press OK to save. Right-click on Users / Views / createForm1 node, and press New Category.

New Category context mneu option for 'createForm1' view.

Assign the following values:

Property New Value
Header Text Roles
Description Please select user roles that most closely match user's responsibilities. Roles control access to the areas of this web site. Please contact system administrator if role access restrictions must be changed.

Press OK to save. The Roles field will be added in the next tutorial.

Create another category with these properties:

Property New Value
Header Text Password Recovery
Description These fields are required to help a user to recover a forgotten password. During the recovery process the user will be asked to enter a user name. If a user account exists then a security question is requested to be answered. A correct answer will trigger an email with a temporary password send to the user.

Save the category. Drag the data fields Email, PasswordQuestion, and PasswordAnswer onto Users / Views / createForm1 / c3 – Password Recovery.

Dropping several data fields onto category 'c3 - Password Recovery'.     Data fields moved to category 'c3 - Password Recovery'.

Create one more category:

Property New Value
Header Text Comments
Description Enter any additional comments about this user account. Comment is not visible to the user.

Save the category. Drag the data field Comment onto Users / Views / createForm1 / c4 – Comments category node.

Several data fields dropped onto category 'c4 - Comments'.     Data fields moved to category 'c4 - Comments'.

Click on the data field LastActivityDate. While holding Shift key, click on the data field FailedPasswordAnswerAttemptWindowStart. Right-click, and press Delete.

Deleting the unnecessary data fields from createForm1 view.

Configuring Read-Only Fields and Checkboxes

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

The 'List' option for Fields node of Users controller.

Make the following changes to the list of fields:

Name Read Only Items Style Data Format String
IsApproved   Check Box  
LastActivityDate Yes   g
LastLoginDate Yes   g
LastPasswordChangedDate Yes   g
CreationDate Yes   g
IsLockedOut   Check Box  
LastLockedOutDate Yes   g
FailedPasswordAttemptCount Yes    
FailedPasswordAttemptWindowStart Yes   g
FailedPasswordAnswerAttemptCount Yes    
FailedPasswordAnswerAttemptWindowStart Yes   g

Double-click on Users / Views / editForm1 / c1 – User Information / UserName data field.

UserName data field node of 'editForm1' of Users controller.

Change the Read Only property:

Property New Value
Read Only Yes

Press OK to save. Double-click on Users / Views / editForm1 / c2 – Password Recovery / PasswordQuestion data field.

PasswordQuestion data field node of 'editForm1' of Users controller.

Change the Read Only property:

Property New Value
Read Only Yes

Press OK to save. Double-click on Users / Views / createForm1 / c1 – New User Information / Password data field node. Make the following change:

Property New Value
Text Mode Password

Save the data field.

Tuesday, November 27, 2012PrintSubscribe
Advanced User Manager for Custom Membership and Role Provider: Overview

Create “Users”, “Roles”, and “UserRoles” tables using one of the scripts for Advanced Membership and Tables. Configure the custom membership map and generate the project.

Advanced Membership Provider in Action

When the website is first initialized, the standard user accounts admin and user will be created, and can be used to sign in to the web application. Two roles will be created: Administrators and Users. Both accounts will be assigned Users role, and admin will be assigned Administrators role.

Logging into the Advanced Custom Membership web application with the admin standard user account.

Log in and navigate to the Users page.

The default grid view of Users controller

View the details for any user.

Users edit form. All fields are displayed as editable.

Let’s perform the following enhancements:

  1. The user should not be able to view the fields Password and Password Answer.
  2. The data fields will be separated into several categories.
  3. Is Approved and Is Locked Out will be changed to a check box.
  4. All date and count fields will be read-only.
  5. Roles will be added as a many-to-many field.

In addition to these changes, the Users page will be moved to the end of the menu, and will only be visible to administrators.

The final step would be to prevent default CRUD operations from being performed, and create business rules that will use the ASP.NET Membership API to perform updates to the Users and UserRoles table.

This is the final Users grid view.

Customized User Manager screen.

The final Users form will look like the picture below:

Final user management screen.Final user management screen.

Monday, November 26, 2012PrintSubscribe
SQL Business Rules for Oracle Databases

SQL business rules are implemented in the programing language supported by application database engine.

If an Oracle database is the foundation of your data tier, then the programming language of SQL business rules is PL/SQL.

Consider Employees page displaying createForm1 in a project created straight from HR sample database.

Page 'Employees' displaying 'createForm1' view in a project created from the sample HR database available with Oracle database engines

None of the fields has a default value. Let’s assign default values to First Name, Last Name, Hire Date, and Salary.

Start Project Designer, activate Controllers tab, locate EMPLOYEES data controller and start creating a new SQL business rule.

Creating a new SQL business rule in Code On Time application generator

Configure the rule as follows:

Property Value
Command Name New
Type SQL
Phase Execute
Script

begin
    :FIRST_NAME := 'John';
    :LAST_NAME := 'Doe';
    :HIRE_DATE := sysdate;
    select avg(SALARY) into :SALARY from EMPLOYEES;
end;

Save the rule.

The script is written in PL/SQL. The highlighted field names are referenced as parameters in the script text.

image

When executed, the script will assign static values to First Name and Last Name fields.

The current system date will be assigned to Hire Date field.

An average of all employee salaries will be assigned to Salary field.

SQL business rule writtent in PL/SQL assigns default values to the field when a user starts creating a new record

The full power of PL/SQL is available to application developers when creating applications with Code On Time.