Defining a Style template in Web Intelligence by using Cascading Style Sheets
With Web Intelligence (since 4.0 SP3), you can modify the default style of your Web Intelligence documents (WID). This will allow you to set the style template in order to have a consistant style through all documents and reports. This style is defined with the Cascading Style Sheet core syntax (slide 5) and stored in a DefaultStyleSheet.css file on the webi Server. A copy of this file is automatically embedded in each new WID and will be used from there then.
To modify the style of existing documents, the export, edit, import, and reset operations are operation available in the Document Properties dialog box.(Slide7)
To define and implement a style to a set of documents, we advise you to iterate by small modifications of the CSS (slide 12), then to update the other documents (slide 13) and finally publish the CSS on BOE Servers and Web Intelligece Rich Clients (slide 14).
Once that environment set, all report designer will automatically have the right style (colors, fonts, table header backgrounds, etc..) when they create reports and/or add a new report elements. For example you can set the horizontal autofit width property to on to avoid the resizing of each columns after table creation.
Note: By default, reports elements default values come from the CSS content embedded into the WID file.
Note: When the Webi document is modified, the CSS file is not modified.
Note: The modification of the CSS is done by extracting it from the WID (step2) and then importing it (step 6) The modification of a style using CSS is an iterative operation of small modifications (Step 4) and then seeing the result on a sample report (steps 5, 6 and 7).
Note that if a syntax error occurs on the CSS file, the rest of the file is ignored. We advise you to keep intermediate versions of the css on your file system to be able to come back on a valid and working version if necessary.
Note: Publishing the CSS on servers to be THE style standard of new documents needs to be sure of the quality of the CSS.
A first test will be to verify that each type of reports elements added in a document have the expected style.
A second test will be to verify that a variety of existing documents can be easily migrated to the new style (steps 1, 2b, 3, 4) .
Note: Once the CSS file validated, it can be published on each server. We advise you to put comments inside the CSS to be able to recognize it afterwards.
Note that the effect of this publication could not be immediately seen by report designers: it will be seen if they create a new WebI document or if they “Reset to standard Defaut Style” an existing document.