+1 Nicolas for maintaining history(if we are going to maintain it) in separate entity rather than adding fromDate, thruDate to GoodIdentification table. The purpose of this entity is to store the identification codes for the product. I don't find any use case where product identifications codes are frequently changed and need to maintain the history of it.
Kind Regards, -- Pritam Kute On Sat, Apr 27, 2019 at 1:17 PM Nicolas Malin <nicolas.ma...@nereide.fr> wrote: > I'm mixed about that idea. > > GoodIdentification like PartyIdentification are useful to search on > multiple identification shared by other system. Add life-stamp will add > complexity the resolve quickly a element. Like a name 99% case it's more > important to have the current identification list. Maybe a history > entity (as GoodIdentificationHistory) would be more simple to implement > and sufficient to your problematic ? > > Nicolas > > On 27/04/2019 09:22, Arun Patidar wrote: > > +1, looks good to me. > > > > This will require changes in existing CRUD operations related to > > GoodIdentifications. Also may need migration service or SQL scripts. > > > > > > -- > > Best Regards, > > Arun Patidar > > www.hotwax.co > > > > > > > > On Sat, Apr 27, 2019 at 12:42 PM Aishwary Shrivastava < > > aishwary.shrivast...@hotwaxsystems.com> wrote: > > > >> Hello, Devs > >> > >> We should add support of fromDate and thruDate in the GoodIdentification > >> entity for tracking and history purpose. > >> > >> As of now, if we need to update any Good Identification record for a > >> product, then we have to replace its value and this history isn't > >> maintained. > >> It will also enable the user to maintain multiple goodIdentifications > of a > >> product. > >> > >> Best, > >> *Aishwary Shrivastava* | HotWax Systems <http://www.hotwaxsystems.com/> > >> >
