Live Forms v5.1 is no longer supported. Click here for information about upgrading to our latest GA Release.

Skip to end of metadata
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 43 Next »


The forms home page appears after you create and edit an application.

On This Page:

 

You won't see any forms the first time you use , but as you soon as you create some you'll see them here. Forms are single page forms. There are three icons at the top of the forms home page. Each is described below.

  • Click the  icon to create a new form. Once you have created some forms, the forms will be displayed based on the creation date with the oldest form on top. You cannot change this default sort order.
  • Click the  icon to upload a form zipfile previously downloaded to disk.
  • Click the  icon to edit the application properties.

To the right of each form name are five icons. Each is described below.

  • Click the icon to attach a thumbnail icon to your form. You can select one of the icons provided by  or you can upload your own. The icons will display on the iPhone and iPad mobile devices. See the Mobile Forms tutorial for more information.
  • Click the  icon to create/edit an Access Control List for a form. The Access Control List is a way to allow other users access to various functions of a form such as submissions. See Shared Items for further details.
  • Click the  icon to internationalize a form with translations in different languages.
  • Click the  icon to publish your form as a template that you can use when creating other new forms. See Templates.
  • The next icon controls the Visibility of the form and functions as a 3-way toggle. The  icon tells you that your form is a private form, meaning only you (the owner) can edit, test or use it. Clicking this icon once will change it to this  icon and make the form usable by anyone who has an account (username/password) and is logged in to your tenant. Clicking the icon again will change it to this  icon and make the form public so anyone can use it even if they are not logged in. If the form is public, clicking the icon will make it private.
  • Click the  icon to delete the form. Keep in mind there is no Undo feature so this action is permanent. 

Deleting a form also deletes all associated form submissions and any saved in-process form instances. See replacing forms.

Below each form name are eight more icons. Each is described below.

  • Click the  icon to open your form and edit it in the Forms Designer.
  • Click the  icon to test your form. See Testing Forms.
  • Click the  to make a copy of your form. The newly copied form will be independent from the original; any changes you make to the copy won’t affect the original and vice versa. Since the newly copied form will be your most recently created form, it will appear at the bottom of your list of forms. 
  • Click the  icon to download the automatically generated schema associated with your form. This schema will contain all the controls added to your form from the Palette ControlsPalette Controls. This will not contain controls added to your form from your own schemas. See Schemas for more details.
  • Click the  icon to download a zipped version of the form to disk. A single zip file will be created with the name of your form, followed by _form.zip. This icon also appears on the Applications home page so you can zip your entire application, including all the forms it contains. The zip file name will be the name of your application, followed by _app.zip.
  • Click the  icon to share your forms in a number of different ways. Before you click this remember to mark your form public or you will not be able to share it with others. See Sharing Forms.
  • Click the  icon to view the submissions for this form.
  • Click the  icon to deploy a form to Production state and remove the Development watermark. This toggles the icon to the  undeploy icon. If your form server license enables a limited number of Production forms you will get an error message when you hit your license production form limit.
  • Click the  icon to undeploy a form and move it from the Production state back to the Development state.

Production Forms

New forms have a default deployment state of either Production or Development. The  icon on each form toggles this state. Forms in the Development state have a watermark. Change them to Production to remove the watermark. Your license key controls the number of forms that can be set to Production.

The deployment state defaults to Development irrespective of the default deployment state set by your license key and by your tenant admin for the following scenarios:

  • When a form is uploaded into your application from disk
  • When you make a copy of your form
  • When you create a new form from a form template other than the default template

To manage production forms go to your My Account -> Manage Production forms page. See managing production forms for more information

Deleting Forms

When you delete a form, by clicking the  icon the form is permanently removed and cannot be restored. The delete operation also deletes all submissions from ' submission repository and any saved in process form instances.

Before deleting you may wish to download a copy of the form to disk by clicking the  download icon. Click here for information on deleting applications and here for deleting flows.

Uploading/Replacing Forms

If your goal is to update your form to a new version that you had previously downloaded to disk or to revert to an older version previously downloaded to disk, do not first delete the form since, as stated, this removes all associated saved/submitted/pending form instances. Instead leave the original as it is and upload the version from disk by clicking the  upload icon. A dialog will display that lets you browse to the form on disk and give you the option of replacing the current with this new version. Checking the option to ignore XML schemas in the form being uploaded if those schemas already exist in the application, results in the existing schemas being used. 


 

 

  • No labels