Samstag, 19. September 2020

Close a APEX modal dialog, by clicking on the main window

When your #orclAPEX app shows modal dialog windows, the app user has to click a button or the little X-icon in the upper right corner to close this dialog. Moving the mouse to these buttons takes your user's time.

You can enable the user to close a dialog window, by clicking or tapping on the main window. Put the following javascript code in the 'Execute when Page Loads' section of your APEX page:

$(document).on('click', 'div.ui-widget-overlay.ui-front', function(){

    apex.navigation.dialog.close(true, false);

});


Mittwoch, 26. August 2020

Schema & Data Browser – Part 3

A new release of the Schema & Data Browser app has been published on GitHub.com 

here is are links to the demo with an apex account
https://yboieokpjit8ejk-strackdev02.adb.eu-frankfurt-1.oraclecloudapps.com/ords/f?p=2000:101
https://apex.oracle.com/pls/apex/f?p=48950:101

Schema & Data Browser V 1.8.77 Release Note

New features 
on page Manage Schema
1. Export UI Defaults 
Enables you to download a UI Defaults definition PL/SQL script file for tables of the current schema with additional attributes like optimal width, max length, format masks, and LOVs for references, Yes/No fields, and check constraints with IN-Lists.
You can import this file with APEX to improve the default appearance of new forms on your tables.
Example: https://github.com/dstrack/Schema_Data_Browser/blob/master/Examples/hr_uidefaults.sql

2. Export Updatable Views - download a PL/SQL Script with Create View statements for updatable views.
The data browser displays this kind of view as report variant 'Import View'.
In the Dialog Window 'Show query' you can choose 'Create View' to see the Script for the currently selected table. The setting for 'Import Controls' (Compare Case Insensitive, Search keys unique, Search keys unique) and UNIQUE CONSTRAINTS for the display values of your LOVs will control the generation of these views.
The views will have INSTEAD OF INSERT OR UPDATE OR DELETE triggers that will manage the processing of DML statements on those views.
You can import and execute this file with the APEX "SQL Workshop / Scripts" page to install these views. You may use this view as a data source in Interactive Grid.
There you will be able to search in the display values based on LOV for references, 
and you will be able to edit data in each column.
Example: https://github.com/dstrack/Schema_Data_Browser/blob/master/Examples/hr_imp_views.sql

Bugfix: The generated query SQL code for rendering the form will call APEX_ESCAPE.HTML for character columns to prevent Cross-Site Scripting.
The bug was discovered by Ved Prabhu from Bangalore, India, and then reported by Joel R. Kallman from Oracle.

UI-Appearance Option: Added a global control to show or hide Breadcrumbs below the page title. The control can be set by the online user via the Navigation Bar menu.

Data Browser: The style of the View Mode Navigation List has been changed to Navigation Tabs to improve the highlighting of the current View Mode.
The entries for 'Entity Relationship Diagram' and 'Springy Diagram' have been removed from the View Mode Navigation List and have been added to the 'Actions' menu.

Improved descriptions and help text and improved german translation of the App UI.


Features of the application: Data Browser  

The key functionality of the SQL query and PL/SQL generators
1. Produce a description of any record 
Candidate keys are detected and serve as the unique display column set to describe any table record in LOVs, References, Record Labels, Link Labels.
2. Identify any record
Primary keys are detected and serve as internal identifiers that are hidden from the users. Functions to produce new identities(from sequence or sys_guid), references (columns Link_ID$, Row_Selector$),  and access methods (by column name or ROWID) are automatically applied.(Weak constraint definitions like unique index definition are also detected and considered)

2. Produce formatted descriptions
Any Number and Date field will be formatted with predefined or calculated format masks.

3. Produce recursive description
Any foreign key in the display column set is replaced by the reference target description.
4. Perform reverse key lookups
 This functionality is used to process imported data without any programming.

Any data that is entered or loaded in unique description fields from joined tables can be reduced to new or existing primary key values. This is possible when the tables have primary keys and candidate keys defined and the referenced rows exist or can be inserted because no constraint is violated.
Rows can be inserted when the table definition has default value or functions for all required columns that are not included in the view or that are empty in the import dataset. Required columns must have default values or can be initialized from the context (container references).

5. Produce a description of any relation 
For any foreign key constraint, a description of the reference source and target is composed to produce Report Labels, LOV queries, master-details reports. The relationship of tables is used to produce a navigation tree there tables are shows as childs of parent tables when they have foreign key references to that parent table.

