I want to add Product model for my project
What class should i extend?
I think like Task model class extends MashableActivity.
And i found similar Mission model class extends OwnedSecurableItem with MashableActivityInterface
MashableActivity question
Started by pauk, Oct 18 2012 09:32 PM
4 replies to this topic
#2
Posted 18 October 2012 - 10:24 PM
Depends on what you are doing with the product model. Do you need to secure it or will everyone be able to see it? Can you describe your use-case more?I want to add Product model for my project
What class should i extend?
I think like Task model class extends MashableActivity.
And i found similar Mission model class extends OwnedSecurableItem with MashableActivityInterface
Jason Green
Zurmo Team
Need support? Upgrade now
#4
Posted 20 October 2012 - 10:39 AM
look at this diagram
http://api.zurmo.com...y_interface.php
Let consider Meeting and Conversation classes
Meeting extends MashableActivity that has parent OwnedSecurableItem (and MashableActivityInterface)
Conversation extends OwnedSecurableItem directly ( and MashableActivityInterface too)
Why this classes has one interface but different extends way.
Maybe we can Conversation extend thru MashableActivityClass directly?
http://api.zurmo.com...y_interface.php
Let consider Meeting and Conversation classes
Meeting extends MashableActivity that has parent OwnedSecurableItem (and MashableActivityInterface)
Conversation extends OwnedSecurableItem directly ( and MashableActivityInterface too)
Why this classes has one interface but different extends way.
Maybe we can Conversation extend thru MashableActivityClass directly?
#5
Posted 22 October 2012 - 03:00 AM
The idea behind the MashableActivityInterface is that many things could be mashable. This means they can show up underneath the activities subpanel in the detailviews of accounts for example, or on the lastest activities home page portlet.
MashableActivity is designed to be the parent class of what is traditionally considered 'activities' in CRM, notes,meetings, calls and tasks. Calls/Meetings are combined into just one model for simplicity.
So something like products would most likely not extend MashableActivity as it is not really an activity. I don't really think it should implement the MashableActivityInterface because it is not really an event that occurs at a specific time. I think if you make a product model, you should have it extend OwnedSecurableItem for security, then you can make a new portlet for it. Similar to how there is a related Contact portlet to show related contacts in the account detailview for example.
MashableActivity is designed to be the parent class of what is traditionally considered 'activities' in CRM, notes,meetings, calls and tasks. Calls/Meetings are combined into just one model for simplicity.
So something like products would most likely not extend MashableActivity as it is not really an activity. I don't really think it should implement the MashableActivityInterface because it is not really an event that occurs at a specific time. I think if you make a product model, you should have it extend OwnedSecurableItem for security, then you can make a new portlet for it. Similar to how there is a related Contact portlet to show related contacts in the account detailview for example.
Jason Green
Zurmo Team
Need support? Upgrade now
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users









