Professional Documents
Culture Documents
guide to Create
Aria Application
in Oracle APEX
http://www.dbcon.com
2 Step-by-step guide to Create Aria Application in Oracle APEX
Table of Contents
Introduction ............................................................................................................................................ 4
Preparing the environment..................................................................................................................... 5
Getting Started........................................................................................................................................ 7
Creating the Application ..................................................................................................................... 7
Installing application’s theme ........................................................................................................... 12
Create supporting objects and load data.......................................................................................... 19
Create Application Users ...................................................................................................................... 23
Page – 410 – Login ................................................................................................................................ 26
Shared Components.............................................................................................................................. 28
Application Items .............................................................................................................................. 28
Lists ................................................................................................................................................... 31
Navigation Bar Entries....................................................................................................................... 40
List of Values ..................................................................................................................................... 47
Build Options..................................................................................................................................... 50
Authentication Scheme..................................................................................................................... 53
Authorization Schemes ..................................................................................................................... 56
Application Definition ....................................................................................................................... 59
Application Processes ....................................................................................................................... 61
Page 0 ................................................................................................................................................... 64
Page – 99 – Dummy Page to support images ....................................................................................... 79
Page – 1 – Quick Search ........................................................................................................................ 86
Test Page 1 .................................................................................................................................. 115
Page – 2 – Detail View......................................................................................................................... 119
Testing Page 2 ............................................................................................................................. 132
Page – 3 – Organization Chart ............................................................................................................ 135
Testing Page 3 ............................................................................................................................. 154
Page – 18 – Relate ............................................................................................................................... 157
Testing Page 18 ........................................................................................................................... 180
Page – 19 – Relation............................................................................................................................ 181
Testing Page 15 & 16................................................................................................................... 190
Page – 80 – Management Chain ......................................................................................................... 193
Testing Page 80 ........................................................................................................................... 202
Page – 6 – Advanced Search ............................................................................................................... 205
Introduction
Oracle provides some pre-created applications in Oracle Application Express known as packaged
applications. Packaged Applications are fully functional applications that you can view, use and
customize. These packaged applications can be downloaded from URL
http://www.oracle.com/technology/products/database/application_express/packaged_apps/packag
ed_apps.html .
Even if you download and use packaged application, sometimes and especially for beginners it
becomes a challenge to really understand how these packages applications have been developed
and decipher each and every component of it. This step-by-step guide is an attempt to address that
problem, where you will recreate each any every component of the application yourself and have
full understanding of it.
One of such packaged applications is “Aria Employee Directory Lookup”. Aria is used globally within
Oracle to look up phone numbers, email addresses and other information about employees. Each
employee can update his or her preferred contact information and upload an image for the
employee profile page. Using this guide you will be able to create Aria Employee Directory Lookup
application from scratch.
Once you have learnt Oracle Application Express, the next step is to put it to use. Training is
necessary for getting the fundamentals right but there can be many challenges when you actually
get down to create an application. Having a step-by-step guide that will walk to you through the
different steps of how to create an actual application will give you an added advantage. It’s like
taking an expressway to gain experience to develop real life applications.
Please do ensure that you are following the instructions carefully to get the application up and
running. Any small typo or overlook may cause the application not to function properly. We will also
highly recommend you to go through these step by step guide at least twice to have a thorough
understanding of the entire application.
Please do not forget to send your comments, feedback and suggestions to contact@dbcon.com .
Please specify “Aria Employee Directory Lookup” in your subject line for all communications with
regards to this document.
To use this guide effectively you must have the basic understanding of Oracle Application Express. If
you are an absolute beginner in Oracle APEX we will highly recommend you to look at our training
program “Developing Applications with Oracle Application Express” before you dive into this guide.
Last but not the least, support environment causes. Please do not print this document if you can
avoid it.
Enjoy !
Team DBCON
http://www.dbcon.com
Like any other application, Aria Employee Directory Lookup is also dependent on other supporting
objects. These support objects include
Database Objects likes tables, indexes, packages, procedures, functions, sequences
etc.
Sample data in the tables
Image Files
Javascript Files
CSS Files
In order to get started with the development of this application, you need to prepare your
environment first. As our focus is just on creating the Aria Employee Directory Lookup application in
Oracle APEX, a script has been provided which will create all of the above mentioned supporting
objects in your APEX workspace. (If you do not have an APEX workspace, you can sign up for one at
http://apex.oracle.com . The workspaces are provided free of charge and the only limitation is you
cannot have more than 10 MB of data)
DBCON can also provide you an APEX workspace to complete this exercise at a charge of US$ 10 per
month. If you want to sign up for an APEX workspace at DBCON, please send us a mail at
contact@dbcon.com . We will give you instructions on how to pay and access your workspace.
Once the script is downloaded and you have got an APEX workspace follow the following steps to
prepare the environment. Please ensure that you do not have any database objects that start with
the name ARIA.
IMPORTANT
To avoid overwriting any existing objects with the objects of this application, it is highly
recommended that you create a new workspace and a new schema so that you have a fully separate
environment for this step-by-step guide.
Getting Started
Creating the Application
Specify the application name (The Application ID will be assigned automatically). Click next
Specify page name & type, click add page (As it is mandatory to create at least one page at this step,
we will just add a dummy page here. This page will be deleted later)
Click next
Click create
Aria application has got its own theme. Themes control the look and feel of the applications. The
following steps will install a new theme in the application that you have created in the previous step.
Click delete button to delete the page. We will recreate all the pages ourselves with the new theme.
Once you delete page 1 the control will go page 101. Click on delete to delete this page as well
Select Component Defaults tab and change the default for page to " No Tabs with Sidebar " (It is
necessary to change the page default to a different template before installing and switching to the
new theme. Failing to do so will result into error while switching to a new theme)
Select the Theme export file from your PC (If you have not download the supplementary files
required to create this application, please go to URL http://www.dbcon.com/apexapps_aria.html
and download the file). Click ‘Next’
Click next
Once the theme is installed click on Switch Theme to switch to new theme
Click next
Once you have switched the theme, the new theme will have the asterisk mark denoting that this
theme is the currently active theme.
Aria application needs support objects like database objects (tables, indexes, views, packages,
procedures, functions, CSS files, javascript files etc. Follow these steps to create these supporting
objects before you start building the application.
Locate the file AriaSupportingObjects.sql and click upload (If you have not downloaded the
supplementary files required to create this application, please do to URL
http://www.dbcon.com/apexapps_aria.html and download the file).
Once uploaded click on the file name to run the script file
On results page, scroll to the bottom of the page and ensure that all the commands in the script
have been executed without any error. If there are any errors, please correct the error before
continuing.
Create the application users. These users are employees in ARIA application and they will be able to
update their information in the application.
Specify the user name as SKING. Also specify password (passwords are case sensitive), email address
and set require change of password on first use to no. Click on create and create another.
Create another user with name JCHEN. Specify password, email and require change of password on
first use. Click on create and create another
Follow these steps to create page 410 which will be the login page for the application.
Shared Components
Shared Components are components that are defined once and then can be used in multiple places
in the application. First create the different shared components that are required in the application.
These components will then be used in the different pages of the application that you will be
creating in subsequent steps.
Application Items
Application Items are used as global variables in an APEX application. Application items are not
associated with a page and therefore have no user interface properties.
In this step-by-step guide, all application items will have a prefix of " AI_ " as a standard naming
convention
Click on Create
Repeat the above 2 steps to create the following application items also
AI_FORWARD_NAME
AI_CURRENT_USER_PERSON_ID
AI_RELATE_TO_PERSON_ID
AI_TEMP_ID
AI_TEMP_PAGE_ID
Once all the application items are created it should look as following
Lists
A list is a shared collection of links. You add a list to a page by creating a region and specifying the
region type as List. You control the appearance of a list through list templates. Follow these steps to
create lists
Click on Create
Select Entry tab. Specify List Entry Label. Click Target tab
Click on target tab and specify the target attributes (All the target pages will be created in
subsequent steps)
Select Current List Entry tab. Specify List Entry Current for Condition
Repeat the above steps to create the following list entries under list Employee View Options
Once all the List entries are created it should appear as following
Click on create button under Shared Components -> Lists to create another list called ‘Edit Options’
Select current list entry attribute and specify list entry current for condition. Click create and create
another
Contact Information
Select target attribute and specify the details (Notice that there is a trailing “ . “ after
&AI_PERSON_ID)
Select current list entry attribute and specify list entry current for condition. Click on create and
create another
Select current list entry attribute and specify list entry current for condition. Click on create and
create another
Navigation bar entries offer an easy way to move users between pages in an application. For
example, a navigation entry enables you to display a link from an image or text. The associated page
template determines the location of a navigation bar.
Click create
Click Create
Click create
Click on Logout Navigation Bar Entry (This navigation bar entry was created automatically when the
application was created)
Select Authorization tab and specify the authorization scheme. Click Apply Changes
List of Values
Click on create
EXTENDED_INFORMATION_TYPE
Specify the query for dynamic LOV, click create list of values
Build Options
Build options enable you to conditionally display specific functionality within an application. Build
options have two possible values: INCLUDE and EXCLUDE. If you specify an attribute as being
included, then the Application Express engine considers it part of the application definition at run
time. Conversely, if you specify an attribute as being excluded, then the Application Express engine
treats it as if it did not exist.
Click on Create
Authentication Scheme
Authentication is the process of establishing each user's identify before they can access your
application. Authentication may require a user identify a user name and password or could involve
the use of digital certificates or a secure key.
Click on create
This will create the authentication scheme and make this authentication scheme current.
Authorization Schemes
An authorization scheme extends the security of your application's authentication scheme. You can
specify an authorization scheme for an entire application, page, or specific control such as a region,
item, or button. For example, you could use an authorization scheme to selectively determine which
tabs, regions, or navigation bars a user sees.
Click on create
begin
wwv_flow.g_user := replace(wwv_flow.g_user,'nobody','Public');
return true;
end
(This authorization scheme is not actually being used as an authorization scheme. It is just to change
the username from "nobody" to "Public". In Aria application there are some pages which can be
accessed by anyone (there is no logon required). When a page is accessed by anyone, the username
is set to "nobody". This authorization scheme will change the username from "nobody" to "Public" for
public users.)
(Some pages in this application can be accessed by anyone (i.e. open to public), but to access some
pages, users will need to logon. This authorization scheme will prevent Public’s access to those pages
which needs users to logon)
Application Definition
Click on Definition
Click on Logo tab and specify the logo type and image (Image file aria_logo.gif is created by the
script AriaSupportingObject.sql that you executed in earlier steps). Click Apply Changes
#WORKSPACE_IMAGES#aria_logo.gif
Click on Security -> Authorization Tab. Specify the authorization scheme, click Apply Changes
Application Processes
Click on Create
(aria_detail is a procedure that has been created in the database. This on demand application
process is simply calling that database procedure)
Page 0
Page zero functions as a master page. The Application Express engine renders all components you
add to page zero on every page within your application.
Click Finish
Specify the region source (available as " Code: Page-0-1 " in AriaLabSupplement.txt), click next
Specify the region condition (available as " Code: Page-0-2 " in AriaLabSupplement.txt). Click create
region
Specify the region source (available as " Code: Page-0-3 " in AriaLabSupplement.txt), click Create
Region
Specify region source (available as " Code: Page-0-4 " in AriaLabSupplement.txt). Click Create Region
Specify region source (available as " Code: Page-0-5 " in AriaLabSupplement.txt), click Create Region
Select Header and Footer attribute. Specify Region Header & Region Footer, click Apply Changes
Region Header
<div style="float:left;">
Region Footer
</div>
<img src="#WORKSPACE_IMAGES#20px_search.jpg"
onclick="doSubmit('P0_QUICK_FIND')" style="cursor:hand;cursor:pointer;"
align="top" alt="Quick Find" id="QUICK_FIND_IMG" />
Select Conditions tab, specify condition type and expression 1. Click on apply changes
This page is a dummy page to support displaying images in the application using
APEX_UTIL.GET_BLOG_FILE_SRC. This page will never be accessed directly by the users. Item created
on this page will be used in Page 2 and page 15
Click next
Click next
Click finish
Click next
Click finish
Click on security tab and change the authentication to “Page is Public”. Setting this to public will not
prompt the users to logon and anyone will be able to view this page.
Select HTML Header tab. Specify the HTML Header attribute (available as " Code: Page-1-1 " in
AriaLabSupplement.txt)
Select HTML Body Attribute tab and specify the Page HTML Body attribute
Onload="PageInit()"
Select display attributes tab and specify cursor focus. Click apply changes
<style>#P1_SEARCH{font-size:14px;width:400px;display:block;}</style>
Navigate to ‘Header and Footer’ attribute and specify the following in HTML Header and Footer.
These attributes will centre align the region on the page. Click on Apply Changes.
</td></tr></table>
Click next
Specify Region Source (Available as " Code: Page-1-2 " in AriaLabSupplement.txt). Click next
Specify the computation, click next (this will remove the text ‘@ORACLE.COM’ from the search string
entered by the user and will convert the search string to upper case. For example if user enter the
search string ashish.agarwal@oracle.com it will be changed to ASHISH.AGARWAL)
trim(replace(upper(:P1_SEARCH),'@ORACLE.COM'))
Click create
Click next
Click create
Create a validation for P1_SEARCH. Click on create under validations under page processing
Specify display attributes, click next (The region sequence number here should be lower than the
sequence number of the region Quick Search that was created in earlier steps)
Specify display attributes, click next (The sequence number of this region should be higher than the
sequence number of the region Quick Search but lower than the sequence number of the region
Results)
<br />Search any part of: <br /> Last Name, First Name, userid, Last 4
digits of work phone.</center>
Select Link attribute. Specify link text. For link attributes specify the following
onmouseover="ARIA_DETAIL(this, '#PERSON_ID#')"
(ARIA_DETAIL is a javascript function that has been defined in aria.js file. This file is created in
the workspace when you run AriaSupportingObjects.sql . This file is included in all the pages
in the application as it has been defined in page 0 in the region named 0.
Also ARIA_DETAIL will call application process Person_Detail and Person_Detail will call the
database procedure aria_detail.)
The link target will be page 2. Pass the PERSON_ID as parameter to page 2. Click >
Click >
For EMAIL column specify the link text, target as URL and URL as ‘ mailto:#EMAIL# ’. click >
For column TITLE specify the Link Text, Target as page ‘3’. Pass the parameters PERSON_ID to page 3
Test Page 1
As the page is displayed, here is where different parts of the page are coming from
Page Template “ No Tabs with Page 0 -> Region – Page Template “ No Tabs with
Sidebar “ -> Footer Attribute Accessible Version Sidebar” -> Footer Attribute
Type % in the search box and press search. All the employees will be displayed
Click next
Just specify a dummy query here. This query will be modified later. (Specifying the actual query here
gives error - ORA-01461: can bind a LONG value only for insert into a LONG column). Click next
Click finish
Click on Help Tab. Specify the Help Text (available as " Code: Page-2-1 " in AriaLabSupplement.txt).
Click apply changes
Select Source attribute. Replace the Region Source with the following query (available as " Code:
Page-2-2 " in AriaLabSupplement.txt)
Select Header and Footer attribute and specify the following. Click apply changes
SELECT forward_name
FROM aria_current
WHERE person_id = nv('AI_PERSON_ID')
AND current_flag = 'Y'
Click create
Testing Page 2
Run application
Hover your mouse on manager’s name and a box will appear specify the manager’s details. The
report template ‘Person_Detail’ contains the onmouseover event which calls javascript function
ARIA_DETAIL defined in aria.js file
Click next
Click finish
Navigate to HTML Header attribute and enter the HTML Header (available as Code: Page-3-1 in
AriaLabSupplement.txt). Click Apply Changes
Click on help tab and specify the page help (available as " Code: Page-3-2 " in
AriaLabSupplement.txt). Click apply changes
Specify source (available as " Code: Page-3-3 " in AriaLabSupplement.txt), click next
Specify source (available as " Code: Page-3-4 " in AriaLabSupplement.txt), click next
Select the source attribute and specify region error message. Click apply changes
Specify region source (available as " Code: Page-3-5 " in AriaLabSupplement.txt), click next
Select layout and pagination tab and change pagination scheme to "No Pagination Selected"
Click on Messages tab and remove all the messages. Click apply changes
Repeat the above two steps for other regions "Employee" & "Reports" also
SELECT forward_name
FROM aria_current
WHERE person_id = nv('AI_PERSON_ID')
AND current_flag = 'Y'
Click create
Testing Page 3
Type " Eleni " in the search box and press search button. In the search result click on the employee
name
Page – 18 – Relate
Click finish
Navigate to Header and Footer tab and specify region header. Click on apply changes
Specify region source (available as " Code: Page-18-1 " in AriaLabSupplement.txt), click next
Select column attributes tab and change the report column headings and the order in which they
appear.
Select link tab and specify the link details. Click apply changes
replace(upper(:P18_RELATE_TO_FIND), '@ORACLE.COM')
Click create
Click create
Testing Page 18
Page – 19 – Relation
Click next
Click finish
aria_api.relationship_html(:AI_PERSON_ID, :AI_RELATE_TO_PERSON_ID);
Select Header and Footer tab and specify the header and footer attribute. Click Apply Changes
Type % in the search box and click search. Click on an employee name (e.g. “Sundar”)
Enter the name of the person to which you want to relate the person selected in previous step (e.g.
“Gerald”. Click search. All the employees whose name matches with the search string will be
displayed. Click on the name of the employee to which you want to relate the person to.
Page 18 ->
Region - Relate
Click on “Gerald” name will take you to page 19 where the relationship between “Sundar” &
“Gerald” will be displayed graphically
Click next
Click finish
<style>
.orgManager td{text-align:center;border:2px #CCCCCC solid;font-
size:11pt;padding:2px;}
.orgManager td a{display:block;}
.orgManager td.dashed{border:2px #ccccCC dashed;}
</style>
Select Security tab. Change the authentication to “Page Is Public”. Click apply changes
Specify region source (available as " Code: Page-80-1 " in AriaLabSupplement.txt), click create region
Select Header and Footer tab, specify Region header and footer. Click Apply Changes
Testing Page 80
Run application
Type % in the search box and click search. From search output, click on any name
Click on Management Chain (clicking on Management Chain will take you to page 80)
Management Chain from the employee you selected in the previous step will be displayed to the top
management.
Click next
Click finish
Click on header and footer attribute. Specify the region header, click apply changes
Specify the region source (available as " Code: Page-6-1 " in AriaLabSupplement.txt). Click next
htp.p('elap='||to_char((dbms_utility.get_time -
wwv_flow.g_package_instantiated ) * .01,'999990.00'));
P0_QUICK_FIND
Repeat the above steps to create the following items with the following difference (For all other
attributes please select the value as specified above)
Run the page and the page should like the following at this stage
Repeat the above steps to create another button with following changes (rest of the attributes will
remain the same as specified above)
Click create
Testing Page 6
Clicking on advanced search will run page 6. Enter any search criteria and click on find button. The
search output will be displayed.
Click finish
Specify region source (available as " Code: Page-17-1 " in AriaLabSupplement.txt), click create region
Select header and footer tab and specify the region header.
Click on report attributes and select column attribute tab. Change heading type
Select layout and pagination tab and change the report template. Modify the attributes and click
apply changes
aria_api.get_person_id_by_account(v('USER'))
Select source tab and specify the computation error message. Click apply changes
SELECT forward_name
FROM aria_current
WHERE person_id = nv('AI_PERSON_ID')
Test Page 17
As page 17 is not accessible to public, it will first take you to the login screen. Logon to the
application using the usernames that you created in earlier steps.
Once you logon as SKING, the record of SKING will be displayed which can then be edited.
Click next
Specify branching
Click finish
Change title
Add extra information such as a cell phone, a pager number, perhaps a link
to web site.
Select header and footer tab. Specify region header, click apply changes
Specify display attributes, click next. (The sequence number of this region should be lower than the
sequence number of the other region)
Edit &AI_FORWARD_NAME.
Select LOV tab and specify LOV attributes. Click > to edit the attribute of next item (i.e.
P8_PERSON_ID)
Select name attribute tab and modify display as attribute. Click >
Change the ‘Display as’ attribute of item P8_PICTURE_URL. Click > to edit the attribute of next item
(i.e. P8_PHONE1_DESC)
Click on Element tab and change the Horizontal / Vertical Alignment to ‘Left Top’. Click > to edit the
attribute of the next item (i.e. P8_PHONE1_DATA)
Under Element tab change the value of Horizontal / Vertical Alignment attribute to ‘Left Top’
Select Label tab and change the attribute Horizontal / Vertical Alignment to ‘Above’. Click > to edit
the attribute of the next item.
Repeat the steps above (i.e change the label alignment and element alignment) to change the
attributes of following items. Click on apply changes for the last item
P8_PHONE1_TYPE
P8_PHONE2_DESC
P8_PHONE2_DATA
P8_PHONE2_TYPE
P8_PHONE3_DESC
P8_PHONE3_DATA
P8_PHONE3_TYPE
P8_PHONE4_DESC
P8_PHONE4_DATA
P8_PHONE4_TYPE
P8_PHONE5_DESC
P8_PHONE5_DATA
P8_PHONE5_TYPE
Under items click on item ‘P8_PHONE1_TYPE’ to edit the attribute of the item
Select LOV tab and specify the list of value. Click apply changes
P8_PHONE2_TYPE
P8_PHONE3_TYPE
P8_PHONE4_TYPE
P8_PHONE5_TYPE
Run the page. The page should now look like this. Click on "Edit Page 8" to go back to page definition
&AI_PERSON_ID.
Click create
Specify process attributes (ensure that this process has the lower sequence number than the other
process Fetch Row from ARIA_UPDATABLE_DATA), click next
Specify the process (available as " Code: Page-8-1 " in AriaLabSupplement.txt), click create process
Specify process attributes, click next. (Ensure that this process has the lowest sequence number from
all other processes)
Specify process (available as " Code: Page-8-2 " in AriaLabSupplement.txt), click create process (This
process will ensure that the employees can edit only their own details and not the details of any other
employee)
Click on create under validations. A validation will be created to ensure that users are not entering
any " javascript " or " img " tag in the contact information
Specify validation source (available as " Code: Page-8-3 " in AriaLabSupplement.txt). Click next.
Click delete to delete the reset page process. (This is process is usually used to clear the cache when
the records are deleted. Since we are not providing any delete option to users, this process is not
required)
Specify branch condition, click create branch. (The branch sequence number should be lower than
the existing branch sequence number)
Test Page 8
As page 17 is not accessible to public, it will first take you to the login screen. Logon to the
application using the usernames that you created in earlier steps.
Once you logon as SKING, the record of SKING will be displayed which can then be edited. Click on
Contact Information which will call page 8
Edit the information and click apply changes. Pressing apply changes will take you back to page 1.
Navigate to the same screen again and ensure that the information you entered is getting displayed.
Once you are back on page 8 again, enter " javascript " in the second field and press apply changes.
The validation created on the page will display an error message.
Click next
Click finish
Click on help tab and specify the help text. Click apply changes
Your detail page provides for one optional photo. You can use this page to
upload a new photo.
Click next
SELECT *
FROM aria_updatable_data
WHERE person_id = :AI_PERSON_ID
AND picture_url is not null
return '<img
src="'||apex_util.get_blob_file_src('P99_BLOB_CONTENT',:AI_PERSON_ID)||'"
/>';
if nvl(aria_api.get_person_id_by_account(v('USER')),'1') !=
nvl(v('AI_PERSON_ID'),'2') then
raise_application_error (-20001,'No privilege for attempted
operation.');
end if;
You must specify a photo file from your hard drive before clicking the
"Upload Photo" button.
aria_image.remove(:AI_PERSON_ID);
Testing Page 15
Click finish
Edit &AI_FORWARD_NAME.
If this image is the image you would like to make your current image then
press the “Save This Picture” button.
<ol>
<li>Identify file containing your photo.</li>
<li style="font-weight:bold;">Validate the uploaded image is proper.</li>
</ol>
Specify item source (available as " Code: Page-16-1 " in AriaLabSupplement.txt), click next
Specify process (available as " Code: Page-16-2 " in AriaLabSupplement.txt), click next
aria_image.add (
p_person_id => v('AI_PERSON_ID'),
p_filename => v('P15_PHOTO')
);
Locate the picture on your PC and click upload photo (clicking on upload photo will take you to page
16)
Once you save the picture, it will take you back to page 2 where now you can view the picture. Click
on edit my information again to delete or change the photo
Click on photo
Page 15 –>
Region - Your
Current Aria
People Photo
Click next
Click finish
Specify the multiple HTML region title and template. Click on create regions
Enter your search criteria in the field above and press return. Search any
part of:
<ul>
<li>Last Name</li>
<li>First Name</li>
<li>Maiden Name</li>
<li>userid</li>
<li>Last 4 digits of work phone</li>
</ul>
Click on the second region name to modify the attributes of the region
Click on the third region name to modify the attributes of the region
Click on the fourth region name to modify the attributes of the region
Test Page 11
Specify SQL Query (available as " Code: Page-400-1 " in AriaLabSupplement.txt), click next
Click finish
Select display attributes tab and change the page template and title.
Select help tab. Specify the the help text, click apply changes
Enter search conditions then press the Find button. Use the "%" for
wildcards. Searches are case insensitive. The first 100 rows that meet your
search criterion will be displayed.
<p>
The profile search box queries unstructured data entered by users into
their aria Profile section. Similarly, the Contact search box queries
unstructured data entered into people's Contact Information section. All
other data elements query structured data. The profile attribute can
include "and" and "or" operators. Use the synonyms checkbox to include
synonyms for profile search terms.
<p>
Wildcards are not supported for the profile attribute. If you do not use
a wild card for a structured attribute (any attribute except profile) then
the search looks for an exact (case insensitive) match.
Select conditions tab and specify region condition. Click on Apply Changes
Enter a search condition and click Go. All the employee names having the search string will be
displayed.
Conclusion
This finishes step-by-step guide to create Aria People application. We sincerely hope that you
enjoyed creating the application and it helped you in understanding how applications are developed
in Oracle Application Express.
If you have any comment, feedback or suggestions do send a mail to contact@dbcon.com with “Aria
People Application” in your subject line. If you notice any error in this step-by-step guide, do let us
know so that we can make corrections in the document.
If you are finding it difficult to understand the different components of the application in this guide
and why certain things were done in a certain way, we will suggest you to consider taking our
training courses in Oracle Application Express. For beginners we will build a solid foundation by
explaining the individual components of Oracle Application Express and then will move on to explain
how to exploit the advanced features of Oracle APEX.
In our training program, we have also come up with exhaustive hands-on lab exercises with each
topic. We will give you step-by-step instructions on how to build the application using wizards and
manually. How to build different components individually and then like the pieces of a jigsaw puzzle
put everything together to see the big picture.
To learn more about our training programs in Oracle Application Express visit
http://www.dbcon.com/courses.html
Team DBCON !
E-Mail: contact@dbcon.com
URL: http://www.dbcon.com