1.5 Configuring Workspace Preferences

Configure workspace preferences for workspace login controls, access to App Builder and SQL Workshop, support for PL/SQL editing and RESTful services, and access to Team Development.

Some workspace preferences can also be configured for an entire instance. If applicable, the section includes references to any instance-level settings.

Tip:

You can access many workspace administration functions (such as Manage Service, Set Workspace Preferences) from both the Administration menu and the Workspace Administration home page. For consistency, this section navigates the user to the Workspace Administration home page.

• Creating Account Login Controls for a Workspace
  Configure workspace login controls such as account expiration and locking, maximum number of failed login attempts, and password lifetime.
• Controlling Access to App Builder
  Control whether developers can access App Builder.
• Controlling Access to SQL Workshop
  Control whether developers can access to SQL Workshop. SQL Workshop includes tools for viewing and managing database objects.
• Disabling PL/SQL Program Unit Editing for a Workspace
  Determine whether developers have the ability to edit and compile PL/SQL program units from Object Browser.
• Enabling RESTful Services for a Workspace
  Workspace administrators can control whether RESTful Services are enabled in the current workspace.
• Enabling Team Development File Upload for a Workspace
  Enable support for file upload in Team Development.
• Managing Legacy Team Development for a Workspace
  Use the options under Legacy Team Development (Deprecated) to specify whether Legacy Team Development is available in the current workspace, enable support for file attachments, and specify the maximum size of uploaded files.

1.5.1 Creating Account Login Controls for a Workspace

Configure workspace login controls such as account expiration and locking, maximum number of failed login attempts, and password lifetime.

• About Login Controls
  Workspace administrators can configure login controls for an individual workspace.
• Configuring Workspace Account Login Controls
  Configure workspace account login controls on the Set Workspace Preferences page.

See Also:

"Configuring Authentication Controls for an Instance"

1.5.1.1 About Login Controls

Workspace administrators can configure login controls for an individual workspace.

Workspace administrators can also configure login controls for an entire Oracle Application Express instance. 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."

1.5.1.2 Configuring Workspace Account Login Controls

Configure workspace account login controls on the Set Workspace Preferences page.

To configure login controls for a workspace:

1. Navigate to the Workspace Administration page:
   1. Sign in to Oracle Application Express.
   2. At the top of the Workspace home page, click the Administration menu and select Administration.

   The Workspace Administration home page appears.

2. Click Manage Service.
3. Click Set Workspace Preferences.
4. Under Account Login Control:
   1. 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.
   2. 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.

      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.

   3. 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.
5. Click Apply Changes.

See Also:

"Configuring Authentication Controls for an Instance"

1.5.2 Controlling Access to App Builder

Control whether developers can access App Builder.

To control access to App Builder:

1. Navigate to the Workspace Administration page:
   1. Sign in to Oracle Application Express.
   2. At the top of the Workspace home page, click the Administration menu and select Administration.

   The Workspace Administration home page appears.

2. Click Manage Service.
3. Click Set Workspace Preferences.
4. Scroll down to App Builder.
   • To Enable App Builder, select Yes.
   • To disable App Builder, select No.
5. Click Apply Changes.

Tip:

These settings can be overridden by an Instance administrator. See "Managing Component Availability for an Instance."

1.5.3 Controlling Access to SQL Workshop

Control whether developers can access to SQL Workshop. SQL Workshop includes tools for viewing and managing database objects.

To control access to SQL Workshop:

1. Navigate to the Workspace Administration page:
   1. Sign in to Oracle Application Express.
   2. At the top of the Workspace home page, click the Administration menu and select Administration.

   The Workspace Administration home page appears.

2. Click Manage Service.
3. Click Set Workspace Preferences.
4. Scroll down to SQL Workshop.
   • To Enable SQL Workshop, select Yes.
   • To disable SQL Workshop, select No.
5. Click Apply Changes.

Tip:

These settings can be overridden by an Instance administrator. See "Managing Component Availability for an Instance."

1.5.4 Disabling PL/SQL Program Unit Editing for a Workspace

Determine whether developers have the ability to edit and compile PL/SQL program units from Object Browser.

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:

1. Navigate to the Workspace Administration page:
   1. Sign in to Oracle Application Express.
   2. At the top of the Workspace home page, click the Administration menu and select Administration.

   The Workspace Administration home page appears.

2. Click Manage Service.
3. Click Set Workspace Preferences.
4. Scroll down to SQL Workshop.
5. 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.

6. Click Apply Changes.

