Skip to content

Commit f6ae975

Browse files
sixhobbitssixhobbits
authored
Merge pull request #485 from ritza-co/19.07.13
Docs 19.07.13 release (Week 50, 2025)
2 parents a5ade6f + 43fb1b5 commit f6ae975

File tree

3 files changed

+265
-20
lines changed

3 files changed

+265
-20
lines changed

‎docs/auto-discovery/enrichai-data/index.mdx‎

Lines changed: 40 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -6,55 +6,75 @@ sidebar_position: 99
66
import ThemedImage from '@theme/ThemedImage'
77
import useBaseUrl from '@docusaurus/useBaseUrl'
88

9-
EnrichAI Data is a Device42 service for enhancing discovered data. Device42 supports the enrichment of Operating System (OS) and vendor data for discovered devices.
9+
EnrichAI is a Device42 cloud-based service for enhancing discovered data. Device42 supports the enrichment of software applications, operating systems (OS), and vendor that are discovered by Device42 Autodiscovery.
1010

1111
## Data Fields
1212

13-
The EnrichAI Data service populates the following vendor attributes, operating system attributes, and support date fields according to the available data. The data is mined from validated, authoritative sources to ensure accuracy.
13+
The EnrichAI data service take the vendor name, product name, and version number fields as populated by the product vendor and uses it to replace those values with cleansed and normalized values. In addition, it adds values for an extended set of fields, like categories and support lifecycle dates. The enriched data is mined from validated, authoritative, public sources to ensure accuracy.
14+
15+
The following is a partial list of enriched fields:
1416

1517
### Vendor Attributes
1618

1719
| Vendor Attributes | Description |
1820
|-------------------------|---------------------------------------------------------|
1921
| Vendor Name | The standardized vendor company title |
20-
| Parent | The name of the vendor's corporate parent company (if one exists) |
21-
| Vendor Name Aliases | A list of any other names the vendor is known as (if they exist) |
22+
| Parent Vendor | The name of the vendor's corporate parent company (if one exists) |
23+
| Vendor Aliases | A list of any other names the vendor is known as (if they exist) |
24+
| URL | The official vendor website URL |
25+
| Copyright | The official legal name of the vendor entity |
2226

2327
### Operating System Attributes
2428

2529
| Field | Description |
2630
|---------------------|---------------------------------------------------------------|
27-
| OS Name | The standardized name of the OS |
28-
| OS Family | The OS release family |
29-
| OS Edition | The identifier indicating the edition of the OS |
3031
| OS Vendor | The name of the OS vendor |
32+
| OS Name | The standardized name of the OS |
33+
| OS Family | The OS release family (Linux, Windows, etc.) |
34+
| OS Edition | The edition of the OS (Enterprise, Datacenter, etc.) |
3135
| OS Version Number | The general version number of the release |
36+
| OS Family | The OS release family (Linux, Windows, etc.) |
37+
| Service Pack | The service pack level of the OS release |
3238
| Key Support Dates | See the details for the available date fields in the table below |
3339

3440
The **OS Architecture: 32 vs 64 bit** field is no longer part of EnrichAI Data. The 32- and 64-bit architectures have been coalesced into a single entry, since the architecture does not affect OS dates, licensing, patches, or risk profiles.
3541

