After launching FOEX 3.0 back in April, one of the questions we got asked most frequently was: Does it work with APEX 5.1? And if not, when will you release the compatibility update?
Today we are happy to announce that APEX 5.1 is supported on both version 2.2 and 3.0 of the FOEX Plugin Framework. In addition to providing support for APEX 5.1 here’s what else you can expect to see:
Enhancements in FOEX 3.0.1
Oracle DB 12.2 support
In earlier versions of FOEX we used PLJSON for JSON reading and writing capability in PLSQL. This meant that we had several types defined i.e. JSON which conflicted with v12.2 of the Oracle Database since a native JSON type was introduced. We have resolved this conflict in v3.0.1 and 12.2 is now officially supported.
Individual Form Item Validation
You can now execute the defined APEX validations for individual form items e.g. on change, using the “FOEX Form Item Validation” action, rather than validating the entire form which you had to do in previous versions.
PLSQL & Static Region
You can now choose to execute any scripts that are contained within your HTML on region refresh
Behaviour Changes in FOEX 3.0.1
In this version to support Oracle DB 12.2 we have had to rename all the PLJSON types
Due to the form submission changes in APEX 5.1 the file browse item will no longer upload via a single Form POST and will do so using a chunked base64 encoded series of AJAX calls using HTML5 File Reader API.
The ability to restrict file types and file size has been added and a progress bar will be seen during the upload of the file.
Behaviour Changes in FOEX 2.2.1
In order to support APEX 5.1, we no longer upload files via an iframe. Instead we upload the file in bas64 encoded chunks via AJAX using the HTML5 File API. This means that the file browse item can now restrict files to specific file extensions and also set a maximum file size limit.
To check the bug fixes made in release 3.0.1 and release 2.2.1 of the FOEX Plugin Framework, please check the FOEX Change Log page.