Capture Geometry vs. Display Capture Geometry

Permanently deleted user

5. April 2012 00:30

Hello Workflow Developers,

I'm currently working on a workflow that takes a selection set via Capture Geometry and passes the geometry to a Query Task. This works wonderfully as long as I use the Capture Geometry activity, but I would like to take advantage of the richer graphical interface provide by the Display Capture Geometry activity. But when I swap out the Capture Geometry to the Display Capture Geometry nothing seems to get selected in my map after I deploy the workflow. A graphic gets drawn when I use the tool, but noting seems to get pasted to my subsequent query task. What am I missing?

 

Do any of you kind folks have any luck using the Display Capture Geometry vs the Capture Geometry activity?

I know the code gallery sample of "geometry points selection" uses the Display Capture Geometry activity but I'm not seeing anything obvious why the Capture Geometry activity would work in directly passing the selected geometry to a query task and not the Display Capture Geometry activity.

 

-Alex

0

• 

  Jeff Siemens

  5. April 2012 01:00

  Hi Alex,

  I've seen lots of examples of people successfully using this activity.  How do you know that the geometry isn't being passed to the query task?  Are you sure you assigned the geometry output of the activity to a variable in your workflow?  Can you monitor your traffic to the query task?  You can use Fiddler, for example, to monitor traffic between a workflow running on the server and ArcGIS Server.  It helps to filter Fiddler traffic to only non-web-browser processes if you want to do this.

  Jeff

  0
• 

  Permanently deleted user

  5. April 2012 01:38

  Thank you Jeff, for the idea of using fiddler, its very helpful.

   

  I have my results from the Display Capture Geometry to a variable called geometry with a type of Geometry , made sure my variable was within my scope.

  I even added a alert box to see what I was capturing, but that never fires. Nothing fires after the drawing of the polygon.  If I delete the Display Capture Geometry activity and wire in Capture Activity

  everything starts working. Looking at the traffic with fiddler, seems that the Display Data Capture activity is waiting for something to tell it, its completed and to go on to the next step.

   

  -Alex

   

  0
• 

  Permanently deleted user

  5. April 2012 01:51

  I figured it out, I needed to add a button that caused validation. 

  Does anybody know if there is a way to not require a user to click a validation button to execute to the next step in the workflow?

  -Alex

  0
• 

  Permanently deleted user

  6. April 2012 02:25

  Hi Alex:

  We're using DisplayCaptureGeometry a couple of times and in each case there's a Next button that causes validation.  I imagine it's set up that way in case the user is not pleased with the geometry s/he drew, that way there's a way to redo it before moving on (?).  Having DisplayCaptureGeometry expanded to have an option to continue automatically once the geometry is successfully captured sounds like a nice option.  Maybe as a workaround you could configure a list box with the different geometry types as choices, then use a Flow Switch to set the geometry type of a subsequent CaptureGeometry.  It may be more bubble gum than is required though. 

  Nate

  0

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