Latest Contributions by PiyaliKundu2

Hi @BigLouC - You can continue to leverage and integrate with Survey123 when using tasks with Field Maps. Tasks essentially allows you to add an integration link action to your task layout template (i.e., as a button) so it would operate in the same manner Workforce's integration with Survey123 did (i.e., a button to launch a survey). Furthermore, the nature of that survey can also be more dynamic, as the integration links in tasks can be configured with Arcade, and therefore, dynamically generated based on your other data/factors. In terms of differences in UI/workflows between Survey123 and Field Maps, there are still quite a few differences between the two. Field Maps supports Arcade, but not custom Javascript. So if your survey is pulling data from non-ArcGIS/third party sources, that could be a limitation. Field Maps's Arcade could pull data from other layers in the map or even feature services in the org (via FeatureSet functions), but not third party data sources. Field Maps does not support grid UI, and is vertical scrolling only. It does support grouping of questions in the editable form which can be expanded/contracted and that setting can be set as default. Field Maps currently does not yet have multiple-select question types; however, this is a feature we are working to implement in the future. Field Maps currently does not support graphical signature UI question types, which could be a legal requirement for some forms. The Field Maps UI cannot be custom colored. In terms of the "nested question", I would need to understand that a bit better. Can you provide a screenshot or configuration XLSForm? You can use Arcade calculations to copy answers between form inputs in the editable form. And you could use the new tasks capability's action buttons to copy data from even a related record to a parent feature, but there could be some limitations here depending on more nuances of the nature of your form. All-in-all, I imagine that Field Maps could easily replace Workforce in your situation, as being the means to view assigned tasks in a list, update the status of the task, and open a Survey123 survey. However, it's not clear yet to me if Field Maps could also replace Survey123 for your use case, and I would advise to initially keep the role of Survey123 as-is in your workflow until further testing and exploration could be done to identify any gaps or changes in functionality. In terms of location updates - yes, workers can either opt to share their location or be required to share their location in Field Maps when opening a map - similar to Workforce. The one current difference in sharing location between Workforce and Field Maps is that workers cannot yet share their work status (i.e., Working, On break, Offline) using location sharing in Field Maps. This is something else that is currently under development as we understand this could be an important feature in users workflows. I hope this helps! ... View more

Hi @SarahKendell -- Geofences are created when you first open the map or create the map area and enable Location Alerts/Location Sharing. The geofences are based off the current features (as defined in the Geofences configuration in Field Maps Designer). If you want to activate geofences off newly created features, then you will need to disable/re-enable Location Alerts. You can do so from the GPS Details bar located towards the top of your map. Tap the GPS Details bar, disable the Location Alerts switch, then switch it back on, and in the "Map Requires Location Alerts" dialog pane select "Turn on". ... View more