Hi Ruth,
I'm trying to work out the cleanest way of implementing my
requirements with minimal changes to the existing code base. My
current thought is that I will create an ECA that will recognize when
TOKEN products have been purchased and then update a PARTY_TOKEN
table. The PARTY_TOKEN table
Hi Chris:
Your solution sounds very plausible. Are the tokens unique across all
products? Like a license key? If so, you might want to think about using
serialized inventory to hold them. And then the inventory logic can keep
track of when one is sold and which product it is associated with.
I would like to be able to sell tokens for services using ofbiz.
A customer will buy a token (e.g. for £30). The token will allow
unlimited access to a single resource (e.g. downloading a particular
document/book) as many times as the customer requires. Therefore, the
token is tied to a
Sounds like what the Subscription and related entities are desired for...
-David
On Sep 14, 2010, at 12:25 AM, chris snow wrote:
I would like to be able to sell tokens for services using ofbiz.
A customer will buy a token (e.g. for £30). The token will allow
unlimited access to a
Hi Chris:
That is what I do on the MyOFBiz.com site. Here is an excerpt from my
seed data:
DataResource dataResourceId=PUB-RSS0710
dataResourceTypeId=OFBIZ_FILE_BIN
dataResourceName=OFBizRSS5StepGuide.pdf
mimeTypeId=application/pdf
Thanks Ruth and David,
I've had some more clarification. The service being sold will be
similar to the concept of online Will production. Here are some
example scenarios:
Customers will enter their personal details to go into the Will. When
they want a pdf of the Will they will have to pay
Hi Chris:
That doesn't sound like anything I've seen out of the box. Maybe David
has some more insight.
I can think of a few ways you might want to implement this, but if
something already exists, I'd be interested in hearing about it.
Regards,
Ruth
On 9/14/10 2:51 PM, chris snow wrote:
