Databases Reference
In-Depth Information
Figure 5-12.
The Add Page section of the wizard as it appears for the example application
Copying Shared Components
The next screen asks whether you wish to copy shared components from another application. This comes in handy if
you have a template application that houses components that are shared across applications in the same workspace.
Copying shared components isn't an advanced procedure, but it does lend itself to a controlled and mature
development process. This feature step in the wizard is a convenience, because the same objects can be copied in
other ways after the application has been created. You don't need this step, because you're creating an application
from scratch. Skip the step as follows:
5.
Select
No
for
Copy Shared Components from Another Application
, and click
Next
.
Application Attributes
The next step in the wizard allows you to set some of the application-level attributes such as the type of authentication
to use, whether to use tabs, and globalization attributes including where to derive the primary language, date formats,
and so on. Let's look at each of these individually so you can gain a full understanding of the ramifications of each.
Selecting an Authentication Method
With every application, you need to make a choice about authentication, even if that choice is no authentication at all.
This topic is discussed further in Chapter 9. By default, the APEX Create Application Wizard provides three options for
authentication:
•
Application Express
: Users and passwords are local to the APEX workspace. These users are
managed in the same way the developer accounts are managed inside the APEX workspace,
and users only work inside the current workspace.
