The smallest release today with some improvements and fixed bugs.
Whiteboard: more icon libraries
We’ve added popular icon libraries to the Whiteboard to help you build diagrams faster:
AWS
Azure
Google Cloud
Now you can quickly add cloud and infrastructure icons while mapping systems, sketching architectures, or explaining ideas to your team.
Improvements
Rich text. Use Cmd/Ctrl + Shift + H to quickly apply the last used color option to selected text (text color, or background color, or text+background color)
Duplicate entity. Now, when duplicating an entity, you have the option to either copy all deeply linked collections associated with this entity or not to copy them.
Default Form for entities creation. When some form is marked as Default on some view, all New actions for this database entities on this view will invoke this form.
AI. Creation of Spaces, Views, and Databases is unified.
Convert entity. Some time ago we ceased to delete source entity after conversion. It appeared this decision was not great, so no Fibery deletes source entity after the conversion, again.
Fixed Bugs
Duplicate entity:
Error on duplicating entity if entity fails to pass validation rule
Fixed several cases where duplicate action failed
Performance: Fixed a problem where add users and groups select is slow if account has a lot of users
Rich text: Navigation by keyboard buttons does not work in Color pop-up
Forms:
Original relation filter is applied by default to the Form but it’s not visible in Filter section
Error on Form when field used in Sort gets deleted
Missing DB selector on Timeline if 1st database from setup has required form
Form blinking and error in console when entity is created on Gantt view
Required form is not appeared when entity is created in the Row/Column and name is generated by formula
Creation entity via required form does not work in to-one reference
Forms where user does not have edit-forrm permissions should be either hidden or opened in read-only mode
Forms list does not get updated by live-updates
Invalid filters should not apply to the Form
Table View: Cell enters edit mode after clicking on Nav or Expand
Convert entity: Error on converting entity - some issue with 1:1 relation
Whiteboard: custom color input requires color to be always correct, otherwise resets to #000000
Could you please clarify ? It was a good thing to not delete it in my opinion. When we want to migrate entities from one DB to another one, it is great to have the original entity side by side with the new one so we can check if no information is lost. If everything is good, then we can manually delete the original one.
I believe the behavior originally was to not delete original, then it was changed to delete original, then recently not delete original, and now delete original again.
I have suggested this in the past: Turn off behaviours of Fibery app - #2 by RonMakesSystems, and I think it can be relevant here. If the architect could see the default Fibery actions in the buttons menu of the database, they could turn specific buttons on or off, or configure specific settings for those buttons.
For example: “Delete original entity after conversion” option settable per DB.
I personally do not understand the point of the “Convert” action, if others (@Jonathan1) can chip in here that would be great. What is the added value of using the “Convert” as opposed to making a custom action button and manually mapping out the fields?
For one-off mistakes I understand, but if its a repeatable process, why not a single button to convert to desired entity which is the next thing in the process? Trying to understand use cases here.
Just my 2 cents :))
And we know that a small release just means there’s big things in the work (or a well deserved break). Waiting patiently.
I find the Convert function useful as it happens that sometimes you create things that you deeply wants/needs to change. But sometimes, it is not possible to do that on the current structure because it is used by other users and you don’t to break everything on something in production. So you create everything from scratch and then you convert your entities to the new structure.
I see what you mean. So indeed you are not using the convert as part of a system/process, but only in specific cases you are re-configuring the system. Right? I would still go the route of adding an action button instead of relying on the default “convert” action. With scripting and AI you can make a button which duplicates the entity to a new structure, maps the fields, and duplicates the child entities as well. Then make a table view which shows all items, check all of them, press the button, and everything is migrated. After the migration, you can delete or disable the button.
Explained above, but to clarify, I wasn’t sure if you are using the Convert as part of a system/process. For example, things enter an “Inbox” database, then you convert it either to a “Task”, “Idea”, or “Inspiration”. In this case, I argue it would also be better to set up action buttons / automatons to handle this conversion instead of using the default “convert” action.
This approach is a death-sentence for usability for people who are not seasoned Fibery veterans. I think one of the biggest barriers to Fibery adoption and expansion of use is feeling daunted by defining the structure and getting it right. I have made plenty of mistakes in my workspaces and Convert is a helpful, built-in tool to manage that process of change. It’s used infrequently, but very useful when it’s needed. Even if a custom AI-built button could do the job as well or better, just having the function as something people can see in the UI has a meaningful benefit vs. them having to understand and think to build what they need with other tools.
Having said all that maybe we’re getting closer to a time where people can be trained to default to AI for all of this kind of stuff. Not just in terms of “use AI to build a button to take care of this need”, but the step before that: “I have important data in one Entity and I want to move it to another Entity as easily and automatically as possible” and then the AI is smart enough to ask if it’s something they need to do more than once, and either generate a durable solution or just take care of it if it’s a one-off.
Lastly, if Convert is going to exist as a function at all, I personally don’t understand the downside of leaving the source entity in-place. It may need some work in UI/UX to make dealing with the leftover entity as easy as possible for those situations/people who don’t want it at all, but having no option to keep it is problematic IMO.
Yeah, I get what you mean, but at the same time building a button automation and mapping fields isn’t that big of an ask if you are the Fibery Architect for your company. The rest of Fibery is much more complex.
But I also agree with this. I don’t think it should be removed. I’m just surprised this got enough feedback to be changed then rolled back so quickly. Considering that in my opinion a custom action button does the same thing but better, but requires more set up. The only time I would not to use a custom action is if it’s a one-time thing for a single entity (accidental entity creations).
I was thinking this as well. I think we’re getting closer and closer to something like this.
I think the (only?) thing that the convert does which an automation can not do is the entity mentions migration. Maybe that’s part of the reason for the default delete? Not sure.
how can we show the left pane with the icons? hhaha, created a whiteboard but the pane on the left is not showing by default. the video is incomplete now it was accessed. went to see the right side pane settings but to no avail. please help thanks
Edit: Nevermind I saw the shapes now. But still the following still applies for mermaid diagram:
and it would be nice to run the icons from the cloud archi under the mermard diagram code similar to this:
architecture-beta
group api(logos:aws-lambda)[API]
service db(logos:aws-aurora)[Database] in api
service disk1(logos:aws-glacier)[Storage] in api
service disk2(logos:aws-s3)[Storage] in api
service server(logos:aws-ec2)[Server] in api
db:L -- R:server
disk1:T -- B:server
disk2:T -- B:db
Yes this is exactly what I’ve doing for last 2 weeks and enjoyed the behaviour. I would hope that destructive actions are behind failsafe. Every other delete is behind “Are you sure?”.
Everyone can have a different use case and preference but the problem is/was the label.
“Convert” is a transformation so I would expect delete original. I was just pleasantly surprised it kept the original.
But if you could maintain the behaviour maybe add it back as a 3rd option under the new Duplicate menu which is “Copy and move” ?
To be honest it’s the “usability death sentence” for everyone including Fibery veterans.
There are very few Architects at each org and they need to spend their time on high leverage activity. Easy things should be easy otherwise it’s frustrating UX and people give up.
If you like the philosophical arguments you may really enjoy the discussion with Stewart Butterfield (around 37min) on that point. Sorry if it sounds “preachy” but it’s awesome insights on how to build great product and I’ve been looking for excuses to tell people to watch it .
Improvements
Fixed Bugs
