v3.1.0 Change Log (December 2017)
Dropzone Multiple File Upload - Region Plugin
We have included the Drop Zone plugin to complement/replace the usage of our existing multiple file upload page item. The plugin supports the exact same features of uploading files to tables, collections, and file system.
Files can be uploaded via Drag & Drop and the area to drop them is the entire space of the region, making it easier to drop them into. The dropzone area will resize according to the region size when the parent region size changes.
Progress Bar - Item Plugin
You can now include either a static or dynamic progress bar item in toolbars or form regions to visually display the progress, usage, or completion of things. The progress bar gives you the ability to control the background/progress color, text, and animation capability.
The plugin comes with an associated dynamic action plugin allowing you to update the progress and dynamically change the colors. You can set the progress check interval, limit the number of requests, and also cancel the progress using actions.
Multiselect Grid Combo - Item Plugin
This plugin features all the same features as a regular grid combo with the commission of setting other values on selection and all regular APEX dynamic action support is provided e.g. enable/disable
Icon - Item Plugin
A simple Font Awesome/Font APEX icon that behaves similar to regular buttons. You can add a badge to the icon to display some text or a count indicator. The icon can enabled/disabled or set to read-only to use it simply as a visual indicator.
Return/Display Grid Combo - Item Plugin
We have included another variation of our grid combo plugin which allows you to enter the ID value of a LOV and perform a lookup. This plugin is a familiar item type for Forms developers. The plugin supports the exact same features as the regular grid combo item including set other items on lookup/selection.
Islamic Calendar Date Picker - Item Plugin
A new date picker that allows you to display and select dates based on the Islamic Hijri calendar. When used within the FOEX Form plugin, on form load the date value queried from the database, the date pickers item value will be automatically converted from a Gregorian value to a Hijri value. On form save the form value will be automatically converted from a Hijri value to a Gregorian value.
Grid Client-Side Validations
The grid will now perform all client side validation on changed rows before saving them to the server, if there are any validation failures then these need to be rectified by the user before the save/AJAX call is made.
The following list of checks will be performed if they have been set on the column editor:
- Not Null (allowBlank: false)
- Minimum Length (minLength)
- Maximum Length (maxLength)
- Minimum Value (minValue)
- Maximum Value (maxValue)
- Date Format (dateFormat)
- Client Side Validation (vtype e.g. email, daterange)
Grid/Tree Grid Select Rows Dynamic Action
You can now select multiple rows with the grid select row dynamic action. You can select the rows by using an index range or a search based on a column/value search. The column/value matching can either be partial/exact or by using a regular expression.
Grid/Tree Grid Refresh Rows Dynamic Action
You can now refresh multiple rows with the grid refresh row dynamic action. You can refresh the rows by using the current row selection(s) or an index range or a search based on a column/value search. The column/value matching can either be partial/exact or by using a regular expression.
Page Level Read Only conditions are now honoured by Grid & Form plugins.
Please note: that read only conditions defined at the component level will override the page level condition. This will allow you to have some regions editable when the page is in read only mode.
We now support the ability to reference the component information in authorizations using a FOEX API call. In order to do this one restriction is that you cannot cache the result within the Authorisation itself, but down’t worry within our code we will. You can use the following syntax within your authorisation PLSQL:
- nvl(fx_p_component_api.get_component_id , :APP_COMPONENT_ID)
- nvl(fx_p_component_api.get_component_name, :APP_COMPONENT_NAME)
- nvl(fx_p_component_api.get_component_type, :APP_COMPONENT_TYPE)
Regular APEX: Execute PLSQL - Error Alert
For visual and consistency reasons we have overridden the browser alert produced by the Execute PLSQL Code dynamic action when an error occurs with an Ext JS Alert.
Grid Cascading LOV’s
You can now base your grid cascading LOV parents based on page items on the current page, not just columns from the current grid.
New Tab Close and Disable Tab Dynamic Action
We have included a new dynamic action to allow you to close/disable one or more tabs based on the current active tab, ID, or Tab Text. The tab ID/Text matching can either be partial/exact or by using a regular expression.
Continue IF Dynamic Action
We have included a new option in the Continue IF dynamic action what gives you the chance to cancel the calling FOEX event e.g. you may listen to a “Before Refresh” event and your Continue IF action returns false you can choose the option of cancelling the refresh action using this setting. Note: this applies to all “before” events.
All LOV items now support being based on a PLSQL Function returning SQL String.
You can now set icons on the tabs/panels opened by the content loader that use the “Triggering Element”. You can do this by adding a data attribute to the HTML elements e.g. grid report column link e.g.
You now have the option to mark form items with a visual indicator (red triangle top left corner) when their value has changed, just like grids do!
Page Level Read Only
The page level read only condition will now be honoured by Forms, and Editable Grids & Tree Grids. However please note that if you define a read only condition at the region or item level the result of that condition will override the page level read only result. This is the same behaviour as in standard APEX.
Region/Item Conditions & Authorizations
On all region AJAX calls e.g. grid refresh, form load etc. we will check all child region/item/button conditions, authorisations, and read only conditions for the region in context and will perform the appropriate action of hiding/disabling failures and enabling/showing successes. This allows you to avoid the need to create many dynamic actions to hide/show enable/disable items/regions. This change may affect existing hide/show dynamic actions with regions/items that have an existing condition defined.
Grid Client Side Validations
As mentioned in our enhancements section, all changed grid rows will have their values validated against any client side validation rules e.g. not null, minimum length, maximum length, minimum value, maximum value. If there are any failures then they need to be corrected by the user before the grid save AJAX call will be issued.
To check the full release notes which include the new features and functionality provided by FOEX 3.1.0, please click here.