Several Feature Requests

Message Share Topic Printable Version Google Delicious Digg StumbleUpon Windows Live Yahoo Bookmarks reddit Facebook MySpace Newsvine Furl Topic Search Topic Options Post Reply Create New Topic

   I have a few suggestions for new features in Email2DB:

- User-defined global properties.  For example, you may refer to a support email address in email messages sent by Email2DB.  It would be good to configure the support email address in one global property, rather than hardcoding it thoughout your triggers.

- Email signatures.  It would be very useful to be able to define one or more email signatures for an account, and then be able to select which signature (if any) will be included with any outgoing emails.

- Search-and-Replace in the script editor.  Currently, you can do a search (Find) in the script editor, but not a search-and-replace.

- Common Shared Scripts.  I know this has been mentioned before, but it would be great if you could write common code in a single location (either for an entire account, or for the entire installation), and then call those functions from within the condition scripts and extraction scripts.

- A single place to configure database connection strings, then choose a database connection string from a dropdownlist of user-defined names (e.g. in the Lookup Field / General tab).  That way, if you change the name of your database instance, or when you deploy from QA to Prod, you only have to change one database connection string.

I've looked through the manual and the forums and haven't seen these things mentioned (other than the common code), but if they are currently possible, please let me know ... Thanks!

Edited by TGaines - 19 Jan 2010 at 8:36pm

Author	Message Share Topic Printable Version Google Delicious Digg StumbleUpon Windows Live Yahoo Bookmarks reddit Facebook MySpace Newsvine Furl Topic Search Topic Options Post Reply Create New Topic
TGaines Members Profile Send Private Message Find Members Posts Add to Buddy List New User Joined: 14 Jan 2010 Location: Canada Posts: 14	Post Options Post Reply Quote TGaines Report Post Quote Reply Topic: Several Feature Requests Posted: 19 Jan 2010 at 5:19pm
	I have a few suggestions for new features in Email2DB: - User-defined global properties. For example, you may refer to a support email address in email messages sent by Email2DB. It would be good to configure the support email address in one global property, rather than hardcoding it thoughout your triggers. - Email signatures. It would be very useful to be able to define one or more email signatures for an account, and then be able to select which signature (if any) will be included with any outgoing emails. - Search-and-Replace in the script editor. Currently, you can do a search (Find) in the script editor, but not a search-and-replace. - Common Shared Scripts. I know this has been mentioned before, but it would be great if you could write common code in a single location (either for an entire account, or for the entire installation), and then call those functions from within the condition scripts and extraction scripts. - A single place to configure database connection strings, then choose a database connection string from a dropdownlist of user-defined names (e.g. in the Lookup Field / General tab). That way, if you change the name of your database instance, or when you deploy from QA to Prod, you only have to change one database connection string. I've looked through the manual and the forums and haven't seen these things mentioned (other than the common code), but if they are currently possible, please let me know ... Thanks! Edited by TGaines - 19 Jan 2010 at 8:36pm

TGaines Members Profile Send Private Message Find Members Posts Add to Buddy List New User Joined: 14 Jan 2010 Location: Canada Posts: 14	Post Options Post Reply Quote TGaines Report Post Quote Reply Posted: 03 Feb 2010 at 2:28pm
	w.r.t. Database Connection Strings, I realized after posting this list that you can use User or System DSNs to partially accomplish this goal. However it would still be nice to configure a connection string only once per account, rather than sprinkling the connection strings among multiple triggers.