irc.libera.chat #tryton log beginning Thu Dec 14 12:10:01 AM CET 2023 | ||
-!- cedk(~ced@gentoo/developer/cedk) has joined #tryton | 23:25 | |
-!- ChanServ changed mode/#tryton -> +o cedk | 23:25 | |
-!- springwurm(~springwur@2a01:76c0:100:f500:7898:c6:6946:f4bf) has joined #tryton | 06:28 | |
-!- mrichez(~Maxime@mail.saluc.com) has joined #tryton | 07:22 | |
-!- cedk(~ced@gentoo/developer/cedk) has joined #tryton | 08:21 | |
-!- ChanServ changed mode/#tryton -> +o cedk | 08:21 | |
-!- springwurm(~springwur@5.104.149.54) has joined #tryton | 08:28 | |
mrichez | hi, is there an easy way to identify a backorder shipment ? I'm thinking about a boolean function field browsing all sales linked to a shipment having more than one shipment... What do you think ? | 09:37 |
---|---|---|
pokoli | mrichez: you can test the number of the stock moves of the sales lines linked to the outgoing moves of the origin. If there is one is done state it is a backorder | 10:22 |
pokoli | Do you need to do some special treatment for them? Normally backorders are just considered as an extra shipment with nothing special | 10:22 |
mrichez | pokoli: i want to create a trigger to warn the user who processed the sale there's a backorder | 10:23 |
pokoli | mrichez: you can use the "partially shipped" shipment state of the sale | 10:24 |
pokoli | when the sale changes from waiting to partialy shipped send the warning | 10:24 |
mrichez | pokoli: hum that's an idea, but would like the warning each time a backorder shipment is created | 10:25 |
mrichez | because sale user needs to take a decision if backorder should be shipped or not | 10:26 |
pokoli | mrichez: why not using the sale shipment exception to raise the warning to the sale user? This will allow him to take the action | 10:26 |
pokoli | and each time it is raised again a new exception will be generated | 10:27 |
mrichez | pokoli: sale shipment exception is raised when cancelling the shipment, no ? | 10:27 |
mrichez | pokoli: in case of backorder there's no exception | 10:27 |
pokoli | mrichez: yes, I'm thinking in automatically cancelling backorder shipments when they are created by the system. Which will raise the exception | 10:28 |
mrichez | pokoli: hum, good suggestion :-)... wondering if there's no problem to cancelling automatically backorders ? | 10:30 |
pokoli | mrichez: I think is doable. You just need to override process to cancell shipments when it already exists a new one | 10:34 |
pokoli | and add a flag (to be set on handle exception) which avoids this cancellation. Once a new shipment is created the flag is disabled so new shipments are already created | 10:34 |
pokoli | The flag is needed because the process is run in a background process when tryton-worker is activated | 10:35 |
mrichez | pokoli: ok will look at this... and it's possible to create a trigger on shipment exception ? | 10:35 |
pokoli | mrichez: yes, exception is a value of shipment_state of the field. So you just need to create a trigger which is raised when sshipment state is changed to exception | 10:36 |
mrichez | pokoli: super. Thanks :-) | 10:36 |
-!- springwurm(~springwur@2a01:76c0:100:f500:3d09:97ee:7c09:ca73) has joined #tryton | 12:54 | |
mrichez | hi, how to manage shipments when choosing "Manual" as shipment method on sale ? | 13:07 |
mrichez | how to create a shipment and link to the sale ? user doesn't have access to origin field, no ? | 13:07 |
cedk | mrichez: by clicking on manual_shipment | 13:16 |
mrichez | cedk: not on 6.8 ;-) | 13:17 |
cedk | mrichez: before it manual means not managed | 13:17 |
mrichez | cedk: thanks | 13:18 |
-!- acaubet(~Thunderbi@194.224.31.235) has joined #tryton | 13:25 | |
-!- acaubet1(~Thunderbi@194.224.31.235) has joined #tryton | 15:43 | |
-!- srgdts_(~srgdts@user/srgdts) has joined #tryton | 19:43 | |
-!- cedk(~ced@gentoo/developer/cedk) has joined #tryton | 22:15 | |
-!- ChanServ changed mode/#tryton -> +o cedk | 22:15 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!