What's New in 1Integrate v5.2

The following describes new features or UI changes for each release of 1Integrate.

For more detailed information including bug fixes, please see the Release Notes. For details of system configuration and dependencies, see System Requirements.

Data Stores

OGC GeoPackage

You can now write non-spatial features as Attributes (adheres to the OGC GeoPackage Encoding Standard 1.2).

Identify True Curves

We've added a new built-in function to identify geometries that were densified from curves from Esri File Geodatabase and GeoPackage data stores. The new "has_curves" Built-in can be used to enhance quality checks in compliance with National Emergency Number Association (NENA) Standards.

See "has_curves" in the Built-in Functions reference tables for more information.

Data Store Types

We've added new categories so that Data Stores are now grouped into one of the following:

  • Core - Data Stores that are provided by default in 1Integrate.

  • Extension - Supported extensions which require additional licensing. For example, Contextual Data Store or Google BigQuery. Please contact 1Spatial support.

  • Custom - Bespoke or custom built Data Sores that are loaded as extensions to the core product.

  • Deprecated - Data Stores that are not recommended for use. These Data Stores will not be supported in future releases of 1Integrate.

Rules

Rule Authoring Enhancement: Automatically open the list of available items when adding a new built-in function, built-in operation, or rule/action template nodes.

Session Summary Report: We've changed the Session Summary dialogue box to match the Report dialogue. Summary scoped reports are now available here. The Summary report download button has been moved to the Show Summary dialogue.

Synchronisation Tool

We've added API key authentication to the Synchronisation Tool. This allows you to generate an API key to login to the Sync Tool (instead of the username and password option) and allows the Sync Tool to be used with SAML enabled environments.

Creating an API Key

API Keys are created by an administrator, see API Keys for more information.

Using an API Key

You can select API Key as the login method instead of username/password. API keys can also be used when running the Sync Tool from the Command Line.

 

Enhancements for Cloud Deployments:

Significant Reduction in Container Size: Optimised the Interface and Engine containers to use a more targeted deployment which reduces the overall attack surface and container sizes.

Security Enhancements: The containers for the latest 1Integrate release are now reissued every week with the latest OS packages.

Service Installation Enhancements

SAML is now a supported authentication option for service installations. An additional option in settings.properties has been added to override the default location of the saml.keystore, if required.

Removed the ability to set JAVA_HOME from the service install scripts as this never reflected the Java install used by the installed 1Integrate service.

Critical Bug Fixes

Fixed a critical regression that prevented 1Integrate from being able to read data from multiple schemas for the PostgreSQL and SQL Server Data Stores.

Future Withdrawal Notices

The following Built-in Functions will be withdrawn from 1Integrate 6.0.0:

Built-in Function

Alternative
http_request http_request_v2
make_2d change_dimension
make_3d change_dimension
get_session_parameter_value 'Session Parameter Value’ within the Rule Builder