...
OEM partners can use the context parameter, frevvo.oem.branding.class to name a css class that will be placed onto the body of the ui pages (form designer, etc.). The Set the context parameter, frevvo.oem.branding.oem.branding.class must be set to oem in the web.xml file. Unzip the frevvo.war file to a temporary directory. class to oem in the web.xml file. The web.xml file is located in <frevvo-home>\WEB-INF\web.xml after the frevvo.war is unzipped to a temporary directory. Refer to Installation Tasks for the steps to unzip and repackage frevvo.war after parameters in web.xml have been edited.
| Code Block |
|---|
<context-param>
<param-name>frevvo.oem.branding.class</param-name>
<param-value>oem</param-value>
<description>This css class will be placed onto the body of the frevvo ui pages. OEMs can then create their own private CSS file(s) with rules based on the body having the oem branding class in
order to customize the frevvo app.</description>
</context-param> |
The oem-branding-.css file is located in <\tmp>\css-XXXXX, where XXXXX=version number\oem. Rezip the frevvo.war file after editing is completed. See Installation Tasks for more information.
...
If you do not wish to create css files from scratch, the default oem-branding.css file is a good place to start.. Any aspect of this file can be changed. The context parameter “frevvo.oem.branding.class” must be set to “oem". Unzip the frevvo.war file to a temporary directory. The oem-branding-.css file is located in <\tmp>\css-XXXXX, where XXXXX=version number\themes\oem. Rezip the frevvo.war file after editing is completed. See Installation Tasks for more information.
...