You can change the behavior of your forms by adding URL parameters to the form URLs found in the various share choices. These URL parameters are each described in detail below. Here are the parameters that work for each share choice. You can think of the code you get via the Share Form page as a starting point. Then you can change the behavior to whatever you need by adding, subtracting and modifying the URL parameters in the share code.

Forms created via the API createInstance method are form instances. They are an actual form to be used by a specific user in memory on the Server. Please see Data API for a list of the parameters that can be used with form instance URLs.  

 On This Page:

Parameter Separators in URLS

If you are appending parameters to a URL, use the ? for separating the form/workflow URL from the parameters and use the & to separate parameters from each other. For example, let's say you want to append the Pacific timezone parameter to the share URL of your form/workflow.

Here is an example using the Link(Email/Web page) URL for a workflow:

Add ?_formTz=America/Los_Angeles to the URL. Use the ? since there are no existing parameters appended.

Here is an example using the Raw Workflow URL for the same workflow:

Add &_formTz=America/Los_Angeles after the last existing paremeter. Use the & since you are separating parameters from each other.

Raw form link

Embedded form link -- "Just the iframe" and "Embedded Form"

Embedding the task list successfully into an HTML page requires setting its width. You must explicitly add %26tasks-width=XXXpx where XXX is the width that you want. Here is an example:

<script>  src="http://localhost:8080/frevvo/web/embed?resize=true&container=true&border=false&URL=http://localhost:8080/frevvo/web/tn/<your tenant name>/subject/{} /tasks%3fembed=true%26container=true%26resize=true%26tasks-width=1000px"


Popup form links – "Full Page Popup" and "Link (Email/Web page)"


When you open a new form via, for example, the Link (Email/Web Page) share URL,  you will always open a new form instance. As you use the form and enter values into the form, the values are immediately cached on the Form Server as you tab to the next form field. If you close the browser tab/window containing the form prior to submitting the form, the Form Server still retains this form instance. By using the special (reserverd) URL parameter called _extId, it is possible to reconnect to an in-memory form instance.

Access to form instance is secure.The form instance cannot be accessed from a different browser or a different device. For Example, if you use the same _extID value in a different browser or on a different device, the form will not load the same instance (i.e the same values filled in the form fields) even if you are logged into  as the same user.

To utilize this feature, try this example:

_formActionUrl, _formActionMethod, _formActionTarget

The Form Action can be overridden by using these special (reserverd) Url parameters. The presence of _formActionURL overrides any Form Action in the Form Designer by specifying which Url to go to when the form gets submitted.

_formActionMethod is optional and can be set to either "get" or "post". If unspecified it defaults to "get" causing the user to get forwarded to this web page when the form is submitted. If set to "post" it will also post the data to this Url.

_formActionTarget is optional and only taken into account when _formActionUrl is specified. It can be set to one of the values: frame, parent, top (lower case). It defaults to frame if not specified.

When the _formActionUrl parameter is set but no Url is given (i.e. ...&_formActionUrl =&embed=...) the top frame will be closed. 

For example... the share Url with &_formActionUrl=, will cause the form to display when it's submitted, even if in the Form Designer you had set the Form Action to be "Display Message" or one of the other options. 

_formActionUrl params are used directly by  to re-direct the browser. When the _formActionUrl (or any parameter)  is received, it is url decoded by the servlet container. Therefore, it is best practice to encode the _formActionUrl paramater value. It is up to the  client to encode passed in _formActionUrls.

_errorActionUrl and _errorActionTarget

Similar to above, these parameters determine what happen if there is an error when submitting the form.

_errorActionUrl overrides any Form Action: Error setting in the Form Designer by specifying which URL to go to when there is an error submitting the form. _errorActionTarget is optional and only taken into account when _errorActionUrl is specified. It can be set to one of the values: frame, parent, top (lower case). It defaults to frame if not specified.


The designer can override the standard message that displays when the user clicks on the Cancel button in a form and redirect them to a webpage of your choice by appending the _cancelUrl=(some Url) to the raw form link. For example, if you want to redirect users to the raw form link should look like this:

The user must click "Yes" for the warning message "Are you sure?" and then will be directed to the specified Url.

Setting _cancelUrl= to blank closes the target window or tab if it was opened by javascript or <a target="new"…/>. Otherwise it will simply show a blank page.