Live Forms v5.1 is no longer supported. Click here for information about upgrading to our latest GA Release.

Skip to end of metadata
  • Created by Former user, last modified by Former user on Jul 11, 2013
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 60 Next »

provides a add-on that you can install into Confluence to create sophisticated forms and workflows integrated with Confluence. The add-on requires installation of an in-house server.

These instructions apply to the  Confluence add-on for use with a  v5 or 4.1.7 server.

On This Page:


Using an In-house Live Forms server

We strongly recommend the installation video.

 

  1. Download and install the  server. Instructions for your platform can be found on the Installation Instructions page.
  2. Setup your In-house  server for Confluence. You must now create a tenant specifically for Confluence. Details can be found in the Installation Video.
  3. Click, Installing and Configuring the add-on to complete the installation.

Installing and Configuring the Confluence add-on

Install the add-on

Using UPM:

We strongly recommend using Universal add-on Manager (UPM). Please follow the Atlassian instructions  for adding an add-on. Search for the frevvo Live Forms and Workflows for Confluence add-on in UPM, select it and click Install. The add-on will be installed automatically.

Manual Installation

If you cannot use UPM, you can download the  add-on from the Atlassian Marketplace. There are two  add-on versions available for Confluence. The   v4.1.7 version is compatible with Confluence v3.3 and higher. The  4.1.8 version is compatible with Confluence v4.0 - 4.2.

  • Download the  Confluence v3.x compatible add-on here.
  • Download the Confluence v4.0 - v4.2 compatible add-on here
  • Download the  Confluence v4.3 compatible add-on here.

Then, follow Atlassian instructions for installing the add-on into Confluence. Remember to first uninstall any previous version.

Configure the add-on

You must first configure the add-on before you can use it. The image below shows the potential configurations available for the Confluence add-on. The image is large so that the text is readable. In most cases, you will not need to specify these configuration parameters and can leave them blank. Click Configure.

Forms Server URL

This is the scheme, host & port on which the forms server is running. The add-on (installed in Confluence) must be able to access the  server. For example, the URL for '  SaaS service is: http://cf.frevvo.com OR https://cf.frevvo.com if you want to use SSL. The URL to your in-house installation might be: http://frevvo.mycompany.com:8082/.

User Name

Enter the tenant admin user for the tenant you created. Remember that you must enter it using the syntax userid@tenant, e.g. admin@mycompany.com

Password

Type in the above admin user's password.

Form Designers Group

You can specify a Confluence group here. If specified, only users belonging to this group can design and add forms, flows or submissions to Confluence pages. If this is left blank, all Confluence users will be able to  add forms, flows or submissions to Confluence pages.

Form Users Group

You can specify a Confluence group here. If specified, only users belonging to this group can add the Task List to Confluence pages. If this is left blank, all Confluence users will be able to add the Task List to Confluence pages. Note that all users can still access public forms on public Confluence pages.

Form Editors Group

This feature is available in Live Forms v4.1.4 and higher. You can specify a Confluence group here. If specified, users belonging to this group can edit forms and flows belonging to any other user. If this is left blank, edit access is restricted to the original designer/owner of the form/flow. If you are using Confluence 5.1.4, users belonging to this group can also view/delete submissions for forms and flows belonging to any other user. Note that the editor has to have designer privileges for this additional capability. 

Confluence Server URL

This is reserved for future use.

Confluence Server External URL

In most cases, you do not need to configure this.

In some configurations, the URL used by a browser outside the firewall to access Confluence may be rewritten before it is internally passed on to Confluence. If that's the case, Confluence URLs generated by  to perform any redirection will be wrong since they will reflect the rewritten internal URL. You can specify the externally visible URL to Confluence here. If not specified, this will be inferred from the HTTP Request received by Confluence.

Forms Server External URL

In most cases, you do not need to configure this.

In some configurations, the externally visible URL to the forms server may be different from the above URL, i.e. the URL that a browser outside the firewall uses to access  could be different from the URL that the add-on (inside the firewall) uses to access .  If that's the case, enter the externally visible URL in this configuration parameter. Your users must be able to access the  server from their browsers via this URL. When the  form, workflow or task list is rendered in the browser, this URL will be used to access . This URL defaults to the above Forms Server URL if not specified.

If Confluence is running over ssl, configuring this URL, helps to render forms/flows on the Confluence pages.  You also need to configure the 'Confluence Server Url' in the tenant you have set up specifically for Confluence. See Manage Tenants.

 

Enable Debugging

If checked, the add-on will print debugging information to Confluence pages. In addition, for forms and flows, you can also specify a parameter to the form macro that is generated in Confluence pages: _norender:true. If this parameter is present, the macro will simply print debugging information but will not actually render the form.

Click the Save Configuration button. If all goes well, the message "add-on configuration updated" should be displayed. You may now logout of the Confluence admin account.

Administration

HTTP Configuration

The add-on makes HTTP requests to the  server, which may be remote in order to process your form. If you find that the  macros do not work, ask your network administrator if Confluence needs to access the Internet through a web proxy.

Please refer to Configure Web Proxy Support for Confluence for further information.

Login to Form Server

There are occasions where you may want to login directly to the Live Forms server rather than via Confluence. Here are a few points to understand:

  1. All Confluence users who create forms and workflows automatically have their user account created on the Live Forms server. In order to login directly to the form server, you must first login as the  admin and then use the login as that user feature available to the admin user to next login to the specific user account.
  2. All forms and flows are created under Application 1 in the Live Forms user account of the same username as the username of the Confluence user who first created the form or flow.

Known Issues

Internet Explorer

If you get this error adding a flow to a Confluence page you an solve this with a simple browser setting.

Internet explorer has modified this page to prevent cross site scripting

Go to IE Tools -> Internet options -> Security tab -> select custom level -> disable XSS Filter

 

  • No labels