POST
|
Hello @BigLouC @ModernElectric - We understand that this experience with Workforce is frustrating and I will forward this BUG case to our product leads to consider. We are also in the process of releasing an enhanced version of Workforce called Tasks within Field Maps with our next mobile release this fall, both of which are built on the latest SDKs. Tasks will provide a far more improved experience and performance as it will be able to take advantage of both, the latest tech in the platform (e.g, view layers, Arcade, popup elements) and support a vastly simplified architecture which will allow users to configure and tailor tasks closer to their desired workflows (e.g., Status values, action buttons, symbology/labels/popups). You can learn more about tasks in our latest blog article, and also join our Early Adopter Program to help beta test tasks before it releases. We definitely encourage all Workforce users to give tasks a try and start checking out the capabilities early, and many Workforce users are already in the beta. We look forward to hearing your feedback about this new capability.
... View more
07-29-2025
09:07 AM
|
0
|
0
|
159
|
IDEA
|
Hello @Jesse - Thank you for sharing this idea. This is a known limitation of ArcGIS Workforce that is addressed with the new field tasks capability being developed in ArcGIS Field Maps. With Field Maps' field tasks capability, you will have more options on how your Decline button (which we call "actions") is configured. You would be able to hook up your Decline action to a single-select prompt with options you have configured. While Field Maps does not yet have select multiple-type form elements, that capability will be coming in the near future. We are excited to announce that field tasks is currently available in a public beta release via the Field Maps Early Adopter program! Please see the following blog for more details on the new task coordination capability and other exciting features coming soon to Field Maps: https://www.esri.com/arcgis-blog/products/field-maps/field-mobility/arcgis-field-maps-beta-is-here .
... View more
05-23-2025
06:07 AM
|
0
|
0
|
83
|
IDEA
|
Hello @ModernElectric - Thank you for submitting this idea. While we do not plan to support a separate Windows desktop application for Field Maps or Workforce at this time, I do think the new field tasks capability we are developing in Field Maps will provide more editing options. A map author will be able to enable a new or existing layer (or view layer) in a map with tasks, making the architecture greatly simplified as it only requires a single geometry-based feature layer in a map. Users with access to that layer and appropriate editing privileges (e.g., Organization Administrators, editors in a shared update group) would be able to edit the attributes of that task feature. Map authors can also leverage view layer filters to further refine which features should be visible to other users in this dispatching/response role. Since tasks run off of regular feature layers, they can be edited in a variety of ways and do not require a specialized dispatching app as Workforce did. As @AndyGeo mentioned above, some of the Solutions have tailored applications for managing and replying to requests (i.e., editing features). You can also configure specialized editing apps via Instant Apps, Experience Builder, Dashboard + Survey123 combinations, and other standard ArcGIS editing interfaces to create or edit the tasks. (For example, we highly recommend the Manager template as a easy and familiar UI for new or non-technical users.) If you truly needed a native desktop application, you could potentially use the following: Survey123 Windows app (using the Inbox capability to search and retrieve features), ArcGIS Pro combined with Pro's Tasks capability to have a streamlined editing experience, ArcGIS for Excel plugin can be used to visualize and edit records in a feature service in a spreadsheet. We are excited to announce that field tasks is currently available in a public beta release via the Field Maps Early Adopter program! Please see the following blog for more details on the new task coordination capability and other exciting features coming soon to Field Maps: https://www.esri.com/arcgis-blog/products/field-maps/field-mobility/arcgis-field-maps-beta-is-here .
... View more
05-22-2025
02:16 PM
|
0
|
0
|
141
|
IDEA
|
Hello @ModernElectric - Thank you for submitting this idea. It seems you would like a few enhancements to your workflows in Workforce, including: To be able to configure specific Status values and labels that better match your workflow and industry terminology, For other users with correct privileges (e.g., Administrators) to be able to interact with and change an assignment's status in the back office. Am I understanding these enhancement requests correctly? If so, I believe that the new field tasks capability we are developing in Field Maps will meet these requirements. Firstly, a map author will be able to enable a new or existing layer in a map with tasks, making the architecture greatly simplified as it only requires a single geometry-based feature layer in a map. As such, users who are given access to that layer and have the appropriate editing privileges (e.g., Organization Administrators, editors in a shared update group) would be able to edit the status of the task feature. Map authors can configure editing apps using Instant Apps, Experience Builder, and other standard ArcGIS editing interfaces to create or edit the tasks. The tasks capability can also be enabled on view layers, so map authors can leverage view layer filters as well to further refine which features should be visible to other users. Second, tasks will enable map authors to configure Status values and labels that better align with your workflows and industry standards. Map authors can configure the Status field to be string or numeric, can add however many status values they need, and can configure the value labels to fit your needs. We are excited to announce that field tasks is currently available in a public beta release via the Field Maps Early Adopter program! Please see the following blog for more details on the new task coordination capability and other exciting features coming soon to Field Maps: https://www.esri.com/arcgis-blog/products/field-maps/field-mobility/arcgis-field-maps-beta-is-here .
... View more
05-22-2025
01:53 PM
|
0
|
0
|
114
|
POST
|
Hello @ModernElectric,
My name is Piyali and I'm a Product Engineer on the Field Apps team, supporting ArcGIS Workforce. We're sorry to hear that you are experiencing these sync issues. Sync issues can occur for a number of different reasons, including underlying issues related to network, device, and data, so it would be great to better understand your specific implementation, workflows, devices, etc.
Have you been able to contact Esri Support and log a Tech Support Case as these sync issues are occurring? That would be the best first step so that we can gather these details and explore further and try to reproduce the issue on our end.
Thank you,
Piyali
... View more
12-03-2024
01:58 PM
|
0
|
0
|
581
|
POST
|
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
02-01-2023
09:06 AM
|
1
|
0
|
966
|
IDEA
|
Specifically label which basemaps are tiled basemaps and which ones are vector tiled basemaps upfront so they can be more easily distinguished. Currently, basemaps that are available in both tiled and vector tiled formats (e.g., Dark Gray Canvas, Light Gray Canvas) have the exact same label. The user must pick a basemap and test it to see which format it is. More specific labeling upfront will help save time and eliminate that step.
... View more
07-14-2017
08:24 AM
|
2
|
2
|
1293
|
IDEA
|
Specifically label which basemaps are tiled basemaps and which ones are vector tiled basemaps upfront so they can be more easily distinguished. Currently, basemaps that are available in both tiled and vector tiled formats (e.g., Dark Gray Canvas, Light Gray Canvas) have the exact same label. The user must pick a basemap and test it to see which format it is. More specific labeling upfront will help save time and eliminate that step.
... View more
07-14-2017
08:24 AM
|
2
|
2
|
1172
|
IDEA
|
The WAB Query widget does not allow the app administrator/DEVELOPER to disable the pop-up functionality within the WAB GUI configuration menu. Currently, the developer can control pop-up functionality from the map service or layer service; however, the Query widget creates a new temporary layer on-the-fly and adds it to the map, which cannot be controlled by the developer from these services. After the widget has run, the app USER can control whether the pop-up is enabled/disabled from the Layer List menu, but this is only after the widget is run and the setting resets every time the Query widget is run. For a web app that's intended to be used by the general public, the actual app USER may not be so tech-saavy, and will probably not think to disable pop-ups to streamline their own user experience. Even if they did, they may not know where to go to achieve this. This responsibility needs to be controlled by the DEVELOPER to streamline the overall user experience prior to app deployment. The overall concern is that the USER will run a query, click on a queried feature, see the duplicated pop-up (generated by the widget), and mistakenly think the app DEVELOPER is either intentionally/unintentionally duplicating features within the original feature layer (i.e., the layer that was queried). The USER likely won't realize that the duplicated pop-up is part of a new layer. (I have tried to encourage clients to configure the pop-up titles to add some explanation to differentiate the query layer pop-up from the original feature layer pop-up as a temporary workaround; however this still does not alleviate the awkward duplication of pop-ups.) It would be great if there were a setting within the Query widget configuration menu that allows the app/AGO developer to disable pop-ups for any layers generated by the widget (and can be done in WAB, so there is no coding required).
... View more
07-19-2016
11:07 AM
|
15
|
1
|
1417
|
IDEA
|
The WAB Query widget does not allow the app administrator/DEVELOPER to disable the pop-up functionality within the WAB GUI configuration menu. Currently, the developer can control pop-up functionality from the map service or layer service; however, the Query widget creates a new temporary layer on-the-fly and adds it to the map, which cannot be controlled by the developer from these services. After the widget has run, the app USER can control whether the pop-up is enabled/disabled from the Layer List menu, but this is only after the widget is run and the setting resets every time the Query widget is run. For a web app that's intended to be used by the general public, the actual app USER may not be so tech-saavy, and will probably not think to disable pop-ups to streamline their own user experience. Even if they did, they may not know where to go to achieve this. This responsibility needs to be controlled by the DEVELOPER to streamline the overall user experience prior to app deployment. The overall concern is that the USER will run a query, click on a queried feature, see the duplicated pop-up (generated by the widget), and mistakenly think the app DEVELOPER is either intentionally/unintentionally duplicating features within the original feature layer (i.e., the layer that was queried). The USER likely won't realize that the duplicated pop-up is part of a new layer. (I have tried to encourage clients to configure the pop-up titles to add some explanation to differentiate the query layer pop-up from the original feature layer pop-up as a temporary workaround; however this still does not alleviate the awkward duplication of pop-ups.) It would be great if there were a setting within the Query widget configuration menu that allows the app/AGO developer to disable pop-ups for any layers generated by the widget (and can be done in WAB, so there is no coding required).
... View more
07-19-2016
11:07 AM
|
15
|
1
|
1065
|
Title | Kudos | Posted |
---|---|---|
1 | 02-01-2023 09:06 AM | |
2 | 07-14-2017 08:24 AM | |
2 | 07-14-2017 08:24 AM | |
15 | 07-19-2016 11:07 AM | |
15 | 07-19-2016 11:07 AM |
Online Status |
Offline
|
Date Last Visited |
3 weeks ago
|