CodeGen 5.5.9

CodeGen Release Notes

• We added a new structure expression token called <IF STRUCTURE_DISPLAY_FIELD>.
• We added a new relation loop expression token <IF TO_DISPLAY_FIELD>, and a new relation loop expansion token <RELATION_TOSTRUCTURE_DISPLAY_FIELD>.
• This version of CodeGen was built with Synergy/DE 11.1.1f and requires a minimum of version 10.1.1 to operate.

CodeGen 5.5.8

CodeGen Release Notes

• We added two new field loop expansion tokens <FIELD_ENUMBASEVAL> and <FIELD_ENUMSTEPVAL>.
• This version of CodeGen was built with Synergy/DE 11.1.1f and requires a minimum of version 10.1.1 to operate.

CodeGen 5.5.7

CodeGen Release Notes

• We fixed a bug that could cause a null-reference exception in some situations when using some of the Harmony Core extensions associated with structure relations.
• This version of CodeGen was built with Synergy/DE 11.1.1e and requires a minimum of version 10.1.1 to operate.

CodeGen 5.5.6

CodeGen Release Notes

• We added two new generic expression tokens to the Harmony Core extensions assembly. These are <HARMONYCORE_RELATIONS_ENABLED> and <HARMONYCORE_RELATIONS_VALIDATION_ENABLED>.
• This version of CodeGen was built with Synergy/DE 11.1.1e and requires a minimum of version 10.1.1 to operate.

CodeGen 5.5.5

CodeGen Release Notes

• The primary reason for this release is that we realized that the installations for the last several releases were incorrectly signed, resulting in Windows SmartScreen reporting the installation as risky, and doing its level best to discourage you from proceeding. The affected versions of the installer were versions V5.5.1 to V5.5.4. But, apparently, developers don't pay too much attention to Windows SmartScreen warnings, because I know there have been lots of CodeGen installations of the affected versions, and not a single person reported the issue! That's actually pretty scary, and as software developers, we really should know better! With one exception (Jeff Greene) I don't know who you are, but YOU know who you are!

  The issue turned out to be related to the fact that we have been working from home for the last three months, thanks to COVID-19, and the code-signing process on my home development system was silently selecting the wrong signing certificate! Sorry about that! Normality should be restored in the 5.5.5 installer, which is signed with the correct certificate.

• We also made all method loop expansion tokens also available in parameter loops.

• This version of CodeGen was built with Synergy/DE 11.1.1c and requires a minimum of version 10.1.1 to operate.

CodeGen 5.5.4

CodeGen Release Notes

• We deprecated the RequiresMatch feature that was added in the previous release, and replaced it with a more comprehensive mechanism involving a new ValidationMode property in the Harmony Core Customization File, and new custom relation loop expressions <IF VALIDATION_NONE>, <IF VALIDATION_VALUE_PRESENT>, <IF VALIDATION_ALWAYS> and <IF VALIDATION_CUSTOM_CODE>. The custom code validation mechanism is still to be defined, so is not operational at tis time. If you are using a Harmony Core Customization File we recommend reviewing the latest documentation and implementing ValidationMode instead of RequiresMatch.
• This version of CodeGen was built with Synergy/DE 11.1.1c and requires a minimum of version 10.1.1 to operate.

CodeGen 5.5.3

CodeGen Release Notes

• We added support for two new types of key loop, specifically Unique Key Loops and Unique Alternate Key Loops. These are very similar to regular Key Loops and Alternate Key Loops, except that they exclude any keys which have identical key segments to a key that has already been processed. For example, if a structure has an ascending key named ZIP_ASCENDING that has a single field segment which is the ZIP_CODE field, and also has a descending key named ZIP_DESCENDING that also has a single field segment which is the ZIP_CODE field, the second key would be included in processing by the original loops, but will be excluded by the new loop structures.
• In the Harmony Core Extensions library, when using a Harmony Core Customization File to override relation processing, we changed the default value of the RequiresMatch property.
• This version of CodeGen was built with Synergy/DE 11.1.1c and requires a minimum of version 10.1.1 to operate.

CodeGen 5.5.2

CodeGen Release Notes

• We added support for Complex Expressions which allow you to use AND, OR and NOT within expression tokens, and also allows you to use parentheses to explicitly define precedence.
• This version of CodeGen was built with Synergy/DE 11.1.1c and requires a minimum of version 10.1.1 to operate.

CodeGen 5.5.1

CodeGen Release Notes

• We added support for Complex ELSE Clauses within expressions, which allow multiple expressions of the same type to be evaluated within a single template file construct. We have future plans to extend the capabilities of expressions even further, but for now this new capability can be used to simplify template file code.
• We improved the error checking that occurs when a processing a Harmony Core customizations file.
• When using the CodeGen API we have added the ability to specify lists of file overrides at the TaskSet level.
• We corrected an error that was causing the <HARMONYCORE_BRIDGE_PARAMETER_TYPE> custom expansion token to return incorrect values for structure parameters.
• This version of CodeGen was built with Synergy/DE 11.1.1c and requires a minimum of version 10.1.1 to operate.

CodeGen 5.4.8

CodeGen Release Notes

• We added new field loop expansion tokens <FIELD_CUSTOM_DBL_TYPE>, <FIELD_CUSTOM_SQL_TYPE>, <FIELD_CUSTOM_CONVERT_FUNCTION> and <FIELD_CUSTOM_STRING_FUNCTION>.
• We added new field loop expression tokens <IF CUSTOM_DBL_TYPE>, <IF CUSTOM_SQL_TYPE>, <IF CUSTOM_CONVERT_FUNCTION> and <IF_CUSTOM_STRING_FUNCTION>.
• We added the ability to override some repository information via a JSON file. For more information please refer to Repository Override Files.
• This version of CodeGen was built with Synergy/DE 11.1.1b and requires a minimum of version 10.1.1 to operate