CodeGen 5.4.5

• We added a new key segment loop expression <IF HARMONYCORE_CUSTOM_SEGMENT_DATATYPE> a new key segment loop expansion token <HARMONYCORE_SEGMENT_DATATYPE> to the Harmony Core extensions assembly.
• When using the CodeGen API we have moved the Interface property from the CodeGenTaskSet class to the CodeGenTask class. This change may break your code!
• We enhanced the Harmony Core Generator application.
• This version of CodeGen was built with Synergy/DE 11.1.1 and requires a minimum of version 10.1.1 to operate

CodeGen 5.4.4

CodeGen Release Notes

• We added a new relation loop variation called a restricted relation loop which differs from a regular relation loop in that in order for a relation to be included and processed the relations TO STRUCTURE must be included in the list of structures being processed. Relations whose TO STRUCTURE is not included in the list of structures being processed are ignored.
• We added a field loop expansion token <HARMONYCORE_CUSTOM_FIELD_DATATYPE> and a field loop expression token <IF HARMONYCORE_CUSTOM_DATATYPE> to the Harmony Core CodeGen extensions library.
• This version of CodeGen was built with Synergy/DE 11.1.1 and requires a minimum of version 10.1.1 to operate.

CodeGen 5.4.3

CodeGen Release Notes

• We added a new structure expression token <IF STRUCTURE_PII_FIELDS> that indicates whether any field in a structure has been tagged as containing PII data.
• We added a new field loop expression token <IF PII_SCRUB> that indicates whether a field has been tagged as containing PII data and a new field loop expansion token <FIELD_PII_TYPE> which inserts the type of PII data a field contains.
• We added a new field loop expression token <IF USED_IN_RELATION>.
• We added a new custom field loop expression token <IF HARMONYCORE_CUSTOM_FIELD> and a new custom field loop expansion token <HARMONYCORE_CUSTOM_FIELD_TYPE> to the Harmony Core extensions assembly.
• We added a new tag loop expansion token <TAGLOOP_FIELD_SNTYPE> and relation key segment loop expansion token <LITERAL_SEGMENT_SNTYPE>.
• As the Symphony Framework is no longer maintained by Synergex and is no longer an open source development effort, we no longer distribute the Symphony Framework CodeGen Extensions assembly with CodeGen. CodeGen continues to support custom extensions and the Symphony Framework extensions can be added back by any Synergy developer with the necessary Synergy .NET development tools.
• This version of CodeGen was built with Synergy/DE 11.0.3 and requires a minimum of version 10.1.1 to operate.

CodeGen 5.4.2

CodeGen Release Notes

• IMPORTANT: We updated the minimum required version of the .NET Framework from 4.5.2 to 4.7.2 so you may need to apply an update before installing this version. For information on how to check the .NET Framework version click HERE. Do download a new version of the .NET Framework click HERE.
• We altered the way that <FIELD_MINVALUE> works for required decimal and integer fields. Previously if a field did not allow negative values then the 0 would be returned even if the field was marked as required. Now if a field is marked as required a minimum value of 1 is returned.
• We added three new custom relation loop expressions <IF TO_ONE>, <IF TO_MANY> and <IF REQUIRES_MATCH> to the Harmony Core extensions assembly.
• We enhanced the CreateFile utility by adding the ability to create and optionally load data into multiple ISAM or RELATIVE data files based on instructions defined in a JSON file.
• We added a new field loop expansion token <FIELD_LDESC2>.
• There were no Symphony Framework CodeGen Extensions changes in this release.
• This version of CodeGen was built with Synergy/DE 11.0.3 and requires a minimum of version 10.1.1 to operate.

CodeGen 5.4.1

CodeGen Release Notes

• We added a new command line option -smcstrs that allows you to determine the list of structures to be processed as all structures listed in a Synergy Method Catalog export file.
• We corrected an error that was causing incorrect file details to be returned when the file overrides (-fo) option was used in conjunction with the multiple structures (-ms) mode and when a structure being processed was assigned to more than one file definition. The -fo option was being ignored and the first assigned file was always being returned.
• We changed the behavior of the parameter loop expansion token <PARAMETER_SAMPLE_DATA> to make it not escape double quote characters with backward slash characters and we added a new token <PARAMETER_SAMPLE_DATA_ESCAPED> to allow the previous behavior to be retained.
• We added a new method loop expression token <IF STRUCTURE_PARAMETERS> that allows you to determine whether the method being processed has any structure parameters.
• There were no Symphony Framework CodeGen Extensions changes in this release.
• This version of CodeGen was built with Synergy/DE 11.0.2 and requires a minimum of version 10.1.1 to operate.

CodeGen 5.4.0

CodeGen Release Notes

