WikiSysop: Text replacement - "\|Platform=([^\|])GenesysEngage-onpremises([\|])" to "|Platform=$1GenesysEngage-cloud$2"

2020-07-25T02:31:59Z

Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "\|Platforms?=([^\|])PureEngage([\|])" to "|Platform=$1GenesysEngage-onpremises$2"

2020-07-15T11:46:08Z

Text replacement - "\|Platforms?=([^\|]*)PureEngage([\|]*)" to "|Platform=$1GenesysEngage-onpremises$2"

Bgrenon: Published

2020-06-08T14:37:03Z

Published

New page

{{Article
|Standalone=No
|DisplayName=Screening rules
|TocName=Screening rules
|Context=Screening rules enable you to analyze messages so that you can decide how to handle them. This page describes screening rules and provides examples for common purposes.
|ComingSoon=No
|Platform=PureEngage
|Role=Administrator
|Application=Platform Administration
|Prereq=
|Section={{Section
|sectionHeading=
|anchor=
|alignment=Vertical
|Media=
|image=
|structuredtext=Screening rules scan an interaction and try to match either a destination address (who the message is going to, whether that is identified by an email address, a cell phone number, or some other parameter), a regular expression, or both. Screening is performed by Classification Server when it is triggered by a Screen Interaction object in a {{Glossaryterm|term=Routing Strategy|text=routing strategy}}.

A screening rule can optionally be associated with a {{Glossaryterm|term=Category|text=category}}.

You can {{Link-SomewhereInThisManual|topic=manageObjs|anchor=top|display text=cut, copy, paste, and delete}} screening rules as well as other eServices Manager objects.

{{NoteFormat|Screening can operate on any interaction that has text somehow associated with it, whether as the body of the interaction (e-mail, chat), or otherwise (as user data, for example). In practice, it is expected that most interactions which are screened will be e-mail messages; therefore, the terms ''e-mail'' and ''message'' are used interchangeably here, to refer to these interactions. In fact, whatever is said here about e-mail applies to any interaction that has associated text.}}

===More information===
See the following links for more information:

*{{Link-SomewhereInThisManual|topic=SRuleUse|anchor=top|display text=How to create and test screening rules}}
*{{Link-SomewhereInThisManual|topic=SRuleRef|anchor=top|display text=Screening rules reference}}—This section includes:
**{{Link-SomewhereInThisManual|topic=SRuleRef|anchor=What_Screening_Rules_Check|display text=What screening rules check}}
**{{Link-SomewhereInThisManual|topic=SRuleRef|anchor=Functions|display text=The functions, arguments, and operators you can use}}
**{{Link-SomewhereInThisManual|topic=SRuleRef|anchor=Regular_Expressions|display text=Regular expressions}}
|structuredtextwide=
|FAQHeading=
|Status=No
}}{{Section
|sectionHeading=Examples of screening rules
|anchor=Examples
|alignment=Vertical
|Media=
|image=
|structuredtext=The following examples show screening rules you can use for typical purposes:

*[[{{FULLPAGENAME}}#CreditCardNumber|Credit card number]]
*[[{{FULLPAGENAME}}#PhoneNumber|North American phone number]]
*[[{{FULLPAGENAME}}#TelltaleWords|Telltale words]]

{{AnchorDiv|CreditCardNumber}}
===Example: Credit card number===
To find text that includes a typical credit card number, you need to match a sequence of four groups of four digits, each group separated by <tt>-</tt>(hyphen):

<tt>\d\d\d\d\-\d\d\d\d\-\d\d\d\d\-\d\d\d\d</tt>


{{NoteFormat|This regular expression also works without the <tt>\</tt> (backslash) before the hyphens. However, it is better practice to write <tt>\-</tt> for the character hyphen, because the hyphen also has a special use in range expressions like <tt>[a-z].</tt>}}
Or if you want to allow for the possibility that some people will omit the hyphens, use<tt>?</tt> to make the hyphen optional:

<tt>\d\d\d\d\-?\d\d\d\d\-?\d\d\d\d\-?\d\d\d\d</tt>

You could also use the repetition notation to shorten each <tt>\d\d\d\d</tt> to <tt>\d{4}.</tt>

{{AnchorDiv|PhoneNumber}}
===Example: North American phone number===
North American phone numbers consists of ten digits, grouped into two groups of three and one of four. There are a number of ways for the groups to be separated:

*203-555-1234
*(203) 555-1234
*(203)555-1234
*203 555-1234
*203.555.1234

The following regular expression matches all of the above:

<tt>(\d\d\d{{!}}$\d\d\d$)[\s\.\-]?\s*\d\d\d[\-\.]\d\d\d\d </tt>

====Phone Number Regular Expression====
{{{!}}
{{!}}+
{{!}}- valign="top"
! colspan="1" rowspan="1"{{!}}Symbols
! colspan="1" rowspan="1"{{!}}Meaning
! colspan="1" rowspan="1"{{!}}Remarks
{{!}}- valign="top"
{{!}} colspan="1" rowspan="1"{{!}}\d\d\d
{{!}} colspan="1" rowspan="1"{{!}}Three digits
{{!}} colspan="1" rowspan="1"{{!}}

{{!}}- valign="top"
{{!}} colspan="1" rowspan="1"{{!}}\d\d\d{{!}}$\d\d\d$
{{!}} colspan="1" rowspan="1"{{!}}Three digits, or three digits enclosed in parentheses
{{!}} colspan="1" rowspan="1"{{!}}<code> \</code> turns off the special meaning of the character <code>(</code>
{{!}}- valign="top"
{{!}} colspan="1" rowspan="1"{{!}}[\s\.\-]?
{{!}} colspan="1" rowspan="1"{{!}}Space or period or hyphen or zero
{{!}} colspan="1" rowspan="1"{{!}}Any one of the items enclosed in square brackets, either once or not at all
{{!}}- valign="top"
{{!}} colspan="1" rowspan="1"{{!}}\s*
{{!}} colspan="1" rowspan="1"{{!}}Zero or more spaces
{{!}} colspan="1" rowspan="1"{{!}}

{{!}}- valign="top"
{{!}} colspan="1" rowspan="1"{{!}}\d\d\d
{{!}} colspan="1" rowspan="1"{{!}}Three digits
{{!}} colspan="1" rowspan="1"{{!}}

{{!}}- valign="top"
{{!}} colspan="1" rowspan="1"{{!}}[\-\.]
{{!}} colspan="1" rowspan="1"{{!}}Hyphen or period
{{!}} colspan="1" rowspan="1"{{!}}Note again the need to use <code>\</code>
{{!}}- valign="top"
{{!}} colspan="1" rowspan="1"{{!}}\d\d\d\d
{{!}} colspan="1" rowspan="1"{{!}}Four digits
{{!}} colspan="1" rowspan="1"{{!}}
{{!}}}

{{AnchorDiv|TelltaleWords}}<br />
===Example: Telltale Words===
To screen for interactions from dissatisfied customers, you might try a regular expression like the following:
<code>(not\s([a-z]+\s)*(pleased {{!}} satisfied)) {{!}} unhappy {{!}} complain</code>

The first part of this expression matches <nowiki>''</nowiki>not<nowiki>''</nowiki> followed by zero or more words followed by <nowiki>''</nowiki>pleased<nowiki>''</nowiki> or <nowiki>''</nowiki>satisfied<nowiki>''</nowiki>; for example, <nowiki>''</nowiki>not<nowiki>''</nowiki> very pleased, not satisfied, not at all satisfied (but it also matches strings like <nowiki>''</nowiki>can not believe how pleased I am<nowiki>''</nowiki>). The rest matches the single words "unhappy" and "complain."
|structuredtextwide=
|FAQHeading=
|Status=No
}}
}}

@@ Line 5: / Line 5: @@
 |Context=Screening rules enable you to analyze messages so that you can decide how to handle them. This page describes screening rules and provides examples for common purposes.
 |ComingSoon=No
-|Platform=GenesysEngage-onpremises
+|Platform=GenesysEngage-cloud
 |Role=Administrator
 |Application=Platform Administration

PEC-ES/Current/Administrator/ScrRules - Revision history

WikiSysop: Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "\|Platforms?=([^\|]*)PureEngage([\|]*)" to "|Platform=$1GenesysEngage-onpremises$2"

Bgrenon: Published

WikiSysop: Text replacement - "\|Platform=([^\|])GenesysEngage-onpremises([\|])" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "\|Platforms?=([^\|])PureEngage([\|])" to "|Platform=$1GenesysEngage-onpremises$2"