Environment Topics in FPN Part 2: Themes
When integrating content into our portal, we’ve come to expect a seamless integration. The same applies for remote content. This means that we would like to see the same look and feel for the remote content as we do for the local content.In most cases, FPN simply reuses that same mechanism that allows this theme integration. For example, when running a WebDynpro Java iView, the theme is sent as a request parameter so the WebDynpro runtime on the producer knows how to render the content. But what happens when there are different versions of the style sheets? Well, the version is also sent as a request parameter.In general, the LAFService tries to use the consumer’s style sheets; however, if the version is older than the producer’s, it tries to use the same theme as the producer. So what if I’m using a custom theme that is not available on the producer? Then the LAFService tries to use the default sap-tradeshow theme.Does this mean I can’t use my custom theme? No, it doesn’t. What you can do is export your theme from the consumer and import it into the producer.
