Skip to main content

Inventory Items in Profiles

What

  • Each Inventory Items has an Internal Name, including Custom Fields which provide extended inventory
  • The Internal Name can be used to reference any Inventory Items in Profiles

When

Internal Name of an Inventory Item may be located from the Inventory Query Editor.  Example shows the Internal Name: ‘device_product_name’

Pasted Graphic 29.png

This may be added into a Profile, effectively customising the Profile per device or user:

Pasted Graphic 46.png

Pasted Graphic 48.png

Custom Fields

Associated Custom Fields may also be used with Payloads settings of Profiles.  Extending the above example, consider a Custom Field for Asset Tag:

Custom Field Definition

Pasted Graphic 44.png

Profile Payload

Pasted Graphic 49.png

Lock Screen

Pasted Graphic 47.png


Improvement

When referencing a Custom Field in a Profile Payload, it could be referenced in one of two ways.  From the above example, it could be either:

  • %asset_tag%
  • %custom_field.asset_tag%

The additional prefix indicates more clearly that this is a Custom Field Inventory Item.  If there was an Inventory Item with a matching name provided by FileWave, the first item in the list would report the provided Inventory Item value for the device and not the Custom Field.

For demonstration, imagine creating a Custom Field called 'My Device Product Name' with Internal Name: device_product_name. 

Pasted Graphic 54.png

There are now two Inventory Items with the Internal Name: device_product_name:

Pasted Graphic 51.png

and

Pasted Graphic 52.png

With the values:

Pasted Graphic 55.png

Altering the above example Lock Message to use both of these:

Pasted Graphic 57.png

The device clearly demonstrates how the value without a prefix uses the FileWave provided Custom Field value:

Pasted Graphic 58.png

To prevent confusion with overlapping Inventory Items between Custom Field and built-in Inventory, always consider using the prefix for Custom Fields

User Customisation

Although FileWave doesn't manage users, if users are associated with devices, this extends the ability to customise Profiles for users.

User details from enrolment may be used, but to extend beyond this, LDAP servers set for extraction can greatly increase the Inventory Items available for Parameters via LDAP Custom Fields.

An example of Profile customisation for users:

image.png

One Profile can therefore be used for multiple devices, tailoring the Payload to the users of those devices.