- Full Description
Beginning Oracle Application Express 4 introduces one of the most talked-about development platforms to come out of Oracle Corporation in years. Oracle Application Express, called APEX for short, enables rapid and easy development of web-based applications that make full use of Oracle Database. The release of APEX 4 brings a huge leap forward in terms of functionality and usability for both the developer and the end user. Power users and programmers alike can quickly put together robust and scalable applications for use by one person, by a department, by an entire company.
Whether you’re new to Oracle or an old hand who’s yet to test the waters of APEX, Beginning Oracle Application Express 4 introduces the processes and best practices you’ll need to become proficient with APEX. The book shows off the programming environment, the utilities and tools available, and then continues by walking through the process of building a working system from the ground up. While the book assumes a foundational knowledge of SQL and PL/SQL, all code used is documented and explained so that those new to the languages will not be lost.
- Covers brand-new functionality in APEX 4
- Provides fully documented and explained example code
- Guides you through creating a working and fully deployable application
What youll learn
- Design, code, and troubleshoot APEX applications
- Create forms and generate reports
- Apply best-practices to database and application design
- Create intuitive navigation that inspires confidence amongst users
- Secure your applications from outside attack
- Deploy applications for one, a dozen, or hundreds of users
Who this book is for
Beginning Oracle Application Express 4 is for programmers and power users wanting to create rich, data-centric applications that are web-based, and that rest on Oracles industry-leading database technology.
- Table of Contents
Table of Contents
- An Introduction to APEX
- A Developer's Overview
- Identifying the Problem & Designing the Solution
- SQL Workshop
- Application & Navigational Components
- Forms & Reports—The Basics
- Forms & Reports—Advanced
- Programmatic Elements
- Application Deployment
- Understanding Websheets
- A WebSheets Example
- Extended Developer Tools
- Managing Workspaces
- Team Development
- Source Code/Downloads
Please Login to submit errata.On page Chapter 12:The source download does not include Chapter 12Author Comment:
On page 16:The text after Websheet Applications mentions chapters ?? - and ?? These should be updated with real chapters.
The next paragraph mentions a Demo Application, but the screen shot is for 114. SAMPLE APPLICATION, and the reference to the application id is also wrong 16878 (it should be 114).
On page 26:git submodule add git://github.com/facbeook/facebook-ios-sdk.git facebook- ios-sdk
git submodule add git://github.com/facebook/facebook-ios-sdk.git facebook- ios-sdk
On page 30:Top paragraph referencing chapters ?? - should have real chapter numbers.
On page 40:THe Column Name "Description" should be changed to "Descr". If this is not done, script ch4_schema_changes will not run cleanly.
Alternatively, you can also edit the script.
On page 42:Last line refers to USERS table when Fig 4-5 shows TICKETS!
On page 42:last line on page says the create script for the USERS table is in figure 4-5. But it is the TICKETS table.
On page 47:I got an error importing data as I selected the data cells and copied and pasted into APEX. The way that worked is to copy the columns and copy and paste.
On page 48:Last para refers to email address and phone number. These are not on the spreadsheet or table
On page 48:reads "If you scroll to the right, you'll see that APEX didn't map the e-mail address or the phone number in your example to a table column. You'll need to map these data elements ..."
"If you scroll to the right, you'll see that APEX didn't map the descr column in your example to a table column. You'll need to map this data element ..."
On page 49,51, 54:The code supplied for Chapter 4 fails as it refers to column DESCR when previously the table was set up with it named DESCRIPTION
On page 54-55:chapter 4 script 3 create view commands fails because tickets.description column name is incorrect.
On page 55:The Statements Processed should be 17 & not 12.
On page 55:
The script ch4_schema_changes.sql (as provided as a source code/download) does not match the script used in the book and is incorrect. For example: it uses a column "desc" that does not exist ("description" does). Also the book states that 12 statements have been processed, but the application states that 15 statements have been executed.
On page 58:
Figure 4-26 shows the TICKETS table has a PRIORITY column. This column was not created in chapter 4.
Figure 4-26 also shows the TICKETS table having a DESCR column. DESCR agrees with the ERD, but not the screen shot (Figure 4-2) of the table creation dialog.
On page 79:Point 3. There is a next to click on, before you can click on Finish
On page 86:List Entry Table should be List Entry Label
On page 87:
In Table 5-2:
List Entry Table should be List Entry List
On page 94:It says: the syntax for specifying a status LOV is as follows.
Where would you enter this?
It then goes onto say: TYPE:DISPLAY;RETURN, DISPLAY;RETURN, ..
Should both expressions (DISPLAY;RETURN
,) be the same?
On page 107:
11. Set page 2 to be a public page. Refer back to Chapter 4 for detailed steps.
11. Set page 2 to be a public page. Refer back to Chapter 5 for detailed steps.
On page 110:It says: For your new tickets form, in the Page Processing section, you see the wizard has created one item for each of the columns ..
This should be the Page Rendering section?
On page 110:It says: In the Page Rendering column, you have a Process Row of Tickets.
This should be the Page Processing column
On page 114:
"11. Set page 3 to be a public page. Refer back to Chapter 4 for detailed steps."
This should actually reference Public Pages on pg 74 of chapter 5.
On page 114:Point 11 refers to chapter 4 when it should say chapter 5
On page 114:Bottom paragraph should say Page Processing not Page Rendering.
On page 121:
Step 8. has a semicolon instead of a colon for the CSS style. It should read:
Step 8. Enter font-weight:bold for the CSS Style field shown in the Column Formatting
section (Figure 6–34). Click Apply Changes.
On page 124:Figure 6-37 shows the results before status has been moved to be the second column
On page 125:Figure 6-39 shows column Details with a different height to that it was set up with originally
On page 127:
Bind variable syntax used for both setting and getting values from session state end with a trialing period. This is correct for substitution string syntax but not bind variable syntax.
On page 132:Table 6-1.'s second entry refers to &APPSESSION and not APP_SESSION
On page 135:Point 4. It says &P200_SEARCH when it should be &P200_SEARCH. i.e. with a full stop after it
On page 138:This refers to the Tickets region, as does Fig 6-53. Previously, wasn't it set up as Manage Tickets?
On page 147:
1. Edit Page 200 of your application.
1. Edit Page 220 of your application.
On page 157:Point 12. You don't say what to set the breadcrumb parent to, if anything
On page 157:Point 15 refers to T_TICKETS when there is only Tickets and T_HOME defined
On page 160:Point 15 doesn't say to set 'Display Null' to Yes
On page 161:Figure 7-12 has the submit button named when it should be 'Save Changes' and the Add button should be 'Add Tickets'
On page 193:Fig 7:64 shows a different Entry Name to that which appears
On page 236:Dynamic SQL code as entered does not function. Code does 'compile' however, following error message appears on main page where Current Open Issues should display :
ORA-01722: invalid number
On page 248:Point 25 says TS1as; it should say TS1 as
On page 249:ch9_data_security_script.sql has compilation errors due to it using DESCR when the book originally said to define the column as DESCRIPTION
On page 255:I'm not sure this is an error in APEX 4.0, but I'm using apex.oracle.com which just has been upgraded to 4.1, and as many probably use this for the examples, I thought I would share my experience.
Creating a authentication scheme from scratch has changed somewhat compared to the example given in the book from page 255 and forward. The steps I took are:
1. Navigate to the Shared Components of your application
2. In the Security region, click on Authentication Schemes; it’s the first one in the list shown in Figure 9–19.
3. Click the Create button in the upper right of the Authentication Schemes tab.
(steps 1. through 3. are taken as is from the book)
4. Choose "Based on a pre-configured scheme from the gallery" and click Next
5. Set the name to "Custom Authentication Scheme" and choose Custom as the Scheme Type
6. In "Settings" set "Authentication Function Name" to authenticate_user and click Create
7. Edit the newly created authentication scheme
7. In "Session Not Valid" set "Go To" to "Login Page"
8. In "Logout URL" set URL to "wwv_flow_custom_auth_std.logout?p_this_flow=&APP_ID.&p_next_flow_page_sess=&APP_ID.:1" (as in ch9_logout.txt
9. Apply changes
This seems to work
On page 256:Point 9 refers to pre-authentication, when it is actually post-authentication
On page 264:Point 36 refers to the Save button; this was named 'Apply changes' previously
On page 265:Point 40 refers to Save button when it has been renamed to 'Apply changes' previously
On page 267:ch9_data_security_script.sql has defined 2 views as ticketS_v and ticketS_secure_v but the book refers to them without the S
On page 270:It says: This is easily visible from Page 200.
It should say Page 210
On page 362:Session State refers to Fig 14-5. It should be Fig 14-7