Troubleshooting errors with email instantiation
During email instantiation, some issues might occur that prevent case creation and, as a result, hinder the workflow in your organization. By troubleshooting errors with email instantiations, you increase the automation of case processing and deliver efficient software.
For example, an insurance agent can send an email to an application to create a case after the agent assesses vehicle damage at a car accident site. By troubleshooting any issues related to email instantiation, you ensure that the application correctly creates a new case, and that the workflow in your enterprise is uninterrupted.Condition
Users want to create a case by sending an email to a specified email account. An issue with the email account configured for email instantiation occurs and case creation fails.
Unavailable email account
The email account that you configured for case instantiation is currently in use by another case type.
Solution: Creating an email account exclusively for a case type
- In the navigation pane of Dev Studio, click Case types, and then click the case type that you want to open.
- On the Settings tab, click Email instantiation.
- Clear the Enable email listener check box.
- Find and manually delete the set of standard rules that your application created
when you enabled email instantiation for your case type.For a list of these rules, see Standard rules used by email instantiation.
- In the case type rule form header, click Save, and then click .
- Create a new email account exclusively for your case type.For more information, see Configuring outbound email in App Studio.
- Enable email instantiation for your case type by using your new email
account.For more information, see Enabling creation by email of top-level cases.
The email account cannot send or receive emails
The email account that you configured for email instantiation has issues when sending or receiving emails.
Solution: Testing and debugging email account connectivity
- In the navigation pane of Dev Studio, click Case types, and then click the case type that you want to open.
- On the Settings tab, click Email instantiation.
- Below the Email address field, click the email address that you associated with the case type, as shown in the following figure:
- On the Email account tab of the email account rule form,
test connectivity:
- If the email account cannot send emails, in the Sender section, click Test connectivity.
- If the email account cannot receive emails, in the Receiver section, click Test connectivity.
- In the Test Connectivity window, review the test results.
- Optional: To obtain more information for debugging, inspect the log files:
- In the header of Dev Studio, click .
- On the Logs tab, in the Log utilities section, click Log files.
- In the Log File Download window, examine the logs.For more information, see Viewing logs.
Redundant HTML tags in incoming emails
Incoming email messages include redundant HTML tags that cause case creation by email to fail.
Solution: Removing redundant HTML tags from an email text
- In the navigation pane of Dev Studio, click Records.
- Expand the Technical category, and then click Activity.
- In the list of activity instances, open the pyTreatIncomingText activity.
- In the rule form header, click Save as.
- In the Context section, in the Apply to field, select a class that includes the case type that you configured for email instantiation.
- Click Create and open.
- In row 1. of the activity that includes a Java method, click Expand to see method parameters.
- In the Java Source text box, edit the Java script to exclude
HTML tags from the email text:
- To remove tags related to script and script elements, include the doc.select("script").remove(); line in the script.
- To remove tags related to styling, include the doc.select("style").remove(); line in the script.
- To remove tags related to formatting, include the doc.select("form").remove(); line in the script.
- To remove line breaks, include the doc.select("br").remove(); line in the script.
- To remove metadata tags, include the doc.select("meta").remove(); line in the script.
- In the activity header, click Save.
Your email account is flagged as suspicious
The email provider that you included in the email account configuration flagged your email account as suspicious.
- Access your email account by using a web browser or supported client application.
- Log in by entering your user name and password.
- Follow any additional steps from your email provider to successfully access the account.
Email listener does not respond
Email listener does not respond because the email messages are marked as read.
Solution: Keep email messages unread
- Do not open and read email messages because email listeners respond only to unread messages. Notify your development team of this restriction.
Previous topic Including indexed data during case search Next topic Standard rules used by email instantiation