BEmail Content Continue - Revision history

Philip Lacey at 16:27, 8 February 2018

2018-02-08T16:27:36Z

Philip Lacey: /* Advanced Settings */

2018-02-08T16:25:20Z

‎Advanced Settings

Philip Lacey: /* Overview */

2018-02-08T16:25:01Z

‎Overview

Philip Lacey: /* Overview */

2018-02-08T16:18:15Z

‎Overview

Philip Lacey: /* Setup */

2018-02-08T16:10:45Z

‎Setup

Philip Lacey: /* Overview */

2018-02-08T16:08:40Z

‎Overview

Philip Lacey: /* Setup */

2018-02-08T16:06:55Z

‎Setup

Philip Lacey: Created page with "= Overview = This engine allows an email that is received to continue a conversation or string of emails in and out of the system through a BEmail set up form. = Setup =..."

2018-02-08T15:49:50Z

Created page with "= Overview = This engine allows an email that is received to continue a conversation or string of emails in and out of the system through a BEmail set up form. = Setup =..."

New page

= Overview =

This engine allows an email that is received to continue a conversation or string of emails in and out of the system through a BEmail set up form.

= Setup =

"Use Content Rules?" must be turned on.

"Content Continue - Field to match on" provides the field to look at to match for the code. Usually the Id field is enough. The field must only contain numbers regardless.

"Content Continue - Match pattern" is the pattern to look for. The setup will be along the lines of ###--ID--#

@@ Line 9: / Line 9: @@
 The result of this process is that body of the email of the latest email in the chain replaces the CDA fields with the latest email.  All of the original emails are placed into the Contact History of the record, including the current received email.
 = Setup =
@@ Line 33: / Line 35: @@
 Put the subject of the External email as "Reply from Helpdesk Reference : ###--ID--#"

@@ Line 22: / Line 22: @@
-"Content Continue - Match pattern" is the pattern to look for.  The setup will be along the lines of
+"Content Continue - Match pattern" is the pattern to look for in the Subject of the emails.  The setup will be along the lines of
   ###--ID--#
 The pattern needs --ID-- in it somewhere to locate the reference code.
 == Outcome ==

← Older revision		Revision as of 16:25, 8 February 2018
Line 5:		Line 5:


−	Imagine you set the form up as a Case Management form. It is a help desk system. If an email comes in from a customer it's a new query. You reply to the customer using an outcome that sends an email. In that email is the reference code to this record. When the customer replies to the email again, bxp can identify the original email from finding the code in the ~~content~~ and link the returning email back to the original send.	+	Imagine you set the form up as a Case Management form. It is a help desk system. If an email comes in from a customer it's a new query. You reply to the customer using an outcome that sends an email. In that email is the reference code to this record. When the customer replies to the email again, bxp can identify the original email from finding the code in the Subject and link the returning email back to the original send.

← Older revision		Revision as of 16:18, 8 February 2018
Line 6:		Line 6:

	Imagine you set the form up as a Case Management form. It is a help desk system. If an email comes in from a customer it's a new query. You reply to the customer using an outcome that sends an email. In that email is the reference code to this record. When the customer replies to the email again, bxp can identify the original email from finding the code in the content and link the returning email back to the original send.		Imagine you set the form up as a Case Management form. It is a help desk system. If an email comes in from a customer it's a new query. You reply to the customer using an outcome that sends an email. In that email is the reference code to this record. When the customer replies to the email again, bxp can identify the original email from finding the code in the content and link the returning email back to the original send.
		+
		+
		+	The result of this process is that body of the email of the latest email in the chain replaces the CDA fields with the latest email. All of the original emails are placed into the Contact History of the record, including the current received email.

	= Setup =		= Setup =

@@ Line 8: / Line 8: @@
 = Setup =
@@ Line 19: / Line 22: @@
   ###--ID--#
 The pattern needs --ID-- in it somewhere to locate the reference code.

← Older revision		Revision as of 16:08, 8 February 2018
Line 5:		Line 5:


		+	Imagine you set the form up as a Case Management form. It is a help desk system. If an email comes in from a customer it's a new query. You reply to the customer using an outcome that sends an email. In that email is the reference code to this record. When the customer replies to the email again, bxp can identify the original email from finding the code in the content and link the returning email back to the original send.

	= Setup =		= Setup =

@@ Line 9: / Line 9: @@
-"Use Content Rules?" must be turned on.
+"Content Continue?" must be turned on.
-"Content Continue - Field to match on" provides the field to look at to match for the code.  Usually the Id field is enough.  The field must only contain numbers regardless.
+"Content Continue - Field to match on" provides the field to look at to match for the code.  Usually the Id field is enough but if you're creating custom reference codes, the engine also accepts any form field.
-"Content Continue - Match pattern" is the pattern to look for.  The setup will be along the lines of ###--ID--#
+"Content Continue - Match pattern" is the pattern to look for.  The setup will be along the lines of