•Fixed an issue where Java runtime was incorrectly purging the node lookup cache on each subsequent table lookup. This caused a problem when the AnyNodeTrue/PositionToNode operation used TableLookups to satisfy its "condition/index" branch.
•Fixed an issue where decimal typed UDO parameters would cause a runtime exception when a long typed value was provided.
•Fixed an issue that was causing the Java runtime to not use named database connections.
•Fixed an issue that was causing the C# and Java runtimes to incorrectly override named database connection settings defined in decisionServer.config with the settings defined within the repository itself.
•Fixed an issue where 'long' typed columns prevented Java runtime generated code from compiling.
•Defining more than one named database connection in a repository no longer causes code compilation to fail.
•Fixed an issue in the Java version of the decision server that was causing a WrongContextException to be thrown incorrectly. This was happening with decision groups that reference a formula (on the same context as the decision group) which then uses the ExternalContext operator pointing at the same context as the decision group itself.
•The SetEffectiveDate operator now only uses the specified date without its time component. This was previously causing a gap in effective table contents/formula references where one starts the day after a previous one ends.
•Generated queries from auto-linked table lookups now use identifier escaping to explicitly tell the database what it wants (some caveats for Oracle). For example in SQL Server, if the table name is "123abc", the generated queries use "[123abc]".
•Fixed an issue that was causing auto-linked table range lookups to return the wrong result when the ranged key isn't unique.