Welcome

About

The ™ Getting Started Guide takes you through the process of designing, deploying and using your first simple form. You'll quickly see how easy it is to create forms with . To use this guide, follow the steps below. Each step contains links to more detailed information.

If you'd rather jump directly into more detailed documentation describing how to design, deploy and use ™ use the navigation links to the left.

For those who prefer to learn via video demonstrations and tutorials please watch and follow our Tutorials.

Step by Step

Starting your Evaluation

It's very easy to get started with an evaluation copy of . You can subscribe to a free 30 day trial account of Online or 30 day trial download and install In-house. See Evaluating for help starting your trial evalutation.

Logging In

1) Open the login page in your browser.

Online: http://app.frevvo.com
In-house: http://<your server>:8082/frevvo/web/login

2) Enter your username and password.

- username = <your userId>@<tenantId>
- password = <your selected password>

What happened to the tenant field? supports two different login styles. The first style has two login fields -- username and password. The username is composed of your userId followed by @ and followed by your tenantId. The second style has three login fields - username, password and tenant. Here the username is just your userId with no @ and no tenantId. Your tenantId is expected in the tenant field.

Online now uses the first style. In-house defaults to the first style but you can configure your software to switch to the second style.

When using the second style you must login as the superuser admin with username admin@d rather than just username admin.

What You See when you are logged In

Create an Application

Upon successful login, you will see a page labeled “Applications”. forms and workflows are organized into Applications. Applications contain one or more forms and workflows depending on your needs. Applications also contain other projects elements such as form submissions, tasks and schemas. Before you create your first form or workflow you will need to create an application.

Click the icon to create your first application. It is given a randomly generated name. You can add additional applications here or delete the ones you no longer need by clicking the icon next to your application’s name.

First, rename your application to something more meaningful by clicking on the properties icon below your application. Give your application a new name and a meaningful description so that when you see it in your application list you’ll be able to quickly tell what it’s about.

The properties page also enables you to set your application’s theme and base URLs. For this simple example, use the default theme Nouveau. And leave the base URLs empty.

Getting Started with Forms

Click Getting Started with Forms to walk through the steps involved in creating a simple form. Also see the Designing Forms and Using Forms topics for more detailed instructions.

Getting Started with Flows

Click Getting Started with Flows to walk through the steps involved in creating multi-page forms and workflows that route your form through an approval process collecting digital signatures along the way. Also see Designing Flows and Using Flows topics for more detailed instructions.

Themes

The Themes tab enables you to customize the style of your forms & workflows so that they fit into the look & feel of an existing web application.

Most customization can be accomplished using the Form Designer and using one of ' built-in themes like Nouveau or Nouveau Blue. See the Form Designer's Form Style Properties and Control Style Properties. But when more extensive customizations are required, you can download one of ' themes and modify it to suit your requirements. See the Customizing Themes for details.

Integration

Eventually you will want to integate your new forms and flows into your existing web application or with other products such as a Database, BPM product, SOA, Web Services. Because is XML compliant and schema aware this is a straight forward task. See Integration for details.