In order to reduce the number of templates used in a site, I tried to expose a number of layout options in a template component. By accessing these option values from the components in the page-to-html transformation, I thought I could control the output of certain areas.
I assumed that the input to this XSLT was the page file content itself, but it seems that the components are already transformed to HTML, and thus the datum elements of each component are no longer available.
Is there a way to use a component to influence the page scope by accessing the component data or output in the page-to-html workflow in Interwoven TeamSite 6.7.2 and SitePublisher.
We finally found a way around this problem.
By creating a Java class and run it in the page generation workflow, it will receive the content of the page file as input.
By reading the component data and adding these to the Page_Display_Properties element, they can be accessed in the XSLT after each component's XML is transformed.