• We added support for custom interface, method and parameter loop expansion and expression tokens.
• We added a new method parameter loop expression token <IF DATEORTIME>.
• We added new method loop expression tokens <IF IN>, <IF INOUT>, <IF IN_OR_INOUT>, <IF OUT>, <IF OUT_OR_INOUT>, <IF RETURNS_DATA> and <IF VOID_SUBROUTINE>.
• We added a new parameter loop expansion tokens <PARAMETER_NUMBER> and <PARAMETER_SAMPLE_DATA>.
• We added new parameter loop expression tokens <IF MORE_IN_OR_INOUT> and <IF MORE_OUT_OR_INOUT>.
• We added a new custom method loop expansion token <HARMONYCORE_BRIDGE_RETURN_TYPE> and a new custom parameter loop expansion token <HARMONYCORE_BRIDGE_PARAMETER_TYPE> to the Harmony Core extensions assembly.
• We altered the mechanism by which we ensure that the <FIELD_SQLNAME> token produces unique field names when the underlying field names differ only by the position of underscore characters. We previously appended one or more $ characters to the end of resulting duplicate field names. We now append "2", "3", "4" and so on to the end of duplicate names.
• We enhanced debug logging to display a list of all defined values that were set via the -define command line option.
• When using the CodeGen API programatically we changed the CodeGenTaskSet.SaveToFile() and CodeGenTaskSet.LoadFromFile() methods to save to and load from a JSON formatted file instead of the previous XML formatted file. We believe that the only impact of this change will be if you are using the CodeGen API (instead of the CodeGen command line interface) to generate your code, and we are not aware of anyone doing that. If you are impacted by this change please contact Synergex for assistance.
• We added a new command line option -save which causes CodeGen to save the configuration options used to generate code to a JSON formatted code generation instructions file.
• We added a new command line option -input which allows a previously saved code generation instructions file re-executed in order to repeat the same code generation process that was previously used.
• We added a new optional utility application named the Harmony Core Generator utility. This desktop application is only installed if the optional Harmony Core Extensions are selected during installation, and can be used to simplify the code generation process when developing RESTful web services with the Harmony Core framework.
• When processing xfServerPlus method catalog export files via the -smc command line option we added a check for old (pre V8.3) method catalog export files which don't contain values for the now required "routine name" property for each method. If you encounter an old method catalog export file it can be converted to the latest format by importing and exporting using the Method Definition Utility.
• There were no Symphony Framework CodeGen Extensions changes in this release.
• This version of CodeGen was built with Synergy/DE 11.0.2 and requires a minimum of version 10.1.1 to operate.

CodeGen 5.3.16

CodeGen Release Notes

• We moved the <IF ONE_TO_MANY>, <IF ONE_TO_ONE>, <IF ONE_TO_MANY_TO_ONE>, <IF ONE_TO_ONE_TO_ONE> and <IF MANY_TO_ONE_TO_MANY> relation loop expression tokens out of the main CodeGen product and into the Harmony Core CodeGen Extensions assembly. These expression tokens have become pretty specific to Harmony Core use cases so we thought it more appropriate to ship and document them there.
• In the Harmony Core Customization File we changed CustomRelationNames to CustomRelations and we added additional information about each relation.
• In the Harmony Core custom extensions code we improved the logic that determines the type of relation being processed.
• There were no Symphony Framework CodeGen Extensions changes in this release.
• This version of CodeGen was built with Synergy/DE 10.3.3g and requires a minimum of version 10.1.1 to operate.

CodeGen 5.3.15

CodeGen Release Notes

• We no longer remove $ characters during PascalCase and camelCase processing.
• We now ensure that duplicate SqlName values can not be produced if the names of two or more fields in a structure differ only by the placement of underscore characters. To ensure uniqueness we append $ character(s) to the end of the names.
• We added a new custom relation loop expansion tokens <HARMONYCORE_RELATION_NAME> and <HARMONYCORE_FROM_RELATION_NAME> to the Harmony Core extensions assembly.
• We added a new mechanism to allow for the customization of various Harmony Core extensions via an optional file named HarmonyCoreCustomization.json which can be placed in the templates folder.
• We added a new key segment loop expansion token <SEGMENT_TAG_VALUE> and a new key segment loop expression token .
• We fixed an issue in the RpsInfo utility that could cause it to crash if the repository environment variables were incorrectly configured. Now the utility should report "Failed to open repository".
• There were no Symphony Framework CodeGen Extensions changes in this release.
• This version of CodeGen was built with Synergy/DE 10.3.3g and requires a minimum of version 10.1.1 to operate.

CodeGen 5.3.14

CodeGen Release Notes

• We added a new extensions assembly containing custom expansion and expression tokens used when developing with Harmony Core.
• We added a new field loop expression token <IF FIRST_UNIQUE_KEY_SEGMENT>.
• There were no Symphony Framework CodeGen Extensions changes in this release.
• This version of CodeGen was built with Synergy/DE 10.3.3f and requires a minimum of version 10.1.1 to operate.

CodeGen 5.3.13

CodeGen Release Notes

• We added a new generic expansion token <TIMEZONE_OFFSET>.
• We added support for Custom Key Segment Loop Expressions.
• There were no Symphony Framework CodeGen Extensions changes in this release.
• This version of CodeGen was built with Synergy/DE 10.3.3f and requires a minimum of version 10.1.1 to operate.