Ced Thank you for your time replying. I think the post on your other thread is on to something good.
Ceds Post
After more thoughts, I think this kind of “shipment for service” should have a quiet similar design as the timesheet works. It should be a very simple model with a minimal workflow but with an optional reference field which allow it to be “plugged” to another document workflow. So if for example, we want to invoice the service once a shipment has been done, the service line is linked to the shipment and once the shipment is shipped the “shipment for service” is triggered to be marked as done.
I think this is a very generic design which allows to support plenty of different cases with simple customization.
The default could just manage unlinked case with a simple button to mark the service as done (and the quantity done).
Ced
And we should split the invoice method on sale between service and goods.
Me: Is this done by the Tryton Devs or something I need get done or figure out?
ME: So how to implement “shipment for service” properly to be clear we do not actually ship any equipment it is all bought and purchased by the end client then we install it.
I understand your thought process on this for lack of a better term shipment for service will work as it would some how plug in the tracking and future records search for warranty or install data information that we need of the workflow process.
I do not know if this is possible in some way in the Project Module as I have not had time to look at it in depth. By making each install or group of installs in a project for the client requesting the work.
Thanks TelematicMan