Difference between revisions of "Setup for opentaps email Handling"
m (Protected "Setup for opentaps email Handling": Sysop page [edit=sysop:move=sysop]) |
(→The Special '''opentaps''' Email Client) |
||
| Line 3: | Line 3: | ||
==The Special '''opentaps''' Email Client== | ==The Special '''opentaps''' Email Client== | ||
| + | This section discusses special '''opentaps''' processing for email, which can be configured by a technical system administrator. | ||
| + | '''opentaps''' includes an email client with some special features that present your business email as a part of the context for teamwork and coordination. Thus, it is well worth the effort to set up email in order that the user's email can appear in the activity information for all business transactions (Cases, Orders, Accounts, etc.) on the system. | ||
| + | |||
| + | '''opentaps''' email makes use of your existing outbound email service (SMTP) and your existing inbound email service (POP3, or IMAP) when the users email IDs are entered by [[Setting User Profile]], and the email server addresses, authentication info, and passwords are configured into the relevant '''opentaps''' system files. Also, a regular expression string is configured to provide for detecting the email addresses that are relevant to your '''opentaps''' business processing. | ||
| + | |||
| + | Some minor additional configuration of your inbound email server software is required to route email to the '''opentaps''' special address for inbound email reception. | ||
| + | |||
| + | When your outbound email is copied to this special address it is archived in context with the related '''opentaps''' transactions similar to the inbound email as we have discussed. | ||
| + | |||
| + | Finally, the teamwork context of '''opentaps''' can be enhanced further by enabling notification emails to your team members whenever certain things happen, which they should be made aware of, including: | ||
| + | |||
| + | * When people are added or removed from activities or events | ||
| + | * When people are assigned to leads and accounts | ||
| + | * When catalog requests have been successfully fulfilled | ||
| + | * Optional -- When a catalog request is fulfilled an email can be sent to the customer who | ||
| + | requested it. | ||
| + | |||
| + | From this description it is evident that configuring the email for '''opentaps''' processing is a task for the same technical administrator who has set up your regular email service, or someone who is familiar with system file configuration, email setup, and programming scripts that use regular expressions. | ||
==Outbound Email Setup== | ==Outbound Email Setup== | ||
Revision as of 19:06, 7 October 2009
Contents
The Special opentaps Email Client
This section discusses special opentaps processing for email, which can be configured by a technical system administrator.
opentaps includes an email client with some special features that present your business email as a part of the context for teamwork and coordination. Thus, it is well worth the effort to set up email in order that the user's email can appear in the activity information for all business transactions (Cases, Orders, Accounts, etc.) on the system.
opentaps email makes use of your existing outbound email service (SMTP) and your existing inbound email service (POP3, or IMAP) when the users email IDs are entered by Setting User Profile, and the email server addresses, authentication info, and passwords are configured into the relevant opentaps system files. Also, a regular expression string is configured to provide for detecting the email addresses that are relevant to your opentaps business processing.
Some minor additional configuration of your inbound email server software is required to route email to the opentaps special address for inbound email reception.
When your outbound email is copied to this special address it is archived in context with the related opentaps transactions similar to the inbound email as we have discussed.
Finally, the teamwork context of opentaps can be enhanced further by enabling notification emails to your team members whenever certain things happen, which they should be made aware of, including:
* When people are added or removed from activities or events
* When people are assigned to leads and accounts
* When catalog requests have been successfully fulfilled
* Optional -- When a catalog request is fulfilled an email can be sent to the customer who
requested it.
From this description it is evident that configuring the email for opentaps processing is a task for the same technical administrator who has set up your regular email service, or someone who is familiar with system file configuration, email setup, and programming scripts that use regular expressions.
