Feature(s) impacted
Smart Actions are not appearing in any Forest Admin collections (QRCode, ServiceProvider, Hotel) despite being properly defined in both routes and actions files. The Smart Actions tab shows “No Smart Action - This collection does not have any Smart Action yet” for all collections.
Observed behavior
-
No Smart Actions appear in any Forest Admin collections
-
Smart Actions tab explicitly shows “No Smart Action - This collection does not have any Smart Action yet”
-
Server logs show “Forest Admin actions registered successfully”
-
Tried troubleshooting with:
-
Incognito mode
-
Disabled browser cache
-
Verified role permissions (single role with triggers allowed)
-
Checked layout editor and Smart View tab
-
Routes are properly defined in forest.js
-
Actions are defined in actions.js but using inconsistent registration methods
Expected behavior
Smart Actions should appear in:
-
ServiceProvider collection (Upload Photo action)
-
Hotel collection (Upload Photo action)
-
QRCode collection (Test Action, Generate QR Codes, Download QR Codes)
-
Smart Actions tab should show these actions and allow configuration
Failure Logs
// From app.js initialization
Forest Admin collections: [Object.keys(forest.collections)]
Forest Admin actions registered successfully
// Actions registration in actions.js using inconsistent methods:
Liana.collection(‘QRCode’).addAction(‘Test Action’, {…}) // One method
Liana.collection(‘ServiceProvider’, { actions: [{…}] }) // Different method
Context
-
Project name: HotelsConnect API
-
Team name: HotelsConnect
-
Environment name: Development
-
Agent technology: nodejs
-
Agent (forest package) name & version: forest-express-mongoose v9.5.0
-
Database type: MongoDB
-
Recent changes: Multiple attempts to register actions using different Forest Admin methods
-
Browser troubleshooting completed (incognito, cache disabled)
-
Role permissions verified (single role with triggers enabled)
-
UI configuration attempted through layout editor and Smart View tab
The core issue appears to be inconsistent action registration methods and potentially incorrect initialization timing in app.js. Client-side caching and permission issues have been ruled out through testing.