Workspace administrators can configure the following preferences for the current workspace, including login controls, support for Application Builder, SQL Workshop, PL/SQL editing, and Team Development.
Topics:
There are two different ways to configure login controls:
An Instance administrator enables account login controls for all Application Express accounts in all workspaces across a development instance.
If your Instance administrator configures these preferences for an instance, those settings display as the defaults for all workspaces. See "Enabling Login Controls for All Workspaces".
If the Instance administrator does not enable login controls across an entire instance, then each Workspace administrator can enable the following controls on a workspace-by-workspace basis:
Require end-user account expiration and locking
Set up a maximum number of failed login attempts for end-user accounts
Set the password lifetime for end-user accounts, that is, the number of days an end-user account password can be used before it expires
This feature applies only to accounts created using the Application Express user creation and management facilities. It provides additional authentication security for applications. See "Managing Application Express Users".
To enable login controls for a workspace:
Log in to Oracle Application Express. See "Logging In To Oracle Application Express" in Oracle Application Express Application Builder User's Guide.
The Workspace home page appears.
Click the Administration icon.
The Administration page appears.
Click Manage Service.
Click Set Workspace Preferences.
Under Account Login Control:
Account Expiration and Locking - Click Enable.
If you select Enable, end-user account passwords expire after a configurable time period and accounts are locked after a configurable number of authentication failures. Account passwords can be set to expire after the first use.
If your Instance administrator set the Require User Account Expiration and Locking preference to Yes, this preference defaults to Enable and you cannot update it.
Maximum Login Failures Allowed - Enter a positive integer for the maximum number of consecutive unsuccessful authentication attempts allowed before an end-user account is locked. If you do not specify a value in this field, the instance-level setting for Maximum Login Failures Allowed is used.
End User Account Lifetime (days) - Enter a positive integer for the maximum number of days an end-user account password may be used before the account expires. If you do not specify a value in this field, the instance-level setting for Account Password Lifetime is used.
Click Apply Changes.
To enable Application Builder:
Log in to Oracle Application Express. See "Logging In To Oracle Application Express" in Oracle Application Express Application Builder User's Guide.
The Workspace home page appears.
Click the Administration icon.
The Administration page appears.
Click Manage Service.
Click Set Workspace Preferences.
Scroll down to Application Builder.
For Enable Application Builder, select Yes. To disable Application Builder, select No.
Click Apply Changes.
These settings can be overridden by an Instance administrator. See "Managing Component Availability".
To enable SQL Workshop:
Log in to Oracle Application Express. See "Logging In To Oracle Application Express" in Oracle Application Express Application Builder User's Guide.
The Workspace home page appears.
Click the Administration icon.
The Administration page appears.
Click Manage Service.
Click Set Workspace Preferences.
Scroll down to SQL Workshop.
For Enable SQL Workshop, select Yes. To disable SQL Workshop, select No.
Click Apply Changes.
These settings can be overridden by an Instance administrator. See "Managing Component Availability".
By default, developers can change and compile PL/SQL source code when browsing database procedures, packages, and functions in SQL Workshop Object Browser. Workspace administrators can disable PL/SQL program unit editing by selecting Do not allow PL/SQL program unit editing on the Preferences page.
To disable PL/SQL program unit editing:
Log in to Oracle Application Express. See "Logging In To Oracle Application Express" in Oracle Application Express Application Builder User's Guide.
The Workspace home page appears.
Click the Administration icon.
The Administration page appears.
Click Manage Service.
Click Set Workspace Preferences.
Scroll down to SQL Workshop.
Under PL/SQL Editing, select one of the following:
Allow PL/SQL program unit editing
Do not allow PL/SQL program unit editing
If you select Do not allow PL/SQL program unit editing, developers can still create and replace PL/SQL program units using scripts or SQL Commands.
Click Apply Changes.
"Disabling PL/SQL Program Unit Editing" and "Using SQL Commands" in Oracle Application Express SQL Workshop Guide
Use the options under Team Development to specify whether Team Development is available in the current workspace and to enable support for file attachments.
Topics:
To enable Team Development:
Log in to Oracle Application Express. See "Logging In To Oracle Application Express" in Oracle Application Express Application Builder User's Guide.
The Workspace home page appears.
Click the Administration icon.
The Administration page appears.
Click Manage Service.
Click Set Workspace Preferences.
Scroll down to Team Development.
For Enable Team Development, select either:
Yes - Select Yes to enable Team Development in the current workspace.
No - Select No to disable Team Development in the current workspace.
Click Apply Changes.
To enable support for file attachments in Team Development:
Log in to Oracle Application Express. See "Logging In To Oracle Application Express" in Oracle Application Express Application Builder User's Guide.
The Workspace home page appears.
Click the Administration icon.
The Administration page appears.
Click Manage Service.
Click Set Workspace Preferences.
Scroll down to Team Development.
For Enable File Repository, select either:
Yes - Select Yes to enable support for file attachments in Team Development. Selecting Yes creates a local APEX$ table to store the files.
No - Select No to disable support for file attachments in Team Development.
Click Apply Changes.