REQUEST A DEMO

Tag: busienss rule

New in Rulemanager: Support for Multiple email addresses for a contact or employee

October 5, 2011 Earlier this summer I blogged some thoughts around multiple email addresses for a contact or employee. I wanted to throw out a little update about how we’re addressing this. We’re addressing this in two ways – via Rulemanager, and via DovetailAgent. I’ll cover the DovetailAgent changes in a future post. Rulemanager We’ve modified Dovetail Rulemanager so that it supports multiple email addresses in a single email field. This could be on the employee or on the contact’s email field. The email addresses can be separated by a comma, semicolon, or a space. Lets see it in action I’ve created a new employee with the ever-so-descriptive name of “Multiple Emails” This employee has two SMTP addresses in the one email address field: If I have a business rule that notifies this employee, I can see that the notification gets sent to…

Multiple email addresses for a contact or employee

June 10, 2011 In today’s modern age, many people have multiple email addresses. They may have a work email, a home email, a personal email, etc. I think I may have at least 1/2 a dozen.   In Clarify (and Dovetail), there’s one field for specifying an email address. Back in 1990, it was uncommon that people had multiple email addresses, so a single field was sufficient.   But what do we do when a contact has multiple email addresses? Where do we store that info?   I’ve seen systems where multiple custom fields are created, such as: table_contact.x_home_email table_contact.x_work_email table_contact.x_alternate_email table_contact.x_alternate_email2   etc.   Yuck.   I’ve also seen systems where multiple email addresses are crammed into the one existing email field.   Yuck again. How about…   I think what would be useful is a table that allowed for many email…