
Vernon_Fowler

7 - App Architect
Comment Post Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
โMay 18, 2019
11:48 PM
Using the Org chart block to represent site architecture is awesome!
The Matrix block allows drag-and-drop to reorganise records. If the same drag and drop functionality existed in Org chart blocks, it would be easy to reorganise heirarchically related records, such as site architecture, and user flows.
Right now, either switching back to a table view or expanding a record from the org chart loses context. Using drag and drop would maintain context when assigning a new parent (or child) This would make it easy to restructure hierarchically related records.
See more ideas labeled with: