What exactly does support of behavior in Aspects mean?

I am pretty new to the aspects term in Documentum 6.5. What I found is aspects support both behavior and attributes. I understand the use of attributes with aspects however, wrt to behavior I am a little confused.I'll first write down how I see aspects as:-

1. They can be used with cross types. i.e. they are instance specific and not type specific.

2. I can create an aspect with two attribs eg. customer_band and customer_Reg_date. What now I can do is, to any object which contains customer infomation I can attach this aspect.I can modify this aspect's values etc.

3. I can also create a method within this aspect say giveCustomerBonus()and provide a logic like If customer is a gold customer and has registered 5 years back, I should perform some custom operations which would say give that customer a bonus.

Now comes my big question :- If I modify customer_band attribute on a particular object instance, I want giveCustomerBonus() call to get executed automatically. I know that once I modify customer_band, I can make a follow up call to giveCustomerBonus() as well but that is not I want. I want Documentum to look after that if any of my aspects attribute value changes I should recieve a call to giveCustomerBonus() method. Is this possible ? Or does a behavior attachment to an aspect only means that it can includes methods along with attributes in its definition and hence one can call them anytime they need it and no behavior can really be attached to event like when aspect value changes from one to another etc etc... ?

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

lastnitescurry

In Aspect extend the doSave method, to also call giveCustomerBonus() if customer_bandhas been modified

All comments

lastnitescurry

In Aspect extend the doSave method, to also call giveCustomerBonus() if customer_bandhas been modified

Raghu_A

Thanks Brain. I'll try and do that..

Raghu_A

BTW in that case I'll have to inherit the Aspect implementation class from DfDocument. Correct? Won't that make the implementation specific to the items who have in the type heirarchy somewhere some connection with the DfDocument? I know that its what most of the time we need but I just want to be sure if I understand it properly and does there exists any other way which in any situation does not limit me to a specific type or only some type's class and its derived classes?

Raghu_A

Any Comments ?

sudhakar.tata@gartner.com

You can override setString() method in your Aspect's implemenation class to call the method giveCustomerBonus(). So thet it gets called whenever customet_band is updated. That way you can add any custom behavior to the Aspect object.