Feature Requests

Escalation workflow on a recurring basis until resolved

Duplicating a custom service request form with conditional logic and response rules (such as field visibility or response validation), does not carry them over to the new form. This forces users to manually reconfigure the logic, which is time-consuming and error-prone. [ALR]

To filter the data breakdown by customers. Total number of leases per customer Total lease value (rates/amounts) per customer Lease duration trends per customer Active vs expired leases per customer --- Active vs Expired Leases: A pie chart showing the proportion of currently active leases versus those that have expired. Lease Duration Trend: A line graph tracking the average lease duration (in months) over the past several months.

Total leases per location Occupancy rates by location Total rental income from each tagged area Lease end dates grouped by location These insights support space utilization planning, localized maintenance budgeting, and revenue forecasting by site.

Total number and value of leases by label category Trends in short-term vs long-term leases Revenue generated from different lease types This adds reporting flexibility and supports better decision-making on lease strategy, pricing models, and resource allocation.

Implement AI-powered suggestions that intelligently recommend the most relevant asset categories (or specific assets) based on the request context. The AI could analyze: Request titles and descriptions Historical linking patterns Frequently linked assets for the same user or request type Keywords (e.g., "aircon" suggests HVAC assets) These recommendations would appear at the top of the selection interface or as a pre-filled suggestion that can be accepted or modified by the user. Why is this helpful? This reduces manual effort, minimizes errors, and speeds up the process of linking assets to requests. It enhances user experience by anticipating intent and providing relevant suggestions, especially valuable for organizations managing hundreds or thousands of assets.

When users or responders attempt to link an asset to a request, they are shown the full list of all assets. This can be time-consuming and inefficient, especially when the asset list is extensive and the user does not use the search function. Introduce a two-step selection process when linking assets: First, the user selects an Asset Category (or Asset Type). Then, a filtered list appears showing only assets within the selected category, from which the user can select or search the specific asset.

Introduce functionality to define parent-child relationships between assets, where: A parent asset can have multiple child assets Each asset record clearly indicates whether it is a parent or child, and shows its linked assets. Searchability: Easily search and filter by parent or child asset names and IDs. [ALR]

For a) criticality b) status c (i) asset category c (ii) asset sub category [ALR]

Shared Device Mode: Ability to use a shared device or all staff to check in/out. [Primech x RP]