12.0 SP1 Updates

• When a subflow was exposed and used multiple times as stages in a dataflow, the inspection on the dataflow was correct. However, if the user selected the exposed stage, then chose "Inspect this Dataflow" to drill-down into the subflow, the input data passed into the subflow remained the same, which was incorrect.
• In Enterprise Designer, the process flow execution history would show started/finished date and time in U.S. format, only.

• In Management Console, users were unable to change the number of malformed records to terminate a job.
• Resolved an issue related to the mapping of LDAP attributes to Spectrum roles. In some cases, the amount of data stored in the Neo4j database exceeded the 32766-byte limit.
• An issue occurred when attempting to override files on file sinks using Job Executor. (This issue is addressed in software update 11.1 S59, also.)

This software update fixes an error that occurs when you run multiple services with basic authentication and overflow audit query enabled. If one or more services are using Write to Hub and the audit queue overflows, the hub will stop processing and generate server log errors. This prevents logins to other services and will generate “unauthorized access” error messages.

These product updates fix an issue where a timeout occurs when a large Enterprise Routing database is added as a data source in Management Console and subsequently a smaller database of the same name cannot be created.

This product update fixes an issue where an External Web Service defined with a valid JSON request schema fails to execute on the server but the same External Web Service defined with an XML request schema executes successfully.

• Resolves a​ performance issue when deleting multiple entries from the ​execution history log
• Removed token update logic that would sometimes cause the system to hang

• LDAP user was disabled in Spectrum Technology Platform, but could still sign in to the system.
• Could not purge large comment in Execution History.

• Two instances of errors that occurred when duplicate Java classes were loaded after system restart.
• A null pointer exception (NPE) error occurred when running multiple, simultaneous instances of a job.
• While a dataflow processes successfully in a standard processing environment, the same dataflow produces no output record in a distributed environment.

We urge you to apply this product update as soon as you are able to do so. If you do not apply this update, your server may become unusable or inaccessible.

• Some Japanese double-byte characters are not available under the Dataflow option.
• Cannot import double-byte files through CLI dataflow.
• Management Console returns incorrect record counts (zero records).

• In Job Executor, the double-byte character Dataflow option name is not replaced with the default value.
• Improved the Japanese language string provided for option "Data from the right port is sorted" in the Record Joiner stage.

• Linux/Unix

  

• Windows

  

• Where input addresses with accented characters did not return results
• Where Enterprise Designer displayed countries in a random order
• Where GGM did not return a centerline candidate for USA

• A licensing issue with Q4 2017 data has been resolved and no longer throws an exception.

This product update fixes an issue of autosize functionality for GeoEnrichmentLookup Options window.

This product update includes:

• Global Address Validation PO Box support for Canada, France, and the United Kingdom.

• Global Type Ahead enhancements including Range and Range Unit support for the United Kingdom and the United States.

• Resolved an issue where input addresses with accented characters did not return results
• Resolved an issue where Enterprise Designer displayed countries in a random order
• Resolved an issue where GGM did not return a centerline candidate for USA

This product update addresses these issues:

• When string input is used to create a point in the Spatial Calculator stage, the strings were being converted into numbers on output. This created problems downstream.

• Spectrum Spatial was not able to open an Oracle table in some cases.

• Spectrum Spatial failed when attempting to read NativeX tables with edited records.

• Using double quotes as aliases in the Query Spatial Data stage was throwing an error.

• A View Table created with an MI SQL GROUP BY clause was not working.

• Running a query that included a geometry predicate function was throwing an exception in some cases.

• When a request was made to Spectrum Spatial, the Spatial JVM made the request back to the Platform JVM to confirm the permission on named resources. This was leading to a deadlock situation when requests were large in number.
• The Write Spatial stage was throwing an error for ‘Delete By’ Filter when the filter uses variables.

• Join with XY Table was not working.

• Write to TAB from the batch job was failing silently to write data to a TAB file that had space in the name.

• Legend images for text features were not being returned.