Assume it's a distributed company, Some idle item would transfer from a site to another. So, In my design there're two key points:
1. Transfering packed in a container. It's a pick-pack-push procedure to simulate the fact. Single or multiple items pick by user, pack with a label(time, departure, destination and unique) then push it out to the server;
2. Ticket the content. While the container received by server, A ticket generated with items info just like a airplane ticket;
Whatever single or multiple items is in the same way. That means i should write a page for this function, And it avoid two flaw:
1. All items in one ticket. All item's serial number would be convert into a string as ticket's content. At present, When user modify an asset's location will automatic generate a ticket;
2. All items in one action. User would scan barcode of items that is ready to transfer in one time. After that, Select the destination and press send, all done. At present, user have to modify every items what is ready to send;
This transfer page will substitute the transfer log. When entry the transfer page, it's draw like a container and waitting for the items. Certainly, there's a entry to access the transfer log.
In conclusion, I'll start a new app named "transfer" to realize above. It's individual app but the data table are belong to assets tool database.
网友评论