1. Administration Guide
  2. Workspace and Application Administration
  3. Configuring Workspace Preferences

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

Parent topic: Workspace and Application Administration

2.5.1 Managing Workspace Account Login Controls

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

See Also:

"Configuring Authentication Controls for an Instance"

Parent topic: Configuring Workspace Preferences

2.5.1.1 About Login Controls

Workspace administrators can configure login controls for an individual 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."

Parent topic: Managing Workspace Account Login Controls

2.5.1.2 Configuring Workspace Account Login Controls

Configure login controls for an individual workspace.

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.

      This feature provides additional authentication security for applications. If you select Enable, user account passwords expire after a configurable time period, accounts will be locked after a configurable number of authentication failures, and account passwords can be set to expire after the first use.

      If the Instance administrator sets the Environment Setting Require User Account Expiration and Locking to Yes, this means that this feature must be enabled for all workspaces, Account Expiration and Locking will display Enable and cannot be changed by the workspace administrator.

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

Parent topic: Managing Workspace Account Login Controls

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

Parent topic: Configuring Workspace Preferences

2.5.3 Controlling Access to SQL Workshop

Workspace administrators can control access to SQL Workshop. Use the SQL Workshop to access 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.
  5. Under SQL Workshop, Enable SQL Workshop:
    • Yes- Enable access to SQL Workshop.
    • No - Disable access to SQL Workshop.
  6. Click Apply Changes.

Tip:

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

Parent topic: Configuring Workspace Preferences

2.5.4 Disabling PL/SQL Program Unit Editing for a Workspace

Workspace administrators can control whether developers can 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 SQL Workshop, PL/SQL Editing, select one of the following:

    • Allow PL/SQL program unit editing

    • Do not allow PL/SQL program unit editing

      Disabling this feature discourages developers from changing PL/SQL code directly from the Data Dictionary. If you select Do not allow PL/SQL program unit editing, developers can still create and replace PL/SQL program units using scripts or the SQL Command Processor.

  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

Parent topic: Configuring Workspace Preferences

2.5.5 Enabling RESTful Services and Defining a Path Prefix 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:

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. Under SQL Workshop, Enable RESTful Services:

    • Yes - Enables developers to expose report regions as RESTful services.

    • No - Prevents developers from exposing report regions as RESTful services.

  6. Under SQL Workshop, Path Prefix:

    Path Prefix only displays if Enabled RESTful Services is set to Yes.

    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, path to the RESTful service:

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

See Also:

Parent topic: Configuring Workspace Preferences

2.5.6 Configuring Team Development in an Existing Workspace

Configure Team Development for a workspace.

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.

To configure Team Development 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 Team Development, configure the following:

    Tip:

    These settings do not affect existing workspaces.

    1. Enable Team Development - Specify whether to enable Team Development in the current workspace. Select Yes or No.
    2. Enable Issue File Repository - Specify whether to enable file upload in the Team Development central file repository:

      • Yes - Select Yes to enable file upload.

      • No - Select No to disable file upload.

    3. 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.
    4. Enable Feedback File Repository - Specify whether to enable file upload for Feedback:

      • Yes - Selecting Yes creates a local APEX$ table to store the files.

      • No - Select No to disable file upload for Feedback.

    5. Maximum Feedback File Size (in MB) - Select the maximum file size for any file uploaded into the Feedback file repository. The default value is 15 MB.
  5. Click Apply Changes.

See Also:

Parent topic: Configuring Workspace Preferences

2.5.7 Configuring Session Timeout for a Workspace

Use the Session Timeout attributes for a workspace to reduce exposure at the application-level for abandoned computers with an open web browser.

Workspace administrators configure Session Timeout for a workspace on the Set Workspace Preferences page.

To configure Session Timeout attributes 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 Session Timeout:
    1. Maximum Session Length in Seconds - Define how long (in seconds) sessions can exist and be used by applications in this workspace. This setting is superseded by the corresponding application-level setting.

      • Enter a positive integer to control how long a session can exist.

      • Enter 0 to have sessions exist indefinitely.

      • Leave the value empty in order to use the time defined at the instance-level.

    2. Maximum Session Idle Time in Seconds - The Session Idle Time is the time between the last page request and the next page request. This setting is superseded by the corresponding application level setting.

      • Enter a positive integer to control the default idle time for sessions used by applications in this workspace.

      • Leave the value empty in order to use the idle time defined at the instance-level.

    3. Session Timeout Warning in Seconds - The session timeout warning time defines (in seconds) how long before a session times out (either maximum session length, or maximum session idle time), to warn the user. For the maximum session idle time warning, the user will have the opportunity to extend the session. For maximum session length warning, the user will be prompted to save any work, to avoid loss of data when the session maximum time is reached. This setting is superseded by the corresponding application level setting. Options include:

      • Enter a positive integer to control the default idle time for sessions used by applications in this workspace.

      • Enter 0 to switch off session timeout warnings for sessions used by applications in this workspace.

      • Leave the value empty in order to use the warning time defined at instance level.

  5. Click Apply Changes.

See Also:

Parent topic: Configuring Workspace Preferences