42+
### Software Attributes
43+
44+
| Field | Description |
45+
|---------------------|---------------------------------------------------------------|
46+
| Vendor | The standardized vendor name |
47+
| Product Name | The standardized product name |
48+
| Market Version | The name that the version is commonly known as (2012, 2016, etc.) |
49+
| Edition | The software edition (such as Professional or Enterprise) |
50+
| Release | The name of the release (often an update or patch) |
51+
| Version | The full version number including major, minor, patch, and build values (using [Semantic Versioning](https://semver.org/)) |
52+
| Service Pack | The service pack level of the software release |
53+
| Category | The product category this software application belongs to |
54+
| Key Support Dates | See the details for the available date fields in the table below |
55+
3656
### Key Support Dates
3757

3858
| Key Support Dates | Description |
3959
|------------------------------------|-----------------------------------------------------------------------|
40-
| Base Release Date | When the OS became available |
41-
| Release Start Date | When support for the specific OS release became available |
42-
| Release End Date | When support for the OS release will end |
43-
| End of Life Date | When the OS will no longer be sold |
60+
| Base Release Date | When the product became available |
61+
| Release Start Date | When the release became available |
62+
| Release End Date | When the release stopped being distributed |
63+
| End of Life Date | When the release will no longer receive security/vulnerability updates |
4464
| End of Support Date | When mainstream support will no longer be available |
4565
| Extended End of Support Date | When extended support will no longer be available |
46-
| End Of Maintenance Date | When patches will no longer be released under standard maintenance agreement |
47-
| Extended End Of Maintenance Date | When patches will no longer be released under extended maintenance agreement |
66+
| End Of Maintenance Date | When non-security patches will no longer be released under standard maintenance agreement |
67+
| Extended End Of Maintenance Date | When non-security patches will no longer be released under extended maintenance agreement |
4868

4969
:::note
50-
Depending on the vendor, OS, and availability of information, EnrichAI Data may not populate all the date fields.
70+
Depending on the vendor's published information, EnrichAI Data may not populate all or any of the date fields.
5171
:::
5272

5373
## EnrichAI Data Collection
5474

55-
When EnrichAI Data is enabled, the device data collected during discovery jobs is queued, batched, and sent via HTTPS to the EnrichAI Data service, where it is processed in background tasks to prevent negative system impact. When EnrichAI Data finds a match, it responds with enriched data. All enriched data is displayed on the EnrichAI Data page; depending on the number of requests in the queue and system load, this data may not be immediately visible.
75+
When EnrichAI Data is enabled, the device data collected during discovery jobs is queued, batched, and sent via HTTPS to the EnrichAI Data service, where it is processed in background tasks to prevent negative system impact. When EnrichAI finds a match, it responds with enriched data. All enriched data is displayed on the Analytics > EnrichAI Data page; depending on the number of requests in the queue and system load, this data may not be immediately visible.
5676

57-
When presented with a new or unique data entry, the EnrichAI Data service may need to perform a background check with authoritative sources to identify any new or changed data that can be displayed on the next discovery for that device. As such, each discovery is validated by the EnrichAI Data service to ensure the discovered values are correct and up to date. All data sent to EnrichAI Data is anonymous and untraceable; it will never contain identifiable information, such as hostnames, IP addresses, or MAC addresses. Below is a sample of the payload:
77+
When presented with a new or unique data entry, the EnrichAI service may need to perform a background check with authoritative sources to identify any new or changed data that can be displayed on the next discovery for that device. As such, each discovery is validated by the EnrichAI Data service to ensure the discovered values are correct and up to date. No data sent to EnrichAI contains identifiable information, such as hostnames, IP addresses, or MAC addresses. Below is a sample of the payload:
5878

5979
<details>
6080
<summary>Click to expand the code block</summary>
@@ -132,6 +152,7 @@ Please do the following to ensure connectivity with EnrichAI Data:
132152
- `https://enrichai.device42.io/api/normalizations`
133153

134154
3. Register the license online.
155+
4. For enrichment of Software, the Software Enrichment license needs to be listed as Enabled under Tools > Licensing.
135156

136157
Device42 [InsightsAI](/reports/device42-doql/insightsai.mdx) generates queries based on natural language prompts. The prompts you enter are sent to the `ai42.device42.io` endpoint.
137158

@@ -180,11 +201,11 @@ The image below shows a vendor view page with enriched data. Enriched data is al
180201

181202
## Data Handling and Security Practices
182203

183-
1. No personal or personally identifiable data is maintained by the EnrichAI Data service.
184-
2. Unmatched values (those without a corresponding match in EnrichAI Data) are stored for future mining and resolution. This storage has no association with the calling system or installation.
204+
1. No personal or personally identifiable data is maintained by the EnrichAI service.
205+
2. Unmatched values (those without a corresponding match in EnrichAI Data) are stored for future mining and resolution.
185206
3. Only Device42 personnel work with these non-identifiable data elements.
186207
4. Data collected for future enrichment mining is stored in the United States.
187208

188209
:::note
189-
Device42 reserves the right to change and update the internal matching algorithm and the golden records provided with this service.
210+
Device42 reserves the right to change and update the normalized and enriched records provided with this service.
190211
:::

‎docs/integration/imports/spreadsheet-converter-tool.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ The Device42 Generic Spreadsheet Import Tool enables users to take data in exist
77

88
Here is a [video how-to on this Generic CSV import tool.](how-to-videos/generic-csv-import-tool-how-to.mdx)
99

10-
The spreadsheet converter is a standalone executable and is available for download [here](https://www.device42.com/bulk-data-management/) .
10+
The spreadsheet converter is a standalone executable and is available for download at [https://www.device42.com/bulk-data-management/](https://www.device42.com/bulk-data-management/).
1111

1212
### Open an Existing Spreadsheet
1313

‎docs/release-notes/freshservice-mapping/mapping-3.0.mdx‎

Lines changed: 224 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,224 @@
1+
---
2+
title: "Changes in Version 3.0"
3+
sidebar_position: 2
4+
---
5+
6+
These are the changes to the `mapping.xml` file that version 3.0 has from version 2.0
7+
8+
If you are using a custom mapping.xml file, you need to manually apply these updates. See [Manage Customization with Newer Releases](/integration/external-integrations/freshservice-integration/customize-freshservice#manage-customization-with-newer-releases).
9+
10+
## Product Tasks Removed
11+
12+
The following two product tasks were deleted, as they are no longer needed due to a change in how the product is set for the asset:
13+
14+
```xml
15+
<task enable="true" name="Products" type="product" description="Copy Product info from Device42 to Freshservice" d42_min_version="16.19.00">
16+
```
17+
18+
```xml
19+
<task enable="true" name="Products" type="product" description="Copy Product info from Device42 to Freshservice" d42_max_version="16.18.02">
20+
```
21+
22+
## Copy Server Devices Tasks
23+
24+
Similar changes were made to three different versions of the copy servers `Devices` task, which differ by DOQL version and Device42 versions.
25+
26+
### DOQL v2 for Device42 19.04.00 and Later
27+
28+
The following changes were made within this `Devices` task:
29+
30+
```xml
31+
<task enable="true" name="Devices" type="asset" description="Copy Servers from Device42 to Freshservice using DOQL v2" d42_min_version="19.04.00">
32+
```
33+
34+
- In the DOQL query, the following `WHEN` clause was moved up to below the Load Balancer condition:
35+
36+
```sql
37+
WHEN view_device_v2.network_device THEN 'Switch'
38+
```
39+
40+
It now appears directly after:
41+
42+
```sql
43+
WHEN lower(view_device_v2.type) = 'virtual' AND lower(view_device_v2.os_name) similar to '%(f5|netscaler)%' THEN 'Load Balancer'
44+
```
45+
46+
- Added the manufacturer field to the `SELECT` statement:
47+
48+
```sql
49+
view_vendor_v1.name as manufacturer,
50+
```
51+
52+
- Added a `LEFT JOIN` for the vendor table:
53+
54+
```sql
55+
LEFT JOIN view_vendor_v1 on view_vendor_v1.vendor_pk = view_hardware_v2.vendor_fk
56+
```
57+
58+
- The `hw_model` field element was changed from the following:
59+
60+
```xml
61+
<field resource="hw_model" source-type="string" target="product" target-type="string"
62+
target-header="Hardware"
63+
target-foreign="products" target-foreign-key="name" not-null="true" required="true" max-length="255"/>
64+
```
65+
66+
To the following:
67+
68+
```xml
69+
<field resource="hw_model" source-type="string" target="product" target-field="name" target-type="dict" max-length="255"/>
70+
```
71+
72+
- Added a new `manufacturer` field element:
73+
74+
```xml
75+
<field resource="manufacturer" source-type="string" target="product" target-field="manufacturer" target-type="dict" max-length="255"/>
76+
```
77+
78+
### DOQL v2 for Device42 16.19.00 to 19.03.99
79+
80+
The following changes were made within this `Devices` task:
81+
82+
```xml
83+
<task enable="true" name="Devices" type="asset" description="Copy Servers from Device42 to Freshservice using DOQL v2" d42_max_version="19.03.99" d42_min_version="16.19.00">
84+
```
85+
86+
- In the DOQL query, the following `WHEN` clause was moved up to below the Load Balancer condition:
87+
88+
```sql
89+
WHEN view_device_v2.network_device THEN 'Switch'
90+
```
91+
92+
It now appears directly after:
93+
94+
```sql
95+
WHEN lower(view_device_v2.type) = 'virtual' AND lower(view_device_v2.os_name) similar to '%(f5|netscaler)%' THEN 'Load Balancer'
96+
```
97+
98+
- Added the manufacturer field to the `SELECT` statement:
99+
100+
```sql
101+
view_vendor_v1.name as manufacturer,
102+
```
103+
104+
- Added a `LEFT JOIN` for the vendor table:
105+
106+
```sql
107+
LEFT JOIN view_vendor_v1 on view_vendor_v1.vendor_pk = view_hardware_v2.vendor_fk
108+
```
109+
110+
- The `hw_model` field element was changed from the following:
111+
112+
```xml
113+
<field resource="hw_model" source-type="string" target="product" target-type="string"
114+
target-header="Hardware"
115+
target-foreign="products" target-foreign-key="name" not-null="true" required="true" max-length="255"/>
116+
```
117+
118+
To the following:
119+
120+
```xml
121+
<field resource="hw_model" source-type="string" target="product" target-field="name" target-type="dict" max-length="255"/>
122+
```
123+
124+
- Added a new `manufacturer` field element:
125+
126+
```xml
127+
<field resource="manufacturer" source-type="string" target="product" target-field="manufacturer" target-type="dict" max-length="255"/>
128+
```
129+
130+
### DOQL v1 for Device42 up to 16.18.02
131+
132+
The same changes were made within this `Devices` task, with the exception that the DOQL query references `view_device_v1` and `view_hardware_v1` instead of v2:
133+
134+
```xml
135+
<task enable="true" name="Devices" type="asset" description="Copy Servers from Device42 to Freshservice using DOQL v1" d42_max_version="16.18.02">
136+
```
137+
138+
- In the DOQL query, the following `WHEN` clause was moved up to below the Load Balancer condition:
139+
140+
```sql
141+
WHEN view_device_v1.network_device THEN 'Switch'
142+
```
143+
144+
It now appears directly after:
145+
146+
```sql
147+
WHEN lower(view_device_v1.type) = 'virtual' AND lower(view_device_v1.os_name) similar to '%(f5|netscaler)%' THEN 'Load Balancer'
148+
```
149+
150+
- Added the manufacturer field to the `SELECT` statement:
151+
152+
```sql
153+
view_vendor_v1.name as manufacturer,
154+
```
155+
156+
- Added a `LEFT JOIN` for the vendor table:
157+
158+
```sql
159+
LEFT JOIN view_vendor_v1 on view_vendor_v1.vendor_pk = view_hardware_v1.vendor_fk
160+
```
161+
162+
- The `hw_model` field element was changed from the following:
163+
164+
```xml
165+
<field resource="hw_model" source-type="string" target="product" target-type="string"
166+
target-header="Hardware"
167+
target-foreign="products" target-foreign-key="name" not-null="true" required="true" max-length="255"/>
168+
```
169+
170+
To the following:
171+
172+
```xml
173+
<field resource="hw_model" source-type="string" target="product" target-field="name" target-type="dict" max-length="255"/>
174+
```
175+
176+
- Added a new `manufacturer` field element:
177+
178+
```xml
179+
<field resource="manufacturer" source-type="string" target="product" target-field="manufacturer" target-type="dict" max-length="255"/>
180+
```
181+
182+
## Software In Use Tasks
183+
184+
The same change was made to two different versions of the `Software In Use` task, which differ by Device42 version constraints.
185+
186+
### Version 16.19.00 and Later
187+
188+
The following change was made within this `Software In Use` task:
189+
190+
```xml
191+
<task enable="true" name="Software In Use" type="software_installation" description="Create Software Install from Software In Use" d42_min_version="16.19.00">
192+
```
193+
194+
- In the DOQL query, the following `WHEN` clause was moved up to below the Load Balancer condition:
195+
196+
```sql
197+
WHEN view_device_v2.network_device THEN 'Switch'
198+
```
199+
200+
It now appears directly after:
201+
202+
```sql
203+
WHEN lower(view_device_v2.type) = 'virtual' AND lower(view_device_v2.os_name) similar to '%(f5|netscaler)%' THEN 'Load Balancer'
204+
```
205+
206+
### Version 16.18.02 and Earlier
207+
208+
The same change was made within this `Software In Use` task, with the exception that the DOQL query references `view_device_v1` instead of v2:
209+
210+
```xml
211+
<task enable="true" name="Software In Use" type="software_installation" description="Create Software Install from Software In Use" d42_max_version="16.18.02">
212+
```
213+
214+
- In the DOQL query, the following `WHEN` clause was moved up to below the Load Balancer condition:
215+
216+
```sql
217+
WHEN view_device_v1.network_device THEN 'Switch'
218+
```
219+
220+
It now appears directly after:
221+
222+
```sql
223+
WHEN lower(view_device_v1.type) = 'virtual' AND lower(view_device_v1.os_name) similar to '%(f5|netscaler)%' THEN 'Load Balancer'
224+
```

0 commit comments

Comments
 (0)