Flexera One app version 1.4 available now in the ServiceNow Store

Flexera helps you improve the value you derive from your ServiceNow investment-from aggregation, normalization, and enrichment of hardware, software, SaaS, and cloud IT asset inventory data to IT service delivery. With Technopedia®, the most trusted source of IT product information in the world, Flexera enhances IT service management (ITSM), Configuration Management Systems, and Software Asset Management with a reliable foundation and accurate data.

Version:Version 1.4 of the Flexera One ServiceNow App has been certified for the Xanadu release of ServiceNow.

This release includes the following new capabilities and resolved issues. For more information about the Flexera One app, see the Flexera One ServiceNow App Help Library on our Flexera Documentation Site.

• Option for enhanced logging for import failures
• Additional data mapping added for Computer tables and Netgear tables
• Optimized logic for updating the start date and end date for hardware lifecycle
• Optimized the logic for updating Computer records
• Updated the logic of primary key for the discovery model and software installation
• Updated reclassify hardware logic to cover Virtualization Servers
• Simplified Flexera One ServiceNow app navigation and added a new Get Support page
• Resolved issues in version 1.4

Option for enhanced logging for import failures

A new feature has been introduced to record the reason for import failures after transformation. The Flexera One app shows the new information in the Rejection column of staging tables. You can enable this enhanced logging functionality by setting the Enable Logging and Record Import Failure Reasons Integration Property to Yes.

For records that fail to import, the Rejection column will indicate the causes and record the following reasons:

• Missing mandatory column values
• Missing required property values
• Missing host device (no matching host device found)

When this integration property is enabled, the Rejection column is available for the following tables:

• Hardware Technopedia Imports 
• Hardware Technopedia Lifecycle 
• Hardware Inventory Imports 
• Hardware Model Power Imports 
• Hardware Model Profile Imports 
• Software Technopedia Imports 
• Software Technopedia Lifecycle 
• Software Inventory Imports 
• Network Adapters Imports 

For more information about the Enable Logging and Record Import Failure Reasons property and other Integration Properties, see Setting Integration Properties.

Additional data mapping added for Computer tables and Netgear tables

With this release, we have added more column mappings for the Computer tables and Netgear tables.

Computer

Netgear

Most Recent Discovered 

Most Recent Discovered 

CPU Type 

 

CPU Speed 

 

Disk Space 

 

DNS Domain 

 

CPU Core Count 

 

As shown above, the Computer table has several new mappings: Most Recent Discovered, CPU Type, CPU Speed, Disk Space, DNS Domain, and CPU Core Count.

The Netgear tables include one new mapping: Most Recent Discovered.

Optimized logic for updating the start date and end date for hardware lifecycle

When hardware lifecycle dates have not been published by the manufacturer, the date for a particular lifecycle event is unknown. The date may be empty or populated with an exception statement. In these cases, where a date is required to import the record, Flexera applies a placeholder date in place of the unknown date. For this release, we have refined the logic for those placeholder dates. Now there are three possible values:

• 1900 is a placeholder date for records in which the exact lifecycle event date is unknown but understood to be in the distant past.
• 2999 is a placeholder date for unknown dates that are still subject to investigation. So 2999 represents dates that are unknown but to be determined.
• 3999 is a placeholder for cases in which the date was never published by the vendor and other exceptions. So 3999 represents dates that are unknown and likely never will be known.

GA date logic update: If GA date does not exist, but the Introduction date does exist, we will use the Introduction date for GA date.

Note:Also, this logic corrects an issue in which the Exception values were being retained after the lifecycle event date was updated to a known date. Exception values are now cleared if the date value is known.

Optimized the logic for updating Computer records

We have improved the logic to update the computer records; now we will no longer check the platform type and platform level field as a mandatory attribute to update the records. This change improves the accuracy of the computer records.

Updated the logic of primary key for the discovery model and software installation

This release includes optimizations to the logic for the discovery model primary key and for software installation:

• For discovery model, we are coalescing to include a unique identifier (Technopedia ID) to set the primary key. Formerly, the discovery model was set based on manufacturer, display name, and version, which had not been sufficiently unique in all cases.
• For software installation, optimized logic better identifies unique records (using a Flexera unique ID) to create and update.

Updated reclassify hardware logic to cover Virtualization Servers

In this release, we have improved the reclassification hardware logic for virtualization servers—VMware ESX Server, Hypervisor, Nutanix, Citrix, and RHV—for the platform level data.

Simplified Flexera One ServiceNow app navigation and added a new Get Support page

In version 1.4, we have optimized the Flexera One application module for easier navigation and added a Get Support page with direct links to selected sections of the Flexera One ServiceNow app documentation as well as links to Flexera pages for technical support, customer community, and learning resources.

Note:Flexera One app navigation changes streamlined navigation. As a result, you may notice that certain pages have been renamed, grouped under a different category, or otherwise moved. For example, Connection Setup has been renamed to Connection and moved into the Import Configuration group. Documentation for this release has been updating accordingly.

Resolved issues in version 1.4

The following issues were resolved in this release:

• Resolved an issue with serial number updates in Software Inventory RTE—This change prevents Software Inventory RTE from modifying the Computer serial number. The mapping of Computer serial number has been deleted.