Version 2.0 - 23 July 2024
New Features
•The VertiGIS Integrator 2.0 comes with improvements across the code and User Interface. In the Protocol table, UT XML (name in VertiGIS/UT Integrator Version 10) can be found now as VI XML.
•The Object Query function now has additional geometry formats: GeoJson, Esri Json and WKT. A new input field for WKID (Spatial transformation system) was added and, if set, the coordinates will be transformed to the special reference system.
•The Queue and Exchange parameters along with their related options (Port and Binding key) are extending the RabbitMQ Inbound service endpoint for a better user experience.
•We have also improved the Email service endpoint parameters. The VertiGIS Integrator Email service endpoint now puts forward the SSL and StartTLS protocols.
•The VertiGIS Integrator comes with inbound processing improvements when the feature service request is generated. The VertiGIS Integrator is now capable to analyze the field type and decide if the value should be put into quotes or not (e.g. strings and globalids are put into quotes in this condition and numbers are not).
•The VertiGIS Integrator comes with a new Cron Job called Feature Service Query that automatically triggers the Object Query at defined times.
•Added support for TLS connection to RabbitMQ service endpoint, including peer verification via certificates.
•We have implemented a deltasync mechanism that allows the VertiGIS Integrator to transfer only changed data of a complete dataset to a feature server.
•We have added 2 new JSON parameters to the Feature Service endpoint in order to limit the number of features that can be sent to the feature server per request and to condition the sending of request packages inside an edit session.
•A new parameter called Protocol XML has been added to all inbound service endpoints to allow users to specify which XML files they want to send to the Protocol table.
Security and Technology
•Shiro has been upgraded to version 2.0.
•Communication tools improvements for Azure ServiceBus endpoints.
Bug Fixes and Improvements
•The SOAP Inbound processXMLAsync is using the version defined in the endpoint. After re-executing in ArcGIS Enterprise, the assetname value is changed in the version to the value defined in the xsl file.
•Inbound Processing with ApplyEdits Request now supports globalid fields.
•Response XSL Template in DBInbound is now fixed. When setting the field Response XML Template to VI XML then next time when the dialog is opened the VI XML value is displayed.
•Fixed error related to the login page for Shiro authentication.
•The UpdateFeaturesBulkRequest functionality now selects features and rows in feature service layers according to a where clause and updates attributes of the selected features and rows.
BEHAVIORAL CHANGES
•VertiGIS Integrator 2.0 exclusively supports GIS software of the current generation: ArcGIS Pro + ArcGIS Enterprise, plain ArcGIS + Utility Network and VertiGIS Network Pro.
•The support for the SOE package, UT-related classes, methods and interfaces, ArcMap and UT specific functions for UTI XSL API is no longer available.
