Now Available: VertiGIS Studio Printing 5.29.1

Hotfix Summary:
This hotfix resolves issues affecting the new SaaS service of the next‑generation ArcGIS Pro–based Printing Engine, as well as problems related to converting legacy templates into ArcGIS Pro–based layouts.

New Features

[Engine CIM3] Added optional strict and debug modes for print‑content validation to support troubleshooting. Configuration options for these modes will be available in the next version of Studio Web. [315697]

Behavioral Changes and UX Improvements

[Designer] Page info item “Page Count” has been removed because it is cannot be used in ArcGIS Pro-based layouts. [362435]
[Engine CIM3] Print layout legend elements now exclude markups, selection graphics, and symbologies. [342256]
[Engine CIM3] An invisible WEBMAP_MAP_FRAME is now added on‑the‑fly for legend pages if necessary. [362437]

Security and Technology

[Designer] Internal SaaS Gen2 VSPE URL is no longer exposed in the browser console. [362431]

Bug Fixes

[SaaS] Fixed an issue where requests were blocked when their content was too large. [362428]
[Designer] Fixed an issue where mandatory layout page types were not added during layout conversion and thumbnails were generated incorrectly. [362471]
[Designer] Fixed an issue where setting the Printing Engine URL was disabled and incorrectly demanded portal admin permissions. [362877]
[Designer] Fixed an issue where legacy templates containing the unsupported XRLabel.TextTrimming property were not processed correctly. [364864]
[Designer] Fixed an issue where boolean parameters caused failures in the print preview. [363737]
[Designer] Fixed an issue where the map info field “Attribution” was not detected correctly in templates. [363740]
[Engine CIM3] Fixed an issue where dynamic elements were not processed correctly for overview page layouts during printing. [319479]
[Engine CIM3] Fixed an issue where default values of custom layout fields were not converted correctly from a legacy template to an ArcGIS Pro layout. [362436]
[Engine CIM3] Fixed an issue where the page info item “Page Number” was not mapped to the field "syn_index" when converting a legacy template to an ArcGIS Pro layout. [362432]

Known Issues

[Known Issue – SaaS] Printing fails when using the SaaS‑hosted ArcGIS Pro–based Printing Engine with map services that enforce geo‑blocking and reject requests originating from foreign countries. [362889]
[Known Issue – SaaS]: Print requests with overly large payloads (multiple megabytes) may fail with the error “HTTP 413: Entity Too Large”.
As a temporary workaround we suggest trying to print with fewer layers enabled, which will reduce the request size. [365671]
[Known Issue – Designer] Batch conversion may fail to display templates when an account contains a large number of saved templates. [364200]
[Known Issue – Designer] Batch conversion produces an unnecessary warning, "key @Type not found in layout JSON", which can safely be ignored. [365187]

On-premises installer:
https://apps.vertigisstudio.com/downloads

VertiGIS Cloud (SaaS)

Printing Designer for ArcGIS Pro based layouts (.pagx format):
  https://apps.vertigisstudio.com/printing
  https://apps.vertigisstudio.eu/printing

Printing Designer for legacy layout
  https://apps.vertigisstudio.eu/printing/legacy/
  https://apps.vertigisstudio.com/printing/legacy/

Printing Engine based on ArcGIS Pro:
  https://apps.vertigisstudio.eu/printing/GPServer
  https://apps.vertigisstudio.com/printing/GPServer

Questions? Check our FAQ pages:
VertiGIS Studio Printing (based on ArcGIS Pro) FAQ
- Printing Installation FAQ
- Printing Integration and Configuration FAQ
- Printing Outputs FAQ
- Printing Designer FAQ
VertiGIS Studio Legacy Printing (based on Chromium) FAQ

Online documentation:
Documentation Center

And join the conversation in the
VertiGIS Studio Printing Community Forum

Commentaire officiel

Jakob Furrer

2 mars 2026 10:56

The issue where SaaS Printing could fail when map services enforce geo-blocking or IP allow-listing has been addressed. [362889]
The outbound traffic of the Studio Printing gen2 SaaS instance now uses a dedicated static public IP pool to ensure reliable access to restricted services.

Customers using allowlists may need to add the following IPs:

135.236.7.93
51.124.49.217
52.157.250.31
20.93.194.196

Eric Kriener

25 février 2026 13:06

RE: [Known Issue – SaaS] Printing fails when using the SaaS‑hosted ArcGIS Pro–based Printing Engine with map services that enforce geo‑blocking and reject requests originating from foreign countries. [362889]

What's the specific fail/error we would get to know that this was the problem?

Which country is it coming from? Canada?

Is there a list of IPs or URLs we can whitelist?

25 février 2026 13:55

Hi Eric,

So far we have had a handful of support cases regarding printing problems due to geo-blocked map services. The customers in question are from the USA and working with governmental data services.
The specific symptoms of the issue are as follows:
- The web map shows no problems in Studio Web for the specific customers, but fails to load when opened by someone working on a computer in Europe (or, presumably, anywhere in non-USA).
- Printing works fine when using the .com instance of the gen1 SaaS Printing.
- Printing fails when when using the .eu instance of the gen1 SaaS Printing or either instance (.com or .eu) of the gen2 SaaS Printing
- The following error is logged when using gen2 SaaS for printing:
Exception: FAILED :: create project from 'WEBMAP_MAP_FRAME': Failed to create layer from service at https://<censored>/arcgis/rest/services/OneView/<censored>/MapServer.
Failed to create layer from service at https://<censored>/arcgis/rest/services/OneView/<censored>/MapServer.
Failed to create layer from service at https://<censored>/host/rest/services/Parcel_Basemap/MapServer.
Failed to create layer from service at https://<censored>/arcgis/rest/services/OpenData/Parcel_Owner/MapServer/3.
Failed to create layer from service at https://<censored>/host/rest/services/Parcel_Query/MapServer/0.

Currently, the gen2 SaaS Printing Engine has a non-fixed IP, presumably identifiable as “European”, but definitely as “non-US”.
We are now working on assigning a (number of) fixed IP, so that those can then be put on the the allow-list of the respective map servers.
Once this has happened, I will write an update here.
Regards,
Jakob

25 février 2026 14:37

yep, those are the errors. and yeah, gen2 saas.

thanks!