Oracle^® Business Intelligence Answers, Delivers, and Interactive Dashboards User Guide > Using Oracle BI Delivers >

Specifying Actions to Execute on Completion of an Oracle BI Delivers iBot

Use the Advanced tab to specify one or more actions to execute when the iBot completes. Actions will be executed on behalf of each user who is a recipient of the iBot. You can change the default behavior for each iBot action. Actions include the execution of other iBots, custom scripts, custom Java programs or Workflows defined using the Oracle's Siebel Workflow Version 7.7 (or higher) application. You can also specify actions to execute either when iBot conditions are satisfied, or when no records are returned.

NOTE:  By default only Oracle BI administrators have the necessary privileges to specify all of these actions. Users that are not administrators can only specify the execution of other iBots action.

Added actions are shown with a Properties button that you can click to view or modify properties, and a Delete button that you can click to delete actions.

This section contains the following topics:

• About iBot Action Properties
• About Custom Script Action Properties
• About Workflow Action Properties
• About Custom Java Program Action Properties
• Procedures for Specifying Actions to Execute on Completion of an Oracle BI Delivers iBot

For an overview of Oracle BI Delivers, see Overview of Oracle BI Delivers.

About iBot Action Properties

You can specify the next iBot to run when the current iBot completes.

To enter details into the Path field, you use the Browse button to display the Select iBot dialog box, and you select the iBot that you want to run.

The following options are the choices for the scope of recipients from the Execute for Recipients drop-down list.

• Of specified iBot

  Select this option to use the iBot referenced in this dialog.

• Of current iBot

  Select this option to use the current iBot containing subsequent actions.

• Of both specified and current iBot

  Select this option to use the union of both iBots.

• Common to specified and current iBot

  Select this option to use the intersection of both iBots.

• Of specific iBot, but not current iBot

  Select this option to use the referenced iBot and exclude recipients from the current iBot.

If you have filters from originating iBots applied to subsequent iBots, filter values are generated by the conditional request specified at the Conditional Request tab. The iBot specified at the Advanced tab will execute once for each row in the conditional report, with filters generated by the values in that row.

About Custom Script Action Properties

You can specify the filename of a custom script to execute (on Microsoft Windows) when the current iBot completes. The custom script file must reside on the same server as the Oracle BI Delivers server (the Scheduler). The custom script type can be either Javascript or VBScript. By default, only Oracle BI administrators have the necessary privileges to configure Custom scripts. For information about the procedures to configure this capability, see Oracle Business Intelligence Scheduler Guide.

You can select options for whether results are passed to the script, as well as desired formats. You can also manually add additional parameters.

Depending upon the type of content to be passed (from either the conditional request or the delivery content), results may be passed in some of the following formats:

• MHTML (MIME HTML used in email)
• XML (extensible markup language)
• Plain Text
• CSV (comma separated values)
• PDF (portable document format)

About Workflow Action Properties

You can configure iBots to trigger workflows in Oracle's Siebel Workflow Version 7.7 (or higher) application. By default, only Oracle BI administrators have the necessary privileges to configure iBots to trigger workflows. For information about the procedures to configure this capability, see Oracle Business Intelligence Scheduler Guide.

Dynamic properties are generated by the conditional request specified at the Conditional Request tab. The Workflow will be initiated once for each row in the conditional request, with dynamic properties generated from the values in that row. You can also choose a column from a conditional request.

About Custom Java Program Action Properties

You can specify a custom Java program to execute (on Windows and UNIX) when the current iBot completes. By default, only Oracle BI administrators have the necessary privileges to configure Custom Java programs. For information about the procedures to configure this capability, see Oracle Business Intelligence Scheduler Guide.

You can select options for whether results are passed to the Java program, as well as desired formats. You can also manually add additional parameters.

Depending upon the type of content to be passed (from either the conditional request or the delivery content), results may be passed in some of the following formats:

• MHTML (MIME HTML used in email)
• XML (extensible markup language)
• Plain Text
• CSV (comma separated values)
• PDF (portable document format)

Procedures for Specifying Actions to Execute on Completion of an Oracle BI Delivers iBot

This section provides procedures for specifying the action to execute when an iBot completes.

To select the next iBot to run when the current iBot completes

1. Click the Add Action button and choose iBot.
2. Click the Browse button to select the next iBot to run.
3. Choose the scope of recipients from the Execute for Recipients drop-down list.

   For more information, see About iBot Action Properties.

4. To specify that filters in the current iBot be applied to the next iBot, click the following option:

   Propagate filters from parent

   NOTE:  This step applies only if the content you select contains filters.

5. To add additional filters, click the Add button.

   To remove all additional filters, click the Clear button.

To specify a custom script to execute when the current iBot completes

1. Click the Add Action button and choose Custom Script.

   The Custom Script Properties dialog box opens.

2. Type the path to the script in the Filename text box.

   NOTE:  The script must reside on the same server as the Oracle BI Delivers server (the Scheduler).

3. Choose the script type from the Type drop-down list.
4. In the Results area, make your selections for whether results are passed to the script, and if applicable, the format in which to pass results.
5. To add additional parameters manually, click the Add button.
6. To remove all entered parameters, click the Clear button.
7. Click OK.

To specify a Workflow to execute

1. Click the Add Action button and choose Workflow.

   The Workflow Properties dialog box appears.

2. Type the name of the Workflow in the Workflow Name field.

   NOTE:  Specify a Workflow defined using Oracle's Siebel Workflow Version 7.7 (or higher) application.

3. To pass Name and Value pairs to the Workflow, enter them in the Static Properties section.
4. Click the Add button to add additional static properties.

   To remove all added static properties, click the Clear button.

5. Enter the appropriate dynamic values in the Dynamic Properties section.
6. To add multiple dynamic properties, click the Add button.
7. To remove all added dynamic properties, click the Clear button.
8. To choose a column from a conditional request, select it from the Value Column drop-down list.
9. Click OK.

To specify a custom Java program to execute when the current iBot completes

1. Click the Add Action button and choose Custom Java Program.

   The Custom Java Program Properties dialog box appears.

2. Type the fully qualified implementation class for the Java program action into the Class Name field.

   For example:

   • MyCompany.Application.Class1
3. Type the name of the jar file containing the Java program in the Class Path field.

   NOTE:  The path is restricted to the name of the jar file. You cannot specify a relative or absolute path.

   NOTE:  The Jar file must be in the default user Jar file path, as specified for the Oracle BI JavaHost. For more information, see the Oracle Business Intelligence Scheduler Guide.

4. Type the names of other jar files (containing utility classes and libraries that the Java program requires to run) in the Additional Class Path(s) field.

   NOTE:  Additional paths are restricted to the names of the jar files. You cannot specify relative or absolute paths.

   NOTE:  If more than one additional Jar file is specified, separate each using a semi colon character (;).

5. In the Results area, make your selections for whether results are passed to the Java program, and if applicable, the format in which to pass results.
6. To add additional parameter values manually, enter the details and click the Add button.
7. To remove all entered parameters, click the Clear button.
8. Click OK to add the custom Java program to the iBot.