PEC-OU/Current/CXContact/CompTools - Revision history

WikiSysop at 10:00, September 2, 2022

2022-09-02T10:00:54Z

Arjun.D.IX: Published

2022-01-26T05:38:47Z

Published

Mary.hachey@genesys.com: Published

2021-10-13T17:48:16Z

Published

Mary.hachey@genesys.com: Published

2021-10-06T11:48:40Z

Published

Mary.hachey@genesys.com: Published

2021-10-06T11:42:18Z

Published

Mary.hachey@genesys.com: Published

2021-07-08T13:30:26Z

Published

Mary.hachey@genesys.com: Published

2021-07-05T12:31:26Z

Published

Mary.hachey@genesys.com: Published

2021-06-30T18:54:37Z

Published

Show changes

Merav.levy@genesys.com: Published

2020-11-15T15:13:01Z

Published

Show changes

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

2020-07-25T02:31:57Z

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

@@ Line 337: / Line 337: @@
 {{!}}}
 ===Edit or Delete Custom Rules===
@@ Line 400: / Line 412: @@
 {{!}}'''Headers'''
 {{!}}Specify additional HTTP headers (one per field). Click the [[File: Add_HTTP_header_field.png]] button to add fields.
-This field is empty by default, but shows the proper Header format in a Tool Tip. For example, '''name:value''' and '''ETag: $GSW_RECORD_HANDLE'''.
+This field is empty by default, but shows the proper Header format in a Tool Tip. For example, '''name:value'''.
 {{!}}}
 {{{!}} class="wikitable"

@@ Line 400: / Line 400: @@
 {{!}}'''Headers'''
 {{!}}Specify additional HTTP headers (one per field). Click the [[File: Add_HTTP_header_field.png]] button to add fields.
-This field is empty by default, but shows the proper Header format in a Tool Tip. For example, '''name:value'''.
+This field is empty by default, but shows the proper Header format in a Tool Tip. For example, '''name:value''' and '''ETag: $GSW_RECORD_HANDLE'''.
 {{!}}}
 {{{!}} class="wikitable"

@@ Line 76: / Line 76: @@
 {{!}}Indicates the number of outbound attempts that were made today during a specific time period. The Attempt rule will only count attempts made within the defined time period. Attempts made outside this time period will not be counted by this rule.
 '''Note:''' The Start Time and End Time options are only available when Count attempts between times is turned on. The Timezone source field is not editable. It is set within the campaign group settings.
 {{!}}-
 {{!}}'''Apply Disposition Code'''
@@ Line 312: / Line 321: @@
 {{!}}'''Custom Expression'''
 {{!}}Enter a Java Script expression that evaluates the conditions for a True or False outcome. True allows the dial to occur. False does not allow the dial to occur. Note: You can refer to the user data values attached to the call using <tt>$<user data key name> </tt>.
 {{!}}}

@@ Line 310: / Line 310: @@
 {{!}}Select a Disposition Code to be applied to a call attempt, when the outcome of the call attempt is a negative rule check result. A treatment can be defined for the Disposition Code. If a Disposition Code is not selected, the "Do Not Call" call result treatment may be applied.
 {{!}}-
-{{!}}{{Editgrn_open}}<strike>'''Custom Expression'''</strike>{{Editgrn_close}}
+{{!}}'''Custom Expression'''
-{{!}}{{Editgrn_open}}<strike>Enter a Java Script expression that evaluates the conditions for a True or False outcome. True allows the dial to occur. False does not allow the dial to occur. Note: You can refer to the user data values attached to the call using <tt>$<user data key name> </tt>.</strike>{{Editgrn_close}}
+{{!}}Enter a Java Script expression that evaluates the conditions for a True or False outcome. True allows the dial to occur. False does not allow the dial to occur. Note: You can refer to the user data values attached to the call using <tt>$<user data key name> </tt>.
 {{!}}-
 {{!}}'''Apply custom condition'''

@@ Line 79: / Line 79: @@
 {{!}}'''Apply Disposition Code'''
 {{!}}Select a Disposition Code to be applied to the call attempt when the outcome is a negative rule check result. Treatment could be defined for this Disposition Code. If no Disposition Code is selected, Treatment can be applied to "Cancel Record" call result.
 {{!}}-
 {{!}}}
@@ Line 110: / Line 114: @@
 *Delete - Click the trash can icon.
 *Duplicate - Click the document icon. The '''Duplicate Attempt Rule''' dialog box opens with the settings from the original rule populated. You can change any or all of them. If you do not change the name of the Attempt rule, it will inherit the name of the original Attempt rule, with _duplicate1 appended to it.
 |Status=No
 }}{{Section
@@ Line 243: / Line 306: @@
 {{!}}'''Description'''
 {{!}}Enter an explanation of the purpose of the custom rule.
 {{!}}-
 {{!}}'''Apply Disposition Code'''
 {{!}}Select a Disposition Code to be applied to a call attempt, when the outcome of the call attempt is a negative rule check result. A treatment can be defined for the Disposition Code. If a Disposition Code is not selected, the "Do Not Call" call result treatment may be applied.
 {{!}}-
 {{!}}}
@@ Line 323: / Line 395: @@
 {{!}}Specify the URI for the optional proxy server. This field is empty by default, but shows the proper URI format in a Tool Tip. For example, <code><nowiki>http://proxy.domain</nowiki></code>.
 {{NoteFormat|CX Contact supports only HTTP proxy server.|2}}
 {{!}}-
 {{!}}'''Headers'''
@@ Line 332: / Line 407: @@
 {{!}} nowrap=""{{!}}'''How to enable:'''
 {{!}}On the Compliance Tools tab, click '''External Pre-Dial Validation Rules''' and then, select '''New'''.
-Populate the '''General''' and '''Advanced''' tabs as described in the table above, clicking '''Save''' when completed. The new rule will appear on the External Pre-Dial Validation Rules page.[[File: Ext_PD_Validation.png]]
+Populate the '''General''' and '''Advanced''' tabs as described in the table above, clicking '''Save''' when completed. The new rule will appear on the External Pre-Dial Validation Rules page.[[File: Ext PD Validation.png]]
 {{!}}}

