Latest Contributions by JakeMatthys

Craig, The issue was that we need to use https on our side to access, workforce.  Probably a combination of changes made to Workforce and security software that is running on our side.  Thanks for the help!  - Jake ... View more

Hi Craig,  We are still unable to connect after clearing cache (Chrome, Firefox and IE10.  We can connect using mobile devices and noticed a change to the interface (clustering).  I have emailed you the .HAR file, I didn't see a method to attach it to my forum post.  - Jake ... View more

Hi Craig, We are not getting an error, we are just getting a blank page. I've tried it in chrome and IE10.    - Jake ... View more

Hi nicueber, I took a look at your form and confirm that required fields did not behave in repeaters that were not yet exposed.  Your form is different than my example, your form sets the number of repeaters based on a previous question.  As a user, if I just satisfied the 1st page of the repeater, even though the repeater had more pages, the form was able to submit.  Looks to me like you should continue to forward your issue to the ESRI Survey123 team so that they can investigate.  Good Luck... - Jake ... View more

Hi nicueber‌, I tried to test the scenario that I think you are describing but in my test, the required fields behaved.  In my scenario, I filled out a repeater, added a 2nd page to my repeater, and did not "touch"/add any data to the 2nd repeater and tried to submit my form.  The form would not submit and I was prompted to populate the first required field in the 2nd repeater.  My test was on Survey123 IOS version 1.10.23 on an iPad tablet. Let me know if I did not replicate your scenario.  - Jake ... View more

Thanks Ismael Chivite.  We will begin testing this new release for our customers during our next sprint cycle which will begin after the new year.  - Jake ... View more

Hi Craig, I wanted to follow up with you on this issue.  We have initiated a case (# 01865488) with ESRI support.  I have done some follow up tests and wanted to share my findings with you.  I have attempted to Add/Update our WF Assignments hosted web service using three methods (C# web api calls, rest endpoint user interface, and the WF Dispatch web page) and all attempts have failed due to a timeout.  I have also attempted to add WF Users to the Dispatcher and Worker web services using the WF project configuration web page and was also unsuccessful because of a timeout issue.  I have repeated these tests on 3 different WF projects, same timeout error each time.  We currently do not have any issues submitting Survey123 forms, so it seems that the timeouts are only occurring to our hosted web services that are associated with a WF project.  Our log file shows that the timeout errors first occurred Dec 14 19:15PST.  At this point both our Survey123 and WF hosted services were down until Dec 14 20:55PST (which aligns with ArcGIS Online Health Dashboard ), at which time our process began communication with our Survey123 hosted web services, but the WF hosted web services continued to time out from that point on.  Have you had any reports of this issue from other WF users or does this seem to be isolated to our organization's AGOL portal? Thanks,  - Jake ... View more

Hi James, Thanks for the workaround idea, and please follow up with more information on a resolution as it becomes available. Thanks,   - Jake ... View more

Thanks Craig... That was our issue.  - Jake ... View more

I would like to follow up on this issue as it relates to repeaters with required fields and the repeaters are exposed to the user based on the relevant answers to previous questions. Unfortunately we did not find that using default values in all of the repeaters that meet the above criteria as a valid solution for our use case because we would have overhead in terms of managing the default values and checking for the default value presence to exclude them from downstream reporting. The two main issues that we have encountered with repeaters that have required fields and the repeaters are exposed to the user based on relevant answers to previous questions. (version 1.9.24):  A survey that has a repeater with required fields, but that has not been exposed to the user because the repeater has a relevant that was not satisfied, will prevent a survey from being submitted In a situation where a survey has multiple repeaters, each with required fields and each repeater is relevant on a previous question.  In the case where more that 1 repeater is relevant (based on users previous answers)  as long as 1 of the repeaters has all of the required fields satisfied, than the required fields in the other repeaters are ignored.  Meaning that the required fields in the other repeater do not behave, you can leave some of the questions null and the survey will still submit. ... View more