Marquee Feature:

Feature : APEX 4.2 Early Adopter
Summary
New Features in Oracle Application Express 4.2
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features
Summary
Numerous features and performance improvements
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Advanced transformation rules in Data Upload feature
Summary
Data Transformation rules that are used within data upload feature, are very basic so far. This will introduced most of other useful expressions - plsql , etc
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Allow Focus Area names to be changed in Team Development
Summary
From the team development features tab you can click a task called "manage focus area names". Additionally from the features "focus area" tab you can click a button called "manage" and you can also navigate to the same manage functionality. You can change the name of any given focus area, for example from "Productttivity" to "Productivity"
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Component Settings
Summary
Plug-In attributes of scope "Application" are currently stored within the plug-in definition. If an existing plug-in is getting replaced or if the subscribe mechanism is used those modified settings will always be overwritten and destroyed.

To make these application wide settings independent of the plug-in and to also provide application level settings for native plug-ins a new shared component named "Component Settings" has been added. It will allow you to edit all native plug-ins and installed plug-ins which have custom attributes of scope "Application".

Plug-ins have an option "Subscribe Component Settings" (Y/N) to specify if the component settings of the plug-in in the master application should be subscribed or the local settings should be used.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Control Deep-Linking at the application level
Summary
Provide a feature which prevents deep-linking to an application. Deep-linking into an application can be either be enabled or disabled.
When disabled session state within a URL call is ignored and the user is sent to the home page.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Debug API Improvements
Summary
Re-designed Debug API called apex_debug.
This is renamed from apex_debug_message, but the old synonym is still in place for compatibility.
** apex_debug.enable;
** apex_debug.disable;
** apex_debug.error('Level 1 - Critical error %s occurred - this will always be logged', sqlerrm);
** apex_debug.warn('Level 2 - Non-critical error %s occurred - this will be logged if debug is enabled or the developer is logged into the builder', sqlerrm);
** apex_debug.info('Level 4 - high-level debug message');
** apex_debug.enter('my_procedure', 'p_arg1', p_arg1, 'p_other_arg', p_other_arg);
** apex_debug.trace('Level 6 - low-level debug message');
** apex_debug.message('General-purpose API call to emit the ultimate answer %s at level 3, even if debug is disabled', 42, p_level => 3, p_force => true );
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Debug API Improvements > Provide aliases for the data upload columns
Summary
To avoid the end user having access to the table column names which can be confusing, we can provide a way for the developer to give alias names to the column names.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Debug API Improvements > Allow up to three columns to be passed in Data Upload Key Lookup retrieval
Summary
Currently in data upload feature, with the column lookup it is only possible to pass the value of once column and get back a numerical number as return value.
This feature will be enhanced so that up to three columns values can be passed.
Also, the return value was assumed to be numeric, however there are cases where the return value may have different data type.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Debug API Improvements > Better management of Concurrency in data upload
Summary
Allow developers to define a column for concurrency which will be used to ensure that if after the end user begins the data upload process a row has not been updated by another user.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Debug API Improvements > Character Set conversion for File Upload
Summary
As discussed in different forum threads, the character set conversion is missing and this is a deficiency especially for the users who might be trying to upload files with different character sets.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Debug API Improvements > Multi column data load transformation rules
Summary
Data upload transformation rules are often applicable to different columns. Instead of re-defining the same rule for each column, we can developer the user to re-apply the same rule to a number of different columns at the same time
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Debug Mode should always work if application is executed from APEX Builder
Summary
Debugging of an application should always work if the application is executed from the APEX Builder. The application setting "Debugging" should only be used when the application is directly called.

This will add additional security, because by default the "Debugging" flag could be set to No, because in most cases it's required in a development environment only. This will also prevent that it's forgotten to be set back when the application is exported for a test/production system.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Debug improvements
Summary
Debug Levels - APEX now makes better use of different debug levels when debugging is enabled. It is now possible to enter LEVEL1 - LEVEL9 to control the level of debug detail.
Debug Popup Window - The overview has a new column "Path Info". In the detailed debug rows interactive report, the new column "Call Stack" (not shown by default) displays the PL/SQL call stack for the debug message call. This column only contains values if the log level is 9.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Default page zero to "no URL access"
Summary
When creating page zero via an apex wizard default the page security attribute to no URL access. Making page zero secure by default is good coding practice, and most applications have no reason to run page zero.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Deprecate "DML Fetch Mode" of "Automated Row Fetch" processes
Summary
Deprecate the option "Set Memory Cache On Display" of the "DML Fetch Mode" attribute of "Automated Row Fetch" processes. "Automated Row Fetch" processes should always use the "Set Memory Cache On Fetch" option to avoid confusions and unnecessary digging why session state isn't set.

