Service Email form –
Completing the Request tab

Use the Request tab to map the data from the messages processed by this service to the clipboard.

Message Header

Use the fields in this section to map data from the header of the message.

• Field name - Select To, CC, From, Subject, Date, or Thread-Topic. The Thread-Topic message header of a message that originated from Pega Platform flow processing contains the work item ID and correspondence ID in addition to the original subject text.
• Description - (Optional) Enter a text description of this mapping.
• Map to - Specify the destination or the type of destination for the value in Pega Platform:
  • Clipboard – Map to the page name or property on the clipboard specified by the Map To Key field.
  • XML ParseRule –The incoming data is a stream of XML that must be parsed using the actions defined in a parse XML rule.
  • Delimited ParseRule – The incoming data is in a delimited format that must be processed by a delimited parse rule (an instance of Rule-Parse-Delimited).
  • Structured Parserule – The incoming data has a fixed format with fixed length fields and must be processed by a structured parse rule.
  • HTML PostData – The incoming data value from the sending application is a stream of data from an HTML form that contains property key/value pairs.
    
    If additional choices appear, they identify a custom function rule in a MapTo library. Review the function rule to determine what it does.
• Map to key - Specify the key to locating the property or the rule in the destination specified in the Map To field:
• If the Map To value is Clipboard, enter the property name to which the data is mapped at runtime. Standard properties that you can use are available. See More about Service Email Rules.
• If the Map To value is XML Parse Rule, enter the Namespace name (second key part) and the Element Name name — third key part — of the appropriate Parse XML rule. Separate the Namespace from the Element Name with a space using the syntax "Namespace ElementName" and not "Namespace.ElementName." The system uses the page class of this service rule as the first key part of the parse rule.
• If the Map To value is Delimited ParseRule, enter the Namespace and Record Type names (second and third key parts) of the appropriate delimited parse rule. The system uses the Applies To class of this service rule as the first key part of the parse rule.
• If the Map To value is Structured ParseRule, enter the Record Type (third key part) of a structured parse rule. The system uses the Applies To class of this service rule as the first key to the parse rule.
• If the Map To value is a Rule-Utility-Function from a MapTo library, select or enter the property that holds the results of the custom function at runtime.
• If the Map To value is HTML PostData, leave this field blank. The name/value pairs in the string will be mapped to the parameter page of the service activity rather than the primary page.

Delivery Status Notification (DSN) Data

If the service rule manages delivery failure messages for email correspondence that originated from Pega Platform’s flow processing (outbound email), use the fields in this section to map DSN data.

Note: The email listener for this service must have the Process Delivery Status Notifications option selected or it does not route DSN messages to the service.

• Field name - Select one of the following DSN fields:
  • Reporting-MTA - identifies the server that sent the message
  • Action — the action performed by the Reporting-MTA in its attempt to deliver the message to the recipient address. For example: success, failed, delayed.
  • Status — specifies the DSN status code that indicates the delivery status of the message.
  • Original-text-plain — contains the original email plain text, if available
  • Original-text-html — if the original text used HTML formatting, contains the HTML of the original email message
  • Original-to — specifies the intended recipient of the original message
  • Original-from — specifies the email address set in the From field of the original message
  • Original-subject — specifies the text from the subject of the original message
  • Original-sentdate — specifies the date the message was first sent
• Description - Optional. Enter a text description of this mapping.
• Map to - Specify the destination or the type of destination for the value in PRPC:
  • Clipboard – Map to the page name or property on the clipboard specified by the Map To Key field.
  • XML ParseRule –The incoming data is a stream of XML that must be parsed using the actions defined in a parse XML rule.
  • Delimited ParseRule – The incoming data is in a delimited format that must be processed by a delimited parse rule (an instance of Rule-Parse-Delimited).
  • Structured Parserule – The incoming data has a fixed format with fixed length fields and must be processed by a structured parse rule.
  • HTML PostData – The incoming data value from the sending application is a stream of data from an HTML form that contains property key/value pairs.
    
    If additional choices appear, they identify a custom function rule in a MapTo library. Review the function rule to determine what it does.
• Map to key - Specify the key to locating the property or the rule in the destination specified in the Map To field:
  • If the Map To value is Clipboard, enter the property name to which the data is mapped at runtime. You can use standard properties here. See More about Service Email Rules .
  • If the Map To value is XML Parse Rule, enter the Namespace name (second key part) and the Element Name name — third key part — of the appropriate Parse XML rule. Separate the Namespace from the Element Name with a space using the syntax "Namespace ElementName" and not "Namespace.ElementName." The system uses the page class of this service rule as the first key part of the parse rule.
  • If the Map To value is Delimited ParseRule, enter the Namespace and Record Type names (second and third key parts) of the appropriate delimited parse rule. The system uses the Applies To class of this service rule as the first key part of the parse rule.
  • If the Map To value is Structured ParseRule, enter the Record Type (third key part) of a structured parse rule. The system uses the Applies To class of this service rule as the first key to the parse rule.
  • If the Map To value is a Rule-Utility-Function from a MapTo library, select or enter the property that holds the results of the custom function at runtime.
  • If the Map To value is HTML PostData, leave this field blank. The name/value pairs in the string will be mapped to the parameter page of the service activity rather than the primary page.

Message Data

Use the fields in this section to map the body of the message.

• Description - Optional. Enter a description of the data being mapped.
• Map to - Specify the destination or the type of destination for the value in PRPC:
• Clipboard – Map to the page name or property on the clipboard specified by the Map To Key field.
• XML ParseRule –The incoming data is a stream of XML that must be parsed using the actions defined in a parse XML rule.
• Delimited ParseRule – The incoming data is in a delimited format that must be processed by a delimited parse rule (an instance of Rule-Parse-Delimited).
• Structured Parserule – The incoming data has a fixed format with fixed length fields and must be processed by a structured parse rule.
• HTML PostData –The incoming data value from the sending application is a stream of data from an HTML form that contains property key/value pairs.
  
  If additional choices appear, they identify a custom function rule in a MapTo library. Review the function rule to determine what it does.
• Map to Key - Specify the key to locating the property or the rule in the destination specified in the Map To field:
• If the Map To value is Clipboard, enter the property name to which the data is mapped at runtime. Standard properties are available for your use. See More about Service Email Rules.
• If the Map To value is XML Parse Rule, enter the Namespace name (second key part) and the Element Name name — third key part — of the appropriate Parse XML rule. Separate the Namespace from the Element Name with a space using the syntax "Namespace ElementName" and not "Namespace.ElementName." The system uses the page class of this service rule as the first key part of the parse rule.
• If the Map To value is Delimited ParseRule, enter the Namespace and Record Type names (second and third key parts) of the appropriate delimited parse rule. The system uses the Applies To class of this service rule as the first key part of the parse rule.
• If the Map To value is Structured ParseRule, enter the Record Type (third key part) of a structured parse rule. The system uses the Applies To class of this service rule as the first key to the parse rule.
• If the Map To value is a Rule-Utility-Function from a MapTo library, select or enter the property that holds the results of the custom function at runtime.
• If the Map To value is HTML PostData, leave this field blank. The name/value pairs in the string will be mapped to the parameter page of the service activity rather than the primary page.
• Handle HTML content - Select one of the following to specify how email messages with HTML formatting are treated:
• As HTML attachment - HTML content in email is contained in the attachment page as an HTML file. The text body of the email is used for mapping.
• Inline - prefer text – If any text body exists, it is used for mapping and any HTML is discarded. If no text body is available, the HTML content is used for mapping.
• Inline - prefer HTML – If any HTML body exists, it is used for mapping and any text body is discarded.
  
  Note: This feature works with email listener inline image embedding, which is designed for HTML message data. In that case, this setting have either the As HTML attachment or Inline - prefer HTML option selected.

About Service Email rules

Open topic with navigation