What's new in Forest Admin: Collapsible Action Forms, Duplicate Workspace...

Although we lost an hour of sleep in the past month, we've been busy cultivating some new features and enhancements in Forest Admin, to ensure your teams get to make the most of these brighter evenings.

Collapsible action forms

If you've ever had to stop filling out an Action Form halfway through, because you needed information available behind it in a Workspace, or on another Forest Admin page, you'll be happy to know that it will now automatically collapse as soon as you click away from it.

This will enable you to navigate your project as needed, and pick up where you left off by accessing the ongoing Action from the top-right hand corner of your screen once you've found what you needed.

And also...

Duplicate a Workspace

Need to put together a new workspace based on an existing one? You can now simply duplicate it so you can start from the same base.

N.B.: this is currently only possible within the same Team

UI Branch Creation

Developers can now create new branches straight from the UI, adding to the CLI method. Learn more about our Development Workflow on how to push UI changes from one environment to the other.

Mongoid <> Ruby

Mongoid datasources are now available for Ruby agents.

Coming soon

Forest Admin MCP Server

Our Product team is currently looking into building an MCP server, which could be used to create AI Agents!

Does that sound in line with your plans? Feel free to book some time with us so we can discuss this together!

Multi-inbox in Workspaces

What's better than an Inbox in a Workspace? Several Inboxes in that same Workspace!

Provided that they're set up on the same Collection, it will soon be possible to configure multiple Inboxes, without having to re-map every single linked component, enabling your operational teams to use the same Workspace, while benefiting from better segmented records to process.

Organize your Segments independently from their Collection

Operationally speaking, records that belong to a single DB table may be handled very differently depending on their Status, Country, or any other field.

To better reflect this, it will soon be possible to organize Segments independently from their parent Collection, so they can be placed alongside Workspaces, Inboxes, or Dashboards that are relevant to how you need to process them, not how they exist architecturally.

That's all for this month, folks!