...

You can collect location information by turning on ' Geo location feature and use it conjunction with rules to show longitude, latitude, accuracy and/or errors in your form. will always know it's current location and will submit that information when the form is completed. You can also get information about the area depending on the _get parameters that are used in the associated ruleassociated with your location. For example, a section of a Police Incident Report, shown in the image, collects the form position plus the address information associated with it.

Image RemovedImage Added

Latitude and Longitude display the coordinates of the user location. Accuracy represents the accuracy of the location in meters - a low Accuracy value means the position is more precise. You can display a position error code and the text description of error message in your form if desired. 

This feature works on a desktop or mobile devices. You may see slight differences in the behavior based on the browser you are using.

The option to turn on the Geo location feature is located in the middle section of the  Properties panel in the Form Designer. Select one of three options from the Geo location dropdown in the middle section of the Properties panel in the designer.

• None - (no location) - this is the default
• On Load - at start time
• Custom - allows the designer to specify a periodic refresh

You can turn on/modify the feature for all form activities by clicking on a form activity in a flow as well. which will display the form Properties panel.

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. 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 repository.

...