The "DML Fetch Mode" attribute will only be visible if the DML currently is using "Set Memory Cache On Display". New processes will never show that attribute anymore.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Expose "Compatibility Mode" attribute in Application Properties
Summary
Expose the "Compatibility Mode" attribute in "Edit Application Properties"
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Globalization: allow grid editing of translated text
Summary
Text Messages now support grid editing in Application Express 4.2. At the request of a customer in EA1, it would improve productivity to be able to Grid Edit the translation repository.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Grid Edit of text messages
Summary
To improve productivity of editing translatable text strings in APEX a new grid edit capabilities has been provided
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Improve Usability of Supporting Objects
Summary
Enhance the usability of Supporting Objects by allowing list of supported object to be filtered using an interactive report. Additionally add ability to resequence (by increments of 10) existing supporting object scripts.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Improve creation of On-Demand processes
Summary
Minor enhancements to the creation of On Demand processes:

1) During the creation of on-demand application level processes, inform the developer that ideally, these should be created on the page level.

2) Default the creation of application-level processes to have an initial authorization scheme of "Must Not Be Public User". This will avoid the application level process being executed by users in unauthenticated sessions.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Improvements to failed login handling
Summary
The ability to lockout an account for a period of time long enough to deter brute force attacks has been implemented. This is triggered when a configurable threshold for the maximum number of failed authentication attempts is exceeded.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Increase Page Item Limit on page to 200
Summary
Change the limit on the number of enterable items on a page from 100 to 200.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Integrate latest AnyGantt version
Summary
Integrate the latest version of AnyGantt, release 4.2.0
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Integration of new CKEditor 3.6.2 with Apex
Summary
Integration of New CKEditor 3.6.2 with Apex. Many bugs including Translation issues are fixed and IOS 5.0 support provided in the new version.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Make authorization on application level optional for public pages
Summary
Add a flag to authorization on application level to only enable it for pages that require authentication.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Named branches
Summary
Add support for developer-provided branch names.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > New attribute - Show Page Items above/below region content
Summary
Regions have an attribute "Items Display Position" with the values

Above Content
Below Content

Currently this is stored within the display points (Page Template Body 1 - 3) and hard-coded for the others (Region Position 1 - x), which is very in-flexible.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > New built-in APP_SESSION_VISIBLE
Summary
Provide a built-in substitution which should be used for Public applications that use session ID 0.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > New function APEX_ESCAPE.SELECTIVE_ESCAPE
Summary
A new function that can escape common simple HTML tags but not others. This can be used to escape HTML entered into database data, yet not escape common formatting HTML such as <h2>, <p>, <br />, <ul> etc. Can help to reduce XSS vulnurabilities.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > RESTful Web Services
Summary
Include the ability to define RESTful Web Service calls from the database.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Read-Only attribute at Page and Region level
Summary
Currently we support read only at the item level, but not at the page or region level. This makes it inefficient and slow to show read only data.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Remove the restriction that on-demand processes can't have a condition or authorization
Summary
Currently on-demand processes don't include the ability to define authorization or conditions. This has been incorporated to provide the same options for on-demand processes as for other components.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Shared session state across applications ("global" variables)
Summary
Large logical application are often separated into several physical apps that live in the same workspace and share the same session. This can be implemented by configuring the same cookie name in these applications.

The applications often also need to share a few global state variables. While the number of these items should be kept small, they are an important means for inter-application communication. Examples are

- additional properties of the current user (email address, employee number, ...)
- current company in a multi-tenant application

This feature will implement these variables. They are implemented as an extension to application items. If application items with the same name in different applications have scope "Global", the Apex runtime will access the same session state from within each application.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Support for attachments within Team Development
Summary
Allow file attachments for bugs, todo, and features.
Feature : APEX 4.2 Early Adopter > APEX 4.2 Other Features > Update to most recent jQuery and jQuery UI versions
Summary
Update to the latest available version of the jQuery and jQuery UI versions. This also now needs to be compatible with the version of jQuery Mobile we ship with.
Feature : APEX 4.2 Early Adopter > Application Builder Enhancements
Summary
Improvements made to the Application Builder
Feature : APEX 4.2 Early Adopter > Application Builder Enhancements > Add ability to synchronize column order with region source in classic reports and tabular forms
Summary
Add ability to synchronize a classic report's column order, with the column order defined in the region source query. This has the following benefits:

Allows a developer a way to keep these 2 definitions consistent.
Provides an accessible way for a keyboard-only or screen reader user to re-order the report columns.
Feature : APEX 4.2 Early Adopter > Application Builder Enhancements > Application Builder Interactive Reports modernized
Summary
All interactive reports in APEX 4.2 application builder have been modernized. Buttons are larger, the search field is larger, the icons used to change between list and icon view have been modernized. Buttons in the "right of interactive report search" region position have also been increased in size. The pull down menus have also been modernized, the icons used in the dialogs have been cleaned up. The Dialog used for "action" menu actions now appears to pull down over the entire width of an IR.
Feature : APEX 4.2 Early Adopter > Application Builder Enhancements > Edit Page (4000:4150) modernization
Summary
Improved readability and usability of page edit component view.

