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

2020-07-25T02:33:52Z

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

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

2020-07-15T11:47:00Z

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

Bgrenon: Published

2020-06-08T14:36:55Z

Published

New page

{{Article
|Standalone=No
|DisplayName=Field Code Examples
|TocName=Field Code Examples
|Context=View examples of the use of field codes.
|ComingSoon=No
|Platform=PureEngage
|Role=Administrator
|Application=Platform Administration
|Section={{Section
|sectionHeading=Using a custom variable
|anchor=CustomVariable
|alignment=Vertical
|structuredtext='''Purpose:''' This is a simple example of the use of a custom variable in a standard response.

'''Prerequisites'''<br />
This example assumes a category tree that includes categories called <tt>Cookbooks, Mysteries,</tt> and <tt>Reference.</tt>

'''Steps'''<br />

#In eServices Manager:
##Create a custom variable called QueryTopic (see See Creating field codes).
##Create a field code called <tt>Query_Topic</tt> that consists of the variable <tt>QueryTopic.</tt>
##Create a standard response of type <tt>Autoresponse</tt> called <tt>AUTO</tt> that includes the sentence <tt>Thank you for your inquiry about <$ Query_Topic $>.</tt>
##Create the following screening rules:
##*<tt>Cookbook: RegExFind("cook") {{!}} {{!}} RegExFind("recipe") {{!}} {{!}} RegExFind("food") {{!}} {{!}} RegExFind("cuisine")</tt>
##*<tt>Mystery: RegExFind("murder") {{!}} {{!}} RegExFind("crime") {{!}} {{!}} RegExFind("case of the") {{!}} {{!}} RegExFind("detective")</tt>
##*<tt>Reference: RegExFind("dictionar") {{!}} {{!}} RegExFind("encyclopedia") {{!}} {{!}} RegExFind("almanac")</tt>
#In Interaction Routing Designer, create a strategy that applies these screening rules one after the other, assigning a different value to the custom variable for each screening rule:
##Create a variable called var_screen.
##Create a strategy. Start the strategy with a <tt>Screen</tt> object. On the <tt>General</tt> tab of the <tt>Screen</tt> object, select the <tt>Cookbook</tt> rule.
##On the <tt>Result</tt> tab, click <tt>Assign values of the key-value pairs.</tt> Then under <tt>Output values</tt> select <tt>var_screen</tt> for <tt>Variable</tt> and enter <tt>ScreenRuleMatch</tt> for <tt>Key from output.</tt>
##Connect the <tt>Screen</tt> object to a <tt>Generic Segmentation</tt> object. Create two segments: <tt>var_screen = true</tt> and <tt>var_screen = false.</tt>
##Connect an <tt>Autoresponse</tt> object to the top green port (the one corresponding to <tt>true</tt>) of the Segmentation object. In the Autoresponse, select the <tt>Select standard response</tt> radio button and select <tt>AUTO</tt> in the associated drop-down list.<br />
##Still in this <tt>Autoresponse,</tt> go to the <tt>General</tt> tab and in the <tt>Field Codes</tt> area (bottom of the tab) click the <tt>New</tt> icon, enter <tt>QueryTopic</tt> under <tt>Key,</tt> and enter <tt>cookbooks</tt> under <tt>Value.</tt>
##:This will generate an e-mail that includes the sentence ''Thank you for your inquiry about cookbooks.''
##Return to the <tt>Generic Segmentation</tt> and connect a new <tt>Screen</tt> object to its second green port (the one corresponding to <tt>false</tt>).
##On the <tt>General</tt> tab of the new <tt>Screen</tt> object, select the <tt>Mystery</tt> rule. On the <tt>Result</tt> tab, click <tt>Assign values of the key-value pairs.</tt> Then under <tt>Output values</tt> select <tt>var_screen</tt> for <tt>Variable</tt> and enter <tt>ScreenRuleMatch</tt> for <tt>Key from output</tt>.
##Proceed as in Steps 4–6: Connect this <tt>Screen</tt> object to a new <tt>Generic Segmentation,</tt> again with segments for <tt>var_screen = true</tt> and <tt>var_screen = false.</tt>
##As in Step 5, connect a new <tt>Autoresponse</tt> object to the green port for <tt>true,</tt> select the <tt>AUTO</tt> standard response, and enter <tt>QueryTopic</tt> under <tt>Key.</tt> This time enter <tt>mysteries</tt> under <tt>Value.</tt>
##Return to the second <tt>Generic Segmentation’s</tt> green port for <tt>false</tt> and repeat Steps 7–10, creating a third <tt>Screen</tt> object and <tt>Generic Segmentation.</tt> In the <tt>Screen</tt> object, select the <tt>Reference</tt> rule; in the <tt>Segmentation</tt> object, set the custom variable to <tt>reference</tt>
#:The figure "Strategy Using Custom Variable" shows the strategy as described. The single standard response <tt>AUTO</tt> generates three e-mails, each with a different word filling the blank in ''Thank you for your inquiry about ___.''

[[File:mm_us-25.png|center|Strategy Using Custom Variable]]
|Status=No
}}{{Section
|sectionHeading=Using a Complex Field Code
|anchor=ComplexFieldCode
|alignment=Vertical
|structuredtext=The following is an example of a complex field code:

<tt><$ If (Time() - Interaction.DateCreated > 14, “Please accept our apologies for not having replied sooner. ”, “”) $></tt>

This field code inserts a tardiness apology if more than 14 days have elapsed since the interaction first entered the system. It uses the function <tt>If,</tt> which has these properties:

*Its syntax is <tt>If (Boolean, TrueResult, FalseResult)</tt>
*If <tt>Boolean</tt> evaluates to <tt>True,</tt> it returns the second argument.
*If <tt>Boolean</tt> evaluates to <tt>False,</tt> it returns the third argument.

In this example, the three arguments of <tt>If</tt> are as follows:

#<tt>Time() - Interaction.DateCreated > 14</tt>
#:A formula that returns <tt>True</tt> if the difference between the date created and the current system time is more than 14 days. (The result of a mathematical operation on dates is given in days.)
#<tt>“Please accept our apologies for not having replied sooner. ”</tt>
#:A text string apologizing for tardiness, inserted if the formula evaluates to <tt>True.</tt>
#The null string: if the reply is not late (the formula evaluates to <tt>False</tt>), nothing is inserted in it.
|Status=No
}}{{Section
|sectionHeading=Next steps
|anchor=NextSteps
|alignment=Vertical
|structuredtext=Go on to create and manage {{Link-SomewhereInThisManual|topic=ScrRules|anchor=top|display text=Screening Rules}}.
|Status=No
}}
}}

@@ Line 5: / Line 5: @@
 |Context=View examples of the use of field codes.
 |ComingSoon=No
-|Platform=GenesysEngage-onpremises
+|Platform=GenesysEngage-cloud
 |Role=Administrator
 |Application=Platform Administration

PEC-ES/Current/Administrator/FCexmpls - 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"