# July 18, 2024 / đŸ± Bunch of improvements **URL:** \ **Category:** Changelog\ **Created:** [July 18, 2024, 1:20pm UTC](https://community.fibery.io/t/july-18-2024-bunch-of-improvements/6413 "2024-07-18T13:20:37Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [July 18, 2024, 1:20pm UTC](https://community.fibery.io/t/july-18-2024-bunch-of-improvements/6413/1 "2024-07-18T13:20:37Z")
For the next couple of months we will _mostly_ work on improvements, including views, entities creation, settings, etc. We are going to streamline many workarounds and improve overall Fibery experience. Here we go! ## Reactions and entities mentions in inline comments Now you can react to inline comments and mention entities using # shortcut. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/3a1912e6557d18ae0aeff1d02d8292aad9490b46.png) ## Specify the exact Rule instead of Fibery (rule) in audit log and entity history Previously, when trying to trace back why a field value was changed by some rule, it was **very** challenging to identify the exact rule that triggered the change, especially when multiple rules were at play. Now you can clearly see the rule that did the change. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/c/c8a9d7365a95e178735506adf6ba7d12a99251bb.png) ## Multiple Highlight Databases You can create and manage multiple Highlight databases and change their names and colors, just like any other database in Fibery. The only restriction is that you cannot set the same source in different Highlight databases. However, there are no restrictions for Highlight targets. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/4/410d75e829f5e4f5c28004a03dd1cf8474a655e3.png) This feature can be handy if you would like to use the Highlight feature for different use cases. ## Switch Field visualization on Grid (Table) View Previously, we enabled the ability to change how a Field is displayed in most Views, including the Entity View. Now, this feature is also available in the Grid View. You can access this option through the individual Field settings in the Columns menu. ![preview_gif](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/d/d3e10b27cef1e5e03819b40527ea8bb72bfbe7a5.gif) ## Import from Space screen database menu You can import CSV files from the Database menu. Using this option, the default setting will be “Existing database” import and the corresponding space and database will be preselected to avoid importing data to the wrong place. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/e/e0ec87b8eca9667bf009f875069b0737129cd144.png) ## Hide 3-dot menu for Pinned units when nothing is pinned We’ve hidden the `More` menu from Pinned Units section of 2-Column layout when no Units are pinned in order to free up some space. First Unit can be pinned via Field’s `More` menu. Others can be pinned either from Field’s `More` menu, or the old way. We’ve kept the ability to unpin Units and change their visualization from the original `More` menu when it’s present on screen. ![gif_preview2](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/77a6099e5fff22816d3e68c07ebb234df0672fdb.gif) ## Whiteboard: show 2+ relations between entities of the same nature Now, you can view and manage multiple relations between entities of the same nature on one line. For instance, `Feature` → `Tasks`, and `Feature` → `CriticalTask`. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/9/9487dd5db3affbc8f1f265a597346fe501714691.jpeg) The new update introduces a Relation popover with additional options, allowing you to view each relation on a separate line for better clarity and unlink all or any specific relation. ## 🩋 Improvements - Public Space Form View should work as it is shared. When there is a Form View in a space and space is shared to web, anybody is able to access this form and submit a new entity now. - AI limits for rules are enforced now. ## 🩐 Fixed Bugs Some random bugs: - Error in AI highlight suggestions - Deleted space stays displayed in sidebar of shared workspace - Inline comments: Convert to entity mention does not work - Inserting link into view description or comment suggests Mention but it can not be really added there - When sorting groups in Table View the sorting column requires to be present Whiteboard bugs: - Escape does not work on whiteboard as described in shortcuts - No error on UI if user tries to draw relation line between entities to which he doesn’t have edit permissions - No error on UI if user tries to delete relation line between entities to which he doesn’t have edit permissions - Line doesn’t look selected if it’s locked - Guest can draw relation lines on whiteboart created in My Space - Shortcut for Unlink button is not shown in relation line actions - ‘Unlink’ should not be displayed for relation that are not allowed to be unlinked - Arrange Strategy doesn’t take Relations into account when Inserting Many Entities - Spot shouldn’t be draggable if it lies on Relation Link which represents more then one actual connections between Entities - Copy-paste shapes with text in it incorrectly-overrides text in every shape but one - Line does not get really locked right after selecting ‘Lock’ option - Invalid Link copy-pasting ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [July 18, 2024, 1:20pm UTC](https://community.fibery.io/t/july-18-2024-bunch-of-improvements/6413/2 "2024-07-18T13:20:45Z")
---
**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\ **Post date:** [July 18, 2024, 2:53pm UTC](https://community.fibery.io/t/july-18-2024-bunch-of-improvements/6413/3 "2024-07-18T14:53:56Z")
Awesome release! > [@mdubakov](#): > > Specify the exact Rule instead of Fibery (rule) in audit log and entity history This saves so many time! 😍 ---
**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\ **Post date:** [July 18, 2024, 3:23pm UTC](https://community.fibery.io/t/july-18-2024-bunch-of-improvements/6413/4 "2024-07-18T15:23:04Z")
> [@mdubakov](#): > > Specify the exact Rule instead of Fibery (rule) in audit log and entity history Best of the bunch! ---
**Author:** ![njyo](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/njyo/32/923_2.png) [@njyo](https://community.fibery.io/u/njyo)\ **Post date:** [July 18, 2024, 4:21pm UTC](https://community.fibery.io/t/july-18-2024-bunch-of-improvements/6413/5 "2024-07-18T16:21:26Z")
Great release that will ease overall usability! 🙂 > [@mdubakov](#): > > For the next couple of months we will _mostly_ work on improvements Happy to hear! While we always wanna have new toys, it’s great that y’all oscillate and also spend time on refinements! Looking forward to it! ---
**Author:** ![Marloes](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/marloes/32/5926_2.png) [@Marloes](https://community.fibery.io/u/Marloes)\ **Post date:** [July 19, 2024, 6:21am UTC](https://community.fibery.io/t/july-18-2024-bunch-of-improvements/6413/6 "2024-07-19T06:21:30Z")
Love this release! Thanks. ❀ ---
**Author:** ![DarrenLSchultz](https://avatars.discourse-cdn.com/v4/letter/d/45deac/32.png) [@DarrenLSchultz](https://community.fibery.io/u/DarrenLSchultz)\ **Post date:** [July 19, 2024, 6:01pm UTC](https://community.fibery.io/t/july-18-2024-bunch-of-improvements/6413/7 "2024-07-19T18:01:07Z")
First and foremost, I must say that each of these enhancements — especially: (1) extending to **_inline_ comments** the _ **entity** _-_mention_ functionality of which (in stark contrast to their **_entity_-level** counterparts) they’d been previously denied (and thus erasing the last mark of discrimination between the two, and in so doing bringing the two classes of the Fibery “Comment” into a state of full equality); (2) the exact disclosure of a triggering-rule’s identity (hugely helpful!); and (3) the ability to have (not-just-one-but-multiple) Highlight DB’s (what a fascinating and unexpected surprise) — is a truly superb, hugely life-improving, and exceedingly time-saving one, and (whether each is considered alone or when together) evoke the great sense of respect, care, and love that the Fibery Team surely has and must have for (first and foremost) Fibery itself, and more importantly for its users. That is so very much appreciated, and as always my many thanks to you, Michael — and the entire Fibery Team — for bestowing upon each of us such a wonderful array of gifts. Secondly (and admittedly based merely on my few minutes of use with these new functionalities so far) I do have one quick question if I may, specifically regarding the first of the above-listed improvements — the addition of _inline_-comment _entity_-mention functionality. More specifically, it appears that — unlike their _entity_-comment counterparts — _inline_-comment entity-mentions **do not seem to trigger the usual/expected generation of a back-link/reference** in the referenced entity’s References field (i.e., as seen when entity-viewing the same). As this behavior appears to differ entirely from what happens everywhere else in Fibery, I respectfully suggest that it is indisputably unexpected. And so, if I may ask, then: is this in fact (as I assume it to be) _unintended_ behavior (or could it instead be intended)? As, in my view, the natural extension of such back-link/reference functionality to the newly-added inline-comment entity-mention would be tremendously helpful and beneificial across the board, I very much hope it to be the former. Either way, my many thanks for your time and consideration (and for all things “Fibery” as always). ---
**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Post date:** [October 13, 2025, 10:26am UTC](https://community.fibery.io/t/july-18-2024-bunch-of-improvements/6413/8 "2025-10-13T10:26:34Z")
> [@mdubakov](#): > > - Public Space Form View should work as it is shared. When there is a Form View in a space and space is shared to web, anybody is able to access this form and submit a new entity now. I can’t get this to work. When the database the form is for is also part of the shared space, it works. But if the database is part of a different space, and the form publicly shared, the form view in the public space does not work. The database should not be in the public space, as that would give everyone access to the data in the database (form submissions) ---
**Author:** ![Polina\_Zenevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/polina_zenevich/32/480_2.png) [@Polina\_Zenevich](https://community.fibery.io/u/Polina_Zenevich)\ **Post date:** [October 16, 2025, 2:03pm UTC](https://community.fibery.io/t/july-18-2024-bunch-of-improvements/6413/9 "2025-10-16T14:03:07Z")
At the moment, public Form Views only work if the Form’s database belongs to the same space that’s shared publicly. This is a deliberate design choice — it prevents unintended access to or modification of data from unshared databases. In other words, if the database isn’t part of the shared space, the system blocks submissions to keep your data secure. If you need to allow anonymous form submissions **without exposing existing data** , this isn’t currently supported out of the box. The only available option is to temporarily place the database inside the shared space (which, as you noted, makes all entities publicly visible). ---
**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Post date:** [October 16, 2025, 4:21pm UTC](https://community.fibery.io/t/july-18-2024-bunch-of-improvements/6413/10 "2025-10-16T16:21:57Z")
I see, makes sense. Would it make sense to extend the “Do not share databases with spaces” feature coming up to public spaces? I don’t know if it’s within current scope, but maybe then a use case like this could be supported? Right now it needs two databases, one to capture in the shared space, then send it into a database in a non-shared space, and then delete the one made in the shared space. Not ideal. I think this is quite a common problem as forms in public spaces are often used to get people’s details, which is sensitive information. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [October 16, 2025, 4:41pm UTC](https://community.fibery.io/t/july-18-2024-bunch-of-improvements/6413/11 "2025-10-16T16:41:45Z")
> [@Polina\_Zenevich](#): > > public Form Views only work if the Form’s database belongs to the same space that’s shared publicly Just to clarify for anyone reading this out of context, a form view can be shared on its own i.e. without necessarily sharing an entire spac, and will be functional for anonymous submissions. The explanation above relates to sharing a space, that contains a form view in the sidebar.