Merge pull request #471 from ritza-co/19.07.02

Docs 19.07.02 release (Week 35, 2025)

Author: sixhobbits

docs/auto-discovery/load-balancer-f5-autodiscovery.mdx

@@ -14,6 +14,8 @@ To get started, first [create and run an SNMP job](network-auto-discovery.mdx) t
 
 Device42 discovers Cisco ASA, Cisco UCS, NetScaler, and cluster devices via their native APIs. Devices from A10 Networks should also produce good output using SNMP. 
 
+Citrix NetScaler load balancer API discovery is used to build TCP or UDP connections within application groups. NetScaler discovery will not add new devices and resources to the system. New devices and resources are typically added via SNMP scans. 
+
 ## Load Balancer Discovery
 
 ### Prerequisites
@@ -47,7 +49,7 @@ To discover UCS or other cluster devices, select **UCS** from the **Platform** d
 1. Give your job a meaningful, descriptive name and specify the server hostnames, IP addresses, IP ranges, or CIDR blocks for your cluster devices.
 2. Choose a Remote Collector (RC) if desired, specify the correct port, and select or unselect the SSL option as needed
 3. Choose one or more sets of credentials that will allow Device42 to authenticate and query your UCS/Cluster devices.
-4. Set other options (explained below) as needed, ceate a schedule if desired, and save your job.
+4. Set other options (explained below) as needed, create a schedule if desired, and save your job.
 5. Select **Run now** from the list page to run the discovery job now.
 
 Visit the [dedicated Cisco UCS / ACI discovery docs page](cisco-ucs-auto-discovery.mdx) for more information.
@@ -103,7 +105,7 @@ After saving, you can select the **Run Now** option to run the job immediately.
   }}
 />
 
-Newly created jobs will not run on the first day they are created to prevent an unintentionally large amount of jobs from running initially. If you want to run a job after its initial creation, select **Run Now** from the autodiscovery list page.
+Newly created jobs will not run on the first day they are created to prevent an unintentionally large number of jobs from running initially. If you want to run a job after its initial creation, select **Run Now** from the autodiscovery list page.
 
 <ThemedImage
   alt="Run now option on list page"

docs/integration/external-integrations/freshservice-integration/customize-freshservice.mdx

