Blog: Posts from November, 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 November, 2012
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.

Wednesday, November 21, 2012PrintSubscribe
November 2012 Enhancements

The following bug fixes and enhancements are incorporated in the Code On Time release 7.0.5.0:

  • RepresentationalStateTransferBase class implements IRequiresSession interface to enable access to session variables when handling REST API calls.
     
  • Fixed the runtime bug in Visual Basic version of ActionResult.Refresh method.
     
  • Added a fix for “missing buttons” exception in Designer.
     
  • Library downloader uses temporary files when downloading code generation library updates from http://codeontime.com to minimize the file locking.
     
  • Visual Studio 2012 detection has been enhanced to work correctly on  system with Visual Studio 2010 only.
     
  • Client library uses "-" instead of "$" in the CSS classes of UI elements rendered for all actions. 
     
  • Custom membership provider correctly maps Email field.
     
  • Custom membership provider correctly implements the version of method GetUser that accepts a provider key as an argument.
     
  • “Data sheet” lookup will not automatically close when displayed for the first time.