User defined property schemas can be used to set up custom properties for applications in Fusion Sport’s Human Performance Framework (HPF). This module was developed to give Smartabase builders even more configuration options when building event forms for HPF applications, such as the Smartabase Athlete and Smartabase Kiosk apps.

The user defined property schemas module is located in the Smartabase builder interface, so any person with builder access can see the module. However we recommend you initially contact your Smartabase representative to make sure it’s the best solution for your workflow. There is a limited selection of custom property schemas available for use in this module, but the list will continue to grow over time as new options are added.

A screenshot showing the custom app properties in the form sidebar.
Once a user defined property schema has been added to your builder site, it will appear in the left sidebar when editing a form, section or field (this will depend on the Applies To setting, explained below). The Category of the schema will define the name of the sidebar section your property appears in.


A screenshot showing an example of the settings for the 'Lock Entry DateTime' property schema.

The image above illustrates the user defined property schema set-up for the Lock Entry DateTime property. You’ll find the required information for setting up other schemas at the bottom of this article, but we do recommend you discuss this module with your Smartabase representative before implementing on your site.

  1. Log in to the Smartabase builder interface.
  2. Select the User defined property schemas module. This will only be visible if you have the appropriate system permission as part of your role.
  3. Give your property schema a Name. This will display as the property’s name in event forms and fields, so should clearly describe the function.
  4. Give your property schema a Description. This will display as a tooltip beside the property name, so is useful for providing additional context to the builder.
  5. Specify what item the property schema Applies To. This will be set to Form, Section or Form Item, depending on the nature of the property.
  6. Choose the type of Selector for the property schema, which determines how you will set the property. The options available include Text, Number, Dropdown or Multiple Selection. Each available schema will require a specific selector type based on its intended function.
  7. If the property schema’s selector type is set to dropdown or multiple selection, add the appropriate Options for the property. You will see these options populated in the property when setting it in an event form, and they must be the correct options for the schema that you’re using.

List of supported schemas

Currently, the following user defined property schemas are available:

Lock Entry DateTime: this property schema can be applied to an individual event form, and prohibits an athlete user from editing the date and time of a record.

This property is not designed to be used in conjunction with the Date Override form property, so must not be used on any forms where this property has been enabled.

This feature is only available for forms being used in the Athlete app, and must adhere to the following settings:

  • Name: Lock Entry DateTime (suggested)
  • Description: Use this setting to prevent users editing the date and time of a record (suggested)
  • Categories: Athlete App (enforced)
  • Key: lock_entry_datetime (enforced)
  • Applies To: Form Item (enforced)
  • Selector: Dropdown (enforced)
  • Options: TRUE, FALSE (enforced)

A screenshot showing the 'Entry Date and Time' field locked in the Athlete app.

As an athlete, you won’t be able to adjust the date and time of a record once this setting is applied to an event form.

Back to the list of supported schemas

Bluetooth Input Device: it is possible to configure individual fields in an event form to receive data directly from a Bluetooth device. Any field configured for this will not be available for manual entry, and users of the app will only be able to input data into the field if they have the correct Bluetooth device. This property can be used for multiple fields within the same event form, and can be applied to forms being used in the Smartabase Athlete and Kiosk apps.

Enabling this setting does not automatically work for any Bluetooth device; support needs to be configured for all different device makes and models by Fusion Sport. Currently the following Bluetooth devices are supported (with the intention of adding other devices in the future):

  • Kinsa Thermometers:
    • Kinsa QuickCare Smart Thermometer
  • Masimo Pulse Oximeters:
    • MightySat Rx (3 and 5 parameters)
    • MightySat Consumer

Third-party device manufacturers tend to change their products, discontinue and introduce new models. Sometimes, these new products have the same name as older devices but work differently. Please check with your Smartabase representative before committing to a particular device based on the list above.

The Bluetooth property schema must adhere to the following settings:

  • Name: Bluetooth Input Device (suggested)
  • Description: Use this setting to assign the field to a Bluetooth device (suggested)
  • Categories: Bluetooth Device (enforced)
  • Key: bluetooth-input (enforced)
  • Applies To: Form Item (enforced)
  • Selector: Dropdown (enforced)
  • Options: kinsa-thermometer-c, kinsa-thermometer-f, masimo-pulseox-pr,  masimo-pulseox-spo2, masimo-pulseox-pvi (enforced – must have at least one of these options)

Once the Bluetooth Input custom property is enabled for a field, you will see the Bluetooth-enabled field in the event form on the Athlete app. As an athlete, the first time you use the form you will need to connect a device to the Bluetooth-enabled field using the following steps:

  1. Click on the Bluetooth-enabled field.
  2. Click Scan and select the device from discovered devices once it appears.
  3. Close the Bluetooth connection pop-up.

A screenshot showing the steps involved with adding a bluetooth device via the Athlete app.
After you have connected a device, the value collected by the device will automatically populate in the field. It will also connect to that field during any subsequent log-ins. If it doesn’t connect automatically, you can search for the device again using the process outlined above.

Back to the list of supported schemas

Was this page helpful?