Feature(s) impacted
We have a smart action for our users that allows them to upload a document. Sometimes, we also need to let them fill out additional information related to the document. To achieve this, we created an action that pulls the different document types. Each type has a corresponding database field we called extras, which is a JSON object where we define the fields we need.
When a document is selected, we fetch the extras and dynamically generate the additional fields required. This functionality was working perfectly until a few weeks ago when it suddenly stopped working. From our side, we didn’t make any changes or updates to this part of the system, so we suspect the issue might be due to a Forest Admin frontend update.
To help diagnose the issue, I’ve attached our extras JSON configuration and a screenshot of the current state of the smart action. Currently, all we see are six status fields, which is unexpected.
{
"fields": [
{
"type": "Dateonly",
"label": "Closing Date",
"isReadOnly": true,
"isRequired": true,
"description": "Document specific field"
},
{
"type": "String",
"label": "Current Financial Institution",
"isReadOnly": true,
"isRequired": true,
"description": "Document specific field"
},
{
"type": "String",
"label": "New Financial Institution",
"isReadOnly": true,
"isRequired": false,
"description": "Document specific field"
},
{
"type": "Number",
"label": "Mortgage Charge Amount",
"isReadOnly": true,
"isRequired": true,
"description": "Document specific field"
}
]
}
Observed behavior
Expected behavior
We are expecting for the smart action to open up and let us pick a document type from there it will then show the fields we need to fill out
Failure Logs
Logs are not returning back any errors
Context
- Project name: Ourboro
- Team name: Ourboro
- Environment name: ourboro-development
- Agent technology: (nodejs)
- Agent (forest package) name & version: “@forestadmin/agent”: “^1.49.0”,
- Database type: postgres
- Recent changes made on your end if any: …