Merge pull request #22 from Bertievh/main

Deploy 25.1 documentation updates

Author: rweesner

docs/administration/settings.md

@@ -57,10 +57,16 @@ When enabled, this rule will split the deployment of schedules and scripts.
 * Script definitions are no longer imported into the Deploy database during schedule import.
 * Script definitions are no longer deployed along with schedules / packages.
 
-When using this rule, script definitions must be imported and deployed separately using the SCripts Menu. Schedule definitions will only contain a reference to an embedded script in job definition.
+When using this rule, script definitions must be imported and deployed separately using the Scripts Menu. Schedule definitions will only contain a reference to an embedded script in job definition.
 There is also no attempt made to ensure that version numbers are consistent across OpCon systems.
 It is therefore up to the users to ensure that a script and its version is available during the deployment process. If the script, runner or version is not available in the target OpCOn database, the deployment will terminate with an appropriate error message.
 
 As the version numbering may be inconsistent across OpCon systems, it is suggested that the 'Latest Version' is used in the embedded script job definition.
 
-When the Script_Name transformation rule is used, the users must ensure that the required script is available in the script repository of target OpCon database. 
+When the Script_Name transformation rule is used, the users must ensure that the required script is available in the script repository of target OpCon database. 
+
+### Exclude calendars from Schedule Deployment
+
+When enabled, this rule will prevent calendar updates during the deployment of schedules / packages. 
+* Calendar definitions are no longer imported into the Deploy database during schedule import.
+* Calendar definitions are no longer deployed along with schedules / packages.

docs/batch-devops-integration.md

@@ -100,6 +100,13 @@ Devops.SMAOpConDeployClient.exe supports the following arguments:
 
 * Optional argument required for script EXPORT action. Defines the version of the script to export.
 
+**-iss**	
+
+* Optional argument for schedule EXPORT action. Extracts all sub-schedules associated with the named schedule and creates a single definition file containing all schedule definitions.
+
+**-noi**	
+
+* Optional argument for schedule and script EXPORT action. When present does not insert the exported definition into the Deploy database.
 
 ## Examples
 

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 **25.0**.
+The current version is **25.1**.
 
 ## Overview
 

docs/release-notes.md

@@ -14,11 +14,42 @@ Deploy contains compatibility checks to ensure that features supported in newer
 The ImpEx2 Server portion of Deploy is paired with each specific OpCon release and is part of the OpCon Release. Therefore the ImpEx2 
 server for each release is patched and released within the OpCon release cycles.   
 
+## Version 25.1
+
+2025 March
+
+**Migration Considerations**
+
+New rule **Exclude calendars from schedule deployment** removes calendar updates during the deployment process. The default value for the rule is false, so it will not have an impact on existing installations. Once this rule is enabled, the calendar definitions will no longer be included in the schedule definitions in the **calendarList** section.
+
+**New Features**
+
+:eight_spoked_asterisk: **OC-325**: Support new job type RPA. Due to the specific nature of the RPA scripts being associated with specific agents, the deploy process does not include the scripts in the deployment process.
+
+This requires 25.1.0 or greater.
+
+:eight_spoked_asterisk: **OPCDEPLOY-1398**: Added new fields on 'CheckInSummary' screen during schedule Import process to allow for the creation of a package from the selected schedules. The existing checkbox **Include Sub-Schedules** can be used to extract all sub-schedules associated with the selected schedules and included in the package.
+- **Create Package from Schedules** When selected creates a package from the list of imported schedules (requires Package Name).
+- **Package Name**                  The name of  the package to create.  
+
+:eight_spoked_asterisk: **OPCDEPLOY-1403**: Implemented new a new feature to prevent the update of calendars during the deployment process. 
+When this feature is enabled, calendars are no longer included in the schedule import and deployment processes. 
+
+For more information see **Exclude calendars from Schedule Deployment** rule in **settings** section.
+
+:eight_spoked_asterisk: **OPCDEPLOY-1405**: Added new argument '-noi' to Devops.SMAOpConDeployClient.exe client for the schedule and script EXPORT action. This option will prevent the exported schedule or script from being inserted into the Deploy database during the EXPORT action.
+
+:eight_spoked_asterisk: **OPCDEPLOY-1406**: Added new argument '-iss' to Devops.SMAOpConDeployClient.exe client for the schedule EXPORT action. This option will include all sub-schedules associated with the named schedule creating a single definition file containing all the schedules.
+
+**Fixes**
+
+:eight_spoked_asterisk: **OPCDEPLOY-1404**: Fixed a problem when using the Devops.SMAOpConDeployClient.exe client to deploy a schedule containing embedded scripts. During the deployment process the schedule and scripts are inserted into the Deploy database. When inserting the scripts into the Deploy database, a check for missing script versions is performed causing the NPE as there is no source OpCon system (source is DevOps repository). 
+
 ## Version 25.0
 
 2025 January
 
-**Migration COnsiderations**
+**Migration Considerations**
 
 This release of Deploy requires matching OpCon versions 25.0.0 and version 23.0.9 and 22.0.20. A special ImpEx2 patch for opCon 22.0.19 can be requested from support.
 

docs/schedules.md

@@ -29,9 +29,10 @@ Once Next has been selected, the list of schedules will be retrieved from the ch
 ![Schedule Import Schedule Selection Image](../static/img/schedule-import-schedule-selection.png)
 
 Once Next has been selected, the selected schedule(s) will be displayed in the Schedule Import (Summary) dialog appears. This provides a summary of your selections, allows selection of import options and allows a description to be added to the import process.
-Supported IMport Options:
+Supported Import Options:
 - **Refresh SAP Job Definitions** indicates if OpCon SAP R3 jobs are encountered in the schedule, then the SAP server job definitions should be extracted from the SAP server (otherwise, uses values in 13100 and 13101 records).
 - **Include Sub-Schedules** indicates if container jobs are encountered in the schedule, the associated sub-schedule should be included in the import process. The schedules are checked recursively and each sub-schedule is imported as a separate schedule. The result of all schedule imports is displayed in the results message.
+- **Create Package from Schedules** indicates if a Deploy package should be created from the list of schedules. If selected, a package will be created using the **Package Name** field. If the package exists, a package update will be performed creating a new version of the package with the new schedule definition or the current schedule definition if the schedule version is already defined in the Deploy database.
 
 ![Schedule Import Summary Image](../static/img/schedule-import-summary.png)