The first impression of Tryton is a blank slate. This is bad as discussed in Blank state improvements. The user on login should see the important information according to his role (groups). This information should also be an entry point to navigation.
E.g.: a salesmen should see how much draft or quoted sales are pending and open them directly to act.
dashboard module was a way to have this feature but it did not work because it is an optional module and so modules does not fill it with data (actions).
We deprecate the
dashboard module and include it in
We add on the user a
dashboard field (similar to the
menu) but restricted to board view. This screen is displayed only when there is no tab opened (so on login). The view is refreshed each time it is display again (when last tab is closed).
We define in
res module a default board view that each module will fill with its data.
The clients must call a dedicated method to retrieve the boad view. This method will be in charge to remove any action that the user may not have access to (and optionally add cache).
The layout of the board is divided in two parts.
The first part is composed of a group of relate buttons.
The second part is composed of graph and list. They are limited to a fixed height.
- Party: link to parties
- Product: links to products and variants
- links to invoices, lines to pay, payments, statements, non-reconciled lines, dunnings
- list: journal cash
- links to shipments, inventories
- links to purchases, requests, requisitions, amendments
- links to sales, opportunities, complaints, amendments
- graph: opportunities per months
- graph: employee timesheet per day for current week
- links to productions, works