Skip to main content

Custom Property

Last Updated: December 30 , 2025
Document Version: 1.0
Prepared for: Emgage HRMS Implementation Team

The Custom Property module allows administrators to define reusable data fields that can be attached to asset records across categories.
These fields support additional asset attributes such as serial number, invoice details, maintenance dates, warranty information, brand details, and more.

This module enables flexible metadata configuration, validation control, field-level activation, and centralized property management.

System Overview​

The Custom Property module consists of the following key components:

  1. Custom Property Table – Displays configured custom fields and their attributes
  2. Toolbar Controls – Add new property fields and apply filters
  3. Add Custom Property – Create new asset-level custom fields
  4. Edit Custom Property – Modify existing property attributes
  5. Filter Panel – Search and refine property records

Custom Property Table​

The Custom Property Table lists all configured asset properties and their current status.

Custom Property Table Placeholder

Table Columns​

ColumnDescription
NameInternal name assigned to the custom property field.
Input TypeField data type (Textbox, Dropdown, Date, etc.).
LabelUser-facing caption displayed inside asset forms.
StatusIndicates whether the field is Active / Inactive.
Created Date / Created ByTracks when and by whom the field was configured.
ActionsAllows editing of an existing custom property.

Toolbar Controls​

Located above the property list, the Toolbar provides core field-management actions.

Toolbar Controls Placeholder

Toolbar Options

  • + Custom Property → Create a new custom property field
  • Filter → Search or refine fields using parameters such as name, label, type, or status

Add Custom Property​

Administrators can create reusable custom fields that appear across relevant asset forms.

Add Custom Property Form Placeholder

Mandatory Fields​

FieldDescription
NameSystem name of the custom property.
Input TypeDetermines the field format (Textbox, Dropdown, Date, etc.).
LabelUser-visible name displayed inside asset records.
Error MessageValidation message shown when incorrect input is entered.
NoteHelp text describing the purpose of the field.
StatusActivate or deactivate field availability.

Actions​

  • Reset → Clear input fields
  • Submit → Save and activate the custom property

Edit Custom Property​

Used to modify an existing property field without deleting or recreating it.

Edit Custom Property Form Placeholder

Editable Attributes​

  • Field Name
  • Input Type
  • Label
  • Error Message
  • Note / Description
  • Field Status (Active / Inactive)

Actions​

  • Reset → Revert unsaved changes
  • Submit → Save updated configuration

Filter Panel​

The Filter panel allows administrators to search and refine custom property records.

Custom Property Filter Placeholder

Available Filters​

FilterDescription
NameSearch by field name
LabelSearch by displayed caption
Input TypeFilter by data type (Date, Textbox, etc.)
StatusActive / Inactive

Filter Actions​

  • Submit → Apply filter conditions
  • Reset → Clear all selections

Implementation Guidelines​

For System Administrators

  1. Define commonly used asset fields as custom properties to maintain consistency.
  2. Use meaningful field names and labels to improve user understanding.
  3. Keep only relevant fields Active to avoid clutter in asset forms.
  4. Configure validation and error messages thoughtfully to reduce data-entry mistakes.

For Asset Managers

  1. Review property activation before attaching fields to asset records.
  2. Avoid duplicating existing properties — reuse standardized fields.
  3. Document purpose of each property using the Note field.
  4. Periodically review and deactivate unused properties.

Common Issues & Solutions​

IssuePossible CauseSolution
Field not visible in asset formProperty status is InactiveActivate field in Edit Property.
Duplicate property createdSimilar field already existsReuse or update existing field.
Validation error during entryIncorrect data type inputUpdate or refine error message.

Best Practices​

  1. Prefer standardized reusable properties over one-off fields.
  2. Use clear, descriptive labels to support end-users.
  3. Keep error messages user-friendly and instructive.
  4. Review fields periodically to maintain a clean asset metadata structure.
  5. Align custom property definitions with compliance and audit requirements.

Was this page helpful?