6. Produce a description of any reference 
Any foreign key column can be replaced by a description of the reference target. The replacement can produce multiple formatted columns. Unique columns headers are produced by combining source column names and target table names.

7. Produce composed description 
The columns of a tables display column set can be concatenated with predefined delimiters to produce a composed description. The composed description is used to produce the display values required in 'Select List' und 'Popup List of Values' form items and in for link labels.

8. Produce human-readable and updatable views on any sufficiently defined table.
All available information from the data dictionary is aggregated in snapshot views for fast access. Functional programming is applied to enable spontaneous query and code generation. A query generator is invoked to produce new functions that render reports and forms. Code generators are invoked to produce new functions that perform controlled and correct data manipulations.

9. The system catalog is the single source for table and column names and their attributes.
With name pattern matching, functional properties are applied to matching columns. Any changes in the system catalog are reflected immediately in the rendered reports and forms. Spontaneous changes to the running applications are supported. Projects with an agile workflow and DevOp projects are possible. But projects with more conservative demands are also supported. It is possible to model forms and reports and then extract and copy the generated SQL Queries and PL/SQL Code. You can use it as UI Defaults, in static Apex pages, in the Data Reporter App, and PL/SQL libraries. The report queries can be extracted as updatable views that can be utilized in Apex Interactive Grids.

Forms 
Dynamically produced tabular and single record forms in Readonly or Edit Mode for any table. 
Changes in the schema definition are reflected immediately in the rendered forms.
Produce Field labels
Detect and removes common column prefixes and postfixes.
Compose unique field names for columns of joined tables.
Column Infos 
Help Text with column comments, format mask, description of constraints, functional meaning, statistics: Min, Max, Count, Density.
Developers have options to alter the comments and constraints (range of permitted values).
Produce a diverse variety of input fields 
Including formatted numbers, date, date-time, timestamp, text, multiline textbox, office documents, images, boolean (Yes/No switch), 
Popup links and modal dialogs for 'Rich Text Editor', PDF preview, Office document preview, Image Preview, 'Select Lists' and 'Popup List of Values' (LOVs). LOVs are produced for foreign key columns and check constraints that define value lists. (Example constraints: col_x references table_y; check (col_x in (1, 2, 3)); check (col_y = 1 or col_y = 3) ).
Boolean fields are detected by analysing constraints, default, datatype, length, nullable, cardinality, contradictions and column name pattern.
Functional fields for row selection, link to single record views, ordering rows in a set, hashed passwords, encrypted passwords, file metadata, audit information.
Logical enclosed references are suppressed in the default display column sets. This is done to avoid the display of redundant information. These hidden columns are automatically initialized in key lookup and DML operations.

Automatic validations
When an input field is changed, validations are performed immediately. Any simple check, size limit, reference, or unique constraint defined in the data dictionary is evaluated. On submit of the form any complex check constraint and required constraint defined in the data dictionary is evaluated.

