...

test.wlselb.frevvo.com/frevvo/web/tn/nancy.com/user/designer/app/_EVHJUIP-EeG1bcc-I8Sq_w/formtype/_cm3dAIP-EeG1bcc-I8Sq_w?_method=post&edit=true&showPalette=false

...

OEM branding class

...

OEM partners can use the context parameter, “frevvo.oem.branding.class” that can be set  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  app.In addition to the context parameter being placed into web.xml, OEMs (or frevvo the  application. 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” if set to “oem. 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 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.

If the OEMs do not want to create a new CSS from scratch, they may also simply edit the oem-branding.css file added as part of v5.0. This file is intended as a starter file for any OEM and the OEM can change any aspect of this file. The default oem-branding.css relies on the context parameter “frevvo.oem.branding.class” being set to “oem”. OEMs would get oem-branding.css from the WAR file and re-WAR it after editing it. 

 

Disabling Submission Repository

...