Jira Planned Maintenance

2019-03-09 Thread Sharan Foga
Hi All

I’ve seen a bit of Jira activity happening today so a quick note to let you 
know that there is some Jira maintenance planned for tomorrow (Sunday) around 
11am UTC so don’t be surprised if Jira is down for a few hours.

Thanks
Sharan


Re: Create return till ...

2019-03-09 Thread Pierre Smits
I meant the solution suggested by Arun regarding ProductFacility.

Best regards,

Pierre Smits

*Apache Trafodion , Vice President*
*Apache Directory , PMC Member*
Apache Incubator , committer
*Apache OFBiz , contributor (without privileges)
since 2008*
Apache Steve , committer


On Sat, Mar 9, 2019 at 2:50 PM Pierre Smits  wrote:

> I don't think that the solution provided by ProductFacility will offer a
> good solution. I will - again - require a field to be added to the entity.
> And user would need to propagate the value to field for each
> product-facility combo. Consider Multiple store, multiple warehouse a
> big burden on the adopter's employees. And it does not give store defaults.
>
> We also have to keep in mind that this requirement is at a higher level,
> namely at agreement/order level. There the details must be captured,
> because - when agreed upon - they provide the particulars at a binding
> contract, that will propagate into lower level (namely receipt of the goods
> returned). And yes, the settings at store/product level (should) feed into
> orders, but agreement (when established with long-term contract partners)
> details may/must override those store/product settings.
>
> As always, ad-hoc business decisions may override long-standing
> (technical) terms in store, product and agreement. Giving a customer a few
> more days than the default, may lead to having the company retain the
> customer than sticking to dogmas. And even then product warranty laws may
> prevail.
>
> Best regards,
>
> Pierre Smits
>
> *Apache Trafodion , Vice President*
> *Apache Directory , PMC Member*
> Apache Incubator , committer
> *Apache OFBiz , contributor (without privileges)
> since 2008*
> Apache Steve , committer
>
>
> On Sat, Mar 9, 2019 at 1:15 PM Arun Patidar <
> arun.pati...@hotwaxsystems.com> wrote:
>
>> We can use ProductFacility entity for storing number of days and can copy
>> to it to OrderItem during order creation.
>>
>>
>> Kind Regards,
>> *Arun Patidar* | Manager, Enterprise Development
>> HotWax Systems 
>> Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center,
>> Indore, M.P. 452010
>> Linkedin: *Arun Patidar* 
>>
>>
>>
>> On Sat, Mar 9, 2019 at 4:37 PM Rishi Solanki 
>> wrote:
>>
>> > +1 for having this. The only thing I would like to add go for global
>> > setting which should be overridden by product level setting. For
>> example; A
>> > site may deal in industry  which may require different number of days
>> for
>> > the different products.
>> > Also agree with Pierre on point we should be aware of the fact that
>> > unnecessary data model extension should be avoided.
>> >
>> > Question: how should we manage if we would like to have two store and
>> for
>> > both stores we want to have different number of days limit for return.
>> > My Answer: While configuring the store the System property should be
>> > configured against prefix/suffix of store id.
>> >
>> > Please feel free to add more details or alternative way for handling
>> this.
>> >
>> > Best Regards,
>> > --
>> > Rishi Solanki
>> > Sr Manager, Enterprise Software Development
>> > HotWax Systems Pvt. Ltd.
>> > Direct: +91-9893287847
>> > http://www.hotwaxsystems.com
>> > www.hotwax.co
>> >
>> >
>> > On Sat, Mar 9, 2019 at 1:20 PM Suraj Khurana 
>> > wrote:
>> >
>> > > Hello,
>> > >
>> > > In OFBiz, we can create a return for order without checking when that
>> > order
>> > > is placed, it might be years long.
>> > > IMO, we should have a field something like daysToReturn at product
>> store
>> > > level to allow creating return till after that much days of order
>> > > completion.
>> > >
>> > > I could not find anything else relevant to this and this is a very
>> common
>> > > e-commerce scenario for any business.
>> > >
>> > > Am I missing something?
>> > > Please share your thoughts on the same.
>> > >
>> > > --
>> > > Best Regards
>> > > Suraj Khurana
>> > > TECHNICAL CONSULTANT
>> > > mobile: +91 9669750002
>> > > email: suraj.khur...@hotwax.co
>> > > www.hotwax.co
>> > >
>> >
>>
>


