I just finished watching the Products Updates Webinar (thanks Polina!). Seeing as whiteboard is in focus at the moment, I think this is relevant.
Whiteboard as a view is really confusing to me… As it currently stands, a whiteboard is unstructured data, just like a document. Just like a rich text field, adding a “canvas” field into an entity could give it whiteboard powers. It has references (which are not, but should be shown in the target’s reference), inline comments, adhoc text, image embed. It would fit so much more nicely into the Fibery building blocks. I really do not see how a whiteboard is a view… Imagine adding an ability to Multi-entity-insert into Documents and calling it a view… Is it more of a technical limitation?
Missing features to make it work and bring it to the same level as RTF:
This is opposed to what others (myself included) have suggested before: to make a whiteboard act more like a view, but I think it is 2 different things. 1. Whiteboard (current, unstructured data) 2. Network view (just a view of entities which was originally part of Fibery V1 vision, not sure what happened to it.). I think you guys have been trying to get both in one, when they are totally different things in reality. Whiteboard has so much potential, and it’s a shame to not have the ability to use it effectively in the workspace (as it currently stands).