Latest Contributions by CraigGillgrass

Jason, I don't have an update on the timeline for this, it is in our backlog, but we haven't assigned it to a release.  We have other work scheduled for Workforce that is ahead of this in the backlog. Your summary of what a worker would need to do to support this correct and the workaround for the time being. Craig ... View more

Hi Brent, Yes, I'd recommend removing them from all assignments (and optionally giving those assignments to another dispatcher) before removing them from the organization. Craig ... View more

Hi Jay, It is not possible to configure the assignments tab in Workforce.  However, there is a location text field that is populated based on x,y or the results of your geocoder when you click on the map to create the assignment.  This location text field can then be edited anyway you like. Craig ... View more

Keith, While this is currently technically possible, it will not be supported in future releases of Workforce. Craig ... View more

Keith, Yes, that should be possible. One thing to note, we do have it on our roadmap to support editing and display of non-workforce fields in the Assignments feature layer.  Not quite a related record approach, but that could meet your needs when that is implemented. Craig ... View more

Hi Keith, Unfortunately, neither of these requests (Tracking Costs and Activities Associated with Workforce Work Orders) are on the roadmap for Workforce.  We've decided that these are outside of our current product plan for Workforce.  We have several Business Partners who offer solutions that do tailor to solving these requirements. With respect to adding the ability for Workforce to edit related tables, this is also not on our roadmap. We don't have any plans to extend the assignments feature layer to support related tables. If we do consider this to satisfy a use case, then that would provide the opportunity to add that ability. thanks, Craig ... View more

Hello, Can you try accessing the web app at "https://workforce.arcgis.com"? Make sure to use the https protocol. Craig ... View more

Thanks Jeff, unfortunately, there really is no easy to support/solve this issue at this time. The integration workflow between Workforce and launching other apps is targeted at the creation of new data.  Adding the ability to open existing data (features or surveys) is in our roadmap, but hasn't been assigned to a release. Craig ... View more

Jeff, The surveys that you want to assign to the Inspector to open in Survey123, are these new surveys or are they pre-existing surveys? From reading you reply, I think these are pre-existing surveys but would like to confirm. Craig ... View more

Jeff, This blog outlines one way you can handle this scenario: Workforce and Survey123: Creating assignments in the field  Another, is to add the Survey123 feature service to the Dispatcher web map, so that your Dispatchers can create assignments from the features in Survey123.  However, with this workflow, it's not as easy to just get the information from Survey123 into Workforce. Craig ... View more

Hi Brent setting to the worker to null/empty for the departing worker though not ideal should probably work for us Good to hear - let me know if you run into issues we could probably calculate the worker name into a the notes field That is one technique I've seen used - it could work well here. I do continue to worry about the ramifications of workers from outside of our agency accounts getting deactivated. Understood, we'll look at this again and see if we can reproduce the issue. ... View more

Brent,  I'm afraid to say that isn't supported at this time.  While you can remove the named users from your organization, if they're removed from the Workforce project prior to removing them from the organization, you'll receive error messages indicating there is a problem.  I don't think you want to go this route, it's going to be disruptive to Dispatchers. Another alternative; to remove the association between completed assignments and workers being removed.  This will involve set the assignments.workerId field to null/empty and ensuring the workers you want to remove from the project are not associated with any assignments.  You won't see who was assigned the work. Neither of these are great options, and speak to the fact that we don't support this workflow.  It may help to outline why you need to maintain the completed assignments in the Workforce project.  I may have another alternative based on your use case. Craig ... View more

Brent, When you mention "...while maintaining their completed assignments within Workforce?" - do you also need to maintain an association with the worker who completed the work?  Another way to ask this is - when viewing the completed assignment information in the Dispatcher web app, do you need to see the worker information associated with the assignment? Craig ... View more