Now we have a subscription, isn't using the subscription a better way to go then the shopping list? A much better implementation especially if you think that a subscription is repetitive in nature anyway.
and....one way should not exclude the other way? is there a problem when i would add this? What is the opinion of the community? On Thu, 2008-05-15 at 00:35 -0600, David E Jones wrote: > The current design uses the Subscription entity only for already paid > subscriptions. > > For automatic renewals the current code and such uses the ShoppingList > with the auto-reorder type to automatically reorder the product that > will extend the Subscription. > > -David > > > On May 15, 2008, at 12:30 AM, Hans Bakker wrote: > > > Question to the community: > > > > I have a customer who would like to have subscriptions extended > > automatically unless cancelled before 1 month before the ending of the > > subscription period. > > > > What i was thinking about is adding some fields to the subscription > > entity called 'extent' which could be 'N' indicating the subscription > > should not be extended. It is also required to be able to add a period > > before the subscription can be cancelled. > > > > Then we will need a service which creates automatically an order, > > copying the original order for the next subscription period, at the > > moment the subscription expires. This order will then create a new > > subscription. > > > > So i think we need 3 new fields: > > > > extent: N or Y/blank > > cancelPeriod > > cancelPeriodUomId > > > > Is this the best way to do it? > > > > Regards, > > Hans > > -- > > AntWebsystems.com: Quality OFBiz services for competitive rates..... > > > > -- AntWebsystems.com: Quality OFBiz services for competitive rates.....
