Live Forms v6.3 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 Mar 17, 2016
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 6 Current »

As forms are used, the values entered into form fields are cached on the  Server until the form is submitted. Each time you navigate a browser to a form URL, for example the URL you can copy/paste into a browser from the Email/Web Page share choice, you will see a blank form. That is, the form fields will be blank if you left them blank when you were designing the form in the Form Designer, or will have any default values you entered into the Form Designer. Also the form fields may contain values from your back-end systems if you used the Advanced Document URI feature.

If you close your browser window/tab and again open the form via the share URL, you will again get a blank form.

Another approach for minor changes is to make a copy of the form, make your changes in the copy, then migrate the changes to the original form. This minimizes the time period during which users may experience error conditions.

On this page:

Making Forms Public

The Visibility setting determines who can see and use a form, and whether other  users can access your forms. You can set this property on the Forms Home Page  or the Flows Home Page by clicking on the icon and filling out the Access Control screen.  You can also display the Access Control wizard by clicking the  icon located on the form/flow designer toolbar.

Sharing Forms

When you click the icon to share your form, you’ll see a Share Form page with five different options at the right. Three options (Embedded Form, Full Page/Pop Up and Just the iframe) are different ways to let users submit the form from your Web page without having to navigate elsewhere. These options have associated code on the left; this is for you to cut and paste into your Web page. Specific instructions for the code also are provided.

Be sure to use the Share icon in the Forms Designer when you want to share a form or add it to a web page. Do not use the browser URL you see when you're running or testing a form — this URL represents an ''instance'' of the form, not the actual form itself.

When you run or test a form, you'll notice that the browser URL includes a -extID parameter (for example, .../popupform?embed=true_extId=0.5427066243050674). This means that it's an in-memory instance of the form. You can use the _extID parameter yourself if you want to collaborate with others on an instance of a form. See the _extID topic for more information.

Share Link for Forms

Share Link for Flows

The two Link options give you a link to the form/flow. You can send the link in an email or publish it on your web page. 

Each option is discussed below. Remember to make your form public or users won’t be able to access the form no matter which method of sharing you choose.

  • Embedded Form – This is the easiest option. Simply copy and paste the code into your web page where you want the form to appear. takes care of the rest. This option will render the form on your Web page in its entirety, without requiring users to click scroll bars when using the form.  You cannot control the height nor the width that the form will use on your web page when embedded in this fashion. The length used by the form automatically resizes as repeats are added and sections expanded/collapsed or made visible/invisible. Refer to the EmbeddedForm/flowsonMobileDevices topic for the details regarding mobile devices.
  • Embedded Form Link – This option should be used to embed your form into a Portlet container. 
  • Full Page/Pop Up – This lets users access the form in its own pop-up window so users can complete the form and return to your Web page when they are done.
  • Link (Email/Web Page) – This lets you add a link to your form on your Web page or simply email the link to the people whom you want to submit your form. 
  • Just the iframe – This is similar to the Embedded Form option but requires you to specify your form’s width and height. In fact the script tag is the same except it has different form Url parameters. For instance Just the iframe option does not contain center=true, so the form will not be centered nor have a border. Using this option, the user may see scroll bars when they use your form if you do not specify a height long enough to contain the form when it is fully expanded. (Remember that your form can "grow" from its initial height if users select repeat items, expand sections that are initially collapsed, and so on.) The height and width are form properties but the height property generally is blank since the form sizes dynamically when you design it. There are a number of freeware tools (for example, MeasureIt) that you can use to measure your form’s height.
  • Raw Form Link – This lets you email a link to the form just as the Link (Email/Web Page) option does, but it is intended for filling out a form collaboratively and requires coordination between the parties filling out the form. The first person can fill out a portion of the form but must make sure '''not''' to submit it. He or she then can copy the URL (which will have been updated to collect the entered data) and mail this updated URL to the next collaborator. When this person accesses the URL, the form will be displayed with the values entered by the previous collaborator. The other difference between this option and the Link (Email/Web Page) option is that this option does not include an iframe border decoration.

Keep in mind that if you have shared your form via one of the link options and subsequently marked your form private, users will see an error message indicating that the "Access denied. Are you trying to access a private form / flow?".

Embedded Form/flows on Mobile Devices

The Embedded Form share link dynamically determines if it should embed an iframe for (desktop) or a link for (mobile). Using the Embedded Form share link on a mobile device, embeds a basic link in the page rather than an iframe, etc. The designer can customize it with Url parameters.

