Latest Contributions by TylerBragg2

Also, I'm not sure of your exact needs or workflow, but I created an in depth video about how I built our asset inspection setup.  It's about an hour long, but the first part gives an overview, then I go into more detail in the second part.  You may or may not find this useful in your application.  Here's the link: Webinar: Conducting, Managing, and Archiving Asset Inspections Using ArcGIS and Integromat ... View more

I realized that the xlsform didn't attach.  It should be attached to this post now.   ... View more

Will do.  I eagerly look forward to this release.  As always, thanks for your help.   Tyler ... View more

Craig,  Thanks for the response.  That's great news that it is on the agenda to be addressed, and with the release coming up next month, even better.  Do we have a scheduled release date in April?  You are correct - the other Workforce project is a classic project.  I can't remember exactly how I got it to work (maybe I was just able to check the box for editor tracking and that's why I can't remember it being this difficult to enable.) The one I'm working with now is actually the replacement/upgraded version of the old one.  I didn't do a direct migration because I'm adding in quite a bit of additional functionality and wanted to start fresh (You just recently helped me out with another issue regarding Survey123 app integration).  Obviously, I'm skirting around the edges of current functionality with what I'm trying to do!  Tyler ... View more

@CraigGillgrass do you have any insight regarding this question? I'm having the same issue.  It seems as though there is a bug - NIM102295 that might be contributing to the issue.  It seems that if your editor tracking fields are already present in the feature layer, you can't enable the "Keep track of created and updated features" option, even though the fields are there to support it.  Without this option checked, it seems you cannot add a feature level webhook to the assignment layer.  You would think that if Workforce adds these "track edit" fields when the feature layer is created (when a new workforce project is started), the solution would be for workforce to ensure that the Change Tracking option is activated on that layer.   This is frustrating to me because I have another workforce project that I found a work-around for this last year and set up the feature level webhook, but I can't for the life of me remember what I did to get this enabled.  I'll keep looking though.  I can't believe the OP didn't get any response...  ... View more

Craig,  That's good news - supporting the editing of additional fields in a simpler manner.  I think that will really make Workforce more broadly useful, especially for situations like mine where we HAVE to collect additional information about each work order.  I'm actually planning on using Feature Reports in Survey123 to take this workflow one step further and generate a "Work Order Report" PDF that highlights the work that was completed for each work order/assignment.  In our scenario, we have to report work of a certain assignment type to higher level of government, so I'll use Integromat to watch this feature layer for features of that assignment type that are completed.  When they are, I can have it automatically run a workflow to generate the feature report and upload it to our cloud servers.  Then we will have it ready when it's time to send the report up the chain.  It would be nice to bring that Feature Report service into Workforce.  I think a work order report is probably a common requirement.  Maybe I'll see if that's in the ideas section.   ... View more

Craig,  Regarding "closing the app" - Yes, that's what I mean.  Kill the app by swiping up on iOS or choosing the "recently used apps" button on Android and ending all applications.  Our workers do NOT leave any ArcGIS field apps (Workforce, Field Maps, Survey123, etc) open on their devices.  It kills the battery life of the device.  So they make it a habit of doing what they need to do, then closing the app.  But you answered my question.  In my case, theirs should sync edits when they open the app up again, which is problematic, if I'm trying to see what they've done from the office.  They might not open it back up for hours.  So they'll have to add that extra "manual sync" step before they close so the edits will be synced as soon as they finish editing.  That's something I could see being easily forgotten by field staff...  Thanks again for your help Craig.  I consider this matter answered and closed.   ... View more

@CraigGillgrass , One other thing I did notice when I changed the URL parameters to open the web app in edit mode - The Workforce project settings page is showing an error for the Survey123 app integration.  See the screen shot below:   I don't know if this will really be an issue or not, but it does tell me that the URL scheme for the web app in edit mode is technically "not supported." ... View more

Craig,  Thanks for the explanation and your fast responses.  One additional question: If the worker makes edits (either in Workforce or to the integrated survey) and immediately closes the app, when does Workforce sync?  The next time they open the app?   ... View more

