Idea Summary
To support asynchronous downloads of large files, that would otherwise cause problems or timeouts, add a “Download in Background” ACTION to the reports.  This would, via configuration, write the BLOB to a table in the parsing schema to support downloads at a later date.  The downloaded file SHOULD reflect the UI state of the report in terms of visible columns and manual filters applied to columns.

Use Case
To support asynchronous downloads of large files for later retrieval.

Preferred Solution (Optional)
Ideally I would add a “Download Background” action, and add some configuration which can be set to write the values into an Oracle table you specify, where you specify the column to store the EXECUTION_ID, APP_USER, FILE_NAME, FILE_SIZE, MIME_TYPE, EXECUTION_STATUS, ERROR etc.

When a user selects “Download Background”, an asynchronous job is started which takes into account the current state of the interactive grid, and writes the corresponding BLOB file and filename to the table specified in the configuration.  Users could then create a report based on this table to allow people to download the blobs at a later time, create jobs to clear down the blobs periodically and even add triggers to the table to send emails when the status of a download is complete.