Skip to main content

Idea pipeline (top 25)

1859 Ideas

Extend custom_display_format functionality to get Excel like field display/edit possibilitiesOn the backlog

The SF and data domains offer little possibilities to control the presentation of numbers. I thought the custom_display_format extenders would be the solution but I found some shortcomings that make them less useable in practice. I discussed this with Thinkwise people: The current behaviour is as intended but they think the following would be a good improvement.Simple example for a currency datatype NUMERIC(18,3) where users normally want to see only 2 decimals but the extra decimal is needed for calculation accuracy. By using an extender with "€ 0.00" format for the domain you get the following behaviourPositive:Display with 2 decimals is correct and third decimal is used for rounding up/down correctly An entered number with 3 decimals is correctly stored in the underlying tableNegative:When EDITING data there is no way to see the third stored decimal When EDITING it is not possible to edit the existing number; you have to clear the field and reenter the complete numberThe behaviour is the same in grid and form screens. We would expect behaviour like e.g. Excel:Display data using the Extender. They are called custom_display_format for a reason I think. Possibility to edit the exact stored dataWithout this behaviour the introduction of the extender seems of little use; the same could be achieved using an expressions field. But a task would be required to edit data and this is what we want to prevent.An extra improvement would be if the scope of the extender could be specified on a lower level than a domain. Then you would get the possibility to present and edit the same table field in multiple ways; the exact data for the finance department and in another screen rounded numbers for sales but still the possibility to edit the exact number.

SanderAdam
Captain
SanderAdamCaptain

Single click tasks for card lists on mobile devicesNew

Hello all,We have a scenario where we want the user to navigate to a details tab, the user in this case is on a mobile device. While on a tablet, there are some options to make a detail tab appear on the side of the screen, this option is not doable for mobile phones. And some of our users are going to use mobile phones instead of tablets.We used a task link before, so the user can click on a task on a record, but this is not ideal. This is not the web and mobile way. As Nielsen and Norman's 10 usability heuristics put it: recognition rather than recall. On mobile and web applications (looking at apps like Outlook and Gmail) it is common to have a single click on a record. Just on the record, not on a task button integrated in the record.A user will recognise a single click on a card record to navigate to the details, rather than having to actively push an integrated button, link or a double click. This is all very Windows oriented and not quite how web and mobile apps are built. We find it to be inconsistent with web standards. So that is why I would like to request a single click option: as single click on a card record, like in Outlook or Gmail to get to a detail view of a said record via a task and (if necessary) process flow.Though I've seen merged ideas to the following idea: https://community.thinkwisesoftware.com/ideas/ability%2Dto%2Dshow%2Dtable%2Dtasks%2Don%2Dgrid%2Dline%2D518 This is not what we are looking for. This is still a new feature which is very Windows oriented. We don't want extra buttons in our records, we want the user to just click a record once and navigate to the desired details.This happens to fall nicely under the fourth Nielsen and Norman usability heuristic as well as the sixth:Consistency and StandardsUsers should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform and industry conventions.Jakob's Law states that people spend most of their time using digital products other than yours. Users’ experiences with those other products set their expectations. Failing to maintain consistency may increase the users' cognitive load by forcing them to learn something new.Recognition Rather than RecallMinimize the user's memory load by making elements, actions, and options visible. The user should not have to remember information from one part of the interface to another. Information required to use the design (e.g. field labels or menu items) should be visible or easily retrievable when needed.Humans have limited short-term memories. Interfaces that promote recognition reduce the amount of cognitive effort required from users.At this point in time, we have quite a history of user actions on the internet, and the single click on a card record (like in Outlook or Gmail) is one of them. This would, instead of a new double click action, greatly increase usability of our software, especially for those that are not too well versed in computers and mobile devices.

Sidebar navigation menu: Reposition hamburger switcher + Make full collapsable state possibleNew

Goals of this feature request:The sidebar navigation menu hamburger icon and screen name can be positioned more logically and consistently across all screen sizes (mobile / desktop). On expanding the menu from a collapsed state, the user currently no longer sees the screen name. Make this visible.  Introduce a fully collapsed menu state for maximum use of horizontal screen real estate.  The current sidebar states are as following:  We suggest to make the hamburger switcher stick to the left of the topbar. And then let the navigation sidebar work from below the topbar (it currently overlays it). Also introduce the possibility for a three-state navigation sidebar (instead of two-state) by clicking the hamburger icon (sequence 1 > 2 > 3 > back to 1): Fully expanded state  Partially collapsed state Fully collapsed state (maximum horizontal screen real estate In a sidebar collapsed state, the menu should expand when the user hovers over the hamburger icon (this is something currently missing as well). This behavior is required to expand the sidebar from a fully collapsed state, while still be able to collapse it again when the user leaves the hover-over.  This feature request also coincides with another feature that is already underway, and that is being able to use ALT + M shortcut to automatically set focus to the search field of the navigation sidebar.  For power users (which most users are using Thinkwise systems) the fully collapsed sidebar state in combination with ALT + M to quickly find the menu-item they know (and return to new screen with collapsed menu), provides them with maximum screen real estate to work on at all time while still attaining a fast navigation flow. The end result is also a consistent hamburger menu positioning and sidebar menu behavior across all device types.