Re: Create return till ...

2019-03-09 Thread Pierre Smits
I don't think that the solution provided by ProductFacility will offer a
good solution. I will - again - require a field to be added to the entity.
And user would need to propagate the value to field for each
product-facility combo. Consider Multiple store, multiple warehouse a
big burden on the adopter's employees. And it does not give store defaults.

We also have to keep in mind that this requirement is at a higher level,
namely at agreement/order level. There the details must be captured,
because - when agreed upon - they provide the particulars at a binding
contract, that will propagate into lower level (namely receipt of the goods
returned). And yes, the settings at store/product level (should) feed into
orders, but agreement (when established with long-term contract partners)
details may/must override those store/product settings.

As always, ad-hoc business decisions may override long-standing (technical)
terms in store, product and agreement. Giving a customer a few more days
than the default, may lead to having the company retain the customer than
sticking to dogmas. And even then product warranty laws may prevail.

Best regards,

Pierre Smits

*Apache Trafodion , Vice President*
*Apache Directory , PMC Member*
Apache Incubator , committer
*Apache OFBiz , contributor (without privileges)
since 2008*
Apache Steve , committer


On Sat, Mar 9, 2019 at 1:15 PM Arun Patidar 
wrote:

> We can use ProductFacility entity for storing number of days and can copy
> to it to OrderItem during order creation.
>
>
> Kind Regards,
> *Arun Patidar* | Manager, Enterprise Development
> HotWax Systems 
> Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center,
> Indore, M.P. 452010
> Linkedin: *Arun Patidar* 
>
>
>
> On Sat, Mar 9, 2019 at 4:37 PM Rishi Solanki 
> wrote:
>
> > +1 for having this. The only thing I would like to add go for global
> > setting which should be overridden by product level setting. For
> example; A
> > site may deal in industry  which may require different number of days for
> > the different products.
> > Also agree with Pierre on point we should be aware of the fact that
> > unnecessary data model extension should be avoided.
> >
> > Question: how should we manage if we would like to have two store and for
> > both stores we want to have different number of days limit for return.
> > My Answer: While configuring the store the System property should be
> > configured against prefix/suffix of store id.
> >
> > Please feel free to add more details or alternative way for handling
> this.
> >
> > Best Regards,
> > --
> > Rishi Solanki
> > Sr Manager, Enterprise Software Development
> > HotWax Systems Pvt. Ltd.
> > Direct: +91-9893287847
> > http://www.hotwaxsystems.com
> > www.hotwax.co
> >
> >
> > On Sat, Mar 9, 2019 at 1:20 PM Suraj Khurana 
> > wrote:
> >
> > > Hello,
> > >
> > > In OFBiz, we can create a return for order without checking when that
> > order
> > > is placed, it might be years long.
> > > IMO, we should have a field something like daysToReturn at product
> store
> > > level to allow creating return till after that much days of order
> > > completion.
> > >
> > > I could not find anything else relevant to this and this is a very
> common
> > > e-commerce scenario for any business.
> > >
> > > Am I missing something?
> > > Please share your thoughts on the same.
> > >
> > > --
> > > Best Regards
> > > Suraj Khurana
> > > TECHNICAL CONSULTANT
> > > mobile: +91 9669750002
> > > email: suraj.khur...@hotwax.co
> > > www.hotwax.co
> > >
> >
>


Re: Create return till ...

2019-03-09 Thread Pierre Smits
Following up on Rishi's posting.
I believe we are good entity-wise (meaning: we may be able to avoid using
system property setting, with complex prefix/suffix constructs).

Product can have Attribute settings. So can ProductCategory, see [1].

We can associate products with different ProductCategory values, and have
these different ProductCategory be associated with different ProductStore
values through the ProductCatalog (via ProductStoreCatalog), do ensure the
defaults/overrides. It may be a complex way to calculate, but the solution
will be scalable.

Otherwise, we can add the ProductStoreAttribute entity to simplify matters
to facilitate this, and other - future - field addition requirements on
ProductStore level.

