Siebel Reports Administration Guide > Reports Development Environment > About the Siebel Reports Development Environment >

Actuate File Types

Actuate uses or generates files of the following nine types:

  • ROD (Report Object Design). An ROD file is a report layout file. An ROD file exists for each standard report, and you create a new ROD file for each new report you create. The ROD files for the standard reports are provided with Siebel Tools.
  • ROL (Report Object Library). An ROL file is a library file. A library file contains reusable components you can add to design files. Since you can subclass, copy, or reference objects from libraries, you usually can reuse existing ones, and you do not have to understand how to construct them.
  • BAS (BASIC source code). A BAS file is generated during the build and compilation processes. It is generated from the ROD file being compiled and from the included library modules from ROL files. It is an intermediate file format used in the subsequent compilation step and is not directly modified by the developer. A BAS file can also be used to implement reusable Actuate BASIC routines for inclusion in report designs.
  • ROX (Report Object Executable). An ROX file is an executable report, that is, a compiled ROD file. When you run a report, the Siebel application executes the ROX file. Note that Siebel applications include ROX files for the standard reports. When you customize standard reports or create new reports, you need to replace the corresponding ROX files or add them to the appropriate directory to make them available to the Siebel application.
  • ROI (Report Object Instance). An instance file is what the user sees when the report is running in the Actuate window in the Siebel application. You interact with an instance file only when saving a report or when viewing it using an external viewer (Siebel Mobile Web Client mode).
  • ROV (Report Parameter Values). The parameter values file contains a report request's parameter definitions and values. Actuate creates the parameter values file automatically when users issue a request. The user enters parameter values in the Application screen (see parameterized reports documentation), and the information is written to a parameter values file, which can then be used to generate a report based on the specified parameter values.

    NOTE:  If a control is not seen properly, or seems to have disappeared in the ROI file, review how the control is placed in the ROD file. Check the positioning, the size, and whether the control is overlapping another control. However, even if the control has the correct position or size, it still may not be seen properly in the ROI file.

  • DHTML (Web page). A DHTML file is what the user sees when the report is obtained from the Siebel Reports Server using a Web browser (Siebel Web Client mode).
Siebel Reports Administration Guide Copyright © 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices.