Module identification and assignment: Difference between revisions
Jump to navigation
Jump to search
m (→Dreamforce) |
|||
Line 44: | Line 44: | ||
#[[Requirements#R3: Message Composition|Outgoing messages]] | #[[Requirements#R3: Message Composition|Outgoing messages]] | ||
##Email address lookup | ##Email address lookup | ||
#[[Requirements#R1: Account Type|Account type]] | #[[Requirements#R1: Account Type|Account type]] (done) | ||
##Account wizard (done) | ##Account wizard (done) |
Revision as of 20:47, 9 September 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
- Root folder
- Document folders
- Entity folders
- Messages
- Match/unmatch message buttons
- View in Salesforce.com buttons for matched messages
- Properties
- Address book
- Address book
- Cards
- Groups
- Outgoing messages
- Email address lookup
- 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 (done)
- nsSalesforcePartner (done)
- nsSalesforceLocalBidirectionalPartner (done)
- Address book
- Address book
- Cards
- Groups
- Outgoing messages
- Email address lookup
- Account type (done)
- Account wizard (done)