Changed look and feel, icons, and display of component view of edit page in APEX 4.2. New look has all components grouped together in one region for each of the 3 columns (page rendering, page processing, and shared components). Fonts and many UI treatments made.
Feature : APEX 4.2 Early Adopter > Application Builder Enhancements > Highlight modern themes
Summary
Rather than displaying all of the Application Builder supplied themes only the latest modern themes are displayed, namely Themes 21 through 25. All previous themes are listed under 'Legacy Themes'.
Feature : APEX 4.2 Early Adopter > Application Builder Enhancements > Improvements to the User Interface
Summary
Numerous changes to the look and feel of the Application Builder. This includes a redesign of links to major functional areas and refresh of the page component view.
Feature : APEX 4.2 Early Adopter > Application Builder Enhancements > Informational Text displayed when creating branches and buttons with direct to page
Summary
To better explain the benefit of using RIR and CIR an informational region displays when using the create branch and create button wizards. For create button if you select your button action to be "direct to a page in this application" you will see instructional text. When creating branches, the step that defines the branch target displays the same instruction text.
Feature : APEX 4.2 Early Adopter > Application Builder Enhancements > Modernize APEX logo and Tabs (top 1" of screen)
Summary
Make APEX look more like the Oracle Database Cloud to both modernize the look, improve the HTML and CSS and make APEX look more holistic with the Database Cloud.
Feature : APEX 4.2 Early Adopter > Application Builder Enhancements > Modernize Region and Button Templates
Summary
Update region templates to use CSS to show gradients and rounded corners.
Update button templates to use CSS instead of images, make buttons larger and more consistent with packaged application UI
Feature : APEX 4.2 Early Adopter > Application Builder Enhancements > Modernize Wizards
Summary
Update wizards to show progress train on top of instead of to the left of wizard region
Eliminate steps that are no longer needed
Feature : APEX 4.2 Early Adopter > Application Builder Enhancements > Modernize statistic display on team development dashboard display pages
Summary
In APEX 4.1 we had large orange progress indicators, we have moved to a more stylized blue look and feel for summary information for each team development "dashboard" page.
Feature : APEX 4.2 Early Adopter > Application Builder Enhancements > Remove List Template from Lists
Summary
A default list template for List components can't be supported anymore because of the new multiple user interfaces.
Feature : APEX 4.2 Early Adopter > Application Builder Enhancements > Remove drag and drop item layout from APEX 4.2
Summary
Drag and drop functionality link was removed with redesign of Edit Application Page. Additionally drag and drop is a very old implementation and needs to be modernized, this feature is no longer part of APEX . It may be reintroduced in some future release in a more modern way.
Feature : APEX 4.2 Early Adopter > Application Builder Enhancements > Update / enhance create application wizard
Summary
Update create application wizard to reduce number of steps, and merge options like the "instant application" with the "from scratch" wizard. Also integrate packaged applications.
Feature : APEX 4.2 Early Adopter > Data Upload Enhancements
Summary
Enahancements made to Data Upload
Feature : APEX 4.2 Early Adopter > Data Upload Enhancements > Provide aliases for the data upload columns
Summary
To avoid the end user having access to the table column names which can be confusing, we can provide a way for the developer to give alias names to the column names.
Feature : APEX 4.2 Early Adopter > Data Upload Enhancements > Allow up to three columns to be passed in Data Upload Key Lookup retrieval
Summary
Currently in data upload feature, with the column lookup it is only possible to pass the value of once column and get back a numerical number as return value.
This feature will be enhanced so that up to three columns values can be passed.
Also, the return value was assumed to be numeric, however there are cases where the return value may have different data type.
Feature : APEX 4.2 Early Adopter > Data Upload Enhancements > Better management of Concurrency in data upload
Summary
Allow developers to define a column for concurrency which will be used to ensure that if after the end user begins the data upload process a row has not been updated by another user.
Feature : APEX 4.2 Early Adopter > Data Upload Enhancements > Character Set conversion for File Upload
Summary
As discussed in different forum threads, the character set conversion is missing and this is a deficiency especially for the users who might be trying to upload files with different character sets.
Feature : APEX 4.2 Early Adopter > Data Upload Enhancements > Multi column data load transformation rules
Summary
Data upload transformation rules are often applicable to different columns. Instead of re-defining the same rule for each column, we can developer the user to re-apply the same rule to a number of different columns at the same time
Feature : APEX 4.2 Early Adopter > Dynamic Action Enhancements
Summary
Dynamic Action enhancements
Feature : APEX 4.2 Early Adopter > Dynamic Action Enhancements > Ajax based dynamic actions to work asynchronously
Summary
Change certain server-side actions from firing synchronously to asynchronously. Additionally provide the developers with options on how subsequent actions are fired (queued or executed immediately.
Feature : APEX 4.2 Early Adopter > Dynamic Action Enhancements > Declarative support for buttons to be the affected elements of Dynamic Actions
Summary
Allow selection of buttons within the 'Action > Affected Elements' in dynamic actions
Feature : APEX 4.2 Early Adopter > Dynamic Action Enhancements > Enable existing item types to work with JQuery Mobile
Summary
Existing item types were modified so that they also work with jQuery Mobile when JavaScript / Dynamic Actions are used to manipulate them (eg. Set Value, Enable, Disable).

Text Field (incl. E-Mail, Phone, URL)
Textarea
Number
Date Picker (HTML5) (incl. Date, Date and Time)
Yes/No
Slider
Feature : APEX 4.2 Early Adopter > Dynamic Action Enhancements > Expose jQuery Mobile events through dynamic actions
Summary
The jQuery Mobile framework exposes a number of events that provide useful hooks for developers of mobile applications. This feature extends the events exposed in the dynamic action framework, to incorporate these jQuery Mobile events.
Feature : APEX 4.2 Early Adopter > Dynamic Action Enhancements > Provide 'Custom' event in dynamic actions, to allow definition of any custom event
Summary
Provide a 'Custom' or 'Other' option when specifying a dynamic action's event. This would allow greater flexibility for advanced developers to attach dynamic actions based on events that we do not provide as out of the box events. For example to respond to events from other JS frameworks, or to respond to custom events triggered by the developer on the page.

This would be an additional option in the When > Event saying 'Custom' or 'Other', then an additional field displays allowing freetext specification of any event.
Feature : APEX 4.2 Early Adopter > Dynamic Action Enhancements > Simplify Create Dynamic Action wizard
Summary
Provide a more streamlined and simplified create dynamic action wizard by removing the Standard/Advanced concept, adding additional quick pick options, etc.
Feature : APEX 4.2 Early Adopter > Dynamic Action Enhancements > Switch to new jQuery 'on' event registration (will be used by existing events and new mobile events)
Summary
jQuery 1.7 introduces a new and improved event registration model, via the 'on' method. This combines the previous 'bind', 'live' and 'delegate' methods to register event handlers into 1 easy method. See here for details:
http://www.elijahmanor.com/2012/02/differences-between-jquery-bind-vs-live.html
http://api.jquery.com/on/
Feature : APEX 4.2 Early Adopter > HTML 5 Charts
Summary
Integration of HTML5 charting capabilities
Feature : APEX 4.2 Early Adopter > HTML 5 Charts > Add Chart support for Dynamic Action 'Refresh'
Summary
Refresh should also support our in-built chart component, currently only classic reports, interactive reports and plug-ins that support 'Refresh' are supported.

This should also include adding a 'Page Items to Submit' attribute to charts series so this can be done on a series by series basis.
Feature : APEX 4.2 Early Adopter > HTML 5 Charts > Add Conditions region to Chart Series Page for Conditional Display
Summary
The Chart Series page for Flash Charts should be updated to include a 'Conditions' region, similar to other APEX components, allowing users to determine when and if the chart series is to be displayed on the chart.
Feature : APEX 4.2 Early Adopter > HTML 5 Charts > Chart Enhancements for Mobile
Summary
Add support for regions of type chart which do not require Flash (to enable display on mobile devices).
Feature : APEX 4.2 Early Adopter > HTML 5 Item Types
Summary
Incorporate HTML 5 attributes into existing and new item types
Feature : APEX 4.2 Early Adopter > HTML 5 Item Types > Add CSS class to page item if an error occurred to support CSS styling
Summary
If a validation error has occurred for a page item, it should be rendered with the additional CSS class "apex-page-item-error" to allow CSS styling of all page items which have an error.
Feature : APEX 4.2 Early Adopter > HTML 5 Item Types > Add HTML5 required attribute to support CSS styling
Summary
Add the HTML5 "required" attribute to the generated INPUT/SELECT/TEXTAREA/... HTML controls if the "Required" = Yes for a page item.

This allows advanced CSS3 styling of required page items. See http://www.the-art-of-web.com/html/html5-form-validation/
Feature : APEX 4.2 Early Adopter > HTML 5 Item Types > Add support for HTML5 placeholder attribute to several item types
Summary
The following item types should support the HTML5 placeholder attribute.

Color Picker
Date Picker
Date Picker (Classic)
List Manager
Number Field
Password
Popup LOV
Text Field
Text Field with Calculator Popup
Text Field with autocomplete
Textarea

The new attribute should also be exposed to plug-in developers.
Feature : APEX 4.2 Early Adopter > HTML 5 Item Types > Add support of HTML5 types EMAIL, TEL and URL for textfield item type
Summary
Text Field should have new 'Subtype' to support HTML5 input types (email, phone, url). This is useful for touch based devices which show an optimized keyboard for the type.
Feature : APEX 4.2 Early Adopter > HTML 5 Item Types > New Display Orientation attribute for Checkbox/Radio Group Item Type
Summary
The item types Checkbox and Radio Group should have a new attribute "Display Orientation" with the values

Vertical
Horizontal

The default will be Vertical. This attribute will only be used for jQuery Mobile user interfaces.
Feature : APEX 4.2 Early Adopter > HTML 5 Item Types > New Item Type Slider
Summary
Support new item type "Slider" which renders as

HTML5 range input type which is switched to a nice slider by jQuery Mobile and as
jQueryUI slider in non Mobile Environments
Feature : APEX 4.2 Early Adopter > HTML 5 Item Types > New item type Date Picker (HTML5)
Summary
Add new item type "Date Picker (HTML5)" which is using the new HTML5 input types DATE and DATETIME-LOCAL which are supported by modern smartphone and tablet browsers to pick a date with native operating system controls.
Feature : APEX 4.2 Early Adopter > HTML 5 Item Types > New item type Yes/No (Flip Toggle Switch)
Summary
Support new item type "Yes/No" selection which renders as

Flip Toggle Switch in jQuery Mobile User Interfaces and as
Select List in non Mobile Environments
Feature : APEX 4.2 Early Adopter > HTML 5 Item Types > Textareas should respect Maximum Width page item attribute
Summary
Textareas should be changed to check for the "Maximum Width" attribute of a page item and not allow to enter more characters as defined. This will help to avoid constraint violations when the data gets saved into the database.
Feature : APEX 4.2 Early Adopter > HTML 5 Item Types > Use Browser Resizable Textarea feature
Summary
Textareas should use the built-in resize support of the Browser to provide a better user experience if the browser supports it.
Feature : APEX 4.2 Early Adopter > Interactive Report Enhancements
Summary
Enhancements to Interactive Reports
Feature : APEX 4.2 Early Adopter > Interactive Report Enhancements > Column Formatting for Interactive Reports columns
Summary
Allow HTML expressions to be used in column definitions for Interactive Reports.
This will be rendered in the report and included in the HTML and Email downloads but will not be included in the CSV Download.
Feature : APEX 4.2 Early Adopter > Interactive Report Enhancements > Define "from" address in Interactive Report Subscription and Email Download
Summary
Users can email Interactive report data using Subscription or Email download option. Both features do not have "from" address field. Currently, defined "To" address is used as "From" address. Both features need a way to define valid "from" address.
Feature : APEX 4.2 Early Adopter > Interactive Report Enhancements > Do not allow group by or chart queries to be displayed if they exceed max rows
Summary
display this error when needed, and do not display group by queries or charts:

Your current query retrieves more than (999,999) rows (the maximum row count for this report). The [group by / chart] view is only supported when all rows retrieved can be displayed. Please apply a filter.
Feature : APEX 4.2 Early Adopter > Interactive Report Enhancements > Expose template for IR icon view
Summary
Allow for an optional template for icon view. Current template for IR icon view is hard coded to "#LABEL_COLUMN#". Provide optional override.
Feature : APEX 4.2 Early Adopter > Interactive Report Enhancements > Implement Easy Interface to Remove Interactive Report Subscription
Summary
Enhance Interactive report subscription to include a link to unsubscribe. This way users don't have to guess where the email is coming from and where to stop the future email.
Feature : APEX 4.2 Early Adopter > Interactive Report Enhancements > Improve 'Saved IRs' to be preserved when Application Id Changed
Summary
Currently a "Saved IR" is lost when an application in DEV is created in PROD with a different Application ID (E.g. APP 100 in DEV used to create APP 100, 200, and 300 in PROD - Any Saved IRs in APPs 200 and 300 lost when new version of application built as different WORKSHEET_IDs)

Solution is to introduce an "Immutable" ID which can be used (in conjunction with FLOW_ID) to automagically relink these lost reports.
Feature : APEX 4.2 Early Adopter > Interactive Report Enhancements > Improve Interactive Report Group By Sort
Summary
Interactive report group by previously didn't allow sorting columns beyond the 3rd column. If user defined 3 group by columns and 3 functions, they could sort only up to the 3rd group by column, but not on all of them. The group by sort was changed to have its own sort dialog to list all columns in the group by and let users sort on them.
Feature : APEX 4.2 Early Adopter > Interactive Report Enhancements > Include User information in Interactive report emails
Summary
Interactive report email can spook users with invalid "from" address and email content.
Feature : APEX 4.2 Early Adopter > Interactive Report Enhancements > Increase the number of rows that an IR will allow by default.
Summary
Default newly created IRs to a maximum of 1 million rows and not 100,000
Feature : APEX 4.2 Early Adopter > Interactive Report Enhancements > Interactive Report API Providing Runtime SQL Query
Summary
Provide an API returning an IRR's current SQL query to help advanced developers add functionality that is dependent on the current information displayed in an interactive report region.
Feature : APEX 4.2 Early Adopter > Interactive Report Enhancements > Interactive Report Public API
Summary
Interactive report specific Public API to change interactive report settings. Prior to 4.2, Interactive public API exists in APEX_UTIL. The following in APEX_UTIL will be deprecated:
ir_filter
ir_reset
ir_clear
ir_delete_report
ir_delete_subscription

The use of new API, APEX_IR is encouraged. Having Interactive report specific API will help developers to see what is available and use easily.
Feature : APEX 4.2 Early Adopter > Interactive Report Enhancements > Provide ability to set NLS_COMP and NLS_SORT for Interactive and Classic Reports
Summary
Provide declarative attributes for customers to specify the NLS_SORT and NLS_COMP settings that should be issued before running an Interactive Report or Classic Report query. This is an often-request feature from customers, especially multi-lingual customers like French Canadians. Customers need to be able to provide accent-insensitive searching.
Feature : APEX 4.2 Early Adopter > Interactive Report Enhancements > Support equal,'=', operator for Interactive Report Date column filter
Summary
Interactive report filter dialog supports equal, '=', operator for all other type other than DATE. This feature enables users to filter on a date column to filter on a specific date using equal operator.
Feature : APEX 4.2 Early Adopter > JavaScript / API Enhancements
Summary
Enhancements made to JavaScript and associated APIs.
Feature : APEX 4.2 Early Adopter > JavaScript / API Enhancements > API to check status of build option
Summary
Build options are shared components in an APEX application used to enable / disable functionality. In APEX 4.1.1, there was an API added to set the build option. In APEX 4.2, we need to also provide an API to get back the status of a specified build option.
Feature : APEX 4.2 Early Adopter > JavaScript / API Enhancements > Provide application configuration for inclusion of legacy JavaScript functions
Summary
In development of a cut-down JavaScript library for 4.2, we have moved many old JavaScript functions out to a legacy JavaScript file. This is currently 23KB, and ever increasing as we continue work on the library. This feature will allow the customer to control whether they want to include these legacy functions in their applications, and also how we deal with migration and defaulting.

"Include Legacy JavaScript" option in Application Properties - If set to "Yes", we will include the legacy JS functions in our combined JS deployment file for that application. If set to "No", we will include a different combined JS deployment file that does not include these functions.
Existing applications will default to "Yes" for backwards compatibility, in case the customer may have used some of these functions in their own applications.
New applications will default to "No".
Customers will then be able to configure this in their applications, such that if they are happy that existing applications do not contain any references to these functions, they can switch this to "No". Alternatively of course, if a customer wants to build a new application, and perhaps still include the legacy functions, they can set this to "Yes".
Feature : APEX 4.2 Early Adopter > JavaScript / API Enhancements > Write better AJAX functions (htmldb_Get is outdated)
Summary
Added the following methods to the APEX JavaScript library

apex.server.plugin: Used to call the AJAX callback function of a plug-in
apex.server.pluginUrl: Used to return a URL, that can be used to issue a GET request to the PL/SQL AJAX function which has been defined for a plug-in.
apex.server.process: Used to call an on-demand process on page or application level
apex.widget.util.cascadingLov: Helper function for easier handling of cascading lov item type plug-ins

See API documentation for details.
Feature : APEX 4.2 Early Adopter > Mobile Application Building
Summary
Enhance the Application Builder to enable developers to declaratively build mobile applications
Feature : APEX 4.2 Early Adopter > Mobile Application Building > Define "Global Page" (aka Page 0) for a user interface
Summary
It's now possible to support a global page (before the global page was known as page 0) for each user interface. Therefore, if an application has multiple user interfaces there will be multiple global pages.
Feature : APEX 4.2 Early Adopter > Mobile Application Building > Enable Cascading LOVs for mobile
Summary
Enable cascading LOVs for Select Lists, Checkboxes and Radiogroups.
Feature : APEX 4.2 Early Adopter > Mobile Application Building > New Region Type List View (for jQuery Mobile)
Summary
Add new region type "List View" which is used for jQuery Mobile applications.
Additional features which have been implemented on top of the jQM list view features:

Server Side AJAX search
AJAX based pagination
Support of the "Refresh" dynamic action
Feature : APEX 4.2 Early Adopter > Mobile Application Building > Support grid layout for regions and page items
Summary
On page template level it's now possible to specify which "Grid Layout" should be used to layout regions and page items. This is an alternative to "HTML Table" based layouts used by APEX in older applications. The new jQuery Mobile based theme is already making use of this new feature.

Sub Regions can now also be positioned next to each other as long as the region template doesn't contain a sub region template configuration.
Feature : APEX 4.2 Early Adopter > Mobile Calendars
Summary
Enhancements made to Calendar to support mobile application deployment.
Feature : APEX 4.2 Early Adopter > Mobile Calendars > Calendar Creation Wizard changes to Support Mobile platform
Summary
Based on the Choice made during the Calendar Creation whether it is Mobile version or Desktop version, some of the options shown while creation of calendar need to be changed.

1. Drag &amp; Drop option will be removed for Mobile.

2. Display Type will be defaulted to PPR and option will not be shown

3. Open Link in will not be shown and defaulted to "Same Window"

4. Add Additional Option for Mobile version, like Default Calendar View choice like Month”,”Week”,”Day”,”Agenda”

5. Added option to select automatic Calendar type change based on Orientation
Feature : APEX 4.2 Early Adopter > Mobile Calendars > Create Additional Calendar Views
Summary
Adding a list view/agenda view as an additional option with existing monthly/weekly/daily calendars
Feature : APEX 4.2 Early Adopter > Mobile Calendars > Create Mobile Template for all types of Calendar
Summary
Creation of mobile-friendly calendar templates
Feature : APEX 4.2 Early Adopter > Mobile Calendars > Support of substitution strings in all the Close formats in Calendar Template
Summary
Currently the close formats in the calendar Template like day close, weekend close, non day close does not support substitution, if #DD# is included as part of the close format it will display as it is without substitution.
Feature : APEX 4.2 Early Adopter > Mobile Themes and Templates
Summary
Development of themes to support the development of mobile applications
Feature : APEX 4.2 Early Adopter > Mobile Themes and Templates > Add "CSS Classes" attribute to regions, buttons, page items and report columns
Summary
A new attribute "CSS Classes" should be added to regions, buttons, page items and classic report columns to allow easier styling of this components.
Region and button templates should support the new template placeholders #REGION_CSS_CLASSES# and #BUTTON_CSS_CLASSES#
Feature : APEX 4.2 Early Adopter > Mobile Themes and Templates > Add "Has Edit Links" flag to page templates to specify if "Show Edit Links" is supported
Summary
A new flag "Has Edit Links" should be added to page templates to allow the configuration if the "Show Edit Links" feature of the developer toolbar is available for a page. For normal page templates this will normally be set to Yes, but for jQuery Mobile pages this will be set to "No" because that can disrupt the JQM engine.
Feature : APEX 4.2 Early Adopter > Mobile Themes and Templates > Add PAGE_STATIC_ID substitution to page templates
Summary
Add a #PAGE_STATIC_ID# substitution string to be available for use within a page template's 'Body' section. This is useful for jQuery Mobile, specifically for use on the element that has data-role="page", eg:



The #PAGE_STATIC_ID# should substitute to 'P' || [page ID].

Once this is available, dynamic actions can then hook on to this ID, for the 'Page Load' event when the current page is UI Type = 'JQM_SMARTPHONE'. When using this UI type, the 'Page Load' event internally maps to jQuery Mobile's 'pageinit' event handler, which has to be bound to this with the page data-role.
Feature : APEX 4.2 Early Adopter > Mobile Themes and Templates > Add page and popup transition attribute for Mobile
Summary
Default mobile page and popup transition type (slide, slideup, flip, etc.) specified on theme level.
Page level transition override - should contain an entry "Use Theme Default". Such attributes should only be visible when it's a mobile page template.
Feature : APEX 4.2 Early Adopter > Mobile Themes and Templates > Add support for multiple user interfaces in an application
Summary
An application is able to support different UI. For example, some pages can be be for Desktop browsers, and some for smartphones and some for tablets.

Based on the UI picked for a page, only components designed for that UI are visible. For example it's not useful to show the tree component for a smartphone UI.

It is possible to import multiple themes where each is assign to a specific UI type.

For each UI it is possible to specify the home url and the login url.

There is a new page template placeholder called #SWITCH_UI_TO_[name of UI type]# which can be used to switch to a different UI.

The different UI types support a device detection to automatically show the optimized pages for that device.
Feature : APEX 4.2 Early Adopter > Mobile Themes and Templates > Declarative support to specify JavaScript files and code
Summary
Add new application, page and page template attribute "JavaScript file URL(s)" to support declarative definition of JavaScript files which should be loaded for an application, page or page template.
Feature : APEX 4.2 Early Adopter > Mobile Themes and Templates > Declarative support to specify inline CSS and CSS files
Summary
Add new page and page template attributes "CSS file URL(s)" and "Inline CSS" to support declarative definition of CSS files and inline CSS which should be loaded for a page.
Feature : APEX 4.2 Early Adopter > Mobile Themes and Templates > New Page Template Placeholders
Summary
Page Templates support the new placeholders #GENERATED_CSS#, #GENERATED_JAVASCRIPT# and #DEVELOPER_TOOLBAR# in the "Header", "Body" and "Footer" definition attributes.
Feature : APEX 4.2 Early Adopter > Mobile Themes and Templates > New page template substitution #REQUESTED_URL#
Summary
Page templates should support the new #REQUESTED_URL# substitution which returns the URL of the requested page as the browser has sent it.

This is necessary for jQuery Mobile where AJAX calls are used to load pages and where jQuery Mobile is not able to detect redirects in those calls resulting in a wrong URL which gets displayed.
Feature : APEX 4.2 Early Adopter > Mobile Themes and Templates > New placeholders to include standard APEX CSS and standard JavaScript files
Summary
Add new placeholders #APEX_CSS# and #APEX_JAVASCRIPT# to be used in page templates. This will give greater flexibility where and if the standard APEX Javascript and CSS files should be included.
Feature : APEX 4.2 Early Adopter > Mobile Themes and Templates > New region template substitution #PAGE_TITLE#
Summary
Region templates support the new substitution #PAGE_TITLE# which substitutes the title of the current page. This new substitution is used for the "Header Toolbar" region on page 0 of a jQuery Mobile application.
Feature : APEX 4.2 Early Adopter > Mobile Themes and Templates > Support Content Delivery Networks for jQuery files
Summary
Add a new application level attribute "Content Delivery Network" to support that jQuery and jQuery Mobile files are loaded from a Content Delivery Network (Google, Microsoft, jQuery) to improve performance especially for mobile applications.
Feature : APEX 4.2 Early Adopter > Packaged Applications
Summary
A set of business productivity applications, easily installed into your workspace or Database Cloud service. Also includes a set of sample applications which demonstrate specific capabilities of Application Express.
Feature : APEX 4.2 Early Adopter > Packaged Applications > Allow download of Packaged Applications for deployment
Summary
To allow packaged applications to be installed on a run time only instance we will need to support download of the application and supporting objects scripts. Additionally provide remove application script.
Feature : APEX 4.2 Early Adopter > Packaged Applications > Show locked packaged applications under All Applications in the Builder
Summary
Packaged applications that are locked (i.e. all non-sample apps) are currently only shown on page 50 (app installer page), they should be shown on page 4000:1500 under all-applications and be run-able from there
Feature : APEX 4.2 Early Adopter > Packaged Applications > Unlock packaged applications
Summary
Oracle Application Express includes a number of packaged business applications, which are available free of charge, can be used as production applications and will be supported by Oracle. These packaged applications are locked and can't be modified by customers.

Customers who want to modify a packaged applications or simply review its implementation will be able to unlock the application. Once unlocked, the application is no longer supported by Oracle and can no longer be updated. Customers can always return to a supported version by removing the unlocked copy and re-installing the locked version.
Feature : APEX 4.2 Early Adopter > Plug-In Enhancements
Summary
Plug-In enhancements
Feature : APEX 4.2 Early Adopter > Plug-In Enhancements > Add "Fetched Rows" as standard region type plug-in setting
Summary
Add the attributes "Number of Fetched Rows" and "Number of Fetched Rows (item)" as standard attribute which can be exposed for region type plug-ins. This can be used by region type plug-in to determine how many rows should be fetched/displayed for pagination of the region source data.

The new attribute is exposed as p_region.no_data_found_message in the p_record structure which is passed to a plugin.
Feature : APEX 4.2 Early Adopter > Plug-In Enhancements > Add "No Data Found Message" as standard region type plug-in setting
Summary
Add the attributes "No Data Found Message" as standard attribute which can be exposed for region type plug-ins. This can be used by region type plug-in to determine what should be displayed if nothing was found.

The new attribute is exposed as p_region.fetched_rows in the p_record structure which is passed to a plugin.
Feature : APEX 4.2 Early Adopter > Plug-In Enhancements > Add new apex_plugin_util.get_data and get_data2 APIs which support a name for the search column
Summary
Add new APIs to apex_plugin_util to better support custom plug-in attributes of type "Region Column Name". Instead of passing a column no (eg. p_search_column_no) the APIs should now also support passing a column name (eg. p_search_column_name).
Feature : APEX 4.2 Early Adopter > Plug-In Enhancements > Add support for media queries and IE conditions to apex_css and apex_javascript APIs
Summary
The APIs apex_css.add_file have two new parameters

p_media_query to specify a value for the meta="xxx" attribute of the tag
p_ie_condition to include an Internet Explorer condition for the link tag in the format

The APIs apex_javascript.add_library has one new parameter

p_ie_condition to include an Internet Explorer condition for the script tag in the format

Feature : APEX 4.2 Early Adopter > Plug-In Enhancements > Increase Number of Custom Attributes for Region Type Plug-ins to 25
Summary
The number of custom attributes (scope=component) for region type plug-ins is increased from 15 to 25.
Feature : APEX 4.2 Early Adopter > Plug-In Enhancements > Plug-In Attribute type "Region SQL Statement Column" supports data type checking
Summary
Plug-In Attributes of Type "Region SQL Statement Column" support data type checking
Feature : APEX 4.2 Early Adopter > Websheet Enhancements
Summary
Websheet Enhancements
Feature : APEX 4.2 Early Adopter > Websheet Enhancements > Entend WS?P to link directly to Websheet Data Grid and Data Grid row (form view)
Summary
Allow a link to edit a data grid or a data grid row to be exposed / emailed.
Feature : APEX 4.2 Early Adopter > Websheet Enhancements > Expose cookie name in UI to support session sharing
Summary
For applications of the same workspace (both db apps and websheet apps) to share the same session and not require re-authentication, their session cookie names must be the same. Websheets should expose the cookie name in the UI, to allow them to share the same session.
Feature : APEX 4.2 Early Adopter > Websheet Enhancements > Include "Allow SQL and PL/SQL" option in create Websheet Wizard
Summary
Allow application developers to specify they want to allow SQL and PL/SQL regions and reports when creating the application rather than having to create the application and then having to Edit Properties.
Feature : APEX 4.2 Early Adopter > Websheet Enhancements > Websheet Data Section Enhancement
Summary
Add the ability to include an Add Row button, edit row link and max row display in a Data Section based on a Data Grid.
Feature : APEX 4.2 Early Adopter > Websheet Enhancements > Websheet Toolbar Menu Enhancement
Summary
Enhance Websheet Toolbar Menu as follows:
1. Move the View drop-down to be the first drop-down (before Create)
2. Add as the first entry in the View drop-down: Home Page … Alt-H {which simply navigates to the home page}
3. Remove the Reports entry in the View drop-down
4. Create a new Reports drop-down between Data Grids and Administration drop-down
5. Have same type of entries as in Data Grid drop-down {New Report; (List of Reports); View All … Alt-R}
1 - 137
Early Adopter 1.0