Requirements: Difference between revisions

From Thunderforce
Jump to navigation Jump to search
No edit summary
Line 11: Line 11:
*Folder views for each entity type that supports email attachments
*Folder views for each entity type that supports email attachments
**Entity types, whose presences can be toggled in the account properties (only those that the user has access to can be shown)
**Entity types, whose presences can be toggled in the account properties (only those that the user has access to can be shown)
***Accounts, Campaigns, Cases, Opportunities, Solutions, Products, Custom Objects
***Accounts, Campaigns, Cases, Contacts, Contracts, Opportunities, Products, Solutions
**Matches emails to their entity rows automatically, prompting the user on a case-by-case basis for emails that could not be matched by using the Salesforce.com application within a window. Entity columns are eligible to be shown as columns in each entity type's folder. Important columns for each entity type are shown by default
**Matches emails to their entity rows automatically using case number, subject, In-Reply-To (needs investigation), or References
**A special "Add New" parent folder contains the entity types underneath it to permit unprompted adding of all email sent to the child folders as new entity rows without matching. The contents of those folders only list new entity rows added by the user in the current session
**When an email cannot be matched, it's added as a new entity of the type that the message was copied into
**Special "All Email" folder view that lists all email that the user can see in Salesforce.com along with the entity type, entity name/ID, and contact/lead name/ID as columns
**Entity columns are eligible to be shown as columns in each entity type's folder. Important columns for each entity type are shown by default
**Email template folders
**Record types appear as subfolders of an entity when access to more than one exists on an entity
*Email template folders
*Drafts are stored in the user's personal folder as .eml documents
*Attachments to objects are stored as .eml files, which can be opened in Thunderbird, Outlook, Outlook Express, and other clients
*Add each Salesforce.com account as an outgoing mail server
*Add each Salesforce.com account as an outgoing mail server
*For the "outgoing server" field in the account settings, permit the user to select any server, but default to Salesforce.com
*Use Salesforce.com as the default outgoing mail server to contacts, leads, and users
*Use the default outgoing mail server for other mail, though this is configurable


==Address Book==
==Address Book==

Revision as of 07:02, 29 April 2007

This page lists the present set of planned features for Thunderforce.

Note that none of these features are actually implemented yet. These are the planned features.

Account Type

Present Salesforce.com as a Thunderbird account type

Mock-up of the main window showing Salesforce.com folders that can contain email attachments
  • Account creation wizard tie-in
  • Account properties page for Salesforce.com accounts
  • Folder views for each entity type that supports email attachments
    • Entity types, whose presences can be toggled in the account properties (only those that the user has access to can be shown)
      • Accounts, Campaigns, Cases, Contacts, Contracts, Opportunities, Products, Solutions
    • Matches emails to their entity rows automatically using case number, subject, In-Reply-To (needs investigation), or References
    • When an email cannot be matched, it's added as a new entity of the type that the message was copied into
    • Entity columns are eligible to be shown as columns in each entity type's folder. Important columns for each entity type are shown by default
    • Record types appear as subfolders of an entity when access to more than one exists on an entity
  • Email template folders
  • Drafts are stored in the user's personal folder as .eml documents
  • Attachments to objects are stored as .eml files, which can be opened in Thunderbird, Outlook, Outlook Express, and other clients
  • Add each Salesforce.com account as an outgoing mail server
  • Use Salesforce.com as the default outgoing mail server to contacts, leads, and users
  • Use the default outgoing mail server for other mail, though this is configurable

Address Book

Present Salesforce.com as a Thunderbird address book data source for each Salesforce.com account

  • Support the following objects in an account's address book as cards. By default, all are on. Only those that the user has access to will show up
    • Contacts, Leads, People (person accounts), Campaigns (not a list because that could potentially create a huge list), Users
  • Support the following objects in an account's address book as lists. These can be enabled or disabled in the configuration. By default, all are on. Only those that the user has access to will show up
    • Accounts, Cases, Opportunities, Contracts, Roles, Profiles, Solutions, Products, Custom Objects
  • Add "Salesforce.com Account:" and an account drop-down box into Thunderbird's "Address Autocompletion" preferences after "Directory Server" and enable by default. This is both for global and for the Salesforce account preferences
  • Support address autocompletion using one Salesforce.com account, though limit the query rate to once every three seconds and at least one second after the last character was typed
  • Using a Salesforce.com address book entry will automatically associate an outgoing message with the associated entity. If a contact or individual, however, the user is asked if the email should be associated with the contact/individual, their account (contact), a contract, an opportunity, a case, or some other object

Composition

Add Salesforce.com convenience buttons to the message composition screen

Mock-up of the Compose window showing objects that can be contacted
  • more to be written up...