Versions Compared

Old Version 1

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
Column

The  product installation can be customized in many ways. For example OEM partners can brand  with their own company images and look.

properties make it easy to implement many of the common customizations that all customer and OEM partners will want to consider.

Data API provides a programmatic protocol for viewing and managing resources such as tenants, users, applications, forms, schemas, etc.

Customization properties can be changed in the web.xml or the frevvo.xml files. Any parameter in web.xml can be duplicated in frevvo.xml and the value in frevvo.xml takes precedence over the value in web.xml. We suggest making changes to the context parameter values in the frevvo.xml if you are using the tomcat bundle. This keeps all your modified parameters in one place and makes it easy to upgrade to newer releases. See Installation Tasks for more information.

Code Block
<!-- 
        frevvo war settings 
-->    
    <Parameter name="frevvo.mail.from.email" value="" override="false"/>
    <Parameter name="frevvo.mail.bounce.email" value="" override="false"/>
    <Parameter name="frevvo.mail.debug" value="false" override="false"/>
    <Parameter name="frevvo.actions.debug" value="true" override="false"/>
    <Parameter name="frevvo.rule.debug" value="true" override="false"/>
Column
width350px

On This Page:

Table of Contents
maxLevel2

...

If you are using  in-house, Cascading Style Sheet code that was used in themes applied to forms/flows in previous  releases, it can be added to a newly created style.css file in the frevvo.war file . The context parameter, frevvo.css.url, in the web.xml file must be changed to point to it.  The web.xml file is included in the <frevvo-home>\tomcat\webapps\frevvo.war. The frevvo.war must be unzipped/rezipped after modifications have been made as outlined in the steps below: Let's use the following css code which hides the submit and cancel buttons on all forms/flows as an example:

...

     7. Search for the frevvo.css.url context parameter. set the value of frevvo.css.url context parameter in the web.xml file to point to the newly created style.css file. The frevvo.css.url context parameter should look like this: Remember to save your changes.

Code Block
 <context-param>
         <param-name>frevvo.css.url</param-name>
         <param-value>${context.path}/style.css</param-value>
         <description>Custom Stylesheet URL</description>
 </context-param>

     8. Rezip all the files in the c:\tmp\frevvo-war directory, even the ones you did not edit — if you change directories or zip them differently, Live Forms may not load correctly. Rename the modified file frevvo.war.

...

     7. Add this parameter to the frevvo.xml file. Remember to save your changes.  

 

Code Block
<Parameter name="frevvo.css.url" value="${context.path}/style.css" override="false"/>

If you make these changes, the Login and Forget Password buttons on the  login screen will also be hidden. This is useful for OEMS that embed  in their own application. 

API

The  Data API enables programmatic access to the all resources and data stored in the  server. The API provides a simple protocol for viewing and managing resources such as forms, applications, schemas, etc. OEM partners as well as end user customers can use the API to extend the features and provide tighter integration with other applications.

...