Parse Content

Before we parse the content from an email, we need to understand the different parsing types from an email and define keys in order to map the condition to the defined keys.

To learn more about parsing, refer to the following topics:

• Parse Type
• User Defined Keys

Parse Type

Firstly let's understand the parsing types, the Summit tool offers two ways of parsing content from an email. Once in line form which uses a line delimiter to differentiate the lines in the email body and set the parse condition as required.  The other is called free from which has no strict rules on the content in the email subject or body the Application Designer can set the rules of content extraction for parsing in the unstructured format too.

The following graphical representation explains the difference between the line and the free form of parsing.
Figure: Parse Types

User Defined Keys

Once the parse type is defined in the application you will have to define the user key. Let's learn more about what these User Defined Keys are in the following section:

When setting parse conditions from emails pertaining to service management, user-defined keys are used to extract specific information or trigger actions based on the content of the email. These keys are typically keywords, phrases, or patterns that help identify and classify the email's content. Here are some examples of user-defined keys for parsing emails related to service management:

Figure: User-Defined Keys

These user-defined keys help automate the process of triaging, categorizing, and managing service-related emails efficiently within a service management system. They enable organizations to extract valuable information from emails, trigger appropriate actions, and provide timely responses to service requests.

 To configure content parsing, click on the following links:

Define Keys	Define Conditions