We have the width issues fixed in desk 2.0 and i also think tabs should be used in workflows in forms and workflows between doctypes. Stichlabs which starts at $500 per month and i use it for one of my other companies, works REALLY well and I plan to try to implement a similar strategy after the first release of Desk 2.0 project we are working on but it is currently paused for a month because of a implementation rollout.
I love stitchlabs a lot and they have solved lots of problems. Specifically from clicking on an order. What should someone have the ability to do/need to do next?
- Well they should be able to progress through the related steps of the order workflow at the touch of a button. (see top tabs, think linked doctypes + status = workflow)
- They should be able to go to a different module (see left side)
- They should be able to see / move to other orders without going go back to the full list view. (see mini list view on the right with status icons)
While I do not always utilize the mini list view like I should, the tabs UI that I am showing make his system 10x more usable than ERPnext as of today.
With respect to the entire ERPnext team who have done an amazing job to date. I want to dedicate my resources and expertise to help fix all the UX issues and pull in things that to a developer may seem trivial, but to a user and designer are worth more than in productivity and usability than 90% of the features offered.
Here is the list view before clicking on an order. Do we need tabs as a first step? no, we have way bigger issues to address. But I would say that it will play a huge part in how we solve usability problems of workflows requiring multiple doctypes and linked statuses. I know orders is one…
As i think through each module, there seems to be a universal correlation of workflow = multiple doctypes in a series (some single and some multiple) + overall workflow status linked across these doctypes. Building a flow and linking doctypes and tabs in an order with individual statuses and total workflow status would seem to be as big of an improvement as building a single doctype was.
Its a great thought to have and I really think there is something valuable here to consider. I plan to work on this in the near future…