Added <IF STRUCTURE_DISPLAY_FIELD>

Author: SteveIves

CodeGenEngine/ExpressionEvaluators/ExpressionEvaluatorStructure.dbl

@@ -67,6 +67,7 @@ namespace CodeGen.Engine
             structureExpressionEvaluators.Add("FILE_STATIC_RFA", evaluateFileStaticRfa)
             structureExpressionEvaluators.Add("FILE_STORED_GRFA", evaluateFileStoredGrfa)
             structureExpressionEvaluators.Add("FILE_TERABYTE", evaluateFileTerabyte)
+            structureExpressionEvaluators.Add("STRUCTURE_DISPLAY_FIELD", evaluateStructureDisplayField)
             structureExpressionEvaluators.Add("STRUCTURE_KEYS", evaluateStructureKeys)
             structureExpressionEvaluators.Add("STRUCTURE_LDESC", evaluateStructureLongDesc)
         endmethod
@@ -150,6 +151,16 @@ namespace CodeGen.Engine
             mreturn evaluateStructureExpression(tkn, template, loops, doEvaluate)
         endmethod
 
+        private static method evaluateStructureDisplayField, boolean
+            tkn, @Token 
+            template, @FileNode 
+            loops, @IEnumerable<LoopNode> 
+            endparams
+        proc
+            lambda doEvaluate(str) (!String.IsNullOrWhiteSpace(str.DisplayField))
+            mreturn evaluateStructureExpression(tkn, template, loops, doEvaluate)
+        endmethod
+
         private static method evaluateStructureKeys, boolean
             tkn, @Token 
             template, @FileNode 

CodeGenEngine/Tokenizer.dbl

@@ -1008,6 +1008,7 @@ namespace CodeGen.Engine
             expressions.Add("STRUCTFIELD",                      TokenValidity.FieldLoop | TokenValidity.KeySegmentLoop | TokenValidity.RelationSegmentLoop)
             expressions.Add("STRUCTURE",                        TokenValidity.ParameterLoop)
             expressions.Add("STRUCTURE_ASCII",                  TokenValidity.Anywhere)
+            expressions.Add("STRUCTURE_DISPLAY_FIELD",          TokenValidity.Anywhere)
             expressions.Add("STRUCTURE_FILES",                  TokenValidity.Anywhere)
             expressions.Add("STRUCTURE_HAS_UNIQUE_KEY",         TokenValidity.Anywhere)
             expressions.Add("STRUCTURE_HAS_UNIQUE_PK",          TokenValidity.Anywhere)

Documentation/CodeGen.chm

@@ -9,50 +9,55 @@ This document defines the procedure for distributing a new release of CodeGen on
 
 3.  Build new HTML help and Web help files.
 
-4.  Commit but DO NOT PUSH the documentation change to GitHub with a comment of "Updated documentation in preparation for X.Y.Z release."
+4.  Commit AND PUSH the Windows help file to GitHub with a comment of "Updated help file in preparation for X.Y.Z release."
 
 5.  Build everything in RELEASE mode.
 
-6.  Build and a new installation.
+6.  Build a new local (unsigned) installer.
 
 7.  Install the new version from the local MSI and run as many tests as possible.
 
 8.  Uninstall the locally built (unsigned) version.
 
-9.  Push the "Updatad documentation" commit to GitHub - this will fire the CICD pipeline.
+9.  Push the "Updatad documentation" commit to GitHub.
 
-10. Verify that the CICD pipeline completes without errors or warnings.
+10. Run the Azure DevOps CICD pipeline and verify that it completes successfully.
+    (https://synergexdev.visualstudio.com/Development/_build?definitionId=149)
 
-11. Download the signed installer to the release history folder.
+11. Download the signed installer and place it in the release history folder.
+
+12. Install the signed version locally.
 
 12. Do the release on GitHub.
 
-13. Upload web help files to the web site.
+13. Commit AND PUSH the web help files in the "docs" folder with a comment of "Updated web help for X.Y.Z release.".
 
 14. Bump the version number in CurrentRelease.xml
 
-15. Commit BUT DO NOT PUSH the changes to CurrentRelease.xml to GitHub with a comment of "Announced version X.Y.Z to check for update."
+15. Commit AND PUSH the changes to CurrentRelease.xml to GitHub with a comment of "Announced version X.Y.Z to check for update."
 
 --------------------------------------------------------------------------------
 PREPARE TRUNK FOR NEXT VERSION
 
-1.  Edit CodeGenEngine\codegen.def and bump the version number.
+1.  Edit azure-pipelines.yml and bump the version number.
+
+2.  Edit CodeGenEngine\codegen.def and bump the version number.
 
-2.  Edit CodeGenSetup\product.wxs
+3.  Edit CodeGenSetup\product.wxs
      - Bump the product version number string
 	 - Generate and implement a new product id GUID (DO NOT change the UpgradeCode GUID)
 
-3.  Edit Project Properties for the CodeGenSetup project and change the version number in the Output Name field.
+4.  Edit Project Properties for the CodeGenSetup project and change the version number in the Output Name field.
 
-4.  Create a new folder under releases and record the new GUID in a text file.
+5.  Create a new folder under releases and record the new GUID in a text file.
 
-5.  Use the SetAssemblyFileVersion utility to bump the version number in all AssemblyInfo files.
+6.  Use the SetAssemblyFileVersion utility to bump the version number in all AssemblyInfo files.
 
-6.  Edit azure-pipelines.yml and change the version number in the currentVersion property.
+7.  Edit azure-pipelines.yml and change the version number in the currentVersion property.
 
-7.  Add a new section to the Release notes section of the documentation and build a new HTML help file.
+8.  Add a new section to the Release notes section of the documentation and build a new HTML help file.
 
-8.  Commit and push to GitHub the version number changes with a comment of "Bumped version to X.Y.Z for next release.".
+9.  Commit AND PUSH to GitHub the version number changes with a comment of "Bumped version to X.Y.Z for next release.".
 
 --------------------------------------------------------------------------------
 UPDATE GITHUB ISSUES