Example: In the entity view for my Client DB, in the RTF Description field, I want to embed a Table View of Tasks that are linked to this Client entity via a particular Relation field.
I can use the Table View’s row filter to accomplish this, but I have to manually explicitly select the specific entity (i.e. this Client entity).
If I subsequently duplicate this entity, this filter will no longer be correct, as it will still point to the original entity.
I’d like to see options in the embedded View Row Filters when filtering on a Relation to this entity’s DB that would allow me to specify “is this entity” or “is not this entity”.
This request is specifically about the new RTF embedded Views - I think in an entity’s relation views they can only show related entities (i.e. they are automatically filtered by “related to this entity”), but in the embedded views it appears there is no equivalent, simple, “portable” way to specify the same constraint.
So just checking - when Table view becomes available as one of the relation view types, is there any reason why you would need/want to have context filters for the embedded views in rich text fields?
I envision making “dashboard like” entity Descriptions, that include various Views of the entity’s collections. This is where I imagine it will be very useful to be able to copy one of these Dashboard’s RTF content (with embedded views) and paste it into a different entity’s RTF, and have those embedded views “automatically adjust” to reference the new entity.
If I’m not mistaken, you’ll be able to embed existing Table (and other) Views into Rich Text. I wonder if this would include individual Entity “Context Views”. Sure hope so! If so that should solve this, no?
In other words if you wanted to, say, embed all the context views for a given Entity into its Rich Text so for example you did not have to keep picking them from a dropdown, then you could do this if you are able to embed any Entity’s Context Views in a Rich Text. Here’s hoping. (although a native feature to “pin” multiple context views open would solve this better)
However, this part is tricky and doesn’t currently work as Matt describes:
I envision making “dashboard like” entity Descriptions, that include various Views of the entity’s collections. This is where I imagine it will be very useful to be able to copy one of these Dashboard’s RTF content (with embedded views) and paste it into a different entity’s RTF, and have those embedded views “automatically adjust” to reference the new entity.
So far embedded context Views are always per Entity as opposed to relation Views which are always per Database. We are open to tweaks though
I would love to use embedded context views in our workspace. But for our set-up it’s currently not possible. Will share it below so that you have more use cases/information for future decisions.
Our customers
Will buy the complete Fibery workspace which we’ve designed & build for their company. They never worked in Fibery before and are not tech-savvy. Therefore we want to make things as easy as possible.
Our previous set-up
First we had the ‘normal set-up’. All views/smart folder in the left menu. But because our workspace is so big, it resulted in complete overwhelm.
So we’ve created our own ‘menu’ > basically documents per category with hyperlinks to relevant views.
This felt clean but user needed to click a lot to see relevant information.
Overview of menu page
Klanten (Client) page with all views that are applicable for clients.
Yes, it had a clean look & feel. But the UX sucked. It was not always clear what you could expect ‘behind the hyperlink’. We couldn’t embed all views in the document because
There was not enough flexibility for switching between views such as ‘active / inactive’.
A user can easily delete an embedded view
References were always shown at the bottom of each page which was mainly clutter and not helpful.
New set-up
It has some pretty ugly workarounds But what I did
Replaced the ‘document menu items’ with database entities. I’ve created an entity for every menu category so that they can be clickable via a smart folder.
Because every category has it’s own set-up / relations to the rest of the databases in the workspace, I needed to create a separate database for each menu item.
And it ends with all relevant Wiki articles about the category so that they never get stuck.
My set-up is a solution for the following problems/needs
User wants to work as efficient as possible.
User wants to have a workspace where they can manage their whole company, but they don’t want information overwhelm and losing headspace while looking for the information they need.
User wants to see all information that’s handy for a use case in 1 overview so that they can make decisions fast/easily. Examples:
Our whole workspace is connected. It depends on the use case which information is needed and which filters are applicable.
So on the ‘Clients’ pages you will see contacts but also client projects. Both active/inactive.
On the ‘Planning’ page, we’ve only linked active client projects. There you will also see ‘Internal projects’ since you need both while creating a planning.
While making a planning, you will also see your ‘Goals’ on that same page. Because it impacts your planning.
If user want to create ‘Goals’, they will go to that specific page. There you will see linked internal projects, reflection of past periods, data dashboards etc. Since that’s the information you need when you want to set new/evaluate goals.
If you create a weekly review, you will see it automatically in your monthly review. And that monthly review in your quarterly review. And those in your yearly review. So that you can easily have all handy information in one place. And those reviews are also linked to the applicable planning/goal pages of that period.
What would be handy
Solve the above problems/needs without so many workarounds Wanted to share my set-up/use cases so that Fibery can decide what future improvements are handy for views / menu set-up.
Being able to show entities also wide screen when there is an empty right panel.
Most views are needed on different ‘menu pages’. We’re currently creating views per page.
Would be great if we can somehow have ‘one source’, like we have when we embed a view. But then with the possibility to switch between views. And avoid that users accidentally remove the embed view (with backspace/delete).
As a user, you want to see if there is only one view or multiple views hidden under the arrow. Currently it always looks the same. Therefor you don’t know if there is one view (and you don’t need to click) or multiple views.
Would be great if you can link directly to a context view. Because sometimes that’s enough for a use case. Currently, you can only link to normal views. The context views do have it’s own URL so I hope that it’s technically possible.
If our set-up remains the same, then it would be handy if you have the option to show view description as well. Since it’s not always clear what ‘Name’ field means for example and how to use the view. As a workaround, I’ve put the information in rich text fields.
My use case is that I want to embed a view with related items in a rich text.
For example, let’s say I have an entities called Project with Phases with Tasks. Now of course each of these entities already automatically has a view of the related entities.
However, my Project will have a description and the Phases are a crucial piece of information in that. I want to be able to list them inside the text with the rest of the summary, rather than below or above as a sterile view.
Hope that explains the use case for a “show all Phases related to this Project” type of view. Thanks!
This a another good argument for some kind of “lock content” switch for Rich Texts (either per-entity, or per-field at the DB/schema level).
Otherwise we need awkward workarounds like creating a Rule that overwrites the content with what it “should” be, if it is accidentally modified, or a button to initialize/restore the content, etc.
But what I did
Wanted to share my set-up/use cases so that Fibery can decide what future improvements are handy for views / menu set-up.
