Re: [Proposal] Extend facility entity

Hello all, Here is the link to ticket OFBIZ-10040 raised on JIRA. Thanks & Regards, Vaibhav Jain Hotwax Systems, vaibhav.j...@hotwaxsystems.com On Fri, Dec 1, 2017 at 10:42 AM, Vaibhav Jain < vaibhav.j...@hotwaxsystems.com> wrote: > Hello

Re: [Proposal] Extend facility entity

Hello all, Sorry for late reply as I was out of town. Thank you very much to all of you for sharing this valuable information. As we can conclude this conversation here. I will create a new entity facilityCalendar which will create the one-to-many relationship between facility and calendar.

Re: [Proposal] Extend facility entity

Hi Deepak, Seems to me that FacilityCalendar would be easier My 2cts Jacques Le 27/11/2017 à 07:00, Deepak Dixit a écrit : I think we can use TemporalExpression to manage this data. Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com www.hotwax.co On Mon, Nov 27, 2017 at 9:46 AM, Arun

Re: [Proposal] Extend facility entity

I think we can use TemporalExpression to manage this data. Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com www.hotwax.co On Mon, Nov 27, 2017 at 9:46 AM, Arun Patidar < arun.pati...@hotwaxsystems.com> wrote: > +1 for FacilityCalendar entity with purpose. > > -- > Thanks & Regards > --- >

Re: [Proposal] Extend facility entity

+1 for FacilityCalendar entity with purpose. -- Thanks & Regards --- Arun Patidar Manager, Enterprise Software Development HotWax Systems Pvt Ltd. www.hotwaxsystems.com On Sun, Nov 26, 2017 at 3:31 AM, pierre wrote: > Hi Pierre, > > The "primary" pattern is often

Re: [Proposal] Extend facility entity

Hi Pierre, The "primary" pattern is often used such in productCategory or productStore entity. It can simplify acces for simple use. Thanks Pierre G On 25/11/2017 22:26, Pierre Smits wrote: Why would a new field called primaryCalendarId be required when this could be resolved through you

Re: [Proposal] Extend facility entity

Why would a new field called primaryCalendarId be required when this could be resolved through you proposed FacilityCalendar entity? If there is only one it is the primary. And if multiple are required then one can have facilityCalendarPurposeId =

Re: [Proposal] Extend facility entity

Can we set a primaryCalendarId field on Facility entity and add a join entity FacilityCalendar with fields facilityId, caldendarId, facilityCalendarPurposeId, description for complex use ? Pierre On 25/11/2017 19:18, Pierre Smits wrote: Hi Jacques, All, Consider following scenarios:

Re: [Proposal] Extend facility entity

Hi Jacques, All, Consider following scenarios: 1. A business with a facility in a city center, where city government has placed restrictions on the access of the city center for trucks, and other set of restrictions of opening hours for customers: 1. a calendar for suppliers and

Re: [Proposal] Extend facility entity

Hi Pierre, Actually I was answering to Pierre Gaudin :) More than one calendar for a facility? Do you have an example? Jacques Le 25/11/2017 à 15:53, Pierre Smits a écrit : Hey Jacques, You're welcome. {quote} Anyway, so Vaibhav, I think we can now put directly in Facility {quote} Are

Re: [Proposal] Extend facility entity

Hey Jacques, You're welcome. {quote} Anyway, so Vaibhav, I think we can now put directly in Facility {quote} Are you sure? Is there no scenario possible where a facility would need to apply more than 1 calendar? Best regards, Pierre Smits ORRTIZ.COM OFBiz based

Re: [Proposal] Extend facility entity

Thanks for the info Pierre, Exactly the right answer! I thought there was something in workeffort data model, I know less manufacturing :) BTW, I wonder why TechDataCalendar is in manufacturing rather than in workeffort where IMO it would better fit since it's more general there. Anyway, so

Re: [Proposal] Extend facility entity

Hi, Recently we had to store opening and closing hours for stores. To do so we have linked techDataCalendar with facility             Thanks Pierre On 25/11/2017 11:53, Michael Brohl wrote: +1 for a timetable entity and linking it to facility This will give us much more flexibility

Re: [Proposal] Extend facility entity

Hi All, The facility entity should not have the openedDate and closedDate fields, as these: 1. can't be enough for all the moments a facility can be open or closed; 2. not in line with startDate and thruDate fields (datetime type) used throughout numerous other entities to determine the

Re: [Proposal] Extend facility entity

+1 for a timetable entity and linking it to facility This will give us much more flexibility and avoids adding more and more fields to the facility table. Thanks, Michael Am 25.11.17 um 11:39 schrieb Jacques Le Roux: Hi Vaibhav, That sounds reasonable to me. I notably like this feature

Re: [Proposal] Extend facility entity

Hi Vaibhav, That sounds reasonable to me. I notably like this feature when Googling for a *physical* store to go buying things. Then you should maybe consider having a new Timetable Entity and link it from Facility. I had a look at what already exists in the Data Model, notably Timesheet and

[Proposal] Extend facility entity

Hello all, *Facility* entity has attributes for *openedDate* and *closedDate* which specify that facility opening date and closing date if the facility is closed i.e. not in-use. All facilities are not open on all weekdays. We can have an attribute to record this. A retail store is also a