Method Community

 

Release Notes

Method CRM Updates - October 22 - October 24, 2011

The following indicates which accounting application(s) the release note(s) apply to.
  • QBD = QuickBooks Desktop
  • QBO = QuickBooks Online

Edit Case

  • New - we’ve added a new field to the cases table IsEmailCaseNotificationToContact and made the “Email Case notification to contact when saving?” a bound field.  This way if the preference is enabled/disabled, it will save that preference for that Case. (QBO & QBD)
  • Improved - when attempting to add a new contact from the “Activity Contact” or “Follow-up Contact” dropdown lists, we now check to make sure that a main contact for the case is assigned.  If the case does not have a contact assigned, a message will appear at the top of the screen. (QBO & QBD)
  • Fixed - the miURL link being sent to the contact associated with the case was not automatically prompting for the email address.  This was because the Entity.RecordID was not being provided passed in the actions.  This is now fixed. (QBD & QBO)
  • Fixed - email being sent for activity did not have a default tab group setup for the miURL action.  Changed this to “CRM”. (QBD & QBO)
  • Fixed - email being sent for case did not have a default tab group setup for the miURL action.  Changed this to “CRM”. (QBD & QBO)
  • Fixed - email being sent for follow-up activity did not have a default tab group setup for the miURL action.  Changed this to “CRM”. (QBD & QBO)

New Case

  • New - now you can add a new contact for the lead/customer/vendor associated with the case by clicking the dropdown list for “Activity Contact” or “Follow-up Contact” and selecting < Add New >.  We also now verify that a main contact for the case is selected in the “Contact” dropdown list before attempting to add a new contact. (QBO & QBD)
  • New - we’ve added a new field to the cases table IsEmailCaseNotificationToContact and made the “Email Case notification to contact when saving?” a bound field.  This way if the preference is enabled/disabled, it will save that preference for that Case. (QBO & QBD)
  • New - now when creating a new case, Method will check to see if the user logged in has their default preference set to email the contact associated with the case if any option other than “none” is selected. (QBO & QBD)
  • Improved - now when a different contact is selected from the “Contact” dropdown list, the “Activity Contact” and “Follow-up Contact” dropdowns get pre-filled automatically with the name in the “Contact” dropdown.  The name, phone number and email also get pre-filled. (QBO & QBD)
  • Improved - the “Activity Contact” and “Follow-up Contact” dropdown lists now display the contacts phone number for the second column and email address for the thrid column.  Since we already know the company and entity type, its more useful to have these fields displayed here as additional columns. (QBO & QBD)
  • Improved - updated the radio button option for “Existing Customer/Vendor” to “Existing Lead/Customer/Vendor/Employee”. (QBO & QBD)
  • Improved - made the “Contact” field a required field.  This prevents the chance that a blank contact entry will be created. (QBD)
  • Improved - made the “First Name” field a required field.  This prevents the chance that a blank contact entry will be created. (QBO)
  • Improved - the section header for existing contact has now been changed to “Existing Lead / Customer / Vendor / Employee”. (QBO & QBD)
  • Improved - the Activity Contact and Follow-up Contact fields only appear if the “Existing Lead/Customer/Vendor/Employee” radio option is selected.  he reason we’ve done this is to avoid confusion with these fields appearing blank before the entity is actually saved. (QBO & QBD)
  • Improved - when un-checking the “New Activity?” checkbox, the section for “Schedule a Follow-up” will now hide automatically. (QBO & QBD)
  • Fixed - all images were updated to now use https vs. http. (QBO & QBD)
  • Fixed - the text for “Contact Assigned To” was the wrong size.  Matched this to the other fields to keep a consistent look. (QBO)
  • Fixed - the miURL link being sent to the contact associated with the case was not automatically prompting for the email address.  This was because the Entity.RecordID was not being provided passed in the actions.  This is now fixed. (QBO & QBD)
  • Fixed - email being sent for activity did not have a default tab group setup for the miURL action.  Changed this to “CRM”. (QBO & QBD)
  • Fixed - email being sent for case did not have a default tab group setup for the miURL action.  Changed this to “CRM”. (QBO & QBD)
  • Fixed - email being sent for follow-up activity did not have a default tab group setup for the miURL action.  Changed this to “CRM”. (QBO & QBD)


Special thanks to Judy Syms for providing some great feedback on some of the changes that were implemented in this release.  Star

Cheers,

Danny

 

Comments

No Comments

This Blog

Syndication