Module identification and assignment: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 37: | Line 37: | ||
##Root folder | ##Root folder | ||
#[[Requirements#R3: Message Composition|Outgoing messages]] | #[[Requirements#R3: Message Composition|Outgoing messages]] | ||
## | ##Email lookup using Salesforce.com | ||
##Match/unmatch message buttons | ##Match/unmatch message buttons | ||
#[[Requirements#R2: Address Book|Address book]] | #[[Requirements#R2: Address Book|Address book]] |
Revision as of 04:08, 28 August 2007
Modules
Thunderforce's architecture calls for several high-level modules that can be broken down into the lower-level modules listed below. These all are traceable to the original feature list.
- Salesforce.com data layer
- nsSalesforceBidirectionalPartnerCache
- nsSalesforceLocalBidirectionalPartner
- nsISalesforceBidirectionalPartnerPoller
- nsSalesforcePartnerMetricsCollector
- nsSalesforcePartner
- Account type
- Account wizard
- Folders
- Messages
- Match/unmatch message buttons
- Address book
- Address book
- Cards
- Groups
- Outgoing messages
- Message sending via Salesforce.com
- Match/unmatch message buttons
- Message filters
- Filter criteria
- User interface extensions
- Filter actions
- Rule generation
- Offline mode
- Offline mode
Dreamforce
The following will be targeted for the Dreamforce demo release using the given priority:
- Salesforce.com data layer
- nsSalesforcePartner
- nsSalesforceLocalBidirectionalPartner
- Account type
- Account wizard
- Root folder
- Outgoing messages
- Email lookup using Salesforce.com
- Match/unmatch message buttons
- Address book
- Address book
- Cards
- Groups