SinclairC
commented
6 years ago So, if we have "style" as a variable in the ReportPage class, is that good or are there sometimes multiple styles? Maybe we'll make the variable a List?
There's "defaultStyle" in the XML, which makes me wonder if there are sometimes other, non-default styles mentioned. Is it just saying "This is the base style" and then the
hyndgrinder
A child of layout, and grandchild of layouts. Neither layouts, nor layout will be documented at this time. In this model, reportPage will be a child of Report.
Attributes:
Children:
Page style, is a reference to the Cognos css system, I beleive, and not usually configured from within the report, so it's not a particularly interesting node at this time. We may find use for it down the road, though, once more sample data is available.
pageBody will be where the majority of the work falls. It will produce many different classes of interest. Flattening all the styles that could be present at all the different levels of the data output containers (lists, pivot table, charts & graphs) will require some thought and modelling.
pageHeader generally carries fairly simple content about the report itself. Simple containers with text that describe the report. The 'look and feel' of the reports aesthetics will often be set in the header. Quite often we will come across Layout Component References, or references to a stylistic template in another report. These are particularly difficult to track with Cognos, and is often mishandled while trying to move a report between the dev/test/production phases especially if each phase does not have it's own dedicated environment.