See Also:

"Disabling PL/SQL Program Unit Editing for an Instance" and "Using SQL Commands" in Oracle Application Express SQL Workshop Guide

1.5.5 Enabling RESTful Services for a Workspace

Workspace administrators can control whether RESTful Services are enabled in the current workspace.

Tip:

RESTful Services requires that the web listener in your configuration uses Oracle REST Data Services release 2.0 or later.

To configure RESTful access:

1. Navigate to the Workspace Administration page:
   1. Sign in to Oracle Application Express.
   2. At the top of the Workspace home page, click the Administration menu and select Administration.

   The Workspace Administration home page appears.

2. Click Manage Service.
3. Click Set Workspace Preferences.
4. Scroll down to SQL Workshop.
5. 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.

6. If Enabled RESTful Services is set to Yes, configure Path Prefix. In Path Prefix, specify the URI path prefix to be used to access RESTful Services in the current workspace. The default path prefix value is the name of the workspace.

   For example, a workspace named QA_1 could have a path prefix set to QA. In this case, the sample RESTful service would be available at:

   http://www.example.com/apex/qa/hr/employees/
7. Click Apply Changes.

See Also:

• "Enabling RESTful Services for an Instance " to learn about enabling RESTful Services at the instance-level in the Administration Services application

• "Enabling Data Exchange with RESTful Services" in Oracle Application Express SQL Workshop Guide

1.5.6 Enabling Team Development File Upload for a Workspace

Enable support for file upload in Team Development.

To enable users to attach files to issue comments in Team Development, you must set the Enable Issue File Repository attribute for the workspace to Yes.

Tip:

You can only modify the workpace-level attribute if the instance-level setting, Enable Issue File Repository, has already been enabled. See "Enabling Instance-level Support for File Upload in Team Development."

To enable support for file upload in Team Development:

1. Navigate to the Workspace Administration page:
   1. Sign in to Oracle Application Express.
   2. At the top of the Workspace home page, click the Administration menu and select Administration.

   The Workspace Administration home page appears.

2. Click Manage Service.
3. Click Set Workspace Preferences.
4. Find Team Development.
5. For Enable Issue File Repository, select one of the following:

   • Yes - Allow files to be uploaded into the Team Development central file repository.

   • No - Do not allow files to be uploaded into the Team Development central repository.

6. Click Apply Changes.

See Also:

"Enabling Instance-level Support for File Upload in Team Development"

1.5.7 Managing Legacy Team Development for a Workspace

Use the options under Legacy Team Development (Deprecated) to specify whether Legacy Team Development is available in the current workspace, enable support for file attachments, and specify the maximum size of uploaded files.

WARNING:

Legacy Team Development is deprecated in Oracle Application Express release 19.2 and will be removed in a future release.

• Enabling Legacy Team Development for a Workspace
  Control whether developers can access Legacy Team Development.
• Enabling Workspace-level File Upload in Legacy Team Development
  Control whether Legacy Team Development supports workspace-level file upload.

1.5.7.1 Enabling Legacy Team Development for a Workspace

Control whether developers can access Legacy Team Development.

To enable Legacy Team Development:

1. Navigate to the Workspace Administration page:
   1. Sign in to Oracle Application Express.
   2. At the top of the Workspace home page, click the Administration menu and select Administration.

   The Workspace Administration home page appears.

2. Click Manage Service.
3. Click Set Workspace Preferences.
4. Find Legacy Team Development (Deprecated).
5. For Enable Team Development:

   • Select Yes to enable Legacy Team Development in the current workspace.

   • Select No to disable Legacy Team Development in the current workspace.

6. Click Apply Changes.

1.5.7.2 Enabling Workspace-level File Upload in Legacy Team Development

Control whether Legacy Team Development supports workspace-level file upload.

To determine if Legacy Team Development supports workspace-level file upload:

1. Navigate to the Workspace Administration page:
   1. Sign in to Oracle Application Express.
   2. At the top of the Workspace home page, click the Administration menu and select Administration.

   The Workspace Administration home page appears.

2. Click Manage Service.
3. Click Set Workspace Preferences.
4. Find to Legacy Team Development (Deprecated).
5. Configure the following:

   1. Enable File Repository:

      • 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.

   2. 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.

   Tip:

   Enable File Repository can only be modified if the instance-level setting, Enable Team Development's File Repository, is set to Yes.

6. Click Apply Changes.

See Also:

"Enabling Instance-level Support for File Upload in Legacy Team Development"