New Features in Release 4.1

• Error Handling

  Release 4.1 includes improved error handling and user-defined exception processing. You can now easily capture error messages generated by the Oracle database and replace the message text with user friendly text. For
  example, instead of an error message such as "ORA-00001 unique constraint (EMP_UK) violated" the developer can define a message such as "Employee
  Name must be unique".
  
  
• 
  

  Use of ROWID

  Application Express now supports the use of ROWID for updates, inserts and deletes as an alternative to specifying primary keys. Previously you could only specific two primary key columns. Therefore, if your table had more than two key columns then you could not use the default DML processes and had to manually write your own processes. Use of ROWID is now the default method for any new DML processes generated.
  

• Data Upload

  Developers can now easily add the capability for end-users to load spreadsheet data into existing tables within an application. The developer can utilize a wizard to create a collection of pages that allow the end user to upload a file or cut and paste data into a table. Additionally the developer can define lookup columns and data transformations. End users are then led through a runtime wizard which allows them to load the data, map the columns, see whether the data will be inserted or updated, and review the results.
• 
  

  Calendar

  The calendar wizards have been enhanced to include the ability to create an Edit page as part of creating the calendar. Further calendars can now include drag and drop functionality which allows the end user to change the date and or time of a record by simply dragging it on the calendar itself.
  
  
  
  

• Websheets

  Building on their initial introduction in Release 4.0, the look and feel of Websheets in Release 4.1 has been substantially improved and the controls redesigned to make it more intuitive for users. There are also new page section types, and enhanced data grid integration
  
  

  
  

  
  
• 
  

  Tabular Forms

  Tabular Forms now support all validation types. Depending on the validation type you can use bind variable syntax, substitution syntax, or just specify the tabular form column name. These enhancements allow developers to declaratively define complex validations instead of having to perform extensive manual PL/SQL coding.
  
  
  
• 
  

  Plug-Ins

  Plug-ins enable developers to enhance the existing built-in functionality by writing PL/SQL components for various components. This release expands the plug-in functionality and introduces the ability to create plug-ins for authentication and authorization schemes. View and Download Plug-Ins >
  
  
  
  
• 
  

  Dynamic Actions

  Dynamic Actions allow developers to declaritively define client-side functionality, without needing to master JavaScript and AJAX. With this release, a number of enhancements were added including the ability to define dynamic actions for buttons and also use dynamic actions to set multiple item values.
  
  
  
• 
  

  Accessibility

  Release 4.1 includes dramatic improvement in the HTML generated by the Application Express engine, together with accessibility improvements in existing themes and HTML templates.

Creating an Enable/Disable Declarative Dynamic Action

 Right click P3_JOB and select Create Dynamic Action.

Select Standard and click Next. Note that a Standard dynamic action allows you to create a dynamic action that will fire when a field's value changes, and will subsequently 'Show', 'Hide', 'Enable', or 'Disable' other page items.

Enter JOB EQUALS SALESMAN for the Name and click Next.

You want the Dynamic Action to be fired when the Job item is equal to SALESMAN. Because you created a dynamic action on the P3_JOB item, the values for Selection Type, Item(s) and Condition should already be specified. Enter SALESMAN for Value. Then click Next.

Select Enable for Specify the True Action. This action will be invoked when the value of P3_JOB is equal to 'SALESMAN'. Note that the Create Opposite False Action is checked which will create a Disable action that will be invoked when the value of P3_JOB is not equal to SALESMAN. Click Next.

The item that will be enabled or disabled is Commission. Select Item(s) for Selection Type and select P3_COMM from the list of items and click the Move icon to move it to the right and click Create.

 

You can run the page. Click Run.

Notice that the Commission item is enabled because the Job is equal to SALESMAN.

 

Change the Job to CLERK.

Notice that the Commission item is now disabled.

Input image into region

Create HTML Region

1. Select HTML region and click next























2. Enter title region



3. Write the scrip as an example, make sure the image files have been uploaded to the workspace


4. Create Region and finish