Upgrade to GE 4.7 & GVH 2.8 broke noticing workflows

I upgraded on Friday and today received a call that our public noticing site (https://maps.sanmiguelcountyco.gov/viewer/index.html?viewer=Noticing) workflows - 1 for excel, 1 for a label report - are throwing an error. You can follow either workflow up to the point after it buffers and selects, then I get a "cannot read property 'toJson' of null". If you enter a buffer of 0, it runs to completion. Was there a change to some of the activities, such as FeatureSetToDataTable? I'm not a workflow whiz, and I haven't looked at these for a while. Here is just a snippet of the end of the workflow - the xaml is linked below.

_img_ alt="snippet of workflow" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90660000000PEUI&feoid=Body&refid=0EM60000000HYLJ"_/_img_

Here is the link to the excel workflow on Drive (https://drive.google.com/open?id=0BwY6J3h90ftlbzlVOVRkREpJaG8) . It breaks at the same point as the label workflow, so I'm assuming it's the same problem.

Thanks for any help!

Kevin Penner

1. Mai 2017 23:07

It looks like a 'RunExternalCommand' => AddMarkupGeometry is causing the error. It seems to happen only when the graphics are buffered (the value is >0).

What is happening in the workflow around the AddMarkupGeometry command? What's special/different about the buffered polygons?

1. Mai 2017 23:10

Oh, can you try passing in a single geometry instead of an array/list of geometries to the command? See if that makes a difference.

-Kevin

Permanently deleted user

2. Mai 2017 14:00

Thanks for pointing me in the right direction, Kevin. Somehow there was an extra activity in that branch, which wasn't doing anything, since I iterate through the selected polygons and add them to the markup layer just above.

Once I deleted it, both workflows successfully completed.

Upgrade to GE 4.7 & GVH 2.8 broke noticing workflows

Kommentare

Sie haben nicht gefunden, wonach Sie suchten?