Geolocation field
The Geolocation field lets you record the location of the users, with their consent. You can view the recorded location in a Google Maps view embedded into the form. You can choose to record the user’s current location, set a constant location for all users, or let the users enter their location manually using the map.
Using the Geolocation field
You can find the Geolocation field under Advanced fields. Just like any other field, you can drag and drop the field into your form or click the Geolocation field, which automatically places the field in your form. You can edit the name, help text and make the field a required one, just like the other fields. You can also extract location values from these fields using formulas. Note that you can only add one geolocation field in a form, and geolocation fields are not supported inside Child tables and filters.
The Geolocation field uses Google Maps for recording the location of the users. Therefore, a Google Maps API key is required for the field to function. You can add the Google Maps API key in the Geolocation settings inside Account Administration.
Note:
Only Account Owners and Super Admins can access Account Administration. If you’re not one, contact your Super Admin to add a Google Maps API key.
Configuring the location type
You can modify the behavior of the field by choosing from the three options that let you configure different types of locations.
Current location
By choosing this option, you can configure the field to show the user’s current location by default. For this, the end-users should enable location access for Kissflow in their browsers. This is a non-editable field, therefore, end-users cannot modify their location. The user's location will only be saved upon submitting the form, and will not be saved if the user clicks Save, instead of Submit.
Preset location
By choosing this option, you can pick a location that will be shown to all the users and cannot be modified by them.
Custom location
By choosing this option, the user will be prompted to manually choose a location from the map.
Geolocation settings
You can add, edit or remove your Google Maps API key for the Geolocation field from the Geolocation settings. A Google Maps API key allows the Geolocation field in your form to access and use Google Maps. You can use an existing Google Maps API key or create a new one. To learn more about creating and using Google Maps API keys, click here.
Note
For the API key to work without glitches, please enable the following services in the Google Cloud Console: Maps JavaScript API, Places API, and Geocoding API.
Once you have your Google Maps API key, enter it in the field provided, and the system will validate the API key. If the API key entered is valid, you can proceed to save the settings by clicking Save, If the key is invalid, check the key for typos or enter another key. Note that after changes are made to the API Key, all users are required to reload Kissflow for the changes to take effect.
Note:
The usage of Google Maps API is subject to charges as per Google Cloud Platform pricing and the billing does not fall under Kissflow pricing.
FAQs
1. What are the various soft limits in Kissflow forms?
Ans) To improve performance and ensure efficient use of resources, Kissflow has put up the following restrictions on each form:
A maximum of 1000 fields per form.
A default soft limit of 10 child tables in every form.
A default soft limit of 100 columns per child table.
An upper limit of 5000 rows per child table.
An upper limit of 30 events per form (button fields not included).
2. Can I change field data types in a form with more than 5000 items?
Ans) You cannot change field data types in a form when there are more than 5000 records. This restriction is in place to prevent potential versioning issues when modifying data types for large forms. Changing data types for many values can lead to inconsistencies and performance problems.
3. Are there any field types in Kissflow forms that do not have soft limits?
Ans) Yes, certain field types in Kissflow forms are not subject to soft limits:
Rich text fields.
Grid fields.
Button fields (these have a separate soft limit of 100 buttons per form, in addition to the default form limit).
Rich text and Grid fields are exempt from restrictions as they don't contain metadata.
4. What happens if I duplicate a section with increased limits?
Ans) If a flow with increased limits is duplicated, the new flow will inherit the same incremented limits.
5. Will I receive any warnings when approaching these limits?
Ans) Yes, warnings will appear when you are close to reaching the limits. For example, when you have 990 fields and 90 columns, you will receive warnings indicating that you are approaching the limit and suggesting that you request an extension if needed.