frevvo Latest - This documentation is for frevvo v10.0. Not for you? Earlier documentation is available too.
This Tutorial will show you how you can embed frevvo and workflows in your web site or web application. In some cases, you may wish to integrate authentication between your application and frevvo so that your users don't have to sign in twice yet are automatically authenticated to frevvo. You may want your users to be authenticated for access control, digital signatures, participating in workflows, viewing their task lists or for maintaining an audit trail.
On this page:
If you do not require access control or authentication for other purposes, i.e. your forms are public forms on your Extranet, you can simply use frevvo built-in Share Dialog and copy and paste the code into your HTML, JSP, ASP, PHP or other web page. An example is frevvo' own contact form. No authentication is required and the form is completed and submitted anonymously. You can find instructions for embedding forms and workflows here.
The basic steps are shown in the above Figure. You'll need to be familiar with creating and managing tenants including creating a tenant using the Delegating Security Manager.
The examples below use the API to authenticate to frevvo. Before using the API, you will need to install the client libraries for your language. frevvo offers Java and .NET client libraries. The examples below use the Java client libraries; the .NET versions are very similar. See these instructions for Installing the Client Library and Dependencies.
In order to automatically integrate with frevvo, your web application will first need to establish a session using the frevvo API. This is done by using the com.frevvo.forms.client.FormsService class and by providing proper credentials to authenticate.
In most cases, you will want to use the loginAs() method available in V4.1.1 and higher. loginAs() allows you to login to frevvo as any existing tenant user provided you pass in the tenant admin's user and password credentials. This is convenient when you want login to frevvo using the same user that is logged into your application without having to know their password.
The following snippet shows how to login as a tenant user. This usage assumes that the user has already been created in the tenant.
frevvo can also automatically create users in your tenant if you created it with the Delegating Security Manager.
This will log you in as the specified userId. If a user with that ID does not exist, the user will be automatically created. The user will have any existing roles as well as the role "manager". If you do not want to specify any roles, you may pass in null. Of course, you can pass in a List with as many roles as you want.
If you want frevvo to auto create a new user that can design forms, you need to pass in the frevvo.Designer role when calling loginAs(). This is typically not required unless you are an OEM customer embedding the frevvo Designer in your product. For instance:
Your JSP page code will look very similar to the above. An important thing to note is that the FormsService instance is state-full and the same instance needs to be used throughout the session (this is specially the case when rendering form urls in the browser since an API key is automatically appended and bound to the FormsService session - as soon as you logout() the API key becomes invalid). Typically, in a web application context, the FormsService instance is stored in the HTTP session that the user has with your web application.
Make sure you have read and understood the documentation on making forms and workflows public.
Now that you have logged in, you must use the FormsService created above to get an embed URL for the form/workflow that you want to embed.
The ID is constructed using the syntax: formTypeId!applicationId!ownerId where:
You can find the IDs using the Share dialog for the form or workflow in question. In the Figure below, the Share URL contains:
Once you have the embed URL, embed it in your JSP as:
If your user has a saved form/workflow, you can find it and render the saved form/workflow instead of creating a new one as described above.