[1] ProductCategoryAttribute




Best regards,

Pierre Smits

*Apache Trafodion , Vice President*
*Apache Directory , PMC Member*
Apache Incubator , committer
*Apache OFBiz , contributor (without privileges)
since 2008*
Apache Steve , committer


On Sat, Mar 9, 2019 at 12:07 PM Rishi Solanki 
wrote:

> +1 for having this. The only thing I would like to add go for global
> setting which should be overridden by product level setting. For example; A
> site may deal in industry  which may require different number of days for
> the different products.
> Also agree with Pierre on point we should be aware of the fact that
> unnecessary data model extension should be avoided.
>
> Question: how should we manage if we would like to have two store and for
> both stores we want to have different number of days limit for return.
> My Answer: While configuring the store the System property should be
> configured against prefix/suffix of store id.
>
> Please feel free to add more details or alternative way for handling this.
>
> Best Regards,
> --
> Rishi Solanki
> Sr Manager, Enterprise Software Development
> HotWax Systems Pvt. Ltd.
> Direct: +91-9893287847
> http://www.hotwaxsystems.com
> www.hotwax.co
>
>
> On Sat, Mar 9, 2019 at 1:20 PM Suraj Khurana 
> wrote:
>
> > Hello,
> >
> > In OFBiz, we can create a return for order without checking when that
> order
> > is placed, it might be years long.
> > IMO, we should have a field something like daysToReturn at product store
> > level to allow creating return till after that much days of order
> > completion.
> >
> > I could not find anything else relevant to this and this is a very common
> > e-commerce scenario for any business.
> >
> > Am I missing something?
> > Please share your thoughts on the same.
> >
> > --
> > Best Regards
> > Suraj Khurana
> > TECHNICAL CONSULTANT
> > mobile: +91 9669750002
> > email: suraj.khur...@hotwax.co
> > www.hotwax.co
> >
>


Re: Create return till ...

2019-03-09 Thread Vaibhav Jain
Agree with Arun,

Just an addon
If we are using ProductFacility entity then we should think to move the
returnable flag from product to the productFacility entity.

Kind Regards,
*Vaibhav Jain* | Senior Enterprise Software Engineer
HotWax Systems 
Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center, Indore,
M.P 452010
Linkedin: *Vaibhav Jain* 


On Sat, Mar 9, 2019 at 5:45 PM Arun Patidar 
wrote:

> We can use ProductFacility entity for storing number of days and can copy
> to it to OrderItem during order creation.
>
>
> Kind Regards,
> *Arun Patidar* | Manager, Enterprise Development
> HotWax Systems 
> Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center,
> Indore, M.P. 452010
> Linkedin: *Arun Patidar* 
>
>
>
> On Sat, Mar 9, 2019 at 4:37 PM Rishi Solanki 
> wrote:
>
> > +1 for having this. The only thing I would like to add go for global
> > setting which should be overridden by product level setting. For
> example; A
> > site may deal in industry  which may require different number of days for
> > the different products.
> > Also agree with Pierre on point we should be aware of the fact that
> > unnecessary data model extension should be avoided.
> >
> > Question: how should we manage if we would like to have two store and for
> > both stores we want to have different number of days limit for return.
> > My Answer: While configuring the store the System property should be
> > configured against prefix/suffix of store id.
> >
> > Please feel free to add more details or alternative way for handling
> this.
> >
> > Best Regards,
> > --
> > Rishi Solanki
> > Sr Manager, Enterprise Software Development
> > HotWax Systems Pvt. Ltd.
> > Direct: +91-9893287847
> > http://www.hotwaxsystems.com
> > www.hotwax.co
> >
> >
> > On Sat, Mar 9, 2019 at 1:20 PM Suraj Khurana 
> > wrote:
> >
> > > Hello,
> > >
> > > In OFBiz, we can create a return for order without checking when that
> > order
> > > is placed, it might be years long.
> > > IMO, we should have a field something like daysToReturn at product
> store
> > > level to allow creating return till after that much days of order
> > > completion.
> > >
> > > I could not find anything else relevant to this and this is a very
> common
> > > e-commerce scenario for any business.
> > >
> > > Am I missing something?
> > > Please share your thoughts on the same.
> > >
> > > --
> > > Best Regards
> > > Suraj Khurana
> > > TECHNICAL CONSULTANT
> > > mobile: +91 9669750002
> > > email: suraj.khur...@hotwax.co
> > > www.hotwax.co
> > >
> >
>


