Release Notes v6.20

What's new?

• Added Source field to registered table objects, to match import objects.
• Added DEFAULT_VARCHAR_LENGTH environment variable, primary for Redshift and MSSQL-family databases, to allow an implementation-override of the default varchar length of 4000.
• Added column sort and asset drilldown capabilities to the module import screen.

What improvements have we made to existing features?

• For deployments with SQL visibility enabled and in verbose logging mode, all SQL executed against the customer database will be logged. The SQL will be logged to the application logs for queries executed directly from the application, and to the ELT and report logs for queries executed within an ELT or a report run.
• Simplified the rules for alphanumeric ranges in value sets and lookup tables. Whereas previously the alpha part and the numeric part of the value set value or lookup table key would be considered separately, now they're compared with a straightforward alphabetical sort. One thing that hasn't changed about this simplification is that the comparison is always alphabetical, never strictly numeric, which means for example that "500" would be considered to be within "1-9", and "5" would not be considered to be within "1-10". Users that want a lookup based on a pure numeric comparison should use a CASE WHEN pattern instead.
• Narrowed the rules for value set superinclusivity. It has always been the case that, for example, "F40-F41" would pick up a value such as "F41.1", even though, strictly speaking, such a value falls outside of the prescribed range. This feature remains, but it will only be activated if the next character after the upper limit is a decimal point. So for example, "F419" used to fall into "F40-F41", but now no longer does. This superinclusivity rule has also been removed from lookup table keys altogether.
• Redesign on Module Import screen to highlight branded modules.
• Changed the default configuration settings in analytics portal such that end users are no longer allowed to export from case review to the instance-designated export storage container. This new restriction can be overridden by setting the environment variable ENABLE_END_USER_PHI_EXPORT=true. Architects and admins can still export from case review to the storage container as before.
• Updated import objects to allow cloning, to allow the save of a first-time object, and added a revision history panel.

What's been fixed?

• Fixed a bug for range imports in which the import intent would be remembered as "append to existing table" even if the import had been set to "overwrite existing table".