@CraigGillgrass ,  Thanks for your response!  While I was waiting for a response to my initial post, I did some experimenting with changing the URL parameters to open the web map, just as you described above, and it seems like it's working.  However, there is a bit of variation to the syntax that you listed above in order to make it work.  It looks like this: https://survey123.arcgis.com/share/<ItemID>?mode=edit&globalId=${assignment.globalid}   I received an error stating that the GlobalID parameter was not property defined if I just used the "globalId={GlobalID}" syntax.  I can try to reset the URL parameters and generate the error if you need a screenshot.   In my preliminary testing, I did discover the issue with syncing that you mentioned above.  That prompts a question:  Is there a way to "disable" the offline capability of Workforce with this new version so that syncing is not required?  Or is that built in now in such a way that it cannot be disabled?  That will be really annoying for the field worker if they have to keep re-syncing the assignment every time they make edits.  I don't really need the offline editing capability in my situation, and it would be an advantage if I could disable it.  The ability for offline editing is also causing an issue with my worker map - I have an image service that doesn't appear to be compatible with syncing, and if that image service is in the map it does not display properly.  That's another issue I have to resolve.  Thanks for all your help! ... View more

Peter Klingman‌, Thanks for the update!  I'll check this out and I'm sure I will learn a few things.  I wasn't aware of the "sleep" function in Integromat, so I'll have to look into that as well.  Awesome! Tyler ... View more

Peter Klingman‌, Thanks for the update about the "extractChanges" functionality.  I can say that I have already tried to use this option, and I think there may be some issues with it (or the issue is with me).  I couldn't get it to work consistently.   Specifically, I am using the feature level webhook to trigger a scenario in Integromat when a few feature is added to the feature layer (This particular feature layer is the "assignments" layer in one of our Workforce projects).  The Integromat scenario then sends a text message (email to text) to the field supervisor to make him aware of the new assignment in Workforce.  I want to include the address and priority level of the assignment in the message so he has an initial idea of the location and severity of the problem, which is why I need attribute information.  As I was creating this workflow, I initially set up the scenario to use the extract Changes functionality that you mention above, which returns the Status URL, which contains the Result URL json file.  I tested all my HTTP requests in Postman, and everything worked perfectly.  However, when running the scenario in Integromat, I kept receiving an error when it tried to open the Result URL json file after the webhook trigger.  I can't remember the exact wording of the error, but it basically said that the json file (Result URL) did not exist.  When I went back to review the error (just moments later), it worked just fine and opened it right up.  So I was thinking that there may be a time delay in the creation of the Result URL json file after the extractChanges is triggered, and before that file is actually generated my Integromat scenario has already tried to open it, causing the error.  I don't know if this is actually what was happening, but it was the only explanation I could come up with.  Is there a way to determine the amount of time it takes for AGOL to generate this Result URL json?  Maybe it was an issue with the way I had things set up though.   So as a workaround, instead of using the extractChanges function, once the new feature is created and the webhook is triggered, my scenario makes an HTTP POST request to the feature server, queries where CreationDate was in the last 2 minutes, then grabs the attributes from the feature returned in that query.  It's working, but not ideal, especially in an event where two assignments may be submitted back to back within 2 minutes of each other (not highly likely, as it takes a minute or two to enter all the appropriate information for the assignment).   I would have included screenshots of this issue, but I abandoned the idea when I discovered the workaround, and now I'd have to go back and set the whole thing up for using extractChanges to see what was happening again.  It would be nice to get this working, as I could then parse the Result URL json, grab the "globalID," then make an HTTP POST request back to the feature service and grab the attributes of the feature with that globalID (instead of looking for features created within the last 2 minutes).   Also, the link that you provided above regarding the 'Create Webhooks' API Documentation, as you stated, is more of the API reference information and doesn't actually direct you as to how to go about getting the feature level webhook setup for the feature layer.   Thanks for following up on this!   ... View more