Auto-Populate Fields for Editable Feature Layer

Permanently deleted user

24. August 2018 17:20

I'm working on a site that has ~60 layers, all editable dependent on the user's role, and I'd like to build a workflow that populates fields in the background after a user has finished creating or updating a feature. All the layers would have the same standard set of fields that would need to be updated.

 

I don't want to re-invent the wheel with this, if possible I would still like to still use the Create New Feature tool as opposed to creating a form, drawing and adding geometry, etc. Most of the editing workflows I've found seem to follow that pattern.

 

I'm wondering if it's possible to capture information about a feature when Geocortex applies the edit to the service, through the CollectExternalEventArg activity possibly, and then to use that information to query and update the feature. Though I'm not having much luck with this approach.

 

Anyone have any input on the best way to accomplish this?

0

• 

  Permanently deleted user

  28. August 2018 18:04

  Richard - Thanks for the workflow. I've set it up in my environment, but I'm getting an error in my console when running it. TypeError: Converting circular structure to JSON

   

  I've seen other posts suggesting that I would need to write a custom module to accomplish what I'm trying to do, unless I can remove the circular references from the ExternalObject.

   

  This thread partially defines the module, but I'm not savy enough with coding to complete it.

   

  https://support.geocortex.com/essentialsGSCForum?sub-nav=forum&main-nav=essentials&#!/feedtype=SINGLE_QUESTION_DETAIL&criteria=ALLQUESTIONS&id=9066000000006kZAAQ

   

   

  0
• 

  Permanently deleted user

  6. September 2018 04:14

  this simplest method would be to create a workflow. You can then assign variables after the user creates geometry.

  0
• 

  Permanently deleted user

  21. November 2018 17:12

  Hi Jared,

   

  Circular structures are very common in the Esri Javascript API (Maps have Layers, Layers have a Map, etc).  One way you can avoid this error is by using the new Workflow 5, either completely doing your job with it or by capturing the object and getting only the parts out that you need to run in your Essentials Workflow.

   

  I haven't taken a close look at your workflow to see if it's a good fit here, but I wanted to mention that it can be used to avoid a circular reference.

   

  Regards,

   

  -Malcolm

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.