Skip to main content
LinkedIn
Copied!

Table of Contents

Standard rules used by email instantiation

Version:

Only available versions of this content are shown in the dropdown

When you enable email instantiation for a case type, a set of rules and data instances are created. Although these rules are managed by your application, it is good to know how they are named and what functionality they provide in the event that you need to remove them or debug an issue.

The following standard rules are used by email instantiation:

  • Email account — Contains email account credentials

    The name of this data instance is provided by the person who created the email account. You cannot create an email account by updating the settings of a case type.

  • Email listener — Watches the specified email account for new messages

    The identifier for this rule has two parts:

    • The word "Listener"

    • The class of your case type, the name of your starting flow, and the word "Listener" separated by underscores

  • Service email rule — Runs your starting flow to create a case

    The identifier for this rule has three parts:

    • The class of your case type without hyphens

    • The class of your case type

    • A label that concatenates the word “Create” and the name of your starting flow

  • Service package — Manages services

    The name of this rule is the class of your case type without hyphens.

These standard rules are not displayed in the Application Explorer because they do not have an applies to class. You can find these rules by searching, opening the Records Explorer, or viewing the Dev Studio > Integration > Email landing page.
Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us