Description
👮 Validation rules
Today we're introducing Validation Rules. Validation Rules in Fibery help keep your data accurate and consistent. Think of a validation rule as a bouncer at a club door 😎. Before any data change gets in, the bouncer checks: "Does this meet our standards?" If not, the change is blocked and the user gets a friendly explanation of what's wrong.
A validation rule fires when its condition is true, and it blocks the action. So you're essentially defining "what should NOT be allowed" rather than "what's valid." Condition is a formula, so you have the whole power of formulas to describe conditions.
For example, you can create rules like:
Planned End date should never be before Planned Start date.
Ensure Owner is assigned for In Progress Features.
Do not allow phone number that is not in specific format (for example, (123) 456-7890).
Do not allow sales probability below 0% or above 100%.
In near future we will allow:
😅 Note that some complex formulas may not work, please report them to us and we will make them work.
Validation Rules are available in Pro & Enterprise plans. Check validation rules user guide to learn how they work in details. Please share your first impressions and useful cases!
Entity View: Quickly Show/Hide all fields
Now you can quickly show or hide all fields in entity view. It will help you create new entity views faster.
Whiteboard: New Connector styles and options
We’ve added more arrow types and line styles to support more kinds of diagrams. You can now use line jumps and a double-line style with all connectors, and we’ve updated the connector behavior algorithm to work better with different line thicknesses.
Connectors also support custom colors and styles. When you select the connector tool, a new menu lets you choose the type, color, and style before you start drawing, so everything looks right from the start.
"Periods" integration
Sometimes a date field just doesn't cut it. You want to be able to refer to a specific week, or month, or quarter, and you want these periods to be connected to each other, e.g. February 2026 is part of 2026-Q1.
With the Periods integration template, you can have a complete set of entities, representing periods of different types (granularity levels) and then make connections to them.
Check out the guide to understand how it works and how to configure it, and check out some of the use cases.
🦋 Improvements
Views: View settings now have proper empty states. If a view isn’t configured yet, users will see a helpful message explaining what’s going on.
Performance: Integrations performance improved in many places, including generic improvements and specific things for GitHub, Google Calendar, Readwise. CPU utilisation dropped significantly and there are no more 90% spikes.
🦐 Fixed Bugs
Documents / Rich Text:
Whiteboard:
Views: Now it is possible to see hidden entities under '+ more' items in read-only collection unit
Files: Fixed broken files in a field on Entity View when cmd+z (undo) is pressed after Delete all files
Permissions: Now a user can move or copy documents from Private Space to shared Space (Member / Editor access)
Reports: Now a user can create a report if relative custom date is used in source filter
AI Agent:
Fix in Build mode when Fibery AI creates text fields too often
Fix in Build mode when Fibery AI populates percents incorrectly
Fixed a case when mention links are not parsed correctly resulting in bare text/links
Callout Markdown is recognised now
Fibery AI no longer uses fake emojis in rich-text fields
Fibery AI no longer create broken self-relation hierarchical views
When AI agent runs out of steps, user is informed about the work done now