It's not easy, but we'll look into it. I'm changing the status to "under review"
It's not easy, but we'll look into it. I'm changing the status to "under review"
Since there's an update and solution, I'm closing the thread.
Right now we're not planning any major modifications into the permission system. We might re-visit this thread should more similar requests appear.
Dear Community,
The new Fluent 2 interface is undoubtedly a significant step forward in design and usability. However, I believe there’s room for further refinement to enhance user experience. One suggestion would be introducing a customizable density setting, similar to the “Roomy,” “Cozy,” and “Compact” options available in Outlook.
Such a feature could prove especially beneficial on devices with smaller screens, like laptops. For instance, in scenarios where a form is open with the details panel visible, reducing the spacing between workflow steps could help optimize the available screen space.
Allowing users to set their preferred density could influence multiple elements of the interface, such as:
• Spacing between form fields.
• The layout of the left and top menus.
• The arrangement within the details panel (info panel).
Additionally, this setting might also adjust font sizes in specific areas, like field group headers, the attachments section, and comments titles, ensuring a cohesive and user-friendly experience across different density preferences.
Your feedback and thoughts on this suggestion are more than welcome!
Best.
We'll do it :). Straight to backlog!
We'll address your scenario alongside other form-related project in the future. I'm labeling the thread as "not now", but stay tuned to updates about forms :)
We're working on introduction of "task forms" that should address your scenario. So as such, I'll label your thread as "not now", but keep in mind the solution should come from a slightly different angle :)
Sounds good -> backlog :).
This option will be enabled alongside with introducation of grid-based placement within dashboards.
We'll take it into the account along with other form-related development project. I'm putting it into the backlog.