Siebel Reports Administration Guide > Creating a Simple List Report > Alternative Report Creation Strategies >
Using a Custom Component Library
If you create a design component and child components that will prove useful in similar reports, you can create a custom component library that allows you to reuse these components. An example of a custom component library is the ssQuote.rol library used in various quote reports, including Quotestd.rod, Quotepro.rod, and Quosum.rod.
Typically, this technique is used to reuse page header, page footer, or content frames containing a number of labels and data controls, but any component and its children can be published in this fashion for reuse.
To create a custom component library
- Open the report design that contains the components you want to publish in the custom library.
- Choose Tools > Library Organizer.
The Library Organizer window appears.
- Click New.
- Specify the destination folder (this should be C:\Siebdev\RPTSRC\ENU\LIB or equivalent) and filename (the filename should begin with ss, to designate it as a Siebel custom library and distinguish its name from those of the datastream libraries). Click Save.
If your installation uses a non-English version of Siebel eBusiness Applications, you do not have an \ENU folder. Instead, you have a folder in the appropriate language code for your installation, such as \DEU for Germany.
See Global Deployment Guide for a list of three-letter International Standards Organization (ISO) language extensions.
- Click OK on the Library Organizer window.
The Library Browser window opens for the new library, containing only the top-level library component.
- Drag and drop the desired parent component from the report design (such as a content frame) onto the top-level library component.
The Component Drop dialog box appears.
- Click the Publish the component radio button and click OK.
The component that you published and its children are added to the library. Their names in the report design file are changed to light gray, indicating that they are now subclassed components from the version in the library.