Navigation links
Produce links to parent, childrens, and sister records.
Report Variants 
  • In 'Form View' reports all normal columns of the selected table are displayed. Serial primary key column and audit columns are hidden by default. In read-only mode, foreign key columns display the labels of the referenced rows. In edit mode, foreign key columns are LOV popup or select list fields with automatically composed labels. When available, additional functional columns can be displayed via the actions/columns menu option. In 'Form View', 'Navigation Counter' and 'Navigation Links' reports the height and width of large text blocks and images is constrained to keep the reports readable. When you click on images or document icon, a document preview modal dialog window is opened. In edit mode you can click on text cells with a pen icon to edit large text fields in an HTML-Editor modal dialog window. Column Limits:View up to 100 columns, Edit up to 60 columns.) 
  • 'Navigation Counter' reports by default only display the natural key columns (labels), counters of references and totals of the active table. For each foreign key that references the current table, a column with count of references to a row is displayed. Depending on the setting of the 'Nested View' option, a click on a counter opens the references in a nested table view or on a separate report page. When available, additional functional columns can be displayed via the Actions/Columns menu option. When a number column of a child table is marked a 'Summand' via the Action/Alter Column Rules Dialog, totals for that columns will be displayed.
  • 'Navigation Links' reports by default only display the natural key columns (labels) and totals for the current table. For each foreign key that references the current table, a column with a list of Links to child rows is displayed. A click on a Link opens the reference in a dialog page. When available, additional functional columns can be displayed via the actions/columns menu option. When a number column of a child table is marked a 'Summand' via the Action/Alter Column Rules Dialog, totals for that columns will be displayed.
  •  'Raw Record' reports by default display all data columns of the selected table. Serial primary key column are hidden by default. Foreign key columns display the internal numeric values as stored in the database. 
  • In 'Import View' reports all normal data columns of the selected table are displayed. Serial primary key column and audit columns are hidden by default. In read-only form, foreign key columns display the labels of the referenced rows, while in edit forms, foreign key columns are LOV popup or select list fields of individual label columns. In case of composite labels each component column is displayed as a separate column. The default report column list is suitable for data export and imports. The data import process can validate a convert CSV data files with columns that match the report columns layout. Then the lookup of foreign key references is automatically performed. Depending on the import setting, new lookup values for foreign keys are inserted in the referenced tables or error messages are produced when that is not permitted. When the natural key values (or chosen display columns values) of the imported data matches with existing rows in the current table, then the data is merged for that rows and the data is inserted in new rows when that keys don't match. 
  • In 'Export View' reports by default all normal data columns of the current and the parent table are displayed by default. The serial primary key column and audit columns are hidden by default. Foreign key columns display the natural keys (labels) of the referenced rows. In the case of composite natural keys (labels) each component column is displayed as a separate column. In the modal dialog for Action/Columns Join Options are displayed. You can set the join options to systematically add columns of the referenced tables for each foreign key reference of the current table. After setting the 'All columns' Join option for a table, you can include further columns of the referenced table recursively up to the root of the keys. Independent of your settings, the report will produce one output row for each row in the current report table.
  • In 'History View' reports old versions of the table data can be displayed. The normal data columns and audit information is displayed by default. For foreign key columns, the composed label values are displayed. When the historic data differs from the current row values, that values are highlighted with different table cell background colors. Row changes have to be recorded in a change log to support the History Views. You have to enable the option 'Enable Change Log Support' in the Settings/Edit History Settings dialog page to enable this recording. 
  • In 'Calendar' views data from the current table is displayed in Calendar regions. The natural keys (labels) are displayed in calendar sheets when a calendar start-date and optional end-date column has been registered for the current table. 
  • In 'Tree View' views data from the current table is displayed in a Tree.The natural keys (labels) are displayed as tree nodes when a parent reference column has been registered for the current table. A parent reference is a foreign key reference to the same table with empty parent references for the root nodes. 
Tabular form 
You can add multiple new rows with default values. At least one empty row will be displayed. Show protected rows as display-only in edit forms. The program supports ordering, text search, pagination

 

Single record view
The form can be rendered with 1,2 or 3 column layout.


Publish Reports
A connection to the Data Reporter App enables the publication of reports to other users. Application users and whitelisted tables are automatically synchronized into the Data Reporter App. Any report view can be exported as a data source for the Data Reporter App.

Export formats - Form, HTML, CSV, Native
Data can be rendered in 
  • HTML read-only - with formatted data, scroll boxes for large text, and highlighted search matches.
  • HTML input - with input fields for data entry
  • Native - unformatted for Interactive Reports, 
  • CSV - Unicode text files with comma-separated values for downloads.
Export / Import Cycle
  1. Data from the Import Views can be exported in CSV files to the user's desktop. The columns template of the import view specifies a logical column set that contains all data columns and no serial primary or foreign keys and only display key columns of the referenced tables. The columns template can be downloaded and used as a specification for successful data transfer. On the desktop, the users can alter rows, or append new rows with other applications like MS Excel on Mac Numbers and produce a CSV file.
  2. The user can import CSV files into an APEX collection. After the Import of the file, the data will be automatically validated and a first key lookup is performed. The data is loaded into a temporary collection and is displayed in an edit form. Validation messages are shown at grid cells with bad data. The user can manually fix the errors by entering new data. 
  3. After the inspection of the imported file, the user can perform the import by pressing the 'process import' button. The program will perform the processing to update and insert rows in the database.
Import control parameter provides some flexibility to influence the key lookup processing:
    • Compare Case Insensitive: Allow the keys lookup process to match text column values case insensitive.
    • Search keys unique: Require unique constraints for the imported lookup column sets.
    • Insert new foreign keys: Allow the process to insert new rows in lookup tables. When empty key columns are looked up, the program matches rows with empty columns in the lookup table. When other columns but the key columns are imported, then the table schema should be in the third normal form.  There should be no columns that are dependent on other columns but the primary or candidate keys.

