Workflows not working after Upgrade
We just upgraded from GE 4.9.0 and HTML5 2.10.0 to GE 4.10 and HTML5 2.11 and our workflows are no longer working. The autocomplete forms don't auto populate and if you put in a valid input, you still get an error.
Specifically, the workflows on the server aren't working while the Workflow 5 workflows still work.
Has anyone else run into this issue? Thanks.
0
-
Hi Odiri,
Yes, it is a common issue, please see this article for a fix -
https://support.geocortex.com/essentialsGSCkba?sub-nav=kba&main-nav=essentials&#!/feedtype=SINGLE_ARTICLE_DETAIL&criteria=BESTANSWERS&id=kA3f2000000k9cGCAQ
Regards,
Wayne Richard
Latitude Geographics Group Ltd.
Head Office: 300 – 1117 Wharf Street Victoria, BC Canada V8W 1T7
Tel: (250) 381-8130 | Fax: (250) 381-8132 | wrichard@latitudegeo.com
Developers of Geocortex web-based mapping software | www.geocortex.com
An Esri Platinum Business Partner0 -
Wayne,
How would you account for the URL that is used in the "UpdateFeatures" workflow activity? There is not a "Source" In argument for that activity.
Best Regards,
Rick0 -
To paraphrase, am I reading that support article right that we'll have to repurpose any workflows for 4.11 that use Get Map Service Info, Query Task, Select Features, or Report activities (and Update Features per Richard's comment) on layers that support dynamic layers? 0 -
That's correct John, the loading behaviour changed with GVH 2.11 and now all services that support dynamic layers are enabled upon loading as opposed to when used, causing the issue. Using the 'source' property will avoid this. The issue should not affect the UpdateFeatures activity as it affects dynamic map services and not feature services.
Regards,
Wayne Richard
Latitude Geographics Group Ltd.
Head Office: 300 – 1117 Wharf Street Victoria, BC Canada V8W 1T7
Tel: (250) 381-8130 | Fax: (250) 381-8132 | wrichard@latitudegeo.com
Developers of Geocortex web-based mapping software | www.geocortex.com
An Esri Platinum Business Partner0 -
Hi John,
Just to clarify, if a workflow uses Query Task, Select Features, or Report activities, but NOT Get Map Service Info (ie, the urls are hardcoded or come from hardcoded variables or arguments), it won't be affected.
Any affected workflows would have had the same issue prior to 2.11, but it would only have manifested under certain circumstances (after the user performed certain actions in the viewer). So even though the issue would have existed, we've seen several cases where it's gone unnoticed until this change.0 -
I use Get Map Service Info in virtually all of my workflows, so I guess I'll be updating them. Oh well, I'm sure the cumulative amount of time I've saved by not having hard coded URLs is greater than the amount of time it will take to do the updates when I migrate my viewers! :) 0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
6 Kommentare