This chapter includes the following sections:
The BI Publisher data model supports the following types of triggers:
Before Data — fires before the data set is executed.
After Data — fires after the data engine executes all data sets and generates the XML.
Schedule Trigger - fires when a report job is scheduled to run.
An event trigger checks for an event and when the event occurs, it runs the code associated with the trigger. The BI Publisher data model supports before data and after data triggers that execute a PL/SQL function stored in a PL/SQL package in your Oracle Database. The return data type for a PL/SQL function inside the package must be a Boolean type and the function must explicitly return TRUE or FALSE.
A schedule trigger is associated with a schedule job. It is a SQL query that executes at the time a report job is scheduled to run. If the SQL returns any data, the report job runs. If the SQL query returns no data, the job instance is skipped.
To add before data or after data event triggers:
On the data model Properties pane, enter the Oracle DB Default Package that contains the PL/SQL function signature to execute when the trigger fires. See Section 1.7, "Setting Data Model Properties."
From the task pane, click Event Triggers.
From the Event Triggers pane, click Create New Event Trigger.
Enter the following for the trigger:
Type — Select Before Data or After Data.
Language — Select PL/SQL.
The lower pane displays the available functions in the Oracle DB Default Package that you entered in the data model Properties in Step 1.
Figure 5-1 shows an event trigger.
Select the package from the Available Functions box and click the arrow to move a function to the Event Trigger box. The name appears as PL/SQL <package name>.<function name>.
If you define a default package then you must define all parameters as a global PL/SQL variable in the PL/SQL package. You can then explicitly pass parameters to your PL/SQL function trigger or all parameters are available as a global PL/SQL variable.
A schedule trigger fires when a report job is scheduled to run. Schedule triggers are of type SQL Query. When a report job is scheduled to run, the schedule trigger executes the SQL statement defined for the trigger. If data is returned, then the report job is submitted. If data is not returned from the trigger SQL query, the report job is skipped.
The schedule trigger that you associate with a report job can reside in any data model in the catalog. You do not need to create the schedule trigger in the data model of the report for which you which to execute it. You can therefore reuse schedule triggers across multiple report jobs.
To add a Schedule Trigger:
In the data model editor task pane, click Event Triggers.
From the Event Triggers pane, click the Create New icon.
Enter the following for the trigger:
Name - enter a name for the trigger.
Type — select Schedule.
Language — defaults to SQL Query.
In the lower pane, enter the following:
Options - select this box to cache the results of the trigger query.
Data Source - select the data source for the trigger query.
SQL Query - enter the query in the text area, or click Query Builder to use the utility to construct the SQL query. For information, see Section 2.3.3, "Using the SQL Query Builder."
You can include parameters in the trigger query. Define the parameter in the same data model as the trigger. Enter parameter values when you schedule the report job.
It the SQL query returns any results, the scheduled report job executes. Figure 5-2 shows a schedule trigger to test for inventory levels based on a parameter value that can be entered at runtime.
For information on implementing the schedule trigger in the report job, see "Defining the Schedule for a Job" in the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Publisher.