Release 23.2 Doc updates

docs/index.md

@@ -7,7 +7,7 @@ sidebar_label: 'OpCon Deploy'
 
 OpCon Deploy is a separate application working on a central repository that contains the schedule definitions, transformation rules, and all the required configuration information to deploy the schedule definitions between OpCon environments in a controlled and consistent manner.
 
-The current version is **23.1**.
+The current version is **23.2**.
 
 ## Overview
 

docs/installation.md

@@ -136,7 +136,7 @@ Complete the procedures in this section to install a new OpCon Deploy Server:
    * Select the X (This feature will not be available.) option from the drop-down.
 11. Click Next.
 12. Enter the definitions for the ImpEx2 Server:
-   * OpCon database server name (If a MS SQL instance is being used, enter ```<servername>\<instancename>```)
+   * OpCon database server name (If a MS SQL instance is being used, enter ```<servername>\<instancename>```, if TLS for database connection, add ***;TrustServerCertificate=True*** name)
    * OpCon database name
    * OpCon database login ID
    * OpCon database login ID password
@@ -381,6 +381,28 @@ web.port=9001
 #
 system.debug=false
 
+```
+### Sample Deploy Server Configuration File using TLS SQL Server connection
+
+```
+#
+# OpCon server connection information
+#
+opcon.server.name=EC2AMAZ-2QV0RKO
+opcon.db.name=OPCONXPS;TrustServerCertificate=True
+opcon.db.user=opconsam
+opcon.db.password=sYnk3bzpZybGPbSOrhsr4g==
+opcon.db.using.winauth=true
+opcon.db.connection.max=10
+#
+# REST server configuration
+#
+web.port=9001
+#
+# Logger configuration
+#
+system.debug=false
+
 ```
 ## Deploy Database Backup Scripts
 

docs/release-notes.md

@@ -4,6 +4,29 @@ sidebar_label: 'Release notes'
 
 # OpCon Deploy Release Notes
 
+The Deploy Client is not paired with a specific OpCon Release. 
+
+There are no Deploy patch releases as corrections are applied to the main software and a new version is released on a regular basis.  
+
+Deploy contains compatibility checks to ensure that features supported in newer OpCon Releases are not deployed to older opCon Releases.
+
+The ImpEx2 Server portion of Deploy is paired with each specific OpCon release and is part of the OpCon Release. The ImpEx2 
+server for each release are patched and released within the OpCOn release cycles.   
+
+## Version 23.2
+
+2024 August
+
+:eight_spoked_asterisk: **OPCDEPLOY-1380**: Fixed a problem during deployment when checking if the deployment has a previous deployment failure.
+
+:eight_spoked_asterisk: **OPCDEPLOY-1382**: Fixed a problem during package creation when newly selected schedule versions are removed from the selection list when the Refresh button is selected to search for schedule versions to include in the package.
+
+:eight_spoked_asterisk: **OPCDEPLOY-1383**: Updated database scripts to support SQL-Azure.
+
+:eight_spoked_asterisk: **OPCDEPLOY-1384**: Added a .l4j.ini file for the Deploy client increasing the JVM heap size to prevent heap memory thrashing when very large definitions are being deployed. 
+
+:eight_spoked_asterisk: **OPCDEPLOY-1385**: Fixed a partial update of resource/threshold names during transformation of Threshold Update resources.. 
+
 ## Version 23.1
 
 2024 May

docs/transformations/transformation-rules.md

@@ -155,7 +155,9 @@ It must be noted that wild cards are not supported, instead the text entered in
     * IBMi_Inquiry_Message_Reply
     * Job_Instance_Property
     * Job_Machine_Group_Name
+    * Job_Machine_Group_Name_to_Machine_Name
     * Job_Machine_Name
+    * Job_Machine_Name_to_Machine_Group_Name
     * Job_Name
     * Job_Tag
     * MCP_Arguments