Merge pull request #6 from Bertievh/main

Version 21.1.5 document updates

Author: rweesner

docs/index.md

@@ -5,7 +5,7 @@ sidebar_label: 'EasyVista Connector'
 
 # EasyVista Connector
 
-Latest version of the EasyVista Connector is **21.0.4**.
+Latest version of the EasyVista Connector is **21.1.5**.
 
 The EasyVista Connector can be used to submit incident tickets automatically to EasyVista from OpCon when a task has an error condition.
 

docs/installation.md

@@ -71,7 +71,7 @@ Property Name | Value
 **ADDRESS**                         | The server address of the OpCon API.
 **PORT**                            | The port number used by the OpCon API server.
 **USES_TLS**                        | Must be set to True.
-**TOKEN**                           | An application token used for Authentication when communicating with the OpCon-API. 
+**TOKEN**                           | An application token used for Authentication when communicating with the OpCon-API. This should be encrypted using the Except.exe software.
 **[TICKET DEFINITIONS]**            | header - Used to define information to be used when creating a ticket.
 **DESCRIPTION**                     | The text that is used when creating an incident (description field). Default value  OpCon Task Failure ( date {0} schedule {1} job {2} server {3} error code {4} ). The text is customizable. When a value is required in the text use the {n} syntax  where n is the value of the parameter defined in the table below. 0 is the schedule date when the error occurred (resolves to [[$SCHEDULE DATE-EVIS]] value), 1 is the workflow name (resolves to [[JI.SCHED]] value), 2 is the task name (resolves to [[JI.JOB]] value), 3 is the server name where the job executed (resolves to [[JI.MACH]] value) and 4 is the termination code (resolves to [[JI.ECODE]] value). 
 **TITLE**                           | The text that is used when creating an incident (description field). Default value  OpCon Task Failure (schedule {1} job {2}) The text is customizable. When a value is required in the text use the {n} syntax  where n is the value of the parameter defined in the table below. 0 is the schedule date when the error occurred (resolves to [[$SCHEDULE DATE-EVIS]] value), 1 is the workflow name (resolves to [[JI.SCHED]] value), 2 is the task name (resolves to [[JI.JOB]] value), 3 server name where the job executed (resolves to [[JI.MACH]] value) and 4 the termination code (resolves to [[JI.ECODE]] value).

docs/release-notes.md

@@ -4,6 +4,17 @@
 
 This release of EasyVista is for opCon System 21.0 or greater. The connector only supports connections to the OpCon-API to retrieve job information and insert or update Incident information. 
 
+## Release 21.1.5
+
+### Migration Considerations
+
+When upgrading to the latest release the TOKEN value of the OPCON API section in the Connector.config file should be encrypted using the Exncrypt.exe software .
+
+### New Features
+
+**CON-370**    
+                    Implemented the encryption of the TOKEN value in the Connector.config using the Excrypt.exe software
+                     
 ## Release 21.0.4
 
 ### Migration Considerations