This section describes how to configure workspace preferences for workspace login controls, access to Application Builder and SQL Workshop, support for PL/SQL editing and RESTful services, and access to Team Development.
Tip:
Some of these preferences can also be configured for an entire instance. If applicable, this section includes references to any instance-level settings.This section describes how to configure workspace login controls.
Administrators can configure login controls for an entire Oracle Application Express instance or for each individual workspace. For example, if an Instance administrator configures account login controls in Oracle Application Express Administration Services that configuration applies to all Application Express accounts in all workspaces across an entire instance.
If the Instance administrator does not enable login controls across an entire instance, then each Workspace administrator can configure the following controls on a workspace-by-workspace basis:
End-user account expiration and locking
A maximum number of failed login attempts for end-user accounts
The password lifetime (or number of days an end-user account password can be used before it expires for end-user accounts
Tip:
This feature applies only to accounts created using the Application Express user creation and management. Application Accounts Authentication provides additional authentication security for applications. See "Managing Users in a Workspace."To configure login controls for a workspace:
Navigate to the Workspace Administration page. See "Accessing the Workspace Administration Page."
The Workspace Administration home page appears.
Click Manage Service.
Click Set Workspace Preferences.
Under Account Login Control:
Account Expiration and Locking - Make a selection to determine whether Application Express end user accounts can be expired or locked. This feature applies only to end-user accounts created using the Application Express user management interface. Options include: Enable or Disable.
If you select Enable, end-user account passwords expire after the time period specified and accounts are locked after a configurable number of authentication failures. Account passwords can be set to expire after the first use.
Tip:
If the Instance administrator sets 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.
See Also:
"Configuring Authentication Controls"To control access to Application Builder:
Navigate to the Workspace Administration page. See "Accessing the Workspace Administration Page."
The Workspace Administration home page appears.
Click Manage Service.
Click Set Workspace Preferences.
Scroll down to Application Builder.
To Enable Application Builder, select Yes. To disable Application Builder, select No.
Click Apply Changes.
Tip:
These settings can be overridden by an Instance administrator. See "Managing Component Availability for an Instance."To control access to SQL Workshop:
Navigate to the Workspace Administration page. See "Accessing the Workspace Administration Page."
The Workspace Administration home page appears.
Click Manage Service.
Click Set Workspace Preferences.
Scroll down to SQL Workshop.
To Enable SQL Workshop, select Yes. To disable SQL Workshop, select No.
Click Apply Changes.
Tip:
These settings can be overridden by an Instance administrator. See "Managing Component Availability for an Instance."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 Set Workspace Preferences page.
To disable PL/SQL program unit editing:
Navigate to the Workspace Administration page. See "Accessing the Workspace Administration Page."
The Workspace Administration home 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.
See Also:
"Disabling PL/SQL Program Unit Editing" and "Using SQL Commands" in Oracle Application Express SQL Workshop GuideUse the Enable RESTful Services attribute to control whether developers can expose report regions as RESTful services. You can enable RESTful services for specific workspace or for an entire development instance.
To configure RESTful access for a workspace:
Navigate to the Workspace Administration page. See "Accessing the Workspace Administration Page."
The Workspace Administration home page appears.
Click Manage Service.
Click Set Workspace Preferences.
Scroll down to SQL Workshop.
From Enable RESTful Services, select one of the following:
Yes - Enables developers to expose report regions as RESTful services.
No - Prevents developers from exposing report regions as RESTful services.
For Path Prefix, specify the path prefix to be used to access RESTful Services in the current workspace.
For example, a workspace named QA_1 could have a path prefix set to QA. The default value is the short name of the workspace.
Click Apply Changes.
See Also:
"Controlling RESTful Services for an Instance" and "Using RESTful Services" in Oracle Application Express SQL Workshop GuideUse the options under Team Development to specify whether Team Development is available in the current workspace, enable support for file attachments, and specify the maximum size of uploaded files.
Tip:
This attribute can only be modified if the instance-level setting, Enable Team Development's File Repository is set to Yes. See "Enabling Instance-level Support for File Upload in Team Development."To enable Team Development:
Navigate to the Workspace Administration page. See "Accessing the Workspace Administration Page."
The Workspace Administration home 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 upload in for Team Development file upload:
Navigate to the Workspace Administration page. See "Accessing the Workspace Administration Page."
The Workspace Administration home page appears.
Click Manage Service.
Click Set Workspace Preferences.
Under Team Development:
Enable File Repository - Specify whether to enable file upload in Team Development:
Yes - Enables support for file attachments in Team Development and creates a local APEX$ table to store the files.
No - Disables support for file attachments in Team Development.
Tip:
This attribute can only be modified if the instance-level setting, Enable Team Development's File Repository, is set to Yes. See "Enabling Instance-level Support for File Upload in Team Development."Maximum File Size (in MB) - Select the maximum file size for any file uploaded into the team development file repository. The default value is 15 MB.
Click Apply Changes.