@@ -72,7 +72,7 @@ Let's take a closer look at the attributes and elements of the `<task>` elements
     <task enable="false" name="Products" type="product" description="Copy Product info from Device42 to Freshservice" d42_min_version="16.19.00">
     ```
 
-    Note that if you turn off a task that has `asset` or `asset_relationship` as its corresponding Freshservice type (for example, devices, business apps, and resources in Device42), you'll need to find and remove its corresponding query snippet in the `Delete` cleanup tasks. For an example, see [this answer in the FAQ section](#how-do-i-prevent-a-relationship-between-two-device42-asset-types-from-syncing-to-freshservice).
+    Note that if you turn off a task that has `asset` or `asset_relationship` as its corresponding Freshservice type (for example, devices, business services, and resources in Device42), you'll need to find and remove its corresponding query snippet in the `Delete` cleanup tasks. For an example, see [this answer in the FAQ section](#how-do-i-prevent-a-relationship-between-two-device42-asset-types-from-syncing-to-freshservice).
 
 - `name`: You can edit the task name. Task names appear in the [integration app's **Data Mapping Chart**](#data-mapping-between-device42-and-freshservice).
 - `type`: Holds the [Freshservice classification](https://api.freshservice.com/) of the data. The valid types are:
@@ -112,15 +112,15 @@ Typically, the first `<field>` represents the Device42 data returned from the qu
 - `resource`: The same as the `target` value.
 - `source-type`: Not functionally critical; this provides the data type displayed on the [integration app's **Data Mapping Chart**](#data-mapping-between-device42-and-freshservice).
 - `target`: The Device42 field to be mapped to Freshservice. The Freshservice convention is to use the display name in snake case, occasionally with the ID of the asset type as a suffix. For example, `memory_max_usage` and `memory_reservation_used`. The sync process determines the ID. Please look up which target field names to use in the [Freshservice API documentation](https://api.freshservice.com/). 
-- `escape`: This is used on field elements where `target="name"`. Some characters used in Device42 names aren't supported in Freshservice and need to be substituted. When creating a new task, you can set this to `true` but disable it if mismatching issues occur.
+- `escape`: This is used on field elements where `target="name"`. Some characters used in Device42 names aren't supported in Freshservice and need to be substituted. When creating a new task, you can set this to `true`, but disable it if mismatching issues occur.
 
 :::tip
 Use our InsightsAI chat under **Analytics > InsightsAI** to interpret DOQL query snippets quickly in the context of the Device42 data tables.
 :::
 
 ### Additional Matching Criteria for Updating Existing Items
 
-Some `<task>` elements in `mapping.xml` have a helper `<matching>` element for updating synched data that currently exists in Freshservice but may have slightly different name formats. For example, asset-type syncing tasks include the `<matching>` element to determine which query fields are used to match which asset attributes when trying to find a match. For example:
+Some `<task>` elements in `mapping.xml` have a helper `<matching>` element for updating synced data that currently exists in Freshservice but may have slightly different name formats. For example, asset-type syncing tasks include the `<matching>` element to determine which query fields are used to match which asset attributes when trying to find a match. For example:
 
 <details>
   <summary>Click to expand the code block</summary>
@@ -190,7 +190,7 @@ For a quick look at all the valid Freshservice `types`, see the [The `<task>` El
 | Copy AWS EBS from Device42 to Freshservice | asset | 19.04.00 |  |
 | Copy AWS Key Pair from Device42 to Freshservice | asset | 19.04.00 |  |
 | Copy AWS S3 from Device42 to Freshservice | asset | 19.04.00 |  |
-| Copy AWS Public IP from Device42 to FreshService | asset | 19.04.10 |  |
+| Copy AWS Public IP from Device42 to Freshservice | asset | 19.04.10 |  |
 | Copy Azure VPC from Device42 to Freshservice | asset | 19.04.00 |  |
 | Copy GCP Subnet from Device42 to Freshservice | asset | 19.04.00 |  |
 | Copy GCP VPC from Device42 to Freshservice | asset | 19.04.00 |  |
@@ -213,23 +213,23 @@ For a quick look at all the valid Freshservice `types`, see the [The `<task>` El
 | Copy GCP Network Interface from Device42 to Freshservice | asset | 19.04.00 |  |
 | Copy Azure Resource Group from Device42 to Freshservice | asset | 19.04.00 |  |
 | Copy AWS Image from Device42 to Freshservice | asset | 19.04.00 |  |
-| Copy Azure Public IP from Device42 to FreshService | asset | 19.04.10 | 19.04.99 |
-| Copy Azure Public IP from Device42 to FreshService | asset | 19.05.00 |  |
+| Copy Azure Public IP from Device42 to Freshservice | asset | 19.04.10 | 19.04.99 |
+| Copy Azure Public IP from Device42 to Freshservice | asset | 19.05.00 |  |
 | Copy GCP Image from Device42 to Freshservice | asset | 19.04.00 |  |
-| Copy GCP BigQuery Table from Device42 to FreshService | asset | 19.04.10 |  |
+| Copy GCP BigQuery Table from Device42 to Freshservice | asset | 19.04.10 |  |
 | Copy Azure Key Vault from Device42 to Freshservice | asset | 19.04.00 |  |
 | Copy VMware VCenter Resource Pool from Device42 to Freshservice | asset | 19.04.10 |  |
 | Copy VMware VCenter Network from Device42 to Freshservice | asset | 19.04.10 |  |
 | Copy VMware VCenter Disk from Device42 to Freshservice | asset | 19.04.10 |  |
 | Copy VMware VCenter Datastore from Device42 to Freshservice | asset | 19.04.10 |  |
 | Copy VMware VCenter Datacenter from Device42 to Freshservice | asset | 19.04.10 |  |
-| Copy AWS K8 Pod from Device42 to FreshService | asset | 19.04.10 |  |
+| Copy AWS K8 Pod from Device42 to Freshservice | asset | 19.04.10 |  |
 | Copy AWS K8s Namespace from Device42 to Freshservice | asset | 19.04.10 |  |
 | Copy AWS K8s Deployment from Device42 to Deployment | asset | 19.04.10 |  |
 | Copy AWS K8s Service from Device42 to Service | asset | 19.04.10 |  |
 | Copy AWS K8s Daemon Set from Device42 to Daemon Set | asset | 19.04.10 |  |
-| Copy AWS K8s Replica Set from Device42 to FreshService | asset | 19.04.10 |  |
-| Copy AWS K8s Cron Job from Device42 to FreshService | asset | 19.04.10 |  |
+| Copy AWS K8s Replica Set from Device42 to Freshservice | asset | 19.04.10 |  |
+| Copy AWS K8s Cron Job from Device42 to Freshservice | asset | 19.04.10 |  |
 | Copy GCP Public IP from Device42 to Freshservice | asset | 19.04.10 |  |
 | Copy AWS K8s Config Map from Device42 to Config Map | asset | 19.04.10 |  |
 | Copy AWS K8s Stateful Set from Device42 to Stateful Set | asset | 19.04.10 |  |
@@ -315,7 +315,7 @@ Use the following steps to verify that the field name is correct:
 3. Search the returned JSON for the field label you are interested in to verify the field name. 
 
     <ThemedImage
-    alt="Business Application in Device42"
+    alt="JSON search example"
     sources={{
         light: useBaseUrl('/assets/images/freshservice-integration/verify-field-name-light.png'),
         dark: useBaseUrl('/assets/images/freshservice-integration/verify-field-name-dark.png'),
@@ -509,7 +509,7 @@ Set the `enable` attribute to `false` on those `<task>` elements:
     <task enable="false" name="Device Contract Associations" type="contract_asset" description="Create association between asset and contract">
     ```
 
