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. But,
since you don't have to worry about returns, you might not need these
inventory features. And if the tokens are just to identify people and
not product relationship(s) - like a license key - then you probably
don't need inventory at all. So, IMHO I think what you've come up with
makes a lot of sense.
Yes: There is a Catalog Manager setting to turn on/off support for
returns. Sets a field in the Product entity "returnable".
Good luck. Please let us know how things work out!
Regards,
Ruth
On 9/16/10 2:29 AM, chris snow wrote:
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 will then be maintained by an external
application.
Refunds/Returns will not be applicable for tokens so I will need to
switch this functionality off. Is this configurable at the PRODUCT
level?
Many thanks,
Chris
On Tue, Sep 14, 2010 at 8:39 PM, Ruth Hoffman<[email protected]> wrote:
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:
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 (e.g. $50 for 1
token). After they have bought their token, they can change their
data as much as they want within a fixed time frame (e.g. one year)
and recreate the pdf without any extra charge. The customer's social
security number is used to identify the Will that the token is
assigned to.
Companies may also use the service, the more money they spend when
buying tokens, the cheaper the tokens. Companies may also have more
that one member of staff who can use the tokens. Each token will get
allocated the social security number of the main party of the Will
when the pdf is first created.
The Will data is edited by an external application and the Will data
is stored in an external application. The pdf is created by an
external service. Ofbiz is required for selling tokens and managing
the tokens.
Does the above scenario fit any data models and processes existing in
ofbiz?
Many thanks,
Chris
On Tue, Sep 14, 2010 at 12:08 PM, Ruth Hoffman<[email protected]>
wrote:
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"
objectInfo="/applications/mylibrary/data/PUBLICATIONS/OFBizRSS5StepGuide.pdf"
isPublic="Y" />
<SubscriptionResource subscriptionResourceId="PUB-RSS0710"
dataResourceId="PUB-RSS0710"
description="How To Add An RSS Feed In 5 Easy Steps" />
I also have a Product record and a productId of PUB-RSS07010 which is a
"digital good". So there is a ProductSubscriptionResource record:
<ProductSubscriptionResource productId="PUB-RSS0710"
subscriptionResourceId="PUB-RSS0710" fromDate="2001-05-13 12:00:00.0"
maxLifeTime="180" maxLifeTimeUomId="TF_day" />
You would change the maxLifeTime to a value that suited your
requirements.
FYI - Packt just told me that the OFBiz CookBook that I've been working
on
with them is available on their site:
https://www.packtpub.com/apache-ofbiz-cookbook/book
Not sure when Amazon will have it.
Hope this helps!
Regards,
Ruth
On 9/14/10 2:29 AM, David E Jones wrote:
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 single resource (e.g. downloading a particular
document/book) as many times as the customer requires. Therefore, the
token is tied to a resource id.
Is there already a similar concept in ofbiz that I could use as the
basis for my requirements? Maybe the gift certificate functionality?
Many thanks,
Chris
