StephenM
The latest version of the ServiceNow Flexera Integration app (v5.1.0) is here and with it some important and highly requested changes. This version is fully compatible with Tokyo, and the changes that came with it, and was just recently certified by ServiceNow. A full list of what's changed can be found below for v5.1.0.
Quick facts
- App version: 5.1.021
- Release date on ServiceNow store: December 22nd, 2022
- Supported ServiceNow version: Tokyo, San Diego, Rome
Data Platform and IT Visibility Integration
New Features and Updates
Flexera Integration app v5.1.0 introduces the following new features and updates:
|
TOPIC |
NEW FEATURE |
|
Data Enrichment |
Added a new option to insert IP address and Network Adapter records |
|
IRE Reclassification Control |
Added an option to prevent reclassification of CIs when using IRE |
|
Resolved Issues |
See Resolved Issues in 5.1.0. below |
Added a new option to insert IP address and network adapter records
For this release, users have the option to insert IP address and Network records. This behavior can be configured using two new Import Properties options that permit Flexera access to the network adapter table and allow the addition of IP addresses.
These new options are:
- Allow Flexera to insert records into the network adapter table (property name: x_fls_flexera_fnms.insert_network_adapter)
- Adding IP address records (Requires network adapter creation) (property name: x_fls_flexera_fnms.integration.ip_address.insert)
Set these options to Yes to support the addition of IP addresses.
Tables affected include the cmdb_ci_ip_address and cmdb_ci_network_adapter tables.
Added an option to prevent reclassification of CIs when using IRE
With this release, we have added a new option, called Prevent IRE Class Switch on Update, to Integration Properties under the Integration Methodology heading. This option is on (Yes) by default and prevents the integration from changing the class of existing configuration item (CI) records.
|
RESOLVED ISSUES in 5.1.0 |
|
Fixed “is_deleted” functionality. |
|
Corrected mapping of Virtual Machine Insert/Update property. |
|
Fixed business rule conflict with UI property options. |
|
Fixed error on Network Equipment Transform Map. |
FlexNet Manager Suite integration
New Features and Updates
|
TOPIC |
NEW FEATURE |
|
Database Enhancements and Changes |
UI option for CMDB or SAM tables removed |
|
Computer Transform Map updated to check for serial number on the Coalesce field |
|
|
New fields in the Computer Transform Map |
|
|
New option to insert IP address and Network Adapter records |
|
|
Resolved Issues |
See Resolved Issues in 5.1.0. |
UI option for CMDB or SAM tables removed
Previously, users could choose whether to use CMDB and/or SAM tables for installations on the Integration Properties page. From the 5.03 release on, this option was no longer truly available due to restrictions on CMDB tables associated with SAM plugin required by ServiceNow. We have updated the UI as of this release to reflect the actual behavior as only SAM tables can be used.
IMPORTANT: If you have software installation records that were previously discovered before the installation of the SAM Foundation plugin, you must run a migration script after installing the SAM Foundation plugin; otherwise, these records will be missing in ServiceNow. The migration script can be downloaded from Migrate Software Asset Management Foundation plugin software installations.
Computer Transform Map updated to check for serial number on the coalesce field
The Computer Transform Map has been updated to include serial number in the method used to match/coalesce records in ServiceNow with FlexNet Manager Suite data. This update improves the accuracy in matching and reduces the number of duplicates.
Previously, FlexNet Manager Suite would match records based on the computerID field passed from FlexNet Manager Suite only. This led to duplicates anytime records were added to ServiceNow ahead of FlexNet Manager Suite or in between export/import.
From this release, FlexNet Manager Suite will use “serial number” as the primary means for identification for computers and will use “name” as the primary identifier for VMs. In both cases it will then check whether the record has a computerID. If so, it will check for a match. If not, it will use the name for computers or serial number for VMs as a secondary check to see if it is a match.
If a record is missing the primary means for identification, it will not be imported into the CMDB because it cannot be identified and would create “bad data” in the CMDB.
If a software installation was tied to a piece of hardware that was missing its primary means for identification, it will not be added because the record would be an “orphan” and missing the related machine it is installed on.
If the missing identifier is added to the record in Flexera, the related records will be loaded in the next import.
New fields in the Computer Transform Map
Three new fields have been added to the Computer Transform Map:
- FQDN (fully qualified domain name)
- First Discovered Date
- Last Discovered Date
For more details, refer to Transform Maps for ServiceNow Integration.
New option to insert IP address and network adapter records
As ServiceNow has deprecated the fields on the computer record for MAC address and IP address we have added an option to support the new related records. From this release, users have the option to insert IP address and Network records. This can be configured on the Integration Properties page. If you would like to have all the MAC and IP address information associated to a computer to be included in the import, choose Yes to both of the following properties:
- Allow Flexera to insert records into the network adapter table
- Allow IP address records (Requires network adapter creation)
Note: Currently the ability to provide a one-to-one relationship for MAC to IP is not possible in FNMS. As a result, if a computer record has multiple MACs/IPs associated with it, it will create an IP record for each associated MAC. As soon as FNMS data supports tracking those relationships it is our desire to do the same.
|
RESOLVED ISSUES in 5.1.0 |
|
Fixed an error with data export |
|
Fixed the issue of Mac OS X being misclassified as Mac OS X Server |
Quick Links:
