| Section | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
When your form loads it will send a page view event to your Google Analytics account if you enter your Google account tracking ID into this form property. Please refer to the Google documentation for finding your Google Analytics tracking ID.
Deployment
...
Tracking Url
This property works in conjunction with the Tracking ID and was intended to make it easier to read the long URL's when trying to determine which form/flow is being tracked using Gloogle Analytics. Full functionality will be available in a future release. Please contact Customer Support for the latest information on this feature. Tracking Url is not available for flows at this time.
Deployment
This field lets you toggle a form between two states: PRODUCTION and DEVELOPMENT. When a form is in the development state it contains a watermark. Deploying the form into the production state removes the watermark.
You can change the state of your form from the deployment dropdown or you can click on the deployed/undeployed button on the forms home page.
See the Administrator's Guide Deployment State topic related topic.
Geo
...
Location
You can capture the location where your form was filled in by turning on ' Geo location feature. A forms knows it's current location and will submit that information when the form is completed. uses the HTML5 GeoLocation api. The geo api is well supported on tablet, phone and recent laptop/desktop browser versions. This feature works on a desktop or any GPS capable mobile device.
...
The Geo Location feature works in conjunction with rules that use the the form.positionUpdated identifier. You can set up the rule to execute every time the position is updated. See Business Rules for examples of rules that will do this. Also see Rules Position Data for the complete list of available build-in data.
You can also collect additional information associated with your location. For example, a section of a Police Incident Report, shown in the image, captures the location where the form was filled in plus the address information associated with it. The last position update will be in the submission metadata of your form or flow but it is NOT automatically added to the XML Document. You must create controls (perhaps hidden) and rules to add the location information to the form XML document. The Position Address section of the Police Incident Report has controls and rules to show longitude, latitude, accuracy and/or errors plus the address information.
...
You can also turn on/off/modify the feature by clicking on a form activity in a flow which will display the form Properties panel. The Loc Timeout is the amount of time in seconds the location finder in the browser will search to find the location before it times out. The default value is 5 seconds. To capture additional information based on the location via a Business Rule or to embed a Google map in your form. you need a connection to google.com and you must check the Detailed Loc. checkbox on the Properties panel. You will need to put a message control in your form where you want the map to display. Type f-map-div in the css class field on the message control Properties panel. This is a built in java script that cannot be edited to display the map.
...
Key/Saved Fields Setup
This setting controls which fields are saved to the built-in submissions repository. By default, all your data is saved as an XML document. This is the most efficient way to store/access your data both in terms of speed as well as storage. However, if you prefer to view your data via the submissions user interface, you can choose which fields are saved in addition to the XML data. See submissions data for more information on making this choice. Note that this could incur significant performance overhead and will also consume additional storage in the repositoryyou want the map to display. Type f-map-div in the css class field on the message control Properties panel. This is a built in java script that cannot be edited to display the map.
The map will only display in use mode.
Setup Key/Saved Fields
This setting controls which fields are saved to the built-in submissions repository. By default, all your data is saved as an XML document. This is the most efficient way to store/access your data both in terms of speed as well as storage. However, if you prefer to view your data via the submissions user interface, you can choose which fields are saved in addition to the XML data.
Considerations when deciding which types of fields to configure are listed below.
- Key fields are indexed for easy search of Submissions. You will see the controls designated as Key fields in the Submissions table. This is helpful when trying to locate a particular submission from a long list. Key fields do not affect performance. They are not downloaded when exporting your submissions to Excel.
- Saved fields do affect performance as they are independently stored in addition to XML data. This can significantly reduce performance, especially for large forms and require additional storage in the repository. Saved fields are not rendered in the submission table and cannot be used as search criteria for submissions. Saved fields are downloaded to Excel.
Clicking on the Click to setup Key/Saved Fields link displays the setup wizard. This link is on the form's properties as shown below. If you have navigated away from the form's properties and instead see a control properties panel, just click anywhere on the toolbar to return to the form's properties.
The wizard displays the fields from your form. Only controls that are considered form data will be listed. For Example, the link, signature, image, upload, trigger, section, PageBreak, Message, Form Viewer and video controls will not show up in the saved or key field lists as there is no value to save or query against. Also, group controls (tabs, panels, repeats) will not show up on the list of Available Fields.
...
- Drag and Drop - You can drag the fields from the Available Fields list and drop them into the Saved Fields lists if you re using Firefox, Chrome or Safari browsers. Items may be dragged between lists and within the saved fields list. Items may be dropped between existing items and before the top-most item and below the bottom item. Only a single item may be draggeditem and below the bottom item. Only a single item may be dragged. You can change the order of the Available Fields list if you are using Chrome or Safari bowsers. Currently, the drag and drop function will not work in the Internet Explorer browsers. This issue will be addressed in a future release.
- Center arrow buttons - IE 8/9 users must use the arrow buttons to move selected fields between the Available or Saved Fields lists or to reorder them by moving back and forth as necessary. The arrow buttons always add items to the bottom of the list.
- The > right arrow moves the selected field from the Available Fields list to the bottom of the Saved Fields list.
- The < left arrow moves the selected field from the Saved Fields list to the bottom of the Available Fields list.
- The >> double right arrows move all the form fields in the Available Fields list to the Saved Fields list.
- The << double left arrow moves all the form fields in the Saved Fields list to the Available Fields list.
The image below shows a selected field in the available list ready to be moved to the saved list via drag and drop or arrows. Click Finish to save the changes. Selecting the X in the upper right corner cancels any changes. Remember to save your changes when you exit out of the designer. Saved Fields are stored in the database when the form/flow is completed. The fields you select will be displayed in the Submission Detail for each submission. You can also search the submissions repository for these fields using the API.
| Info |
|---|
If Controls are listed in the Available and Saved Lists using control labels. If you change the label or the name of label of a control in your form and it was that was previously added to the Saved Fields list the control will remain in the Saved List reflecting the new label/name. Control labels are used to populate the Avialble Fields list. In a . In a flow, the label can be different in different activities for controls with the same data element ( name ). The control name (document element name) is used in this casein different activities. Controls are listed using the control name. If the name changes, it will unset the saved field. The newly renamed control will now show on the Available list . The and the designer must move it to the Saved List again. |
...
Let's say you set up the Saved Fields in a Product Order Form as shown below:
...
This feature helps to protect your forms against spamming by automatic submitters. By selecting captcha, an image is displayed when a user submits your form, containing a string and also an audio recording. The user must enter the string into the specified input box. If the string is correctly reproduced, the form submission will be processed as usual. If it is not a new string is displayed and the user may try again. Click on the 
to cancel.
Save/Load
This feature is only available to users with tenant accounts. If you check this checkbox a save 
icon will be displayed at the top of your form. If you don’t want users to be able to save/load your form, uncheck the checkbox so users will not see this icon.
...
If this checkbox is unchecked, tasks for the form or flow will not appear in [[V4_Tasks_Home_Page#Search_History | Task History searches]] Task List Searches. If you want them to appear, make sure this box is checked. Checking or Un-checking it affects all tasks including ones that were created prior to the action.
...
This property is currently ineffective for tenants with the default delegating security manager. However the delegating security manager may support SSO in the future.