Release 8.3.19

Owned by Anthony George
Last updated: Nov 03, 2022
2 min read

PhixFlow. is pleased to announce the release of PhixFlow 8.3.19. This page describes the improvements and fixes in this version. This minor release includes important fixes.

Installing or Upgrading to PhixFlow Version 8.3.19

To install a new PhixFlow instance:

  1. Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.   
  2. Follow the instructions in Installing PhixFlow.
Sections on this page

To upgrade an existing PhixFlow instance: 

  1. Check System Requirements and Compatibility for changes to the system requirements or supported database versions. For example, you may need to upgrade your database or Java version.

  2. Ensure you have a backup of the database before upgrading PhixFlow.

  3. Follow the Upgrading PhixFlow steps. It is important to complete Step 8, in which you apply any Special Upgrade Instructions for all the intermediate releases between your current version and the version to which you are upgrading. The following special instructions apply for this release:

Special Upgrade Instructions

Important Information

None.

Improvements

DEV-12818 New attribute functions have been created to perform geometric operations on "Well Known Text" geometric representations of points, lines and polygons.

Geometry geoBuffer(Geometry left, double distance), Computes a buffer area around the left geometry using the given distance.

Boolean geoCovers(Geometry left, Geometry right), Tests whether the left geometry covers the right geometry.

Boolean geoDisjoint(Geometry left, Geometry right), Tests whether the left geometry is disjointed from the right geometry.

Double geoDistance(Geometry left, Geometry right), Returns the minimum distance between the left geometry and the right geometry.

Boolean geoEqualsExact(Geometry left, Geometry right, double tolerance), Returns true if the two geometries are exactly equal, up to a specified distance tolerance.

Boolean geoEqualsTopo(Geometry left, Geometry right), Tests whether the left geometry is topologically equal to the right geometry as defined by the SFS equals predicate.

Double geoArea(Geometry left), Returns the area of left geometry.

Geometry geoCentroid(Geometry left), Computes the centroid of left geometry.

Geometry geoEnvelope(Geometry left), Gets a geometry representing the envelope (rectangular bounding box) of left geometry.

String geoType(Geometry left), Returns the name of this geometry's actual class. e.g. "Point", "LineString", "Polygon"", "MultiPolygon".

Geometry geoIntersection(Geometry left, Geometry right), Computes a geometry representing the point-set which is common to both the left geometry and the right geometry.

Boolean geoIntersects(Geometry left, Geometry right), Tests whether the left geometry intersects the right geometry.

Boolean geoIsRectangle(Geometry left), Tests whether the left geometry is a rectangular polygon.

Boolean geoIsSimple(Geometry left), Tests whether the left geometry is simple.

Boolean geoIsValid(Geometry left), Tests whether the left geometry is topologically valid, according to the OGC SFS specification.

Geometry geoNorm(Geometry left), Creates a new geometry which is a normalized copy of this geometry.

Double geoGetX(Geometry left), Returns the 'first' x coordinate.

Double geoGetY(Geometry left), Returns the 'first' y coordinate.

If passed a string the geometry functions will automatically convert it into a geometry object.

If the final result of a JEP expression is a geometry object then this will automatically be converted into a String once evaluation is complete.

To convert a geometry object into a Well Known Text string (WKT) so that it can be passed to other attribute functions, toString() must be called.

Bug Fixes

DEV-12740 Resolved issue where a valid SAML session is no longer accepted by PhixFlow.

DEV-12377 Cache extraction filters are now multi-line editors, allowing long multi-line expressions to be edited.

DEV-12915 Stream sets generated by stream actions will now have a cycle of 1 instead of 0. This is shown in the System Console --> Record Sets --> Cycle (column).