-3. If you want to disable Software Licensing from being synced, find the `Copy Software Licensing info from Device42 to Freshservice` task (around line `2437`):
+3. If you want to prevent software licensing from being synced, find the `Copy Software Licensing info from Device42 to Freshservice` task (around line `2437`):
 
     ![Line 2437](/assets/images/freshservice-integration/example-vscode-6.png)
 
@@ -563,7 +563,7 @@ Set the `enable` attribute to `false` on those `<task>` elements:
     <task enable="false" name="Software In Use" type="software_installation" description="Create Software Install from Software In Use" d42_max_version="16.18.02">
     ```
 
-3. Software Licensing from Device42 syncs to `contract` in Freshservice. Find and disable the `Copy Software Licensing info from Device42 to Freshservice` task (around line `2437`):
+3. Software licensing from Device42 syncs to `contract` in Freshservice. Find and disable the `Copy Software Licensing info from Device42 to Freshservice` task (around line `2437`):
 
     ![Line 2437](/assets/images/freshservice-integration/example-vscode-6.png)
 
@@ -644,4 +644,4 @@ If you want Device42 to update `asset_state` values, set `skip-update` to `"fals
         </value-mapping>
     </field>
     ```
-    </details>
+    </details>

docs/integration/external-integrations/freshservice-integration/use-freshservice-integration.mdx

@@ -30,7 +30,7 @@ Make your way to the **Settings** tab, located on the configuration page of the
 
 Data synchronization (sync) imports new CIs and updates the existing ones within Freshservice. Locate the synced data under **Assets > Inventory** in Freshservice.
 
-You can schedule a daily sync and run the sync immediately. We recommend that you run a full sync after installing the integration app.
+You can schedule a daily sync and run the sync immediately. We recommend running a full sync after installing the integration app.
 
 [From the **Settings** tab](#find-the-settings-tab), scroll down to the **Schedule Synchronization** section. 
 
@@ -171,7 +171,7 @@ The **Contract Type** dropdown in Freshservice displays the available contract t
 
 ### Sync Purchase Line Items Types to Contracts
 
-In Device42, a Purchase Line Item is an individual entry associated with a larger Purchase (located under **Infrastructure > Purchases**). Contract Purchase Line Item sub-types include **Lease**, **Warranty**, **Subscription**, **Service**, and **In-Service**. The sub-type **(None)** is used for unspecified types:
+In Device42, a **Purchase Line Item** is an individual entry associated with a larger purchase (located under **Infrastructure > Purchases**). Contract purchase line item sub-types include **Lease**, **Warranty**, **Subscription**, **Service**, and **In-Service**. The sub-type **(None)** is used for unspecified types:
 
     <ThemedImage
     alt="PO Line Item Types in Device42"
@@ -181,13 +181,13 @@ In Device42, a Purchase Line Item is an individual entry associated with a large
     }}
     />
 
-The Purchase Line Item **Lease** and **Warranty** contract types map to the Freshservice **Lease** and **Warranty** types. The other Purchase Line Item contract types (**Service**, **In-Service**, **Subscription**, and **(None)**) are assigned to the Freshservice **Maintenance** type. 
+The purchase line item **Lease** and **Warranty** contract types map to the Freshservice **Lease** and **Warranty** types. The other purchase line item contract types (**Service**, **In-Service**, **Subscription**, and **(None)**) are assigned to the Freshservice **Maintenance** type. 
 
 ![Synced Maintenance Contract Type in Freshservice](/assets/images/freshservice-integration/maintenance-type-contracts.png)
 
-For example, this Purchase Line Item with an unspecified contract type in Device42 is synced to Freshservice as a **Maintenance** contract:
+For example, this purchase line item with an unspecified contract type in Device42 is synced to Freshservice as a **Maintenance** contract:
 
-- Purchase Line Item in Device42:
+- A purchase line item in Device42:
     <ThemedImage
     alt="Unspecified Contract Type in Device42"
     sources={{
@@ -196,7 +196,7 @@ For example, this Purchase Line Item with an unspecified contract type in Device
     }}
     />
 
-- Synced Maintenance Contract in Freshservice:
+- The synced maintenance contract in Freshservice:
 
     ![Maintenance Contract Type in Freshservice](/assets/images/freshservice-integration/line-item-example-fs.png)
 
@@ -219,36 +219,36 @@ Warranty information from Device42 is brought into Freshservice, with **Warranty
 
 ### Software Licensing Syncs to Contracts
 
-**Software Licensing** contracts in Device42 are synced to Freshservice as **Software License** contracts when a Software Component has an associated Purchase Line Item or License Count that is not null (empty).
+**Software Licensing** contracts in Device42 are synced to Freshservice as **Software License** contracts when a software component has an associated purchase line item or license count that is not null (empty).
 
 ![Software Licensing in Freshservice](/assets/images/freshservice-integration/fs-software-license.png)
 
-## Syncing Business Applications to Freshservice
+## Syncing Business Services to Freshservice
 
-Using the default mapping, **Business Applications** in Device42 are synced to Freshservice as the **Business Service** asset type. The Business Application relationships are also synced.
+Using the default mapping, **Business Services** in Device42 are synced to Freshservice as the **Business Service** asset type. The business service relationships are also synced.
 
-- In Freshservice, navigate to **Assets > Inventory** (1) and select **Business Service** as the **Asset Type** (2) to view the synced Business Applications. Click on an item to view its details.
+- In Freshservice, navigate to **Assets > Inventory** (1) and select **Business Service** as the **Asset Type** (2) to view the synced business services. Click on an item to view its details.
 
     ![Business Services in Freshservice](/assets/images/freshservice-integration/fs-business-service.png)
 
-- Click **Relationships** to see a **Mini map** of the selected Business Service. 
+- Click **Relationships** to see a **Mini map** of the selected business service. 
 
     ![Business Service Relationships in Freshservice](/assets/images/freshservice-integration/fs-business-app-mini-map.png)
 
 - When viewing the full map, you can select the **Level of Relationships** to display. 
 
     ![Business Service Full Map in Freshservice](/assets/images/freshservice-integration/fs-business-app-full-map.png)
 
-The example Business Service in Freshservice above looks like this as a Business Application in Device42:
+The example business service in Freshservice above looks like this in Device42:
 
     <ThemedImage
-    alt="Business Application in Device42"
+    alt="Business Service in Device42"
     sources={{
-        light: useBaseUrl('/assets/images/freshservice-integration/business-app-d42-light.png'),
-        dark: useBaseUrl('/assets/images/freshservice-integration/business-app-d42-dark.png'),
+        light: useBaseUrl('/assets/images/freshservice-integration/business-service-d42-light.png'),
+        dark: useBaseUrl('/assets/images/freshservice-integration/business-service-d42-dark.png'),
     }}
     />
 
 ## Deleting the Freshservice External Integration
 
-Before deleting the Freshservice external integration in Device42 or making changes to your Cloud Services configuration, first uncheck the **Enable Freshworks SSO** option in the Appliance Manager, under **Global Settings > SAML/SSO Settings**.
+Before deleting the Freshservice external integration in Device42 or making changes to your Cloud Services configuration, first uncheck the **Enable Freshworks SSO** option in the Appliance Manager, under **Global Settings > SAML/SSO Settings**.