Inventory Usage Information
FlexNet Code Insight 2019 R1
FlexNet Code Insight provides the ability to see and edit usage information for a given inventory item. Usage information is important because it aids users in determining how closely to monitor inventory items for intellectual property (IP) and security risk and in taking appropriate action to approve or reject inventory, create tasks for remediation, and issue alerts and notifications. Usage fields can determine whether the item should be included in Third-Party Notices and what steps need to be taken to satisfy license obligations and conditions of use. They can also help to identify license conflicts and compatibility issues. The following are usage fields available for inventory.
The inventory usage fields are available on the Usage tab for a given inventory item, as found both on the Project Inventory tab (shown below) and in the inventory view in Analysis Workbench. You can update these fields when you manually create or edit inventory items.
|
•
|
Distribution Type—Indicates how you are distributing the item. The distribution type can affect license priority and obligations. |
|
•
|
Externally with your product, shipped to customers (outside of your organization, including a private cloud deployment at the customer’s site) |
|
•
|
As an application hosted in your company’s data center (such as a SAAS application) |
|
•
|
Internally only (such as an internal test framework included in the codebase but not distributed with the product) |
|
•
|
Distribution method unknown |
|
•
|
Part of Product—Indicates whether the item is part of the core product or an infrastructure piece such as a build or test tool. This can affect whether third-party notices are required for this item. |
|
•
|
Linking—Indicates whether the libraries are statically linked (included in the materials), dynamically linked (brought in at runtime), or not linked at all. Linking can affect license priority and obligations. |
|
•
|
Modified—Indicates whether a project contributor, such as a developer, has modified the software from its original form. Modification can be an important factor for determining license obligations and distribution requirements that are governed by a specific license. |
|
•
|
Encryption—Indicates whether the component provides encryption capabilities used in the product. Encryption can affect export controls. |
For explicit directions on viewing or editing inventory usage either in Analysis Workbench or on the Project Inventory tab, see the following:
Open topic with navigation