Configuring email instantiation for a case type

You can configure a case type to support email instantiation. By associating your case type with an email account, you can provide a way for users to create cases remotely and track the related discussion thread in one place.

Note: Email instantiation is not supported in systems that use LDAP authentication.
  1. Create an email account.
    Do not use a personal email account because unread messages are deleted when the email listener is started.
    1. Review the limitations on email accounts to understand how they affect your application.
    2. Create an email account by running the Email Wizard.

      You do not need to create an email service implementation, because your application generates the required rules when you associate the email account with a case type.

  2. Verify that you can connect to the email server.
    1. Open the Email Account form.
    2. In the Sender section, click Test Connectivity.
    3. In the Receiver section, click Test Connectivity.
  3. Ensure that the listener that supports your email account is running.
    1. Open the System Management Application by clicking Designer Studio > System > Operations > System Management Application .
    2. Click the node that hosts your application.
    3. Click Listener Management.
    4. If the listener is not running, select it from the Available Listeners list and click Start.
  4. Manually associate the email account with your case type.
    Tip: To increase the visibility of this association, use a channel interface instead. See Configuring the Email channel.
    1. In the Explorer panel, click Case types, and then click the case type that you want to open.
    2. On the Settings tab, click Email instantiation.

      Only top-level case types support this option.

    3. In the Starting process list, select a flow that runs when the case is created.

      Although case types can have more than one starting process, an email account is associated with only one starting process at a time.

    4. In the Email account field, press the Down Arrow key and select the name of an email account that is not associated with another case type in your application.
      You are warned when you select an email account that is already in use. If you save your case type with this configuration, more than one listener monitors the same email account, which can result in inconsistent case creation.
    5. Select the Enable email listener check box to start the listener that monitors your email account.
    6. Click Save to create the required integration rules.
    7. Optional: For more information about the integration rules that support email instantiation, open the Designer Studio > Integration > Email > Email Listeners landing page.
  5. Test your changes by sending an email message to the address that is specified in the email account.

    You can also reply to the confirmation email that you receive after the case is created, to continue the discussion with a case worker or ask a question about the case.

At run time, the initial email message and replies are stored in Pulse.