Re: Create return till ...

2019-03-09 Thread Arun Patidar
We can use ProductFacility entity for storing number of days and can copy
to it to OrderItem during order creation.


Kind Regards,
*Arun Patidar* | Manager, Enterprise Development
HotWax Systems 
Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center,
Indore, M.P. 452010
Linkedin: *Arun Patidar* 



On Sat, Mar 9, 2019 at 4:37 PM Rishi Solanki 
wrote:

> +1 for having this. The only thing I would like to add go for global
> setting which should be overridden by product level setting. For example; A
> site may deal in industry  which may require different number of days for
> the different products.
> Also agree with Pierre on point we should be aware of the fact that
> unnecessary data model extension should be avoided.
>
> Question: how should we manage if we would like to have two store and for
> both stores we want to have different number of days limit for return.
> My Answer: While configuring the store the System property should be
> configured against prefix/suffix of store id.
>
> Please feel free to add more details or alternative way for handling this.
>
> Best Regards,
> --
> Rishi Solanki
> Sr Manager, Enterprise Software Development
> HotWax Systems Pvt. Ltd.
> Direct: +91-9893287847
> http://www.hotwaxsystems.com
> www.hotwax.co
>
>
> On Sat, Mar 9, 2019 at 1:20 PM Suraj Khurana 
> wrote:
>
> > Hello,
> >
> > In OFBiz, we can create a return for order without checking when that
> order
> > is placed, it might be years long.
> > IMO, we should have a field something like daysToReturn at product store
> > level to allow creating return till after that much days of order
> > completion.
> >
> > I could not find anything else relevant to this and this is a very common
> > e-commerce scenario for any business.
> >
> > Am I missing something?
> > Please share your thoughts on the same.
> >
> > --
> > Best Regards
> > Suraj Khurana
> > TECHNICAL CONSULTANT
> > mobile: +91 9669750002
> > email: suraj.khur...@hotwax.co
> > www.hotwax.co
> >
>


Re: Create return till ...

2019-03-09 Thread Rishi Solanki
+1 for having this. The only thing I would like to add go for global
setting which should be overridden by product level setting. For example; A
site may deal in industry  which may require different number of days for
the different products.
Also agree with Pierre on point we should be aware of the fact that
unnecessary data model extension should be avoided.

Question: how should we manage if we would like to have two store and for
both stores we want to have different number of days limit for return.
My Answer: While configuring the store the System property should be
configured against prefix/suffix of store id.

Please feel free to add more details or alternative way for handling this.

Best Regards,
--
Rishi Solanki
Sr Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com
www.hotwax.co


On Sat, Mar 9, 2019 at 1:20 PM Suraj Khurana 
wrote:

> Hello,
>
> In OFBiz, we can create a return for order without checking when that order
> is placed, it might be years long.
> IMO, we should have a field something like daysToReturn at product store
> level to allow creating return till after that much days of order
> completion.
>
> I could not find anything else relevant to this and this is a very common
> e-commerce scenario for any business.
>
> Am I missing something?
> Please share your thoughts on the same.
>
> --
> Best Regards
> Suraj Khurana
> TECHNICAL CONSULTANT
> mobile: +91 9669750002
> email: suraj.khur...@hotwax.co
> www.hotwax.co
>


Re: Create return till ...

2019-03-09 Thread Pierre Smits
I  am inclined to disagree.

 At product level this can be solved by setting one or more attributes. So
no additional field required to cater for this. At store level we could
work with value set in appropriate system properties. Also no entity change
required.

Best regards,

Pierre Smits

*Apache Trafodion , Vice President*
*Apache Directory , PMC Member*
Apache Incubator , committer
*Apache OFBiz , contributor (without privileges)
since 2008*
Apache Steve , committer


On Sat, Mar 9, 2019 at 11:09 AM Vaibhav Jain 
wrote:

