Footer button submit event doesn't fire
In Geocortex Go, I have a workflow but whenever I click the "submit" button, nothing happens (I put an Alert in the submit event, not fired). That workflow is however working if it's used in GVH.
In my opinion, that bug could be linked to a change event of a Geometry Picker form element (no problem in other workflows that doesn't have it).
Has anyone already had this kind of problem ? Any help will be appreciated.
BTW, the logs aren't helping me at all.
Thx !!
My on-premise versions are up-to-date.
-
@Amanda Frech? or other people from Latitude ?
0 -
@Guillaume Ruelle? Can you attach your workflow, or a simplified version of the form?
When you say "That workflow is however working if it's used in GVH", do you mean that the issue you're describing only shows up in the sandbox or Web AppBuilder, or some other viewer?
Normally submit should work, as long as the button has a value set, and there's no Click event added to the button bar. Can you double check the button value and events as well?
0 -
Hi @Amanda Frech? , the thing we are trying to do is to just take the workflows of a Geocortex Viewer for HTML 5 and adapt them to make them work in Geocortex Mobile Viewer ( Geocortex Go actually).
The one I am sending to you is actually working in GVH, but not in Geocortex Go.
0 -
@Amanda Frech? and here is the workflow
0 -
Hi @Guillaume Ruelle? and @Amanda Frech? - was this issue ever resolved? I am seeing the same problem on a workflow I've created - the "Submit" event on the form never fires in Go, but everything works fine in Geocortex Web.
0 -
@Matt Erbes? , if I remember well, the problem was coming from a "Set Form Element Property" in the load event of the form ( Property : Required = True).
I had to put it in the load event of the form element itself.
0 -
Hi @Amanda Frech? ,
was this issue resolved? I have come across similar issue. I am trying to implement a simple workflow similar to sample attached in Geocortex Go. However I am getting an error on submit. . It works in sandbbox
I am using =$form1.state.geometryPicker1.value.geometry[0] to get the geometry from geometryPicker on form.
0 -
Hi @Rav Herron? ,
I think the issue originally reported here turned out to be very specific to that particular workflow.
In the case with the example you attached, I'm wondering if it might be related to the way the geometry picker is being used, and to the age of the workflow. In newer versions of Go, the tools for collecting locations have been expanded a lot. I found that while testing the attached workflow in Go, I had to either double click a location, or click once and then click "stop" from the geometry toolbar. Then I had to select the checkbox on the workflow form to have the geometry included properly.
If I did those steps the example worked, but if I skipped any of them it would get an error.
I'd recommend the following steps in workflow designer:
- Delete the DisplayForm in the workflow
- Add a new DisplayForm
- Add a Geometry picker to the workflow
- Configure the geometry picker to collect Point geometry, and turn on the "required" checkbox
- Connect the rest of the activities to run after the DisplayForm
With those changes, I still had to either double click my point or click "stop" from the geometry toolbar, but if I missed doing that step, the form would warn me about it being a required field instead of letting me proceed to the error. Also, I found it was no longer necessary to click the checkbox on the form after the geometry was captured.
We do have a known issue (#38878) where very old workflow forms will be missing the right configuration for the geometry picker validation to work correctly in Go. Rebuilding the form usually fixes that problem.
0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
8 kommentarer