I'm building a SaaS product and having doubts on how to organise the navigation and interaction in a user records flow.
The flow consists of a stock transaction record and the document objects are supposed to be stored forever.
In my application menu, I have three elements:
- Remove From Stock
- Add To Stock
- Show Stock Transactions
Remove From Stock and
Add To Stock will open an input page where the user will select the stock item
quantity and a new record is added to database.
type (added/removed) fields are added automatically. The latest added field is shown in screen after commit.
Show Stock Transactions option will show all of my transactions over time. I've opted to use a date filter instead of pagination, as the following example:
The user can select a specific date range (Today, Yesteday, etc.) or choose to type specific dates on the FROM and TO inputs.
In practice, this approach is getting "complaints" from the following points:
a) When adding new transactions, I should be switching screens on the menu. b) Every time I add a new transaction, I have to switch to "Show Stock Transactions" to see the added record. The added record is not easily visible on screen. c) There is no clone buttons. I need to be able to clone a previous transaction, no matter how old it is.
I kindly ask for suggestions on how to improve the usability of the flow and the navigation.