> Hello Suraj,
>
> *Bottom Line:*
> We should have a field to manage days to Return at the product and product
> store level both.
>
> *Story:*
> We have a flag on the product level to manage that product is returnable or
> not.
> We can not manage the information on the product store level only because
> each product is returnable for a different and specific time period
> (depends on business).
> We can manage this on the product store level which can be used if
> the product is returnable but days to return is not specified on
> the product level.
>
> Does this make sense to you as well?
>
> Kind Regards,
> *Vaibhav Jain* | Senior Enterprise Software Engineer
> HotWax Systems 
> Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center,
> Indore,
> M.P 452010
> Linkedin: *Vaibhav Jain*  >
>
>
> On Sat, Mar 9, 2019 at 1:20 PM Suraj Khurana 
> wrote:
>
> > Hello,
> >
> > In OFBiz, we can create a return for order without checking when that
> order
> > is placed, it might be years long.
> > IMO, we should have a field something like daysToReturn at product store
> > level to allow creating return till after that much days of order
> > completion.
> >
> > I could not find anything else relevant to this and this is a very common
> > e-commerce scenario for any business.
> >
> > Am I missing something?
> > Please share your thoughts on the same.
> >
> > --
> > Best Regards
> > Suraj Khurana
> > TECHNICAL CONSULTANT
> > mobile: +91 9669750002
> > email: suraj.khur...@hotwax.co
> > www.hotwax.co
> >
>


Re: Create return till ...

2019-03-09 Thread Vaibhav Jain
Hello Suraj,

*Bottom Line:*
We should have a field to manage days to Return at the product and product
store level both.

*Story:*
We have a flag on the product level to manage that product is returnable or
not.
We can not manage the information on the product store level only because
each product is returnable for a different and specific time period
(depends on business).
We can manage this on the product store level which can be used if
the product is returnable but days to return is not specified on
the product level.

Does this make sense to you as well?

Kind Regards,
*Vaibhav Jain* | Senior Enterprise Software Engineer
HotWax Systems 
Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center, Indore,
M.P 452010
Linkedin: *Vaibhav Jain* 


On Sat, Mar 9, 2019 at 1:20 PM Suraj Khurana 
wrote:

> Hello,
>
> In OFBiz, we can create a return for order without checking when that order
> is placed, it might be years long.
> IMO, we should have a field something like daysToReturn at product store
> level to allow creating return till after that much days of order
> completion.
>
> I could not find anything else relevant to this and this is a very common
> e-commerce scenario for any business.
>
> Am I missing something?
> Please share your thoughts on the same.
>
> --
> Best Regards
> Suraj Khurana
> TECHNICAL CONSULTANT
> mobile: +91 9669750002
> email: suraj.khur...@hotwax.co
> www.hotwax.co
>


Re: storeOrder Service

2019-03-09 Thread Rishi Solanki
Thank you all for your inputs. We will be addressing the issue under -
https://issues.apache.org/jira/browse/OFBIZ-10855




Best Regards,
--
Rishi Solanki
Sr Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com
www.hotwax.co


On Tue, Mar 5, 2019 at 9:16 AM Swapnil M Mane 
wrote:

> +1
>
>
> - Best Regards,
> Swapnil M Mane
>
>
> On Fri, Mar 1, 2019 at 3:22 PM Rishi Solanki 
> wrote:
>
> > Dear All,
> > While working with storeOrder service, I observe that few order header
> > level values not passed and stored in that service. Also no code support
> > exists for those order header fields. Below are the fields which is not
> > taken care by the service code, please let me know if we can add
> > conditional support for these field, that means if the value comes in
> > parameter then it will be stored otherwise not.
> > - priority
> > - isRushOrder
> >
> > These values can be reset after creating order by using updateOrderHeader
> > service, but I think this should be fine to have these and other missing
> > values of header level as IN parameters and handled by the service.
> >
> > Please let me know in case of any objections, I would like to commit the
> > proposed changes.
> >
> > Best Regards,
> > --
> > Rishi Solanki
> > Sr Manager, Enterprise Software Development
> > HotWax Systems Pvt. Ltd.
> > Direct: +91-9893287847
> > http://www.hotwaxsystems.com
> > www.hotwax.co
> >
>