nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Configure additional fields to pass to Survey123 from Workforce

AnthonyRyanEQL

i would like to see the functionality of configuring additional fields (eg. workorderid) to pass to Survey123 (eg. custom url) when setting up assignment types to surveys. This would allow a relationship between assignment & survey to be established. I want to use workforce to manage external contractor works with survey123 for asset inspections but is difficult without a relationship to do further analysis (eg. was the survey done/which asset was missed, etc.)

Thanks

Find more posts tagged with

Implemented

Status: Implemented

Comments

unknown

Survey 123 is not having the capability to create a specific integer field . I need to transfer an integer value to Survey 123 app from Workforce . I guess Survey is lacking creation of integer field , rather selecting the number field its creating the double type .

Do we have any fix to this @CraigGillgrass ?

cgillgrass

Hello,

With the Workforce release that is happening tonight we will be adding the ability to pass any field to any of the apps such as Survey123, Collector or Field Maps.

Please let me know if you see any issues with this.

thanks,

Craig Gillgrass

esri

cgillgrass

Hello,

The new version of Workforce has removed this abilaity. Without this functionality we cannot continue to use Workforce for our needs.

This is still supported and possible in the new version of Workforce and is available by editing the Assignment Integrations table in the workforce feature service.

The ability to add additional fields to the assignments layer is something we are planning to do - and are planning to include it after Workforce moves into the new Field Maps app.

Craig

Tweed_ShireAdmin

We would love this functionality. We have before using the Classic Workforce accessed the JSON to add in additional URLParmeters to pass from the assignments layer to SURVEY 123. The new version of Workforce has removed this abilaity. Without this functionality we cannot continue to use Workforce for our needs.

AnthonyWhitley

We are in the same position; lack of field transference has put our project on hold and possibly looking elsewhere.

se2539

I'm glad I'm not the only one who like to have a list of questions/fields that a worker and/or dispatcher would fill out at the beginning of an assignment and then get automatically transferred to Survery123. We currently have a small pilot project going on for a particular department and this limitation is a hold up; without this functionality I am not sure we can proceed going the 'paperless' route.

NicoleKwan

It would be nice if there was a list of questions/fields that a worker would answer in the beginning of the day/assignment that gets passed onto Survey123 fields. For example, capturing what equipment the worker is using. Instead of entering it into each survey that day, it would mostly be the same equipment that day, autofilled but changeable if the worker needs to change equipment. A configurable list of fields would be much better than ESRI trying to figure out which fields (I understand GLobalID, ID, Location is set up) should be linked.

erica_poisson

It would be nice if the Survey123 custom URL scheme was honored in the "Workers" web map so that attributes from a feature layer (generated from a GeoForm), could be passed into the Survey that is integrated with Workforce. It would provide a significant time savings.

cgillgrass

thanks Tiffany, this helps to understand the use cases for each of the fields.

Passing the GlobalID is definitely on our short term list. Passing Assignment Type information may be something we don't get to right away.

TiffanyRufo

1. Would like to pass the name of the assignment type for readability in printed reports.

2. Assigned on date ( that way we could see the date it was assigned and the date it was completed)

3. This can be disregarded in our use case. Editor tracking can tell us who filled out the survey

4. Either of the three could work: just would like some kind of unique identifier to tie the survey back to.

Hope this helps inform the workflow, Thank you for listening to all of our feedback!

cgillgrass

Hi Tiffany,

A couple questions on the fields you've listed as being important to send to Survey123:

For assignment type; this is an integer field with a coded value domain. Do you want to pass the integer value or the name of the assignment type?

For assignment date, is this the Creation Date, Assigned On Date, or Due Date?

For the assigned field worker; the Workforce schema is normalized, so the workerId field in the assignment feature service is a foreign key to the worker feature service. Would passing the workerId help? If so, how?

Finally, for assignment number, is this the ObjectID, GlobalID or Work Order ID of the assignment?

dick_e_IEHP‌ and anthony.ryan_ergon‌ please feel free to comment as well with your scenarios.

The next release of Workforce, which we're currently working and moving into release certification, will have the ability to pass Work Order ID and/or Location text to Collector and Survey123. We're planning out what other fields to add and when, so this information will be very helpful.

thanks for your feedback on Workforce.

AnthonyRyanEQL

Gianni,

Thanks for the reply but this has clouded my idea. My idea still stands to add the ability to pass parameters to a survey. During the configuring process of assigning a survey123 survey to a workforce assignment_type, allow the user to select which fields from the workforce assignment can be passed to allow pre population of survey fields (eg. workorderid) to enable a linkage between scheduled work & condition assessment, etc. for future analysis, etc.

i'm not after anything complicated, just fields being pre populated of a particular survey as defined by the assignment_type configuration.

i have seen the workforce project json configuration by using ago_assistant tool and know it could be hacked by altering the custom URL scheme for the particular assignment_type but this shouldn't be the way to do it and it would be considered unsupported.

Thanks

GianniCampanile

Hi Anthony,

as far as I know the URL scheme can be used only to pre-populate fields in the survey, not for the where clause in the Inbox. When using survey to edit existing features, the where clause is very useful to filter features using field values or even the logged user, but this is fixed at desgn time and I don't think that URL schema values can be used. For example if I have a general survey to report interventions, I could use it first for features regarding road problems, than for water problems and so on. This is because different people take care of different type of problems but the survey template could be the same.

To be sure I am also posting a question on the forum.

Gianni

AnthonyRyanEQL

Gianni,

Could you explain a little more on what you mean about 'the filter/order the inbox features'? I assumed this would have been considered, etc. when the format/functionality of Survey123's custom URL scheme was developed.

Thanks

GianniCampanile

This is a great idea but for us is a part of the problem. One good idea is to pass parameters to fill in some fields of the Survey, so to avoid retyping; a second one applies if the survey relies on a published feature service: in this case the passed parameters could be used in the "where" clause of the inbox to filter/order the inbox features.

EricDick1

This type of functionality would be great.

We're about to implement Survey123 for data collection and would like to limit the free text needed to complete the form so we're populating the survey with data from a data base. Workforce is being used to manage the field assignments but it would be more efficient if it could pass the required parameters from the database right to the survey.

TiffanyRufo

I would also like to see this kind of functionality.

We are trying to bring up a citizen reporting solution that uses GeoForm, Workforce and Survey123 but are unable to fully implement the solution because there would be no way to tie the Surveys to the assignment.

It would be nice to be able to pass assignment type, assignment date, assigned field worker and assignment number to a survey123 form to be able to tie the records back and analyze the assignments.