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

2020-07-25T02:33:00Z

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

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

2020-07-15T11:44:43Z

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

Bgrenon: Published

2020-06-08T14:35:47Z

Published

New page

{{Article
|Standalone=No
|DisplayName=Field Codes
|TocName=Field Codes
|Context=Create a wide range of field code types, which you can use to customize the standard response sent to a particular customer.
|ComingSoon=No
|Platform=PureEngage
|Role=Administrator
|Application=Platform Administration
|Prereq=
|Section={{Section
|sectionHeading=
|anchor=
|alignment=Vertical
|Media=
|image=
|structuredtext=Although Field Codes are used mostly in standard responses, they are the most complex and powerful aspect of standard responses, so they are described in this separate section.

eServices Manager enables you to create a wide range of Field Codes types, from simple Field Codes that function similarly to a Mail Merge-type word processor feature to complex Field Codes that include multiple objects, formulas, and constants (see {{Link-SomewhereInThisManual|topic=FCexmpls|anchor=Using_a_Complex_Field_Code|display text=Using a Complex Field Code}} for an example).

Once you create a Field Code, you can use it in multiple standard responses.

The interface for creating Field Codes is simple; creating really useful Field Codes requires a deeper understanding of how Field Codes can be constructed. {{Link-SomewhereInThisManual|topic=FCinKM|anchor=top|display text=How to Create and Insert Field Codes}} provides step-by-step instructions, with links to detailed reference information at the relevant places.

The reference information consists of the following topics:

*{{Link-SomewhereInThisManual|topic=variables|anchor=top|display text=Field Code Variables}}
*{{Link-SomewhereInThisManual|topic=FCanatomy|anchor=top|display text=Using Formulas in Field Codes}}
*{{Link-SomewhereInThisManual|topic=FCexmpls|anchor=top|display text=Field Code Examples}}

{{NoteFormat|You can {{Link-AnywhereElse|product=PEC-ES|version=Current|manual=Administrator|topic=manageObjs|display text=cut, copy, paste, and delete}} Field Codes as well as other eServices Manager objects.|2}}
|structuredtextwide=
|FAQHeading=
|Status=No
}}{{Section
|sectionHeading=Field Codes Overview
|anchor=Overview
|alignment=Vertical
|Media=
|image=
|structuredtext=The main use of field codes is to particularize standard responses.

For example, you can use the field code <tt><$Contact.FirstName$></tt> in a response beginning <tt>Dear <$Contact.FirstName$>,</tt> which you send to dozens of recipients. In each message, <tt><$Contact.FirstName$></tt> is replaced by the first name of the addressee of the message (the contact) as listed in the Universal Contact Server database.

More generally, a "field code" is a formula that you insert into an outgoing text object, such as an e-mail that E-mail Server generates when triggered to do so by a routing strategy object.

The most common type of such text object is a standard response (triggered by an Autoresponse or Acknowledgement object), but you can also insert field codes into other types, such as chat transcripts, SMS messages, and forwarded or redirected e-mails. In some cases, the only place you can insert a field code is in the Subject line using the '''Format''' tab in a strategy object.

The following is a complete list of the strategy objects that can use field codes either in a standard response or in the Subject line:

*Acknowledgement
*Autoresponse
*ChatTranscript
*Create EmailOut
*Create Notification
*Create SMS
*Forward
*RenderMessageContent

The following is a complete list of the strategy objects that can use field codes only in the Subject line:

*Redirect
*Reply from External Resource
*Send

When a text object containing such a formula is processed, the following happens:

#The formula performs an operation, which produces a result.
#The result replaces the field code in the text object.

This process of performing an operation and substituting its result is called "rendering."


{{NoteFormat|Field codes can be used in outgoing text objects only.}}

A complete reference list of field codes is available in the [https://docs.genesys.com/Documentation:ES:FldCod:welcome:latest Genesys eServices Field Codes Reference Manual].
|structuredtextwide=
|FAQHeading=
|Status=No
}}
}}

@@ Line 5: / Line 5: @@
 |Context=Create a wide range of field code types, which you can use to customize the standard response sent to a particular customer.
 |ComingSoon=No
-|Platform=GenesysEngage-onpremises
+|Platform=GenesysEngage-cloud
 |Role=Administrator
 |Application=Platform Administration

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