Welcome to the Red Book for HPCC Systems® 7.0.x series. There are several sections in this Red Book as follows:
...
General HPCC Systems core platform
New - Encountering an issue where embedded Java fails
The platform does not currently always enforce a Java Development Kit (JDK) dependency and the embedded Java plugin (javaembed) can fail if a JDK is not available. If you encounter this error, install the appropriate JDK for your Ubuntu distro or the openjdk-devel package for Centos.
https://track.hpccsystems.com/browse/HPCC-25879
NEW - Login and usability issues running ECL Watch under Windows
...
https://track.hpccsystems.com/browse/HPCC-21720
NEW - Remove unwanted ws_store bindings for new environments created using envgen
...
https://track.hpccsystems.com/browse/HPCC-21861
NEW - Error reading CSV file as a FLAT file causes deserialization errors
...
DALI checks file scopes when CheckScopeScans is disabled
CheckScopeScans is meant to control scope enforcement when a user accesses a file list. However, in HPCC Systems 5.6.8, https://track.hpccsystems.com/browse/HPCC-16185 introduced a regression whereby if CheckScopeScans was disabled, scopes would not be checked even for a single file request. This is now resolved in HPCC Systems 7.0.0.
https://track.hpccsystems.com/browse/HPCC-19726
The default implementation of GROUP(dataset, fields, ,ALL) has changed
Previously the output of the operation happened to be globally sorted by the grouping fields, but this will no longer be the case. If any ECL code had been relying on this side-effect, that ECL may generate different results in HPCC Systems 7.0.0 Adding ,SORTED to the GROUP statement will cause the system to use the pre 7.0 implementation and generate globally sorted results.
https://track.hpccsystems.com/browse/HPCC-17415
...
Unicode TRIM now removes only space characters rather than all whitespace
Prior to HPCC Systems 7.0.0, the implementation of TRIM on unicode strings related to removing whitespace, was inconsistent with the implementation applied to standard STRING values. This inconsistency has been fixed in HPCC Systems 7.0.0. In STRING, this is space (0x20), horizontal tab, vertical tab, line feed, form feed, carriage return (0x09 to 0x0D) and non-breaking space (0xA0). In UNICODE, it is all characters with the white space property.
However, it’s possible some code may have been relying on the previous behaviour. If so, you can specify, WHITESPACE on any TRIM expression where you wish to use the prior semantics of removing other whitespace characters as well as space characters.
https://track.hpccsystems.com/browse/HPCC-19075 and https://track.hpccsystems.com/browse/HPCC-19008
...