VertiGIS Studio Web 5.26 Released
VertiGIS Studio Web 5.26 was released on October 25th, 2023.
VertiGIS Studio Web 5.26 is now live in our SaaS environment
https://apps.vertigisstudio.com/web/designer/
On-premises installer: https://apps.vertigisstudio.com/downloads/
This release includes the ability to generate one-click or parameterized saved queries, improvements to .CSV delimiter detection and usage, extensions to button styling, app startup performance improvements, and more.
Full release notes are live and can be found here:
https://docs.vertigisstudio.com/webviewer/latest/admin-help/Default.htm#gwv/release-notes.htm
-
Offizieller Kommentar
5.26.1 27-Oct-2023
BUG FIXES
Resolved an issue in App Designer in processing webmaps that was causing at least some of the crashes and out of memory errors. It was very notable in webmaps with subtype group layers but was affecting other large/complex webmaps as well. [245740]
Resolved an issue with a case-sensitive match that should have been case insensitive affecting attribute retrieval from Postgres DB attributes names in subtype group layers. [246217]
Resolved a Printing issue where the visible state of layers wasn’t correctly passed to printing. i.e. you could see a layer in your print that wasn't visible in your map. [246418]
Resolved a Printing issue where grouped layers were no longer being properly respected and displayed correctly in prints. [246444]
Resolved a regression in the Remove Application Data workflow activity. [246321]
5.26.2 09-Nov-2023
BUG FIXES
Resolved an issue related to VSW apps not working in iOS17. [244807, 244187]
Resolved an issue related to WMTS layers inadvertently creating many layer extensions in config due to how Esri represents WMTS. [246707, 247737]
-
anyone gettin' browser memory issues in VSW since this dropped? Any more than a few layers in the web map and it breaks.
1 -
Not sure if I am having browser memory issues, but I will say, I am experiencing a serious drop in performance with VSW today. Extremely slow in the designer. I have some other tasks requiring my attention today so I bailed on it until Friday or Monday.
0 -
thanks for sharing Bryan, all our apps are at a standstill as we can't even push 2 prod. I'll report back.
2 -
Same here, I even couldn't save the app not sure you could.
another thing I notice is about the vertigis web and pritnig, in the current prod application, vertigis printing doesn't consider the group layer visibility and all layer would be in the map reagrdless of their parent group visibility in the output map. and in the large map it returns the blank screen.
I'll already raised request and hope we can get some workaround quickly.
0 -
Davood Kazemi I had the same problem saving changes a couple of times earlier today but figured it was just me. Now, I have been able to save since then.
0 -
Howdy folks. I'm chasing down a couple of things right now related to your comments above.
So far (not final conclusions) it seems that App Designer serialization code is struggling with apps that contain SubtypeGroupLayers and/or WMTS layers.
I'd love to hear from your examples above if what you are observing is:
In Designer only.
In Web running on its own.
In both Designer and Web.
... also let me know if your apps contain subtypeGroupLayers and/or WMTS layers (I suspect there is s 3rd 'something' out there that is causing the same type of problem in Designer.0 -
Are you both on AGOL or Enterprise (Portal)?
1 -
I'm at AGOL which upgraded yesterday as well
0 -
i'm getting the memory error
in VSW designer at the save-as stage
no wmts referenced in basemaps or in web map
do have custom wms in web map basemap selector
it breaks with all map image layers (so these are grouped using sublayers)
but no "subtypegroup" in map at all
enterprise (portal)
(hope that answers your questions and helps Cam)1 -
currently my staging and prod app works fine in web except printing function as I explained and not sure it's the web or printing issue.
in designer, it crash whenever we try to save in the large map with wmts and group layers.
In designer sometimes map is not loaded sometimes
0 -
Hello again,
I have something staged you can try.
IMPORTANT: Please DO NOT SAVE your app, if you want to try a Save operation please use Save As.
This staged 5.26.1 has a few fixes in it related to Designer loading and webmaps, as well as for subtype group layers, and resolved the issue that prevented printing of some content.
Designer is at:
https://apps-staging.vertigisstudio.com/web/designer/
You can also modify existing app URLs by replacing apps.vertigisstudio.com with apps-staging.vertigisstudio.com
Please let me know if this does (or doesn't) resolve your Designer issues ... and also Davood Kazemi if it resolved your printing issue.
We may have to add a couple more things to this staged release before it is ready.
0 -
Hey Cam Barnard
Thanks for the updates
I was able to:
1- save as the app to new one without crash
2- make some changes on staging designer and save the app ( although I came across a couple of time with low memory issue and browser crash but I think it might be related to staging app and we won't have it in prod one)
3- I was able to print the map in the designer and web and both working fine.
0 -
I've gone ahead and approved the release of a 5.26.1 hotfix to the SaaS environment.
This fixes:
- An issue in App Designer in processing webmaps that was causing at least some of the crashes and out of memory errors. It was very notable in webmaps with subtype group layers but was affecting other large/complex webmaps as well. [245740]
- An issue with a case-sensitive match that should have been case insensitive affecting attribute retrieval from Postgres DB attributes names in subtype group layers. [246217]
- A Printing issue where the visible state of layers wasn't been correctly passed to printing. i.e. you could see a layer in your print that wasn't visible in your map. [246418]
- A Printing issue where grouped layers were no longer being properly respected and displayed correctly in prints. [246444]
- Fixed a regression in the Remove Application Data workflow activity. [246321]
Each of these fixes were focused with little risk and should solve at least some of the issues encountered. There may be additional fixes to do in a 5.26.2 release next week, let us know what issues you are still experiencing.
0 -
Cam Barnard
Thanks Cam for the prompt action
At least new hotfix, resolve the issue of the printing in web. but after couple of work with designer in prod (5.26.1) I found it very unstable and browser crashes after 5-10 moves and out of memory issue.
I do understand my map is a bit large and includes lot's of group type but we didn't have this issue before. I hope you identified the issue so far and it's on the list to fix in the 5.26.2.
Cheers
0 -
i snuck in one save this time but i'm still getting out of memory issues when trying to make changes -
has this been tested on apps with many layers in the map?|
can we go back to previous version?0 -
For those who are still experiencing performance / memory issues with Web Designer 5.26.1
I am still working on this, but it is slow going because thus far I've been unable to create a webmap or a VSW app that reproduces what you are experiencing.
I'm working on building a bigger webmap to try to test with.
If you have map service URLs that I could access, complex webmaps that I could access, or a VSW app exhibiting this behavior that I could access; it would help greatly.
Reach out to me directly at cam.barnard@vertigis.com with anything you think I might be able to use.
2 -
Cam Barnard
Any news on a potential release of 5.26.2?
And will release notes of 5.26.1 added to https://docs.vertigisstudio.com/webviewer/latest/admin-help/whats-new.html ?0 -
Nico Burgerhart ... We started a 5.26.2 release branch for testing. So for it contains two significant fixes. One related to iOS17 breaking VSW apps to make them work again on iOS devices running iOS17. Two an improvement to handling WMTS layer types. WMTS supports a concept of having multiple sets of tiles that can be switched between using an "activeLayer" concept. Esri exposed this via their API as 'sublayers' (the closest thing that matched). For some WMTS layers this could cause the unnecessary creation of a lot of extra layer extensions for the sublayers that aren't actually sublayers. We've adjusted the code to create a single layer extensions representing the primary tileset of the WMTS layer. We think this may have been one of the contributing factors to issues that some customers are experiencing. Internally we tried several different approaches to see if we could reproduce the struggles that ~8-12 customers are experiencing with Designer and could not. While we verify 5.26.2 we are also setting up some customer web meetings to see if we can get direct developer eyes on the environments where this is occurring - which may lead us to another issues to fix.
0 -
Thanks for feedback.
0 -
Good to hear that 5.26.2 is on the way. We have been having the same problems with the app crashing. For us it seems to be a bit intermittent with it crashing sometimes after only making one change, but when the change is replicated the following day it works. We don't have WMTS layers, but there is an OGC WMS layer in the webmap.
0 -
Cam. Thanks for the update. Feel free to contact me at Prince Edward County. Issue I have run into since the update -> swapped out a custom component, and got hung up on the load screen once I hit save changes. This has occurred in both AGOL and Portal VSW apps. Note that the only change to the source code on my component was a modification to CSS (The style of my button changed with the new update). At this point, I am not able to make any changes to my 3 applications (VSW) as they are hung up on load screen when I open Designer.
0 -
Thanks, Cam for the updates,
Using my app on iOS 17.1.1 and Saas 5.26.2 and the app is restarting two times and crashes at the end.
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
23 Kommentare