This release is dedicated to polishing and small improvements in many areas.
Updated Entity View Header
Entity View header was updated to match new Views headers released last week. Multiple Entity Views switcher is more visible, panel navigation is moved to the right, and you can jump to space fron any entity with a single click.
Weâve added a Go-to navigation on Entity View (find >> icon in the top right corner). You can quickly jump to database setup or to any view that contains this database. For example, here you can see all Views we have with Features and I can quickly jump to relevant views and go back.
NOTE: Views in go-to menu are only from databaseâs Space. For example, if Feature is in Product Management Space, then only Views from Product Management Space will be listed.
đŤ Reorder rules & buttons
Now you can drag and drop automation rules and buttons to organize them better. Consistency FTW!
NOTE: Rules execution order is the same you see it on UI, so now for complex cases you can set what rule will be executed first.
Lock Whiteboard
Now you can Lock whiteboard for all users. In this case users will not be able to change it easily. Note that any user with Editor access can unlock a whiteboard. This is expecially useful for whiteboards that you embed into documents.
Improvements
Email integration: To organize related email messages in Fibery, we support email threads in the Email integration now.
Email integration: Both the Inbox and Sent folders are part of the default settings to enable the proper thread view that we released.
To avoid unexpected sync issues, the sync configuration will disable newly added third-party fields to already running integrations.
Fixed Bugs
Whole page gets reloaded on cleaning whiteboard
Import:
CSV Import 2.0 field settings does not work
Do not display/add âdeleted in sourceâ field for Import
Integration: Cancel button inactive on the During sync
Field Creator may fail a batch job where there 10+ fields to create
CSV export is adding extra unnecessary columns
Document header gets hidden forever after i create some stuff in document
Currently, we have 2 databases: Message and Contact. The problem is that there is no easy way to group related messages in threads.
Solution:
Create Thread ID field in Message database which is a relation to a root Message
Populate it using first element of References header in IMAP response which contain Message-IDs (we take 1st since it is the id of the first email sent).
User will be able to create list view and group Messages forming Threads and order child Messages by Date:
This is awesome! After my initial post, I spotted that there are now âThread IDâ and âOriginal Message IDâ in field options for the email integration.
I turned those on for my existing email integration, did a sync, and didnât necessarily notice threading happening 100% of the time. But maybe I mixed something up?
Original Message ID is appearing in the field data, but the auto-linking doesnât seem to be happening in all cases. Maybe I need to just give it some time to process through the messages. Hereâs the setup:
We have one limitation here: Limitation: Some email clients or servers might not properly set these headers, and forwarded messages can break the thread structure.
Maybe indeed it takes some time to sync if you have a lot of emails, but no more than few minutes.
Really appreciate the focus over the last month or so on UX that has improved parity on duplicating and reordering things!
Also love that we can now go directly to the database from an entity, but it feels a little unnatural to have to go to the far right and do two clicks when youâre only a single click away from the space on the far left and the database name is already directly underneath it. In your example, why canât we just click âSPACESHIPâ to âJump to databaseâ?
Great to see the email integration is getting some love as well. Is increasing the sync frequency on the agenda anytime soon, or if not, could you provide some context as to why itâs currently so infrequent (60 mins)? Weâd prefer to use Fibery to manage our customer service inbox, but currently have to use a different platform because the sync infrequency is a deal breaker.
Could you add a âGo-to viewsâ option for views, similar to the âGo-to views/databaseâ option you just added for entities? We need a quick way to see and navigate to all views that are related to an entity when looking at context/relation views.
When the view is in a collapsed/embedded state, itâs easy to change to another view since thereâs a dropdown:
Oh and I really hope you guys can rework the behavior of the search icon in the entity view header.
Because the icons up there are so small, and the search is smack-dab the middle of the other icons, itâs much too easy to accidently mouse over the search icon when trying to get to something else. When that happens, the two arrows expand and block the other icons, which means you need to fiddle your mouse around to get the icons you originally were trying to access to be visible again. Itâs a relatively small thing that isnât so bad the first time it happens, but is really annoying the 10th time it happens in a day!
Simple solution would be to put the search icon to the left of the other icons and then have the search icon and arrows expand to the left of the other icons instead of overlaying them.