Simple data manipulations 
  • Perform validations, lookups, and DML processing for any table. 
  • Sequences related to a table are detected and then used to produce new identities.
  • Change checks are produced to process only relevant rows and to verify that updated rows have not been changed by other users.
  • The processing of the insert, update, or delete operations produces confirmation messages.
    • Success messages inform you about the number of affected rows.
    • Error messages will report any validation or processing error.
    • Validation errors will appear near the corresponding fields in the form.
Advanced data manipulations 
  • Function to duplicate selected rows.
  • In the context of a container reference, there are functions to copy, move, and merge sets of data.
Convenience 
  • The application stores and remembers your settings for the last accessed table, view mode, column layout, and order between sessions. 
  • Sessions can last up to 10 hours before a new login is required.
  • When buttons and menus are invoked by the user, ca. 300 dynamic actions perform the processing and (partial screen updates). This enables fast processing and improved user experience.
  • Field validation is performed when you leave a field.
  • Required-checks are postponed until you submit the form, to avoid needless complaints.
  • Light and Dark Display Themes. 
  • German and English versions of the interface. 
Security 
  • Custom Authorisation - Only registered users can access the Application.
  • all generated links in the application are protected with APEX checksums.
  • Manage User Accounts with access levels, hashed passwords, e-mail validation, request a new password, invite users via e-mail.
  • Control visibility of tables with table name pattern for inclusion, exclusion, admin only.
  • Control write access with table name pattern for edit, read-only.
  • Control (default) visibility of columns with column name pattern for display labels (always), data deduction, hidden, ignored.
  • Deny write access to rows with column name pattern for read-only access.
Developer tools 
  • Query source code: Use a smart switchboard, to display the SQL query that renders the current report. The options are: 
    • Data Source (Table, Memory, Collection)
    • Data Format (Form, HTML, Native, CSV)
    • Data Operations (Select, Insert/Update, Update, Delete, Duplicate, Move, Copy, Merge, Import View Definition, Download Files)
    • Columns Limit, Show at least one row, Compact Queries, Parent Key Visible
    • View and copy the SQL source queries of the current view. 
    • Queries are rendered according to your currently displayed report 
      • relation (master and detail table) 
      • selected columns
      • column ordering and control break
      • the current Report View Mode (Form View, Import View, ...)
      • the chosen Options and Settings for functional columns and other setting rules.
    • View and copy the PL/SQL code for validations, key lookups, and DML processing. Learn, all necessary step to:
      • detect changed rows
      • validate all size limits and imposed constraints and produce human-readable error messages
      • lookup foreign keys for the given situation.
      • perform complicated data manipulations
  • UI Defaults 
Optimize the column descriptions and export them as UI Defaults. UI Defaults will boost productivity when new forms and reports are produced with APEX. A complete set of column attributes is prepared. included attributes are: column label, datatype, input field length, max field length, required/mandatory,  format masks, static default value, static LOV definitions, dynamic LOV definitions, help text (with column comments, format mask, check constraints).
  • Diagrams
    • Entity Relationship Diagrams
    • Database Object Dependencies
    • Dynamic Actions of Apex Pages
The diagrams are rendered using a dynamic springy layout method that is self-optimized and interactive. The user, can zoom, resize, drag and pane to inspect complex relationships and find missing links.
  • DDL tools
    The application derives all attributes of the tables and columns from the schema definitions and the configuration settings of ca. 50 name patterns. For most patterns, common default values exist. The tables that are designed with this application will match the pattern defaults. All data definition statements are written into the app_protocol table.
    • Definition of new tables
      Choose from templates to add functional columns:
      • Parent Tables
      • Referenced tables (Container, Optional Container, Required, Optional)
      • Natural Unique key description 
      • File (Text Editor, HTML-Editor, File, Folder, None)
      • Ordering, Active, Locked, Audit Infos.
    • Add columns
      Define Column Name, datatype, Char length, Default, Required, Unique (Composed, Simple, Non)
    • Alter column comments

    • Alter column rules (constraints)
      Change the setting for Required, Unique, Values List / Range, Default Value / Default Reference.
    • Drop tables.
      Remove table definition and data.
    • Drop Column
      Remove a column from a table.

Donnerstag, 25. Juni 2020

Show or hide Breadcrumbs in APEX Apps

You may want to add a global control to show or hide the breadcrumbs below the page title. This blog post explains how you can do that. Since users can always return to the home page of your app, by clicking on the Application title, it is OK to hide the breadcrumbs in some situations.
A Region can be set to be Customizable, but that affects only the current page.    
You may want to give the users control to hide and show the Breadcrumbs when they don't need it, with a global switch. The control can be set by the online user via the Navigation Bar menu with the following method.

Add a Application Item
Name : APP_DISPLAY_BREADCRUMBS 
Add an Application Computation
Computation Item : APP_DISPLAY_BREADCRUMBS
Computation Point : On New Instance 
Computation Type : PL/SQL Expression 
Computation  : NVL(APEX_UTIL.GET_PREFERENCE(:OWNER || ':DISPLAY_BREADCRUMBS'), 'YES')

Add an Application Process
Name : Set Display Breadcrumbs
Sequence : 100 
Process Point : On Load: Before Header 
PL/SQL Code:
:APP_DISPLAY_BREADCRUMBS := case when :REQUEST = 'DISPLAY_BREADCRUMBS_ON' then 'YES' else 'NO' end;
APEX_UTIL.SET_PREFERENCE(:OWNER || ':DISPLAY_BREADCRUMBS', :APP_DISPLAY_BREADCRUMBS);
Condition Type : PL/SQL Expression 
Expression 1 : 
:REQUEST IN ('DISPLAY_BREADCRUMBS_ON','DISPLAY_BREADCRUMBS_OFF')
Add Navigation Bar entries 
Edit list 'Navigation Bar' and add 2 entries. 
first entry
Parent List Entry &APP_LOGIN_NAME 
Sequence : 100 
Image/Class : fa-toggle-on 
List Entry Label : Hide Breadcrumbs
Target type : Page in this Application 
Page : &APP_PAGE_ID.
Request : DISPLAY_BREADCRUMBS_OFF
Condition type : Value of Item / Column in Expression 1 = Expression 2 
Expression 1 : APP_DISPLAY_BREADCRUMBS 
Expression 2 : YES 
second entry
Parent List Entry &APP_LOGIN_NAME 
Sequence : 110 
Image/Class : fa-toggle-off 
List Entry Label : Display Breadcrumbs
Target type : Page in this Application 
Page : &APP_PAGE_ID.
Request : DISPLAY_BREADCRUMBS_ON
Condition type : Value of Item / Column in Expression 1 = Expression 2 
Expression 1 : APP_DISPLAY_BREADCRUMBS 
Expression 2 : NO 

Load each page that has a Breadcrumbs region 
Click on the Region named Breadcrumbs
Change the Server-side Condition 
Type : Item = Value 
Item : APP_DISPLAY_BREADCRUMBS
Value : YES 
or when you also whant to hide the region in printer friendly mode
Type : PL/SQL Expression 
PL/SQL Expression :
:PRINTER_FRIENDLY = 'NO' AND :APP_DISPLAY_BREADCRUMBS = 'YES'

The method is demonstrated in a demo app. After login click on the username menu entry in the top menu.

Mittwoch, 13. Mai 2020

Highlight current card

In the APEX universal theme, the is_current state is not visible in Cards regions.
Solution: Highlight active card in list regions with template Cards with some CSS.

 li.t-Cards-item.is-active div.t-Card {
    box-shadow: 0px 0px 6px 1px Yellowgreen;
}

Bug with Warn on Unsaved Changes

APEX version >= 5 supports a 'Warn on Unsaved Changes' functionally when the setting on page level is 'Yes'.
Problem: For item types 'Popup LOV' and 'Radio Group' the setting 'Ignore' is not applied and you get the warning message.
Solution: Use the following JS code in 'Execute when Page Loads' to fix this problem.

// for POPUP_LOV
$('input[id$=_HIDDENVALUE]').addClass('js-ignoreChange');

// for RADIO_GROUP
$('input[type=radio]').addClass('js-ignoreChange');

Montag, 4. Mai 2020

Cloud Visitors – APEX App


Application to monitor visitors of remote APEX sites

I have published several demo applications for open-source oracle APEX plugins on apex.oracle.com and other hosting locations. My joy and payback are, to watch the web traffic on the demo site. To do that, go to the Administration\Monitor Activity\Login Attempts report, there you can list visitors with there IP address. I then used a web site like iplocation.net to find out from where in the world the visitors came. I feel a bit connected to the world out there and I believe that it was worth sharing with the community.

