Use cases

From Thunderforce
Jump to navigation Jump to search

This page contains the initial use cases in Thunderforce.

Under development

UC1: Account Type

UC1.1: User creates a Thunderbird account for Salesforce.com

  • Description:
  • Trigger:
  • Precondition:
  • Actors:
  • Flow of events:
  • Postcondition:
  • Priority:
  • Requirement:

UC1.2: User edits a Thunderbird account for Salesforce.com

  • Entity type selection for folders, address book items, and autocompletion
    • Default record types?
    • Fields to show in the views for each entity type? (or allow all, possibly making the list large for some entities?)
  • Select which document folders to view (subscribe?)
  • Username, password, URL
  • Default SMTP server for non-contact/lead/user email
  • Case escalation notification
  • Account name (default to Salesforce.com for the first account?)
  • Columns for the address book
  • Email signature
    • Local
    • On Salesforce.com

UC1.3: User opens a Salesforce.com Thunderbird account

  • Either through opening Thunderbird with an existing Salesforce.com account or creating a Salesforce.com account
  • Cache the icons from Salesforce.com

UC1.4: User clicks on a folder in the folder view

UC1.4.1: User clicks on the root Salesforce.com folder

UC1.4.2: User clicks on a Salesforce.com entity folder

UC1.4.3: User clicks on a record type subfolder of a Salesforce.com entity folder

UC1.4.4: User clicks on the Templates folder in a Salesforce.com Thunderbird account

UC1.4.5: User clicks on the Drafts folder in a Salesforce.com Thunderbird account

UC1.4.6: User clicks on the Documents folder in a Salesforce.com Thunderbird account

UC1.4.7: User clicks on a Documents subfolder in a Salesforce.com Thunderbird account

UC1.5: User copies or moves a message

UC1.5.1: User moves or copies an email message to a Salesforce.com entity folder that supports EmailMessage

UC1.5.2: User moves or copies an email message to a Salesforce.com entity folder that does not support EmailMessage

UC1.5.3: User moves or copies an email message from a Salesforce.com folder to another Salesforce.com folder

  • EmailMessage in source versus destination

UC1.5.4: User moves or copies an email message from a Salesforce.com folder to a non-Salesforce.com folder

UC1.6: User modifies a message in a folder

UC1.6.1: User changes a message flag on an email message in a Salesforce.com folder

UC1.6.2: User clicks on the match button on an email message in a non-Salesforce.com folder

UC1.6.3: User clicks on the manual match menu item within the match button on an email message in a non-Salesforce.com folder

UC1.6.4: User clicks on the unmatch button on an email message in a non-Salesforce.com folder

UC1.6.5: User clicks on the match button on an email message in a Salesforce.com folder

UC1.6.6: User clicks on the manual match menu item within the match button on an email message in a Salesforce.com folder

UC1.6.7: User clicks on the unmatch button on an email message in a Salesforce.com folder

  • Is this a valid use case?

UC1.7: Salesforce.com escalates a case that the user has access to

UC1.8: User views the matched columns in any Thunderbird folder

  • Matched Record, Matched Type, Matched Id

UC2: Address Book

UC2.1: User opens the address book view

  • Cache entity icons

UC2.2: User clicks on a Salesforce.com address book account

  • In either the address book window or in the contacts sidebar
  • Replacing the new card and new list buttons with new entity buttons in the address book window
  • Get the recently-viewed entity objects (either in Thunderforce or, if possible, Salesforce.com)

UC2.3: User selects an item in a Salesforce.com address book

UC2.4: User clicks on a new entity button in a Salesforce.com address book

UC2.5: User clicks on the properties button on an item in a Salesforce.com address book

UC2.6: User clicks on the write button on an item in a Salesforce.com address book

UC2.7: User clicks on the delete button on an item in a Salesforce.com address book

UC2.8: User searches for a contact in a Salesforce.com address book

  • Either in the address book or the address book sidebar

UC2.9: User edits the addressing tab in Thunderbird's composition configuration

  • Autocompletion using Salesforce.com

UC3: Message Composition

UC1.15: User sends an email message using a Salesforce.com Thunderbird account

  • Use Salesforce.com for mail to contacts, leads, and users
  • Use default outgoing server for other mail
  • Include attachments
  • Dispatch message to the message's matched entity objects

UC3.1: User clicks on the unmatch button next to a Salesforce.com object in the message destination in the message composition

  • Causes Thunderbird to send the email without saving it in the matched object's Salesforce.com record

UC3.2: User adds a contact to an email message using the contacts sidebar

UC3.3: User opens an existing email message for reply, forwarding, resending, or another purpose

  • Match Salesforce.com entity objects if not done already
  • Load signature from proper place

UC3.4: User types an email address into a destination field in the message composition window

  • Match with a Salesforce.com entity object

UC3.5: User clicks on a the new entity drop-down button and selects the entity type to create in message composition

UC3.6: User clicks on the attach drop-down menu and selects Salesforce.com document in message composition

UC3.7: User clicks on the attach drop-down menu and selects Salesforce.com email message in message composition

UC3.8: User creates a new message in a Salesforce.com Thunderbird account

  • Load signature from proper place

UC3.9: User saves a Salesforce.com Thunderbird account message as a draft

UC3.10: User sends a mass mailing using mail merge

UC4: Message Filters

Message filter use cases on their way...

UC5: Offline Mode

Offline mode use cases on their way...