The relevant url parameters that may be appended to the share link are:

  • linkId - id to be applied to the rendered anchor (<a>) tag. If none supplied the id will be a generated unique id.
  • linkClass - a space delimited list of one or more classes to be applied to the rendered anchor (<a>) tag. This can be used by the third-party web page designer to style the tag/link.
  • linkTitle - any title text to be applied to the rendered anchor (<a>) tag. This will be seen as a tooltip when hovering with the mouse. If not supplied, then the form name will be used.
  • linkLabel - any text to be used as the link. If not supplied, then the form name will be used.
  • linkTarget - if set then the form will be opened in a new tab/window. Can be any text and is the name of the target window.
  • linkThumbnail - if set to 'true', then the form's thumbnail will shown as the link on the web page.
  • imgWidth - if linkThumbnail=true, then the width of the thumbnail image. Any css units are acceptable.
  • imgHeight - if linkThumbnail=true, then the height of the thumbnail image. Any css units are acceptable.
  • showLink - provides a way for the designer to force the rendering of the link or the form in a frame. If true, always show as a link. If false, always show as a form in a frame. If not set, then the system will automatically show as a link if on a mobile device and as a form in a frame otherwise.

 

Anonymous Access to Public Forms/Flows in Container Managed Tenants

If you are using a tenant configured for a container security manager and you want to allow anonymous access to your forms/flows, you must manually add "public" to the link to make forms/flows accessible to users who are not logged in.  You must do this if you are using any of the url types in the Share dialog for forms and flows, using a  Space or embedding forms/flows in your website. The public URL allows the tenant to be secured while public forms can be accessed anonymously, ex: a job application on an external website.   

Here is an example of a public url used to access a form in a container security managed tenant. The form/flow visibility is set to public via the  Access Control feature. Anonymous users will be able to access the form as the servlet container will ALLOW access to the frevvo.war and ' access control will ALLOW access to the form. Close/open your browser or copy/paste the public url into another browser when testing.

http://10.0.0.6:8082/frevvo/web/public/tn/ldcsm/user/nancy/app/_KOSm0eEAEeOF6Nc8pkcCvQ/formtype/_OeWt0OEAEeOF6Nc8pkcCvQ/popupform

 You will not see the public url listed in the Share light box.  

Browser Session Security

When you create a new form, by default it is marked as private. At this time the only person who can use the form via any of the form's share choices, is the person logged into this  account. Once you are ready to let others use your form you can mark the form as public. Now anyone that is given the form's Url via any of the form's share choices, has access to use and submit the form.

Private vs public appear to be a binary choice. Either no one has access unless you're logged into the  account or everyone has access without the need to login. Another way to make the form accessible is to leave the form locked and share it via browser session restricted access. The  API can generate form Urls that are only valid for the current browser session. The form Url generated in this way (not via the Share choices) cannot be passed to anyone outside of the session as it will not work

Embedding Forms in Your Website

 can easily be added into your existing web site. The option above in the Share section explain the code you need to copy into your web page and the different ways that the forms can be added to your site.

If your web server and  form server are in the same domain (in-house likely scenario), you are able to embed as many  forms into each of your .html web pages as you wish. In order to do this you must give each form a unique id. So if you copy the Share code into the web page a 2nd time, you must edit id to make them different from the 1st copy/paste. Id can be any string as long as it is unique.

<script xmlns=http://www.w3.org/1999/xhtml 
src="http://test.frevvo.com:80/frevvo/web/user/qaforms/app/_-PpqAeCSEdyckfEkZBXSmw/ 
formtype/_FUC50OCTEdyckfEkZBXSmw/embed?container=true&resize=true&id=form1" 
type="text/javascript" language="Javascript"></script> 
 
<script xmlns=http://www.w3.org/1999/xhtml 
src="http://test.frevvo.com:80/frevvo/web/user/qaforms/app/_-PpqAeCSEdyckfEkZBXSmw/ 
formtype/_FUC50OCTEdyckfEkZBXSmw/embed?container=true&resize=true&id=form2" 
type="text/javascript" language="Javascript"></script>

If you experience problems with your web page not resizing correctly to accommodate multiple embedded forms, try setting the height of the form manually. Open the form in the Forms Designer, click the Style tab in the Properties panel, and and type a value in pixels (for example, ''720px'', ''900px'', etc.) in the Height field to set the form height.</

Currently  does not support the ability to embed multiple  forms in a single .html web page iin a cross domain configuration. This is the SaaS scenario, where the  is hosted on www.frevvo.com and your web site is on another domain. In this scenario you currently can only embed a single form into each of your .html web pages.

For this version, embedding the task list successfully into an HTML page requires setting its width. See URL Parameters for more details. 

If you are using a tenant configured for a container security manager and you want to allow anonymous access to your forms/flows from your website, you must create a public URL.

 

 

  • No labels