El 07/01/14 12:59, Cédric Krier ha escrit:
On 07 Jan 12:40, Sergi Almacellas Abellana wrote:
>El dimecres 14 de novembre de 2012 16:24:46 UTC+1, Cédric Krier va
>escriure:
>
>    On 14/11/12 13:21 +0100, Jan Grasnick | grasbauer ug wrote:
>     > Hi all,
>     >
>     > I just wrote a little extension to set the 'effective date' of a
>     > shipment in by hand and then set this date to the stock.moves as
>    well.
>     > The background: User sometimes needs to generate shipments by
>    hand and
>     > for a date in the past.
>     >
>     > Shouldn't this be possible in the generic module?
>
>    If you talk about being able to give an effective date when you
>    validate
>    a shipment, then yes it should be in the base module.
>
>
>I just opened issue3579 for tracking this. I will work on this feature.
>
>Before implementing it, I will prefer to have some feedback on the
>implementation, as IMHO this field can not be modified if you're a
>plain stock user (member of stock group).
Why I don't see any problem here.
You're right. That will be customization.

>The main concern is if a
>new group is needed or we can Reuse the Stock Administration group.
>What do you think?
>
>To let it simple, I won't add the effective date on shipments,
It is already there so both should be adapted.

>and
>manage it directly from moves. Of course, efective_date should be
>readonly on canceled, assigned and done moves.
It should behave the same way as the purchase date on purchase.
On purchase lines the date is managed via on change, and in shipments planned date is managed on write (all moves are updated). So why not using the same logic as planned date?

--
Sergi Almacellas Abellana
www.koolpi.com
Twitter: @pokoli_srk

Reply via email to