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.
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.
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.
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?".
The Google Gadget option in the flow sharing list is not currently supported and will be removed in a future release.
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.
You will not see the public url listed in the Share light box.
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.
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.
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.