Now Available: VertiGIS Studio Workflow 5.27.1
This release fixes some issues that were unfortunately introduced in v5.27.0.
- Inputs attempt to spell check expressions in the Workflow Designer. [184032]
- Input Editor dialog does not show a scroll bar for long text in the Workflow Designer. [184724]
- Number Slider Form Element no longer fires change events when dragging the thumb control. [184801]
- Geocortex Viewer for HTML5 produces an error when attempting to project a geometry for Run Report, Run Print and Generate Webmap for Report activities. [184929]
Check out the Release Notes for a complete list of changes in this version.
-
Hi Ken,
I've using the latest SaaS designer release v5.27.1 today and I am running into all sorts of issues with the syntax checking in the controls. It seems as soon as a syntax error is found (and input box goes red) it won't clear the error status even if you correct the syntax problem.
I have found this with the Create Variable, Parse JSON, and many of the other input boxes. In some cases the only way I can fix it is to copy my input content, remove the activity from the workflow, add the activity back to the workflow and then paste my content back in the input box. Then it is happy.
Seems to me something is broken in this release with syntax validation. Be great if you can look into this and resolve it as current behaviour is very frustrating.
Thanks Owen
1 -
Further to this, as soon as a syntax error is triggered in an input box - which occurs immediately when using Log message activity for example - the auto complete completely fails as well.
0 -
Hi Owen,
I'm sorry to hear you're having difficulties. That sounds frustrating. I don't see what you're describing in my browser. I wonder if it's a caching issue. Could you try forcing the browser to reload the page? On Windows, this would be achieved by pressing Ctrl + F5 while you have the designer open.
0 -
Hi Ken, I've tried that but no luck.
I am seeing slightly different behaviour with this in Edge and Chrome. Chrome is slightly better with syntax validation but Edge is definitely not happy.
As an example:
1. load the sample workflow "Hello World Form"
2. drag a Log activity onto the designer it immediately shows as a syntax error.
3. enter an expression to log the message e.g. =$displayform1.state.TextBox1.value
In both Chrome & Edge the activity starts with the input flagged red with syntax error (empty). In Chrome & Edge when I type =$ I am prompted with the option $displayform1
When I enter =$displayform1. in Chrome it give me the prompt for state but in Edge I get no further prompts after the first . and the syntax error status never clears even after entering the correct expression. However I can successfully run the workflow in both Browsers.
This is Chrome Version 101.0.4951.67 (Official Build) (64-bit)
This is Edge Version 101.0.1210.47 (Official build) (64-bit)
0 -
Also checked this with Firefox 100.0.1 (64-bit) and it shows the same behaviour as Edge.
So I definitely think something is off with the syntax checking in the latest release.
0 -
Hi Owen,
Thanks for the additional information. I've not been able to reproduce it personally, but we have heard of someone else experiencing the same thing as you described. We will investigate and try to get an answer soon.
The bug has been logged in our system. You can quote Bug #185194 when referring to it.
0 -
I cannot reproduce the behavour in Chrome or Edge (same versions).
0 -
Owen Parfrey,
Are you still experiencing this problem? We had one other person who had the same experience and it seems to be working for them now.
My hunch is that it was a network blip relating to switching our production environment to the new version.
0 -
Hi Ken, yes still have the same problem. I have tried it on 3 different computers and different browsers and all show the same issue. The autocomplete and syntax checking just doesn't work for the activities.
I have a 5.26 on premise install and that is working fine. But the 5.27.1 SaaS version does not.
I did notice that when i signed into Workflow designer today it presented me with a MLA license dialog. That's new from yesterday.
0 -
Hi Ken, another update. I did a complete clear of my Browser cache after testing above and now the syntax highlighting seems to be working again. So you are probably right that the combination of the production switch over glitch and my local cache were to blame.
So hopefully we are back in business again now. Phew!
0 -
Owen Parfrey,
I'm glad to hear it's working at last. Now thinking more about the Browser cache, I think I might have an idea of what happened. Whenever we release a new version, most of the generated javascript files include a hash which ensures they have a different name from the old files. This prevents such files from being served as out-of-date information since it's now a request for an entirely different file.
I think that a few files related to the "worker" (which handles syntax validation and suggestions) might have names that do not change. This would make them susceptible to caching problems. I'll see if there's a way we can fix this for a future release to prevent this from happening again.
0 -
I am also seeing this same issue. I am using Saas 5.27.1 in a Chrome browser. After clearing my browser cache it still the syntax issues (even though they are not issues).
0 -
Ken,
I was today with a cliënt we installed test and production (same deployments). I tested 5.27.1 is working great in test but not in production. We deinstalled and installed 5.27 same issue. So we reverted back 5.26.1 (last installed and working version) and it was working again. Any thoughts about what is going wrong?
We rebooted servers, flushed cache everything we could think about but no solution.
I just read the newest announcement. is 5.28 an option?
Kind regards,
Erik Kuipers
Esri Netherlands
0 -
Hi Erik Kuipers,
I'm not clear on what problem you are facing. Was it the above issue with the validation and suggestions not working? That was confirmed to be caused by caching of old versions of JavaScript files with "worker" in the name. This has been solved in Workflow 5.28.
0 -
Ken,
Yeah it was the same issue aas described above. with 5.28 the issue has been resolved.
Erik
0 -
Hi Erik Kuipers,
I'm glad to hear that solved it.
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
16 Kommentare