...
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.). Follow the steps below to do this:
- Explode the Stop , if it is running.
- Unzip <frevvo-home>\tomcat\webapps\frevvo.war file to a temporary directory. You may have to change the file extension from .war to .zip to unzip it. See Installation Tasks for instructions.
- Edit \your temporary directory\WEB-INF\web.xml to set the context parameter, frevvo.oem.branding.class to oem.
- Edit \your temporary directory\css-XXXXX\themes\oem\oem-branding.class file to make your changes. The XXXXX in the directory path represents the Revision Number of . For example, the oem-branding.css file will be located in \your temporary directory\css-19498\themes\oem for a revision number of 5.0.1.19498.
- Recreate the oem-branding.css file to include the modified oem-branding.css file.
- Repackage frevvo.war. Refer to Installation Tasks for instructions.
- Copy the modified frevvo.war file to the <frevvo-home>\tomcat\webapps directory.
- Start .
- Clear the cache before restarting your browser to see the changes.
| 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 edit the included oem-branding.css file with rules based on the body having the oem branding class in order to customize the frevvo app.</description> </context-param> |
...