USE CASE

The current SQL Scripts results page (SQL Workshop → SQL Scripts → Results) renders script output as a plain paginated HTML table. A real script — like the one shown, 378 statements across 25+ pages — makes error hunting extremely painful:

• Statement and Feedback columns are truncated — the full SQL and full error text are cut off
• Errors have zero visual distinction from successful rows — ORA-00955 looks the same as "Statement processed"
• No filtering — finding all errors requires reading every page manually
• The existing Detail/Summary toggle is useful, but still doesn't solve the discoverability of errors
• The Download link exports raw text, not structured data

This affects every developer running deployment, migration, or patch scripts in APEX 24.2 and 26.1 
 

PREFERRED SOLUTION

1. Replace the plain HTML table with a Read-Only Interactive Report

Keep the existing columns (Number, Elapsed, Statement, Feedback, Rows) but render them as a native APEX IR, giving users immediate access to:

• Column filters — filter Feedback column by "Error" / "ORA-" to isolate failures instantly
• Search bar — search for a specific ORA- code or object name across all 378 rows at once
• Sort — sort by Elapsed to find the slowest statements
• The IR already exists as a framework inside APEX — this is a rendering change, not a new engine

2. Status Badge Column

Add a derived Status column with visual badges:

• ✅ Success — "Statement processed", "Table created", etc.
• ❌ Error — any feedback containing "ORA-" or "Error at line"
• ⚠️ Warning

This column becomes the primary IR filter: one click → show only errors.

3. Summary Banner at the Top

Replace (or augment) the current "Status: Complete" text with a structured banner:

✅ 375 Succeeded  |  ❌ 3 Errors  |  ⏱ 4.2s total

Clicking "3 Errors" auto-applies the IR filter. Zero hunting.

4. Full-Content Drill-Down (Read-Only Form / Modal)

The current Statement and Feedback columns are truncated in the table view. Clicking any row — especially an error row — should open a read-only detail region (modal or inline) showing:

• Full Statement — the complete SQL block, displayed in a Code Editor (Monaco) region, syntax-highlighted, read-only
• Full Feedback / Error — untruncated, with ORA-XXXXX codes visually highlighted and the line number reference made actionable (e.g., highlight line 18 in the code editor if the error says "line 1/18")
• Number, Elapsed, Rows affected

5. Structured Export

Upgrade the current plain-text "Download" to offer CSV / Excel export of the IR data, including the full (untruncated) Statement and Feedback columns — essential for deployment audit trails and incident reporting.

Implementation Notes

• The APEX engine already parses each statement's result to build the current table — the structured data exists, only the rendering needs upgrading
• The existing Detail/Summary radio toggle could be preserved as a view mode within the IR (Summary = IR row per statement; Detail = expanded IR with full text visible)
• The Code Editor component is already available natively in APEX — reusing it here requires no new dependencies
• The IR filter state could be bookmarkable/shareable via APEX's native IR URL mechanisms