Setting Integration Properties
Important:The default settings for the Flexera One app’s Integration properties are suitable for most organizations. In most cases, you can keep the default settings.
Here we can configure IRE Properties, enable Flexera Business Service Mapping, and enable logging and test loads.
| • | Changing Integration Property Settings—Describes how to change an Integration setting. |
| • | About Integration Properties—Lists the Integration properties and describes their functions. |
| • | About the Enable Logging and Record Import Failure Reasons Property—Provides additional information about how import failure reasons are recorded. |
Changing Integration Property Settings
Note:The default Integration property settings are appropriate for most organizations.
Follow the instructions below if your implementation requires you to alter the Integration property settings.
To change an Integration property setting
| 1. | Go to Filter navigator and search for Flexera One. |
| 2. | Navigate to Flexera One > Advanced > Integration Properties. |
| 3. | Click Integration Properties, and make your property setting changes. |
| 4. | Click Save. |
See the Integration property descriptions below for details about those properties.
|
Property |
Description |
|
Prevent IRE class switch on Update |
Checked: Prevents changes to the class of an existing record when it is being updated (such as changing a CI class from Windows Server or Linux Server). Unchecked: Allows changes to the class of an existing record when the current record’s class is different than the updated information. Default: Unchecked. |
|
Enable Logging and Record Import Failure Reasons |
Checked: Flexera Logging is enabled and, when an import failure occurs, the reason for the failure is recorded in the Rejection column of the staging tables. Unchecked: Flexera Logging is not enabled. No Flexera related log is generated. Default: Unchecked. See About the Enable Logging and Record Import Failure Reasons Property, below, for more information on how import failure reasons are recorded. |
|
Enable Test Load |
Checked: Allows the insert limited (30,000 records by default) data into Flexera Native Tables in ServiceNow. This is recommended on initial configuration of the integration. It will only import the number of records indicated in the Test Load Record Count property. Unchecked: Does not allow the insert limited data into Flexera Native Tables in ServiceNow. The number of records imported will not be limited by the Test Load Record Count property value. The number of records imported will be the full export from Flexera One. Default: Unchecked. |
|
Test Load Record Count |
This sets the limit for the number of records imported, which may be useful for testing purposes. It is not recommended to deviate too far from this value in either direction. Default: 30,000. |
About the Enable Logging and Record Import Failure Reasons Property
In addition to turning on general logging, the Enable Logging and Record Import Failure Reasons property also causes the Flexera One app integration to record the reason for import failures after transformation. This information appears in the Rejection column of staging tables.
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 |
Note:This property is not enabled by default as the additional logging can affect performance.