The Application Object

This item maps to the Application object in the IT Asset Management compliance database. It supports the addition of custom properties through the Business Importer.

Database interaction

If an incoming Application matches an existing record in the compliance database, details are updated (as allowed for individual properties described below).

Behavior in the Business Adapter Studio

When you create new objects in the Business Adapter Studio, Application appears in the right-click context menu.

Properties

The Application object is linked to the SoftwareTitle table and exposes the following properties in the data model for the Business Importer and the Business Adapter Studio.

Table 1. Data model properties for Application object

Property

Details

Application Full Name Type: varchar. Maximum: 512.

Maps to the SoftwareTitle.FullName table to join the existing record in the compliance database.

This property cannot be modified.

Application Status
Important: If this property is left blank or set as an empty string in the imported data file, it will remain unchanged. This is because the property is non-nullable, meaning it must always have a value and cannot be empty.
Type: varchar. Maximum: 1000.

Maps to the SoftwareTitle.SoftwareTitleActionID table in the compliance database.

Application Status indicates your assessment and processing of an application and can have any of the following values:

  • Authorized — Installation of this application is allowed on computers in your enterprise. If the application is also associated with a license, those installations can be reviewed to determine if they comply with the license terms and conditions.
  • Deferred — You intend to manage this application in due course, but not now. This status is intended to be a temporary state that you will change later. Since it is an administrative convenience only, installations of these applications still count for license consumption.
  • Ignored — Flags this application as irrelevant for software asset management. While you can recover an application from this state at any time, this status, unlike Deferred, is generally applied only to those applications that you do not intend to manage at all (for example, shareware that you permit, but choose not to manage closely).
    Tip: Although you may choose not to manage an ignored application, it may still be licensable. For this reason, an ignored application is not exempted from license consumption calculations. To remove an application from license consumption calculations, either:
    • Disconnect the application from all licenses
    • In the General tab of properties for the evidence that identifies the application, set Ignored to Yes (first check that this same evidence does not also link to a different application that should still be included in compliance calculations).
  • InactiveIT Asset Management assigns this status to applications recorded in the Application Recognition Library, but not yet recognized as installed within your enterprise.
  • Unauthorized — Apply this to flag applications that should not be installed on computers in your enterprise. It is best practice to uninstall such applications.
  • Unmanaged — A new application identified in your enterprise, but not yet assigned any of the above status values.
    Tip: If you do not have the time to process the new records, you can assign the Deferred status to an application, and review it later. This makes it easier to identify any new Unmanaged applications that appear, so that you can manage by exception.
Application Transparency
Important: If this property is left blank or set as an empty string in the imported data file, it will remain unchanged. This is because the property is non-nullable, meaning it must always have a value and cannot be empty.
Type: varchar. Maximum: 5.

Maps to the SoftwareTitle.ImportDetailedEvidence table in the compliance database.

This field supports boolean values (such as, 1/0, True/False, Yes/No)
Note: Values Yes and No can display in any of the languages supported by IT Asset Management. For example, German users can use the words Ja and Nein. This is important because if your UI language is set to something other than English and you generate a report, such as one containing the ImportDetailedEvidence field, it will display the localized equivalents of Yes and No based on your language settings.
Application Version Type: varchar. Maximum: 400.

Maps to the SoftwareTitle.SoftwareTitleVersionID table in the compliance database.

This property cannot be modified.

Note: To ensure that an Application Version matches the value found in IT Asset Management, it's advisable to enclose the version value in double quotes within the imported data file, for example: "1.0". This is because the version is stored as a string in the database, but the Business Importer may interpret it as a numeric value if it appears to be a number. For example, a version like '1.0' might be read as the number 1, which would not match the actual version string in the database. Using double quotes helps preserve the correct format and prevents mismatches during import.
Publisher Name Type: varchar. Maximum: 50.

Maps to the SoftwareTitle.SoftwareTitleProductID table which maps to SoftwareTitlePublisher.SoftwareTitlePublisherID in the compliance database.

This property cannot be modified.

Data model version 13.2

IT Asset Management (Cloud)

Current