New in This Release

The following sections describe features and changes new in Flexera Integration app v5.1.1.

New Features and Updates

Flexera Integration app v5.1.1 introduces the following new features and updates:

Topic	New Feature
Platform Support	Now supporting Utah release of ServiceNow
General Improvements	Option to set the user for Flexera data imports
	Read access to Flexera custom tables
	Improved logging and details related to fix scripts
Resolved Issues	See Resolved Issues in 5.1.1.

Now supporting Utah release of ServiceNow

With version 5.1.1, the Flexera Integration App for ServiceNow supports the Utah release.

Option to set the user for Flexera data imports

Flexera Integration App for ServiceNow administrators can optionally set the user for data imports.

Previously, records updated or created via the Flexera Integration App would use the default user as the user ID. Consequently, the Updated by, Created by, and Run as fields in the Flexera Integration App UI would display system as the user ID for those records. This is the default setting in ServiceNow, but it is not informative. Now, you can customize the user ID to show a more meaningful user ID in the UI—for example Flexera Integration.

For instructions and a fix script that customize the user ID for data imports, see the following knowledge base article in the Flexera Community.

https://community.flexera.com/t5/Data-Platform-Knowledge-Base/Instructions-to-update-the-System-user-to-Integration-user-for/ta-p/271066 

Read access to Flexera custom tables

This version provides cross-scope read access to Flexera custom tables to help support business cases where that data is needed—such as for reporting or dashboarding.

Improved logging and details related to fix scripts

In this version, logging improvements have been made to show the start, end, and errors related to fix scripts in the Application Logs.

Resolved Issues in 5.1.1

The following issues have been resolved in Flexera Integration app v5.1.1:

Resolved Issues
Fixed a potential issue that might cause records to be incorrectly created in the hardware category if a certain combination of properties was selected.
Resolved an issue that could cause imports to get stuck in the rare case where ServiceNow would skip updating the state of a record.