Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Setting up entity property mapping

Updated on June 21, 2021

To improve the responses that your Pega Email Bot™ provides to emails, you can optionally add entity extraction information for a suggested case. As a result, when a case type is associated with an email that you receive, your email bot extracts entities from email content, and automatically assigns them to a case type property in a Pega Platform application.

For example, for the Car Insurance case, you can map the CarModel and CarMake entities to the .CarModel and .CarMake case properties. When these entities are detected in email, their values are automatically assigned to the case properties.
Before you begin: Set up suggested cases for your email bot. For more information, see Adding suggested cases for an Email channel.

Entities contain proper nouns that fall into a commonly understood category, for example, a person, a location, a date, an organization, or a ZIP code.

  1. In the navigation pane of App Studio, click Channels.
  2. In the Current channel interfaces section, click the icon that represents your existing Email channel.
  3. In the Email channel, click the Behavior tab.
  4. In the Suggested cases section, click the Switch to edit mode icon for a case type.
  5. In the Add suggested case window, click the Entities extraction tab.
  6. Add an entity to a case property mapping by clicking Add mapping.
  7. In the Entity list, click an entity.
  8. In the Case property list, click a case property that you want to map to the entity.
  9. Optional: To add another entity to case property mapping, repeat steps 6 through 8.
  10. Click Submit.
  • Previous topic Setting up text analysis for a suggested case
  • Next topic Defining suggested responses for an Email channel

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us