I found the lessons on apex.oracle.com about REST data sources and SQL REST functions.
REST Enabling Database Objects 
Defining Web Sources

Then I took a chance to automate the reporting and location lookup for all my sites in one application that I run in my local development environment.
You can download this application from github.com
https://github.com/dstrack/Cloud_Visitors

You can see a demo of this app here:
https://apex.oracle.com/pls/apex/f?p=143496:LOGIN_DESKTOP

The PL/SQL script file  cloud_visitors_utl.sql creates the view CLOUD_VISITORS_V, the tables CLOUD_VISITORS and CLOUD_VISITORS_IP_BLACK_LIST and the package CLOUD_VISITORS_UTL.

At the demo sites:
Execute the script file cloud_visitors_utl.sql
The packages procedure cloud_visitors_utl.Define_RESTful_Service will be executed to install the REST endpoint.
In the view CLOUD_VISITORS_V, the visitor activity is selected from APEX_WORKSPACE_ACTIVITY_LOG, it is then grouped by session login_date, ip_address, application, and page. The performed requests and time spend is aggregated.

In your localhost:
Install the application in your local APEX development environment. Then go the Shared Components\Web Source Modules to edit the modules. The module IP_Geolocation is used to lookup the geolocations of your visitor's IP addresses and should not be removed. Remove the example modules and add modules for your demo sites.
The app enables you to choose the name of a web source module for a visitor's report.

Launch the app and enter your apex credentials.
The page 'Cloud Visitors'
Here you can display recent visitor's activities in an interactive Report from a local table.
After choosing a web source, you can control the scheduler job for the web source.
Click the 'Update now' button to load the recent information from the data source into the local table could_visitors.
Click the 'Launch refresh job' button to enable the frequent refresh of the report data.
A scheduler job will load the recent information with an SQL REST function from the data source joins it with the IP geolocation data and merges the result into the table cloud_visitors. Your own public IP address is added to the table cloud_visitors_ip_black_list and will be excluded from the reports.

Now you can choose a web source to be displayed and you don't have to wait for the display of the result. The data is updated every 4 hours.

And another problem is solved: The regular call of a web service at xyz.oraclecloudapps.com will also prevent the shutdown of an always free ATP site caused by developer inactivity!

The page 'Visitors - Web Source' shows an Interactive Report from location 'Web Source'. Only one web source (that you have to choose in the program editor) can be displayed and you have to wait up to 30 seconds for the result.

The page 'Visitors - SQL REST function' shows an Interactive Report from an SQL REST function. You can choose a web source to be displayed but you have to wait up to 30 seconds for the result.

The page 'IP Location - SQL REST function' allows you to Lookup the geo-location for an IP-Adress. Your own current public IP address and an IP Black List is shows. Here you can add IP addresses of robots that are excluded from the Cloud Visitors reports.

You may have to increase the Limit of 1000 web service requests that are permitted per day for your workspace, to avoid errors in the web service calls. Log in instance administration and go to page Manage Instance \ Security. In the region 'Workspace Isolation' you can change the 'Maximum Web Service Requests' to a higher value.

Freitag, 3. April 2020

Package IR_Zip_Download

# APEX-IR-Zip-Download
pl/sql code for downloading of large APEX Interactive Reports as ZIP files.
In case you have to download very large reports from an APEX Instance that is running behind a web proxy server or in cases where you have to download reports with more rows than the technical limit allows you to use, you can use the method to successfully download these reports. The Sample App can be installed in an APEX 5 Workspace.


Usage:
1. Install the package IR_Zip_Download in your application schema.
2. add a Button to your Report region.
3. set 'Reload on Submit' to 'Allways' in an APEX 18 and higher.
4. add a 'Branch' of type 'PL/SQL Procedure' or 'Process' of type 'PL/SQL Code' with the following code:

IR_Zip_Download.Download_Zip(
    p_Region_Name => 'Sample Report',  -- Enter your IR region title here
    p_Application_ID => :APP_ID,
    p_App_Page_ID => :APP_PAGE_ID
);

The procedure performs the following steps:
1. extract the query with APEX_IR.GET_REPORT
2. bind the variables
3. Open cursor for query
4. convert to csv.
5. Convert to zip with APEX_ZIP.ADD_FIle
6. start the download to the browser

the code and a sample app can be downloaded here:

The demo app is running here: