Live Forms macros

frevvoform macro

Add and workflows to your Confluence page via the Add menu options that the  add-on incorporates into the Confluence's Add menu. The Add > Form and Add > Flow menu items described in detail in Using the add-on automatically add the frevvoform macro to your page with the correct form identification.

In Confluence v3.x the macro looks like this:

{frevvoform:container=true|_data=(page.id:'9207810',server.url:'http://localhost:8070')|center=false|
formtypeurl=/frevvo/web/tn/dsm/user/designer/app/_i00BcXKYEeC6cd5Wo2bXdQ/formtype/_lTxXMHKYEeC6cd5Wo2bXdQ/embed|
id=form-1304106048646|resize=true|
formtypeid=_lTxXMHKYEeC6cd5Wo2bXdQ!_i00BcXKYEeC6cd5Wo2bXdQ!designer}

In Confluence v4.x - 5.1, the macro looks like this:

You can customize the appearance of the form or workflow by editing the parameters to the macro as described below:

Parameter	Values	Default	Meaning
center	true or false	false	Centers the form on the page. This property applies only when container=true.
container	true or false	true	Generates a border around the form if true. If set to false, the frame will not be seen and hence the Edit and remove buttons will go away too.
_data	Live Forms generated value	generated	Used to initialize the form. You can add parameters here but do not remove the existing ones auto-added by the add-on. See the documentation for more information.
formtypeid	Live Forms generated value		The internal ID of the form/workflow. Do not modify. Not visible in Confluence v4.x.
formtypeurl	Live Forms generated value		The internal URL of the form/workflow. Do not modify. Not visible in Confluence v4.x.
height	numeric		The initial height of the form. Used when you disable auto-resizing.
locale	3 letters		The desired locale (e.g. ger, dan, ara etc.). The form will be rendered in the specified language. See the multi language support documentation for more information.
resize	true, false, vert or horz		Automatically resizes the form. vert enables vertical resizing only and horz enables horizontal resizing only. Auto-resizing can add a URI fragment to the browser URL. If you need to use URI fragments, you must disable auto resizing.
scrolling	no, yes, or auto	auto	If no, scrollbars will never appear, if yes, scrollbars will always be present, if auto, they will be present if required. This property is redundant when resize is true. Auto-resizing will always ensure that the frame is big enough so that scrollbars never appear.
width	numeric		The initial width of the form. Used when you disable auto resizing.

Turning off auto resizing

Auto-resizing is extremely convenient since the form will automatically resize to take up as much horizontal and vertical space as it needs. This can be very useful for forms that have collapsible sections, multiple Tabs, repeat controls etc. and where user actions can alter the vertical space. However, in cross-domain environments where Confluence and  are running in different containers or on different machines, auto-resizing requires adding a URI fragment to the browser URL. The fragment looks something like: #632:234:form-1304106048646 where the numbers can be different. This can affect URLs that you may be using that already contain URI fragments since the  URI fragment will overwrite your URI fragment.

To fix this, you will have to disable auto-resizing. This means that if the form does not fit in its alloted area, scroll bars will automatically appear. To turn off resizing, set the parameter resize=false and specify an initial height and width using the height and width parameters e.g.....resize=false|height=250|width=632|... The form will be rendered with the specified height and width and will never resize.  will not alter the browser's URL either. 

frevvoresolve macro

The frevvoresolve macros can be used in Confluence templates to create or edit Confluence pages using the form submission data.

Here is an example template using the frevvoresolve macros in Confluence v3.x:

h3. This is the client information page for : {frevvoresolve}<ClientName>{frevvoresolve}
h4. [Click here | {frevvoresolve}<form.edit.link>{frevvoresolve}] to edit this information
| First Name | {frevvoresolve}<FirstName>{frevvoresolve} |
| Last Name  | {frevvoresolve}<LastName>{frevvoresolve} |

Here is the same example template using the frevvoresolve macro syntax required for Confluence v4.0 - 4.2:

<h3>This is the client information page for: <ac:macro ac:name="frevvoresolve">[ClientName]</ac:macro></h3>
<h4>[Click here | <ac:macro ac:name="frevvoresolve">[form.edit.link]</ac:macro>] to edit this information.</h4>
<table>
   <thead>
      <tr><th>First Name</th><th>Last Name</th></tr>
   </thead>
   <tbody>
      <ac:macro ac:name="frevvoresolve">
        <tr><td>[FirstName]</td><td>[LastName]</td></tr>
      </ac:macro>
   </tbody>
</table>

Each frevvoresolve macro has a form field embedded in it by name. When the form is submitted, the content of the template will be resolved using the form data to generate the result Confluence page. In the example above there are three macros with form fields ClientName, FirstName and LastName. If the form was submitted with the value "Ford" in the Client Name field, the result Confluence page will contain the line.

This is the client information page for : Ford

First Name, Last Name etc. will also be resolved in a similar manner.

Here is a more complex example using the frevvoresolve macros in Confluence v4.0 to v4.2. This example also makes use of the three special frevvoresolve macro contents described below:

• form.attachment.links
• form.snapshot.link
• form.edit.link

<h3>Expense Report for : <ac:macro ac:name="frevvoresolve">[EmployeeName]</ac:macro></h3>
<table>
 <tbody>
  <tr><td>Misc Total</td><td><ac:macro ac:name="frevvoresolve">[MiscTotal]</ac:macro></td></tr>
  <tr><td>Travel Total</td><td><ac:macro ac:name="frevvoresolve">[TravelTotal]</ac:macro></td></tr>
  <tr><td>Meals Total</td><td><ac:macro ac:name="frevvoresolve">[MealsTotal]</ac:macro></td></tr>
  <tr><td>Mileage Expense Total</td><td><ac:macro ac:name="frevvoresolve">[MileageExpenseTotal]</ac:macro></td></tr>
  <tr><td>Miles Traveled Total</td><td><ac:macro ac:name="frevvoresolve">[MilesTraveledTotal]
</ac:macro></td></tr>
<tr><td>Grand Total</td><td><ac:macro ac:name="frevvoresolve">[GrandTotal]
</ac:macro></td></tr>
  
 </tbody>
</table>
 
<h4>Attachments</h4>
<ac:macro ac:name="frevvoresolve">[form.attachments.links]</ac:macro>

<h4>Snapshot</h4>
<ac:macro ac:name="frevvoresolve">[form.snapshot.link]</ac:macro>Here is the same example template using the frevvoresolve macro syntax required for Confluence v4.0 - 4.2:

<p><a href="<ac:macro ac:name="frevvoresolve">[form.edit.link]</ac:macro>">Click here</a> to edit this information </p>

The frevvoresolve macro syntax in Confluence v4.3 and 5.1 no longer requires Wiki markup. You can add the frevvoresolve macro via the macro browser. This video demonstrates how to create a template using the macro browser to add the frevvoresolve macros. You can find step by step instructions to create this template here.

The frevvoresolve macro has a new parameter (tablerow) that can be used when you add a frevvoresolve macro to a table. The default value of this parameter is false. If you set this parameter to true. each repeating control will go into a new row. See below for more details.

Macros and New Lines

The frevvoresolve macro will exactly resolve its content including new line characters. Be careful, especially when you are trying to merge submission data into an existing Confluence page. For example, if you want to generate a new table row for each form submission, you must make sure to put a new line in the content of the frevvoresolve macro as shown below.

The examples below show macros that display the attachments and form/workflow PDF snapshots on separate lines if you are using Confluence v4.0 - v4.2.

Edit Link

The special frevvoresolve macro body <form.edit.link> in Confluence v3.x and [form.edit.link] in Confluence versions v4.x and v5.1 will automatically generate a link that can be used to Edit the generated Confluence page using the original form. When the link is clicked by a user, the original form will be displayed initialized with the data from the most recent submission. The user can make edits as desired subject to the validation and other constraints imposed by the form and click Submit. The new values will be used to update the Confluence page.

In Confluence v5.1, you can use the macro browser to add a frevvoresolve macro to your template. Adding [form.edit.link] to the frevvoresolve macro will put the link to the submission data on your results page. If you want to make the link clickable, you can add html to the frevvoresolve macro in your template as shown in the example below: 

It will look like this on the Confluence page:

