Sep 19, 2024 / đŸ± Pin Relation Views, Search in Relation Views, Filter search results by final state, and many more usability improvements

Today’s release is like a bento lunch. There is a good chance you will find something useful in the changelog below. Enjoy! :blue_heart:

Pin Relation Views

Now you can pin relation views and enjoy better visibility and faster navigation (in expense of more busy UI). Pinned views looks like tabs, and it makes them less heavy:

Create action is more visible in Search

Create from Search user experienced streamlined. Now you can create new entities fast using just the keyboard.

Search in Embedded & Relation Views

Now you can search in relation views. Click search icon or use Cmd + F (Ctrl + F on Windows) if the view is in focus:

Filter Search Results by Final State

Done and Final items are rarely needed in Search (but sometimes they are needed), so they are filtered out by default now.

2024-09-19 09.34.31

Search in panel icon improvement

New search icon was conflicting with close panel action, we’ve made it less annoying and now you can close panels without problems.

2024-09-19 08.55.22

Keyboard navigation and filter to Go-to Menu

Go-to menu got better: keyboard navigation and quick filter by Views added. Now you can navigate even faster.

2024-09-19 09.36.15

Relay.app integration

Fibery integrates with Relay now. Relay.app is an automation tool that people love for its deep & easy-to-use integrations, embedded AI features, human-in-the-loop functionality, and powerful workflow essentials.

Whiteboard: Updated fonts selector and default font set

We’ve updated our Whiteboard’s font selection with a refreshed default set. Inter is the new standard, along with modern additions like Open Sans, Roboto variants, Merriweather, and Caveat. This update includes custom font rendering on the canvas, a font preview feature in the selector, and an updated font color icon with a color preview.

Whiteboard: Updated header

We’ve updated the Whiteboard header and zoom toolbar interface to ensure consistency with other view types in Fibery. Whiteboard-specific actions are now all in one easy-to-find place in the toolbar.

Support Reply Headers in Send Email action to be able to communicate via Email from Fibery.

Now you can set In-Reply-To: and References: headers in Send Email action, and it means you can actually create a button to reply to emails in Fibery.

  • Make sure that Subject is set as a formula: "RE: " + [Step 1 Message].Name
  • Make sure that In Reply To (and References) fields is set as a formula: [Step 1 Message].[Original Message Id]

Improvements

  • The Fields action menu on Lookups collection is updated to look good.
  • API Token Activity Details. You can now see the “Created” and “Last Used” dates for API tokens, along with the token prefix. For older tokens, the creation date won’t be available and will show as “N/A.” Activity tracking (last used date) will also begin from this release onward.

:shrimp: Fixed Bugs

  • Table View:
    • Another entity get opened in the right panel when click on any cell in the table
    • Sometimes calculated width for columns is too narrow or too wide
  • Whiteboard:
    • there is “Delete” option for View Card but it throws error
    • Bad lines re-positining on moving selected set of cards
    • There should be no Delete option if Entity doesn’t exist
    • It’s impossible to draw curved line on whiteboard after you connect curved line with any other line
    • Selected text color is not applied if opacity is also changed
  • Sidebar: view can’t be dropped to be the last in Space
  • Can not create second entity in relation list using only keyboard
  • Error when user types search query for not configured view and then selects database
  • Wrong place for ‘Search this view’ in public shared view

:sweat_smile: Now tell us what is your favourite improvement?

15 Likes

Wow! Some good ones here. Always looking forward to Thursdays!

4 Likes

“Search in Embedded & Relation Views” :grinning:

4 Likes

Another great release! Thanks for tabs & search in relation views!

Honestly, the biggest thing on this list for us is the table view bug fix because it was incredibly annoying to have an entity open up when we just wanted to edit the value of a cell.

1 Like

WOW :heart_eyes: What a release!

Can’t pick one :joy::joy: all of these :heart:

And really glad with this fix

3 Likes

Initial feedback on Search in relation views (and I think it applies to regular views too, I we just rarely use them):

  1. I wish it would also search the names of any entities that are displayed on the view, including related/referenced entities.

For example, here we have a client entity called “Human_Code” that is displayed within the view normally, but when I search for “human”, nothing gets found.


  1. Since the search is essentially a type of filter, I feels like it should remain visible on the screen when a search query is active, even when the user’s mouse/cursor isn’t still in the search box. Since there’s no “error” or “no results” message that is displayed, users could be confused as to why nothing is being displayed and not realize or remember a search filter is active.
8 Likes

Again constantly impressed by the output of this team. I feel like I’m getting to watch the software develop/evolve in real time.

Love the iteration on the pinned views, more minimal compared to the previous design.

5 Likes

Whiteboard refinements will almost always be my favourites, but lots of refinements are great like the filtering of Done items. :slight_smile:

Your update posts are my highlight of Thursdays, I’m addicted. :face_with_peeking_eye:

7 Likes

Some much goods news but I really like this one

A deep integration with emails would be so valuable. I can understand it is not an easy task but I dream of Fibery as my email client with its multiples views, direct links from messages to opportunities, support requests, projects, 
 and even inbox sharing.
Instead of email clients that add tags, categories or task management, I would prefer a the Fibery semi-structured flexibility linked to my main source of inputs : emails.

Thanks a lot for according this some love recently.

3 Likes

Small bug:

When I work split screen (and even when I don’t work split screen) most of the relation view names are not visible anymore because of the new search field.

Maybe an idea to turn overflow off when a user doesn’t hoover?

image

We are working on improving the search in relation view behavior :pray:

5 Likes

The new create entities via keyboard is awwwwsome

1 Like

I dig into this vision this week btw, and there are a lot of things we should do to make it happen. At least the scope is shaping up, but I am not sure when we will really attack this problem holistically. Here is what is missing

  1. Ability to connect several emails accounts into a single database, otherwise you will end up with many Message/Email databases.
  2. Support Groups emails (like google groups), now they don’t work for Threads
  3. Implement multiple relations, so Email can be linked to any database with a single relation
  4. Many UI improvements for sending and visualizing emails threads
  5. Finally, somehow hide private Emails from anybody (maybe even from admins), so any user can setup email account in Fibery and control what other people see
  6. And maybe more things I missed in my analysis :slight_smile:
2 Likes

Very excited to see this aspect of the product getting some love, as like the OP, my primary input are emails as well. There’s been some amazing leaps in the last handful of releases, and we’re getting closer and closer to this being a nearly-seamless experience between email and Fibery. Kudos to you and the team!

1 Like

Is there a way to go back to the old search where I don’t have to click on “finished items” every time? In our workflow we often reference completed items and this is a major annoyance.

Great update otherwise :slight_smile:

We explicitly made this setting off and not saved, but we may also just save your latest choice and it will solve your case. But it will add some annoyances to other cases.

Is the “original message ID” just the public ID, or is there a new hidden field you’ve created behind the scenes for email entities?

EDIT: Nevermind, I see that there’s a new field that is needed to turn on in the sync settings!

1 Like