Interactive Reporting Studio is an OLE Automation controller. On Windows systems, Interactive Reporting Studio can control external applications (that is, programmable ActiveX objects) that are OLE Automation servers. By making OLE Automation calls, Interactive Reporting Studio can access functionality exposed by other OLE Automation Servers. Examples of OLE Automation Servers, such as Excel and Visual Basic.
<ProgID> is a string that indicates the object to be referenced. Interactive Reporting Studio or Interactive Reporting Web Client passes the string as a reference to the object; for example, Excel.Application. <ProgID> is stored in the registry and contains a string defined as Project.ClassName.
It is recommended that JOOLE calls stored in plug-in scripts be implemented on Internet Explorer.
You cannot embed OLE objects inside Interactive Reporting documents. Likewise, Interactive Reporting Studio and Interactive Reporting Web Client are not OLE servers that produce OLE objects that you can embed in OLE containers.
Example—Invoking an Excel worksheet from a command button created in a dashboard section and writing “Hello World” to rows of a column.
Example—Invoking Outlook from a command button created in a dashboard section and writing a message in the body of the email message:
Example—Using JOOLE to start Outlook on Windows XP:
var obj = Application.Shell("c:\\program Files\\outlook express\\msimn.exe")
Example—Invoking, displaying, and printing a Word document (Hello.doc) from a command button created in a dashboard section:
For example if the Interactive Reporting document is named DashboardText.bqy, Interactive Reporting Studio or Interactive Reporting Web Client creates the text file named DashboardText_trace.txt.