Feature Form Guide

The Feature Form allows administrators to create and configure business features inside a module. Features represent specific functionalities, workflows, screens, APIs, reports, dashboards, and business processes available within the platform.

Overview

The Feature Form screen is used to create and maintain features associated with modules and applications.

  • Associate features with parent applications
  • Link features to parent modules
  • Configure feature web slugs
  • Define primary database base tables
  • Assign FontAwesome feature icons
  • Configure feature category types
  • Select presentation UI engines

Feature Form Fields

The following fields are available in the Feature Form.

Field Description Required
Application Name Select the parent application to which the feature belongs. Yes
Module Name Select the parent module associated with the feature. Yes
Feature Name Enter a unique and meaningful feature display title. Yes
Feature Slug URL-friendly unique identifier automatically generated from name. Must be unique. Yes
Engine Select the UI presentation engine (e.g. List View, Form View, Page Builder). Yes
Base Table Primary database table linked to the feature. Yes
Feature Icon Font Awesome icon class used for navigation display (e.g. fa-solid fa-cube). No
Feature Type Defines the feature category (Configuration / Component or Public Component). Yes
Feature Status Select Active (1) to enable or Inactive (0) to disable feature visibility. Yes
Feature Form

Feature Form Help Guide

The Help Guide panel provides field-level explanations for administrators.

  • Application Name – Feature ownership application.
  • Module Name – Related business module.
  • Feature Name – Business functionality name.
  • Feature Slug – URL-friendly unique web identifier.
  • Engine – UI presentation engine used by the feature.
  • Base Table – Primary database base table.
  • Feature Icon – Navigation menu display icon.
  • Type – Feature classification category.
  • Status – Feature active/inactive visibility state.

Toolbar Options

Import

Import feature configuration data.

APIs

Access feature API documentation.

Back

Return to Features List screen.

Validation & Duplicate Prevention Rules

  • Application Name selection is mandatory.
  • Module Name selection is mandatory.
  • Feature Name input is mandatory.
  • Feature Slug is mandatory and auto-generated in real-time.
  • Duplicate Slug Validation: Submitting a Feature Slug that already exists displays error alert 'Feature Slug Already Exists!' and halts save.
  • Engine selection is mandatory.
  • Base Table input is mandatory.
  • Feature Type selection is mandatory.
  • Feature Status selection is mandatory.

Best Practices

  • Use clear, meaningful feature names.
  • Follow consistent lowercase slug naming standards without spaces.
  • Use standard FontAwesome icon classes.
  • Link features to the correct parent modules and applications.
  • Use proper database table naming conventions.
  • Select the appropriate UI presentation engine.
  • Keep feature configurations organized and maintainable.