If you have questions or if you want to share your opinion about Aware IM post your message on this forum
#245 by denisv
Mon Jan 23, 2006 10:56 pm
Can you advise on the following:

a) I have two business objects, client and product
b) I have associated the two so that I can add mulitple products to client
c) What I want to do is have a field that when I add a product to the client I can select a status (this is not the status of the product but of the client interest in gthe product).
d) Can this be done
e) Alternatively, is there a way of copying data from one business object (product - some atributes) to another by selection (product interest) and then in the receiving business object (product interest) there would be additional attributes, one could be a status field which sould then be updated ?



#247 by aware_support2
Tue Jan 24, 2006 12:15 am

Almost certainly this can be easily done. Before I can give you the details though, could you please describe a more specific example to ensure I understand your task correctly? For example, what do you want to happen when you add a Product with attributes Name 'ABC', Code '123' and Category 'Book' to the Client?

> c) What I want to do is have a field that when I add a product to the client I can select a status (this is not the status of the product but of the client interest in gthe product).
Is Status an attribute of Client?
What should it show?
Do you want Status attribute to automatically register the name of the last Product added to Client?

#252 by denisv
Wed Jan 25, 2006 8:38 am
Thanks for the reply, some of this is not yet in place so forgive the generalities.

a)The scenario would be that the Client Business Object does not have a status attribute
b) There could be multiple products against the product
c) When a product is put against a client it is considered 'an interest'
d) I have no Status attribute yet
e) Ultimately the status attribute (whereever it should be) would contain values such as 'Interested', 'Not Interested', 'Purchased' or 'Rented'
f) The intention is to keep all the 'interests' so that a history can be built up for reporting against both the client and the product
g) Each product is unique but there could be many clients with 'interests' in the same product (and at the same time)

So what I hope to acheive is:

(i)Add Product (with attrubutes like, type, location, name) against one of more clients.
(ii) When added, flag a status.
(iii) be able to change the status depending on result
(iv) Be able to query how many clienst are interested in a specific product now or in the past
(v) Be able to query what products a client is interested in now, or in the past.



#253 by denisv
Wed Jan 25, 2006 8:42 am
Correction to point b)
There could be multiple products against a client.


#255 by aware_support2
Wed Jan 25, 2006 10:36 am

Based on your requirements I would suggest you to consider a design that in addition to objects Client and Product has an intermediary object called, say, ProductAction. This new object would have attribute Status to register the nature of the action (i.e. 'Interested', 'Not Interested', 'Purchased' or 'Rented') and attribute TakenOn to register the date the action was taken. It would also have attributes Client (multiples not allowed) and Product (multiples not allowed) to capture the client and the product for the action. Business objects Client and Product would each have a corresponding matching attribute Actions (multiples allowed) to register actions against a product or a client.

This is how it will work. On the form for object Product you select Add New Item operation for attribute Actions. The system will show the form for object ProductAction. You select a client by clicking Add New Item for attribute Client, set the Status attribute to the appropriate value and the TakenOn attribute to the desired date (for convenience the system can be instructed to automatically set TakenOn to the current date). Once all the details are entered you click Create button to register the new ProductAction. Once registered the new ProductAction will appear on both the Client and the Product forms. You can repeat these steps to register more ProductAction records for the same or different products/clients. You will be able to change the status of any action at a later stage.

With this design you would register each action separately. For example, if a client first got interested in a product and then purchased the product at a later date, you would create two separate ProductAction records to register each of these actions.
In a more elaborate design, object ProductAction can have more attributes so you can track the action history without having to create multiple records. For example, you could add attributes like InterestedOn, PurchasedOn and RentedOn to capture the dates of particular actions the client took against the product. This would reduce the overall number of ProductAction records, which would make the data presentation more compact and convenient for you.

As for the queries, the forms for objects Client and Product would already show all the actions registered against the client/product. You can narrow down the list by entering various criteria, like date range, for the list on the form. If this proves to be insufficient for you, or if you want to have specially prepared reports, with Aware IM you can easily configure specific queries/reports at a later stage.

Please have a look at object Loan in the configuration of the Library sample application for an example of an object that registers interest (and action history) of a library member for a library item. This would be a very similar design to the one described above.

Note the importance of matching attributes. Please consult Aware IM User Guide for details.

#257 by denisv
Wed Jan 25, 2006 12:51 pm
Thanks for the assistance I'll try that.

#268 by denisv
Fri Jan 27, 2006 11:36 am
This worked great - thanks

Who is online

Users browsing this forum: Google [Bot] and 34 guests