Merge pull request SkylineCommunications#28 from EmirVarupa/main

Updated SLC Main version for Ziggo Incident Creator Application

Author: MariekeGO

connector_help/connector-help/Ziggo_Incident_Creator_Application.md

@@ -6,23 +6,38 @@ uid: Connector_help_Ziggo_Incident_Creator_Application
 
 Ticketing System for USMS tickets and trigger IVR.
 
-## About
-
 This connector will automatically create tickets based on correlated alarms. It also allows the operator to manually create tickets on existing alarms and even close them. The connector will list all created tickets and update their status from RSS feeds.
 
-USMS tickets are forwarded towards Ziggo USMS Ticket Gateway connector and IVR is sent to Ziggo IVR Gateway connector.
+USMS tickets are forwarded towards the Ziggo USMS Ticket Gateway connector and IVR is sent to Ziggo IVR Gateway connector.
+
+## About
 
 ### Version Info
 
-| **Range** | **Description** | **DCF Integration** | **Cassandra Compliant** |
-|------------------|-----------------|---------------------|-------------------------|
-| 1.0.0.x          | Initial version | No                  | Yes                     |
+| Range              | Key Features                         | Based on | System Impact |
+|--------------------|--------------------------------------|----------|---------------|
+| 1.0.0.x [Obsolete] | Initial version                      | -        | -             |
+| 1.0.1.x [SLC Main] | Connector is now Cassandra-compliant | -        | -             |
+
+### Product Info
+
+| Range   | Supported Firmware |
+|---------|--------------------|
+| 1.0.0.x | -                  |
+| 1.0.1.x | -                  |
+
+### System Info
+
+| Range   | DCF Integration | Cassandra Compliant | Linked Components | Exported Components |
+|---------|-----------------|---------------------|-------------------|---------------------|
+| 1.0.0.x | No              | No                  | -                 | -                   |
+| 1.0.1.x | No              | Yes                 | -                 | -                   |
 
-## Installation and configuration
+## Configuration
 
-### Creation
+### Connections
 
-#### Virtual connection
+#### Virtual Connection
 
 This connector uses a virtual connection and does not require any input during element creation.
 
@@ -34,11 +49,11 @@ For each Gateway element, you need to configure the DMA ID and element ID on the
 
 On the **Ticket** page, the IP of the **RSS Feed Server** must be configured and an **RSS Refresh Time** must be set. This will update the **Ticket Table** with the info from the RRS feeds every x minutes. The **Resolved TTL** defines the time to live for each resolved ticket before it is deleted from the Ticket Table.
 
-## Usage
+## How to Use
 
 ### Tickets
 
-The **Ticket** **Table** shows an overview of all alarms and the associated created tickets. It also contains tickets from the RSS feed server (if configured).
+The **Ticket Table** shows an overview of all alarms and the associated created tickets. It also contains tickets from the RSS feed server (if configured).
 
 **Tickets stats** provides an overview of all ticket info grouped by platform. The TOTAL row contains statistics for all platforms.
 
@@ -54,26 +69,26 @@ A template can have multiple linked tasks. These are available in the **Template
 
 ### Remote Element Config
 
-This page allows the configuration of the remote Gateway connectors (see "Installation and Configuration" section above).
+This page allows the configuration of the remote Gateway connectors (see [Configuration of Remote Elements](#configuration-of-remote-elements)).
 
 ### Source Tables
 
-Within this page it is possible to find all the tables used to build the Tree Control seen in the **Tree Control Overview** page.
+This page displays the tables used to build the tree control on the **Tree Control Overview** page.
 
-All tables are filled in automatically apart from the last one - **Time Window Table**. For this one, a button (Add...) is available in the **Tree Control Overview** page, where it is possible to set the start and end times for the time window, severity and platform.
+Apart from the Time Window Table, the tables are filled in automatically. For the **Time Window Table**, you can use the **Add** button on the **Tree Control Overview** page. You will then need to set the start and end time for the time window, the severity and the platform.
 
-The **Platform** table is filled in with the values found in the Element Properties (Platform Dashboard).
+The **Platform** table is filled in with values found in the element properties (Platform Dashboard).
 
-Note: for the **Start Time** and **End Time**, only the hour and minute matter but, it is important to choose also a day in the Start Time so that the **Day of the Week** can be filled in accordingly.
+Note: for the **Start Time** and **End Time**, only the hour and minute matter. However, it is important to also choose a day for the Start Time, so that the **Day of the Week** can be filled in accordingly.
 
 ### Tree Control Overview
 
-This tree control follows the next hierarchy (4 tables and relations between them):
+This tree control follows this hierarchy (4 tables and relations between them):
 
-1. Platform (detect from list of values in element property);
-2. Severity (4 level: warning, minor, major, critical);
-3. day of the week (7 days: monday, tuesday, wednesday, thursday, friday, saturday, sunday);
-4. time window: (possibly) multiple time windows during which the time in which auto ticketing is allowed ( in form hh:mm-hh:mm).
+1. Platform (detected from list of values in element property).
+1. Severity (4 levels: warning, minor, major, critical).
+1. Day of the week (7 days: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday).
+1. Time window: One or more time windows during which auto-ticketing is allowed (in the format hh:mm-hh:mm).
 
 ### Close Incident Overview
 
@@ -89,7 +104,7 @@ This tree control follows the next hierarchy (4 tables and relations between the
 
 #### Closing Configuration
 
-There is the possibility to enable **Detailed Logging** in the **Create and Close Config** page**.** If this setting is enabled, the connector is profiding you with all information of the flow of the connector in the logging of the element. If you disable this toggle button, only errors will be logged.
+You can enable **Detailed Logging** on the **Create and Close Config** page. If this setting is enabled, the connector will provide you with all information of the flow of the connector in the logging of the element. If you disable this toggle button, only errors will be logged.
 
 ## Notes