@@ Line 226: / Line 226: @@
 |alignment=Vertical
 |structuredtext=Use the '''New Custom Rule''' option to create a rule that will allow or deny outbound dialing according to a user-defined Java Script expression evaluated for each outbound call immediately before dialing occurs. A custom rule enables you to implement customized business rule logic.
 Custom rules have the following attributes:

@@ Line 283: / Line 283: @@
 |anchor=ExternalPDValid
 |alignment=Vertical
-|structuredtext=External Pre-Dial Validation is an optional custom step that you can use to expand (or replace, depending on the configuration) Compliance Manager's standard pre-dial validation with an HTTP or HTTPS request to an external Web/Application Server. The server must be capable of processing HTTP requests with JSON bodies and respond with 200 OK (Dial) to 409 Cancel (No Dial) requests, based on it's business logic. CX Contact supports both HTTP and HTTPS protocols together with the ability to configure the HTTP Method (POST, PUT, GET), optional HTTP Proxy, and one or more custom HTTP headers.
+|structuredtext=External Pre-Dial Validation is an optional custom step that you can use to expand (or replace, depending on the configuration) Compliance Manager's standard pre-dial validation with an HTTP or HTTPS request to an external Web/Application Server. The server must be capable of processing HTTP requests with JSON bodies and respond with 200 OK (Dial) to 409 Cancel (No Dial) responses, based on it's business logic. CX Contact supports both HTTP and HTTPS protocols together with the ability to configure the HTTP Method (POST, PUT, GET), optional HTTP Proxy, and one or more optional custom HTTP headers. CX Contact passes all properties of the record being validated in the JSON body of the external pre-dial validation request.
-External Pre-Dial Validation is a type of Compliance Rule to which you can apply standard approaches (such as, CRUD control, serialization, audit tracking, RBAC, and PBAC) to Compliance Rules objects. If necessary, you can also configure multiple rules for External Pre-Dial Validation and optionally associate them with Campaign Groups. Since Compliance Rules for External Pre-Dial Validation are optional, each rule must be explicitly associated with a Dialing Profile, Campaign Template, or Campaign Group to take effect.
+External Pre-Dial Validation is a type of Compliance Rule for which you can configure multiple rules and optionally associate them with Campaign Groups. Since Compliance Rules for External Pre-Dial Validation are optional, each rule must be explicitly associated with a Dialing Profile, Campaign Template, or Campaign Group to take effect.
 {{NoteFormat|There's no limit to the number of external pre-dial validation rules you can create for a Tenant.|2}}
@@ Line 303: / Line 303: @@
 The default setting is '''After'''.
 {{!}}-
 {{!}}'''URI'''
@@ Line 315: / Line 317: @@
 {{!}}-
 {{!}}'''Method'''
-{{!}}Select one of the following the HTTP methods:
+{{!}}Select one of the following HTTP methods:
 *'''POST'''
@@ Line 324: / Line 326: @@
 {{!}}-
 {{!}}'''Proxy'''
-{{!}}Specify the URI for the proxy server. This field is empty by default, but shows the proper URI format in a Tool Tip. For example, <code><nowiki>http://proxy.domain</nowiki></code>.
+{{!}}Specify the URI for the optional proxy server. This field is empty by default, but shows the proper URI format in a Tool Tip. For example, <code><nowiki>http://proxy.domain</nowiki></code>.
 {{NoteFormat|CX Contact supports only HTTP proxy server.|2}}
 {{!}}-
 {{!}}'''Headers'''
-{{!}}Specify the HTTP headers (one per field). Click the [[File: Add_HTTP_header_field.png]] button to add fields.
+{{!}}Specify additional HTTP headers (one per field). Click the [[File: Add_HTTP_header_field.png]] button to add fields.
 This field is empty by default, but shows the proper Header format in a Tool Tip. For example, '''name:value'''.
 {{!}}}

@@ Line 12: / Line 12: @@
 *{{Link-SomewhereInThisManual|topic=CompTools|anchor=ContactDates|display text=Contact Dates}}
 |ComingSoon=No
-|Platform=GenesysEngage-onpremises
+|Platform=GenesysEngage-cloud
 |Prereq=
 |Section={{Section

PEC-OU/Current/CXContact/CompTools - Revision history

WikiSysop at 10:00, September 2, 2022

Arjun.D.IX: Published

Mary.hachey@genesys.com: Published

Mary.hachey@genesys.com: Published

Mary.hachey@genesys.com: Published

Mary.hachey@genesys.com: Published

Mary.hachey@genesys.com: Published

Mary.hachey@genesys.com: Published

Merav.levy@genesys.com: Published

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

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