Skip to main content

Custom Fields

Extend Inventory even more? Check.

With FileWave you can even further extend your Inventory Reporting capabilities by creating Custom Fields for your devices. FileWave's Custom Fields can be manually entered per device, imported via CSV file, or scripted for the macOS and Windows clients. These Custom Fields can be leveraged in FileWave's scheduled Inventory Reports, Smart Groups, or accessed via API calls.

Create a Custom Field

This section will outline how to create the most commonly used Custom Field types in FileWave.

All Custom Fields will first be created by opening FileWave Admin and navigating to "Assistants > Custom Fields > Edit Custom Fields".

Static Custom Field

This section will cover creating a "static" Custom Field that can either be manually modified or imported via CSV. This example will create a "Building Code" Custom Field but other examples may include unique Asset Tag, Assigned Cart, or Department.

  1. Open FileWave Admin and navigate to "Assistants > Custom Fields > Edit Custom Fields".

     

  2. Click the "[+]" button in the lower left-hand corner.
  3. Name the Custom Field accordingly and take note of the automatically generated "Internal Name".
    • Custom Fields will be shown in the "Device Details" and are alphabetically sorted, name accordingly.
    • The "Internal Name" will be used as the variable name throughout FileWave. (ex: %building_code%).
  4. Optionally, enter a "Description" for the Custom Field so other team members know what the field is designed for.
  5. Change the "Provided By" drop-down menu to "Administrator".
    • "Administrator" mean you, the FileWave Administrator will provide the Custom Field input.
  6. Optionally, check the "Assigned to all devices" box.
    • This is the recommended option for Custom Fields that can apply to all devices, even if not utilized immediately.
    • If not "Assigned to all devices", please review the section below to learn how to manually assign Custom Fields to devices.
  7. Change the "Data Type" to "String".
    • "String" is the default and recommended for most situations.
  8. Optionally, check the "Restrict allowed values" box.
    • With the "Restrict allowed values" box checked, it will require you to input allowed values for the Custom Field.
    • This will change the input method from a "free type" field to a drop-down menu of allowed values.
  9. Check the "Use default value" box and enter in a placeholder value.
    • This is recommended to prevent blank Custom Fields, especially those used for Device Naming or other variable substitution.
  10. Click "Save".
Building Code Custom Fields.png

Script-based Custom Field

This section will cover creating a script-based Custom Field. A script-based Custom Field will run a script periodically on macOS and Windows clients and return the output of the script to the Custom Field. These can be used to supplement FileWave's native Inventory even more dynamically than a static Custom Fields. Examples may include device Encryption Status from FileVault or BitLocker, Antivirus threats detected, or Registry keys / .plist values.

  1. Open FileWave Admin and navigate to "Assistants > Custom Fields > Edit Custom Fields".
  2. Click the "[+]" button in the lower left-hand corner.
  3. Name the Custom Field accordingly and take note of the automatically generated "Internal Name".
    • Custom Fields will be shown in the "Device Details" and are alphabetically sorted, name accordingly.
    • The "Internal Name" will be used as the variable name throughout FileWave. (ex: %encryption_status%).
  4. Optionally, enter a "Description" for the Custom Field so other team members know what the field is designed for.
  5. Change the "Provided By" drop-down menu to "Client Script".
    • "Client Script" will run a script periodically and return the script's output to the Custom Field.
    • All scripts will be executed as either the "root" user on macOS or as the "SYSTEM" account on Windows.
  6. Optionally, check the "Assigned to all devices" box.
    • This is the recommended option for Custom Fields that can apply to all devices, even if not utilized immediately.
    • If not "Assigned to all devices", please review the section below to learn how to manually assign Custom Fields to devices.
  7. Change the "Data Type" to "String".
    • "String" is the default and recommended for most situations.
  8. Optionally, check the "Restrict allowed values" box.
    • With the "Restrict allowed values" box checked, it will require you to input allowed values for the Custom Field.
    • This will change the input method from a "free type" field to a drop-down menu of allowed values.
    • This is not recommended for script-based Custom Fields unless you can guarantee the output of the script will be consistent.
  9. Check the "Use default value" box and enter in a placeholder value.
    • This is recommended to prevent blank Custom Fields, especially those used for Device Naming or other variable substitution.
  10. Verify the correct scripting language and enter script for "macOS".
  11. Verify the correct scripting language and enter script for "Windows".
  12. Optionally, check the "Use output only when scripts exits with code 0" box.
    • This will depend on the script you are running, however most scripts "exit 0" after a successful execution.
    • You may be able to force "exit 0" by including it in your script.
  13. Optionally, check the "Replace line feed characters with space" box.
    • This is recommended as it will automatically convert multi-line output to single-line output.
  14. Click "Save".

     

 

 

 

 Encryption Status macOS.png

Encryption Status Windows.png
Back to top