Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

On this page:


  1. Default values entered when the form was created in the Form Designer
  2. Values from an XML document(s) sent in the Post request for the form or OnInit.
  3. URL parameters appended to the form URL via the frevvo _data URL parameter
  4. Values retrieved as the form loads from any Document URIs
  5. Default values set via Business Rules as the form loads and during use. See Setting default values in rules and using REST Services in Rules for further details.


titleClick here for a quick refresher about adding URL parameters

If you are appending parameters to a URL, use a ? 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.

Code Block

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

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

Code Block



Certain characters such as % need to be URL encoded. The website describes in detail the reason certain characters must be encoded when used in URLs. And it also contains a tool that lets you enter your string and converts it to a properly encoded string. For example if your value is '% complete' this must be written as '%25 complete'.

The single and double quote characters themselves must be escaped with the  escape the frevvo escape character '!'. For example, the string 'Nancy's Horse' must be written as 'Nancy!'s Horse'. If the '!' is missing from the string the apostrophe will be mistaken as the end-of-string character.



When you initialize controls with Date or Time values, they will always display the exact value passed. However, the Date/Time control is time zone dependent, and will behave differently depending on how the time zone is provided:

  • If the time zone is provided in the Date/Time value, the value will be converted to the timezone of the browser and displayed in the form accordingly. The time for the Date/Time control is proceeded by a capital "T" (Time Zone) and followed by a "Z" (UTC timezone,) such as '2021-08-20T11:13:00Z'.
  • If the time zone is provided in the URL using the _formTz parameter, the Date/Time value will be converted to and displayed in the time zone specified in the parameter. This will also override the browser time zone.
  • If the time zone is not provided using either method, you will see a parsing error such as "Error: The most likely reason in a syntax error in _data." This applies to Date/Time controls only.


Successful initialization cannot be guaranteed if the time zone for a Date/Time control is not provided (either in the XML document or in the _formTz URL Parameter). This does not apply if your form only has Date and/or Time controls.

Here is an example of a URL that initializes a date only, time only, and date/time control. Notice that the Date/Time value does not have a 'Z' or another timezone indicator, but the appended &_formTz parameter supplies the timezone, America/New York.

Code Block,OrderTime:'11:13',OrderDateAndTime:'2021-08-20T11:13:00')&_formTz=America/New_York

The local time will be converted to and saved in a valid UTC format for the time portion of the date/time control in the submission XML document. You may see the time in UTC format with a trailing "Z" (UTC) time or the time value plus or minus the UTC offset. See Initializing Forms with XML Documents and Viewing XML Documents for further information.


The onSubmit function allows you to copy the data from the frevvo form (when that frevvo form is submitted) into your HTML form. Then you can use your own JavaScript on your HTML page to process that data (for example save it somewhere else at your own convenience and time, etc.)

The embedding page and must frevvo must be in the same domain/origin. Typically this means the same URI scheme, host, and port.

The value of onInit must be an in-scope javascript function. This onInit javascript function will be called before the form is instantiated. For example &onInit=getData will cause  to frevvo to call the getData() javascript function. The onSubmit function will be called after the submit button is clicked.

Here is a sample HTML page an embedded  script frevvo script tag and an onInit javascript function. The  script frevvo script tag copied was from the Share dialog and the &onInit Url parameter was appended. Each XML document is placed inside a container element (input, textarea, or any other element such as a div) and assigned an XML id. In this example there is a single XML document placed inside a <textarea> tag.


  1. The Url parameter &onInit=getData used matches exactly the name of a javascript method in the html page also named getData(). 
  2. The xml data is also embedded in the html page in the <textarea> tag.
  3. The <ns:form> content came directly from a prior form submission and was copied out of the  submission frevvo submission repository's Documents tab.


This is how the form looks when initialized via the onInit method. The particular form used in this sample has a repeat control. By default, this form has a single repeating item. When  initializes frevvo initializes the form with repeating data returned from the getData() method it auto creates the additional items. This form also contained an Item Added Rule which is why there is also a value in the Quantity field.