Saving, fetching and deleting
The plug-in requires 3 procedures and 1 table to be successfully implemented in an Oracle APEX application. Procedure APIs are described in The plug-in \ Dynamic Action \ Attributes \ Application Attributes section. These procedures are used to save, fetch, and delete chart reports in/from the specified table.
Chart report
The chart report is the plug-in concept to store changes made with the plug-in to the Oracle APEX JET chart. The table below describes the information needed to successfully save a chart report.
| Property | Description | Example |
|---|---|---|
| Username | To distinguish between user’s reports | bostrowski |
| Chart id | To identify an Oracle APEX chart region Using the static id is recommended if chart reports should be transferable between different environments. | bar |
| report name | To identify a chart report | Example report |
| The JET chart attribute path | Oracle JET chart attribute path that has been customized. | legend.rendered |
| The JET chart attribute value | Oracle JET chart attribute value that been customized. | on |
Procedures
The procedures are executed by the plug-in PL/SQL API when the end-user invokes the Reports \ Save and Reports \ Delete actions or on page load to fetch saved reports. These procedures accept arguments describing the chart report and must be implemented by the APEX developer when the plug-in is installed for the first time.
The example PL/SQL code for saving, fetching, and deleting chart reports is part of the sample application and can be previewed in the UC_JET_CHART_API package.
Table
The table storing saved reports should meet the following requirements:
- should be accessible from Oracle APEX parsing scheme,
- should be able to store (at least) the information described in The plug-in \ Saving, fetching and deleting chart reports \ Chart report section
An example table is part of the sample application and can be previewed in Oracle APEX application builder \ SQL Workshop \ Object Browser \ Tables \ UC_JET_CHANGES.