...
OEM partners can use the context parameter, “frevvo.oem.branding.class” set (in web.xml) to name a css class. This css class will be placed onto the body of the ui pages (form designer, etc.). CSS file(s) with rules based on the body having the oem branding class can be created in order to customize the application. The If you do mot wish to create css files from scratch, the default oem-branding.css file is a good place to start when creating the css files.. 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 and oemto a temporary directory. The oem-branding-.css file will use OEMs would get oem-branding.css from the WAR file and re-WAR it after editing it.In addition to the context parameter being placed into web.xml, OEMs (or frevvo acting for the OEM) would be 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.
OEM partners are responsible for creating the CSS file(s) and putting them into the WAR file. To do this, the OEMs would also have to edit /css/form.pac.css (in the exploded WAR) and add one or more lines like the following: @IMPORT url(“oem_branding.css”); where oem_branding.css is the name of the css file containing the specific oem rules.
...