Latest Contributions by JakeMatthys

Hello, We recently released a Workforce Project into a production environment for utility inspections and the two most frequent requests that we are getting from the users are the following. Add a filter that allows that allows users of the worker app to be able to only view those assignments that are due today.  This filter already exists in the dispatcher app, but the workers would like this ability as well.  Maybe this is something that could be applied in the To Do/Completed filter choice list Add the ability to sort by due date in either ascending or descending order.  Currently the default is ascending, but having an option for descending would be helpful for our users. Thanks,  - Jake ... View more

As our organization begins to increasingly utilize Survey 123 for data collection, I would like ask about the vision that ESRI has for Survey 123 schema changes.  Currently a schema change means that existing data, associated with the survey undergoing a schema change, will be lost.  In the future do you envision the ability to add questions to a survey and re-publishing that survey without losing the existing data stored in the cloud?  Currently we replicate our Survey data down to our enterprise database, but we have had discussions about using the Survey 123 feature layer as our permanent storage, but we do not want that to prevent us from making survey schema changes (adding a question here or there as business needs arise).  - Jake ... View more

I have a survey which has some required fields, the survey also has a number of repeaters and these repeaters also have required fields.  The form has a multi select and each repeating option is relevant to the multi select.  So if the user selects 3 items, lets say pipes, valves and hydrants, the user will get 3 repeating sections to populate.  We are experiencing an issue where the required fields are enforced in the first repeater, but is not enforced in subsequent repeaters.  In the first repeater, if all required fields are populated, the form can be submitted, if not, the form identifies the required field that needs populated.  This holds true for all repeat occurrences within that first repeater.  In the subsequent repeaters the required fields are not validated by the UI.  What we are finding is that as long as the user has populated all the required fields in the main form and in the first repeating section, required fields that have not been populated in subsequent repeater sections are submitted by the form.  I would expect the form to not submit and to warn the user that required fields have not been populated.   Has anyone else experienced this issue?  I have uploaded the excel form document if anyone would like to take a look. Thanks,  - Jake ... View more

I made a schema and form change to an existing survey (added a new column) and published this change.  I was expecting the typical warning that the schema will change and data will be lost, but instead I got the 'Survey will be published without affecting existing data'.  I published the survey and then investigated the results.  I noticed that the form had a new timestamp, but the feature layer did not. When testing the form contains the new question and input, and submits successfully to the feature layer, but the new data does not have a column in the feature layer, so that data does not get captured.   How did I get the form and feature layer out of sync?  I have experienced this issue with other surveys in the past few days, is this an issue with my management of the surveys or a known bug? Thanks for any input.  - Jake ... View more

Is it possible to create hidden question types with default values?  I have tried this in a survey, but when the survey is submitted and I review the data from the rest endpoint, the hidden question contains a null value rather than the default value.  Am I doing something incorrect? ... View more

Our organization would like the ability for a worker to create their own work assignments as well as the ability to distribute their own assignments that are assigned to them while using the Workforce worker mobile application.  The use case for this request is that we have inspectors that arrive on site to perform a Workforce Assignment.  While on-site the contractor asks the inspector to perform an unrelated inspection.  Rather than the worker calling into the dispatcher and waiting for the dispatcher to create a new assignment, the worker would like the ability to create the assignment in the field and self-assign.  Our use case for a worker to redistribute or assign out their own work, is that we have field workers that often need to redistribute their work load throughout the day as work demands change. It would be helpful if a field worker can re-distribute their own work. Our thought is that this could be a new role, maybe a crew leader role, that can create their own work and re-assign work that is in their queue.  This role would not be able to create work of others or re-distribute others work, that would still be reserved for the dispatcher. ... View more

We think that it would be great if the 'Provide Feedback' email link in the worker mobile device application could be configurable so that an alternative email could be substituted for the workforce4arcgis@esri.com email that currently exists.  Our justification for this request is that our GIS staff would like to receive and review any feedback emails that the field staff sends before they are sent to an ESRI inbox.  Our worry is that issues that are training or workflow related will be sent to ESRI rather than to our GIS team.  If the field users truly has an error with the system or the wants to provide feedback to the Workforce team, our GIS team can convey that information to the ESRI Workforce team. Thanks, - Jake ... View more