It is important to note that a form/workflow submission can be edited by any Confluence user using the Edit link from template. For Example, a workflow created with 2 activities A1 (employee) -> A2(manager), submitted by an employee, can be edited by any other employee by clicking the  "Edit" link generated through template. The workflow data can be edited and the workflow submitted again. This is as designed. 

Attachments

The special frevvoresolve macro body <form.attachments.links> in Confluence v3.x and [form.attachments.links] in Confluence v4.x and v5.1 will automatically generate links that can be used to view any attachments submitted with the form or workflow. When the link is clicked by the user, the attachment will be displayed or downloaded depending on its content type.

In Confluence v5.1, you can use the macro browser to add a frevvoresolve macro to your template. Adding [form.attachments.links] to the frevvoresolve macro in your template will put the attachment name in clickable links that allow the user to view them. Here is an example of a template using the form.attachments.links frevvoresolve macro body. Do not use an href tag with form.attachments.links as this will display confusing results on the Confluence page. Note the last letter of the words attachment and link is an "s" in the macro body name.

It will look like this on the Confluence page:

PDF Snapshot

The special frevvoresolve macro body <form.snapshot.link> in Confluence v3.x and [form.snapshot.link] in Confluence v4.xand v5.1 will automatically generate a link that can be used to view the PDF snapshot for a form or workflow. You must check the Save PDF checkbox in the Form/Workflow Designer. When the link is clicked by the user, the PDF will be displayed or downloaded depending on your browser. 

In Confluence v5.1, you can use the macro browser to add a frevvoresolve macro to your template. Adding [form.snapshot.link] to the frevvoresolve macro in your template will put a clickable link to the form pdf on the Confluence page. Here is an example of a template using the form.snapshot.link frevvoresolve macro body. Do not use an href tag with form.snapshot.link as this will display confusing results on the Confluence page.

It will look like this on the Confluence page:

Repeating Controls

Forms and workflows can have repeating data. For example, a person may have multiple nick names. Let's say you have a control on the form labeled Nick Name (as a reminder,  will automatically generate a name for this control without spaces NickName, (which you may edit) and a macro in your template.

Here is an example template using the frevvoresolve macros in Confluence v3.x:

{frevvoresolve}
| Nick Name | <NickName>{frevvoresolve}

Here is the same example template using the frevvoresolve macro syntax required for Confluence v4.0 - 4.2:

<table>
    <tbody>
        <ac:macro ac:name="frevvoresolve">
            <tr><td>Nick Name</td><td>[NickName]</td></tr>
        </ac:macro>
    </tbody>
</table>

If you submit the form with two nick names (Liz and Beth for example), the resulting Confluence page will contain the lines.

| Nick Name | Liz |
| Nick Name | Beth |

Repeating controls will generate one line per repeat item.

In Confluence versions 4.3.2 - 5.1, html syntax for tabular data display has changed in the case of 'repeats'. When you add a frevvoresolve macro in a table row, the macro now has a new parameter (tablerow). The default value for this parameter is false. If you leave the parameter set to false and merge the data to a Confluence page, the data will  accumulate in same cell. Here is an example of a Webinar Registration Results Page that uses a merge template that contains a table with frevvoresolve macros left at the default value. 

You must set this parameter to true for ALL frevvoresolve macros in your table if you want each repeating control to go into a new row. To set the parameter to true, click on the frevvoresolve macro in the table of your template, click edit, select true from the dropdown and click "Save".

Here is the Template for the Webinar Registration Form shown above with the frevvoresolve macros for the four fields set to true.

This merge template produces a Webinar Registration Results Page that looks like this:

When you merge to page, there will be an empty looking thin row generated at the bottom. This row cannot be removed at this time.

frevvotasks macro

You can access your pending workflow tasks and any saved forms directly from your Confluence page via the frevvotasks macro. See using the task list for details.

frevvosubs macro

Form submissions can be viewed directly in your Confluence page via the frevvosubs macro. See viewing form submissions for details.

frevvoattachments macro

Create/Update Confluence Pages

Please click here for detailed instructions on creating/updating Confluence pages via  and workflows.

Merge into existing Confluence Page

Please click here for detailed instructions for merging form/Workflow submissions into an existing Confluence page.

Workflows in Confluence

Please click here for detailed instructions for using workflows in Confluence.