PE-GPR/9.0.0/Deployment/DL-CfgFile - Revision history

WikiSysop at 12:45, March 31, 2022

2022-03-31T12:45:39Z

Lakshmi.krishnamurthy@genesys.com: Published

2021-04-26T04:31:39Z

Published

Vivian.hood@genesys.com: Published

2021-03-23T13:01:49Z

Published

Vivian.hood@genesys.com: Published

2021-01-22T14:49:26Z

Published

Vivian.hood@genesys.com: Published

2020-11-25T15:49:01Z

Published

Vivian.hood@genesys.com: Published

2020-11-06T20:38:26Z

Published

Show changes

Vivian: Published

2020-09-22T17:05:17Z

Published

Show changes

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

2020-07-25T02:31:03Z

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

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

2020-07-15T11:45:49Z

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

Vivian: Published

2020-04-17T18:54:44Z

Published

@@ Line 66: / Line 66: @@
 *'''dataset-&lt;<em>name</em>&gt;''' - When you create this configuration section, replace &lt;<em>name</em>&gt; with a dataset name of your choice. For example, you can create a section called '''dataset-interactions'''.
 **{{Optionslink|link=Options:DataLoader:dataset-zname-:chunk-size}} - Defines how many interactions you want Data Loader to upload at once by specifying a period of time. Data Loader uploads all interactions that occur during this amount of time in a single batch.
 **{{Optionslink|link=Options:DataLoader:dataset-zname-:upload-schedule}} (in release 9.0.018.00 and higher) or {{Optionslink|link=Options:DataLoader:dataset-zname-:update-period}} - Specifies how often Data Loader runs an upload process to get new and updated data.

@@ Line 135: / Line 135: @@
 **{{Optionslink|link=Options:DataLoader:dataset-zname-:csv-separator}} - Tells Data Loader what separator type you are using so it can correctly parse the .csv file.
 **{{Optionslink|link=Options:DataLoader:dataset-zname-:data-type}} - The value for this option must be <tt>outcomes</tt>.
-**{{Optionslink|link=Options:DataLoader:dataset-zname-:location}} - Enter the Data Loader Docker container path to the .csv file containing your Customer Profile data. This path is related to the path inside the Docker container.
+**{{Optionslink|link=Options:DataLoader:dataset-zname-:location}} - Enter the Data Loader Docker container path to the .csv file containing your Agent Profile data.
 **{{Optionslink|link=Options:DataLoader:dataset-zname-:upload-dataset}} - This option is set to <tt>true</tt> by default, which tells Data Loader to start uploading data at the interval specified in the {{Optionslink|link=Options:DataLoader:dataset-zname-:update-period}} option. To pause uploading, set this option to <tt>false.</tt>
 *'''schema-agents-&lt;''name''&gt;''' - Shows how to configure the schema for an agent Dataset to be uploaded from a .csv file. It has only one mandatory field, but you must also configure options specifying the data types for all other fields. Add the <tt>anon</tt> parameter if the field must be anonymized.
@@ Line 146: / Line 146: @@
 **{{Optionslink|link=Options:DataLoader:dataset-zname-:csv-separator}} - Tells Data Loader what separator type you are using so it can correctly parse the .csv file.
 **{{Optionslink|link=Options:DataLoader:dataset-zname-:data-type}} - The value for this option must be <tt>outcomes</tt>.
-**{{Optionslink|link=Options:DataLoader:dataset-zname-:location}} - Enter the Data Loader Docker container path to the .csv file containing your Customer Profile data. This path is related to the path inside the Docker container.
+**{{Optionslink|link=Options:DataLoader:dataset-zname-:location}} - Enter the Data Loader Docker container path to the .csv file containing your Feedback data.
 **{{Optionslink|link=Options:DataLoader:dataset-zname-:upload-dataset}} - This option is set to <tt>true</tt> by default, which tells Data Loader to start uploading data at the interval specified in the {{Optionslink|link=Options:DataLoader:dataset-zname-:update-period}} option. To pause uploading, set this option to <tt>false.</tt>

@@ Line 56: / Line 56: @@
 **{{Optionslink|link=Options:DataLoader:dataset-zname-:csv-separator}} - Tells Data Loader what separator type you are using so it can correctly parse the .csv file.
 **{{Optionslink|link=Options:DataLoader:dataset-zname-:data-type}} - The value for this option must be <tt>customers</tt>.
-**{{Optionslink|link=Options:DataLoader:dataset-zname-:location}} - Enter the complete path to the .csv file containing your Customer Profile data.
+**{{Optionslink|link=Options:DataLoader:dataset-zname-:location}} - Enter the Data Loader Docker container path to the .csv file containing your Customer Profile data.
 **{{Optionslink|link=Options:DataLoader:dataset-zname-:upload-dataset}} - This option is set to <tt>true</tt> by default, which tells Data Loader to start uploading data at the interval specified in the {{Optionslink|link=Options:DataLoader:dataset-zname-:upload-schedule}} (in release 9.0.018.00 and higher) or {{Optionslink|link=Options:DataLoader:dataset-zname-:update-period}} option. To pause uploading, set this option to <tt>false.</tt>
@@ Line 135: / Line 135: @@
 **{{Optionslink|link=Options:DataLoader:dataset-zname-:csv-separator}} - Tells Data Loader what separator type you are using so it can correctly parse the .csv file.
 **{{Optionslink|link=Options:DataLoader:dataset-zname-:data-type}} - The value for this option must be <tt>outcomes</tt>.
-**{{Optionslink|link=Options:DataLoader:dataset-zname-:location}} - Enter the complete path to the .csv file containing your agent data.
+**{{Optionslink|link=Options:DataLoader:dataset-zname-:location}} - Enter the Data Loader Docker container path to the .csv file containing your Customer Profile data. This path is related to the path inside the Docker container.
 **{{Optionslink|link=Options:DataLoader:dataset-zname-:upload-dataset}} - This option is set to <tt>true</tt> by default, which tells Data Loader to start uploading data at the interval specified in the {{Optionslink|link=Options:DataLoader:dataset-zname-:update-period}} option. To pause uploading, set this option to <tt>false.</tt>
 *'''schema-agents-&lt;''name''&gt;''' - Shows how to configure the schema for an agent Dataset to be uploaded from a .csv file. It has only one mandatory field, but you must also configure options specifying the data types for all other fields. Add the <tt>anon</tt> parameter if the field must be anonymized.
@@ Line 146: / Line 146: @@
 **{{Optionslink|link=Options:DataLoader:dataset-zname-:csv-separator}} - Tells Data Loader what separator type you are using so it can correctly parse the .csv file.
 **{{Optionslink|link=Options:DataLoader:dataset-zname-:data-type}} - The value for this option must be <tt>outcomes</tt>.
-**{{Optionslink|link=Options:DataLoader:dataset-zname-:location}} - Enter the complete path to the .csv file containing your feedback data.
+**{{Optionslink|link=Options:DataLoader:dataset-zname-:location}} - Enter the Data Loader Docker container path to the .csv file containing your Customer Profile data. This path is related to the path inside the Docker container.
 **{{Optionslink|link=Options:DataLoader:dataset-zname-:upload-dataset}} - This option is set to <tt>true</tt> by default, which tells Data Loader to start uploading data at the interval specified in the {{Optionslink|link=Options:DataLoader:dataset-zname-:update-period}} option. To pause uploading, set this option to <tt>false.</tt>

@@ Line 45: / Line 45: @@
 *'''schema-agents-gim''' - In this section, create one option for each column in your Agent Profile dataset. You must include the columns/options listed below. If you modified your SQL query to read values from additional fields, you must also add those fields as options in this section. The option values are the datatype, and, if the field contains sensitive or PII data, the value <tt>anon</tt>.
 **'''dbID'''
-**'''employeeId'''
+**'''EMPLOYEE_ID''' (note that this field name must use exactly this format, all caps with an underscore)
 **'''groupNames'''
 **'''skills'''
 **'''tenantDbID'''
 ====2. Customer Profile====
@@ Line 116: / Line 115: @@
 *'''Customer_language'''=schema-customers
 *'''Customer_ANI'''=schema-customers
-*'''employeeId'''=schema-agents-gim
+*'''EMPLOYEE_ID'''=schema-agents-gim
 *'''Feedback'''=schema-feedback
 *'''groupNames'''=schema-agents-gim
@@ Line 139: / Line 138: @@
 **{{Optionslink|link=Options:DataLoader:dataset-zname-:upload-dataset}} - This option is set to <tt>true</tt> by default, which tells Data Loader to start uploading data at the interval specified in the {{Optionslink|link=Options:DataLoader:dataset-zname-:update-period}} option. To pause uploading, set this option to <tt>false.</tt>
 *'''schema-agents-&lt;''name''&gt;''' - Shows how to configure the schema for an agent Dataset to be uploaded from a .csv file. It has only one mandatory field, but you must also configure options specifying the data types for all other fields. Add the <tt>anon</tt> parameter if the field must be anonymized.
-**employeeId=string,id,anon
+**EMPLOYEE_ID=string,id,anon
 ====Upload outcome data====
@@ Line 153: / Line 152: @@
 **Customer_ANI=string,anon
-**employeeId=string,anon
+**EMPLOYEE_ID=string,anon
 **Feedback=string
 **InteractionID=string
@@ Line 203: / Line 202: @@
 The following fields are mandatory in your agent data SQL file:
-*'''employeeId''' - The id of the agent. Must match the name of the ID Field in the Agent Profile dataset.
+*'''EMPLOYEE_ID''' - The id of the agent. Must match the name of the ID Field in the Agent Profile dataset.
 *'''dbID''' - The agent's configuration database DBID. Obtained from the Genesys Info Mart RESOURCE_.RESOURCE_CFG_DBID field.
 *'''tenantDbID''' - Obtained from the Genesys Info Mart RESOURCE_.tenant_key field.
 *'''groupNames''' - List of group names assigned to the agent.
@@ Line 213: / Line 211: @@
 *'''InteractionID''' - Obtained from the Genesys Info Mart INTERACTION_FACT.media_server_ixn_guid field.
-*'''employeeId''' - field that defines the Agent ID, which must match the name of the id_field in the agents dataset
+*'''EMPLOYEE_ID''' - field that defines the Agent ID, which must match the name of the id_field in the agents dataset
 *'''WHERE clause''' - Must include the following:
 **irf.start_date_time_key - This value must fall between the dates set in the <nowiki>:</nowiki>start_ts and <nowiki>:</nowiki>end_ts parameters. Data Loader replaces the <nowiki>:</nowiki>start_ts and <nowiki>:</nowiki>end_ts fields with the start and end time of the interactions dataset chunk, in epoch format.
@@ Line 222: / Line 220: @@
 *<nowiki>:</nowiki>user_data_fields in the SELECT clause and <nowiki>:</nowiki>user_data_joins in the WHERE clause to extract the user data stored in the Info Mart database.
 *<nowiki>:</nowiki>vq_filter in the WHERE clause to enable filtering of the interaction records by the Virtual Queue names defined in the {{Optionslink|link=Options:DataLoader:dataset-zname-:vq-filter}} option.
 *If you use {{Link-SomewhereInThisVersion|manual=Deployment|topic=DL-CFEP|anchor=userdataRule|display text=multiple mapping rules for one KVP}}, you need to specify how Data Loader should include them in the dataset.
 '''NOTES:'''

@@ Line 222: / Line 222: @@
 *<nowiki>:</nowiki>user_data_fields in the SELECT clause and <nowiki>:</nowiki>user_data_joins in the WHERE clause to extract the user data stored in the Info Mart database.
 *<nowiki>:</nowiki>vq_filter in the WHERE clause to enable filtering of the interaction records by the Virtual Queue names defined in the {{Optionslink|link=Options:DataLoader:dataset-zname-:vq-filter}} option.
 '''NOTES:'''

@@ Line 7: / Line 7: @@
 |UseCase=
 |ComingSoon=No
-|Platform=GenesysEngage-onpremises
+|Platform=GenesysEngage-cloud
 |Role=
 |Application=

@@ Line 5: / Line 5: @@
 |Context=Learn how to configure Data Loader to upload data to your instance of the GPR Core Platform for analysis and agent scoring.
 |Dimension=GPRDataUpload
 |ComingSoon=No
 |Platform=PureEngage
 |Section={{Section
 |sectionHeading=Overview
 |anchor=overview
 |alignment=Vertical
 |structuredtext=Data Loader uploads data to the GPR Core Platform for analysis and agent scoring. GPR uses the following types of data:
@@ Line 24: / Line 30: @@
 '''NOTE:''' Once you have configured a schema in the Data Loader <tt>Application</tt> object and uploaded your data to the GPR Core Platform, you cannot modify the schema.
 |Status=No
 }}{{Section
@@ Line 29: / Line 37: @@
 |anchor=basicUpload
 |alignment=Vertical
 |structuredtext=This section explains how to configure Data Loader to upload the essentials for Predictive Routing. These essentials are the Agent Profile dataset, the Customer Profile dataset, and an interaction dataset.
@@ Line 46: / Line 56: @@
 **'''dbID'''
 **'''employeeId'''
 **'''groupNames'''
 **'''skills'''
 **'''tenantDbID'''
@@ Line 76: / Line 84: @@
 *'''schema-&lt;''name''&gt;'''- When you create this configuration section, replace &lt;''name''&gt; with the same dataset name you entered for the '''dataset-&lt;''name''&gt;''' section. If your dataset section is called '''dataset-interactions''', this section is '''schema-interactions'''.
 |Status=No
 }}{{Section
@@ Line 81: / Line 91: @@
 |anchor=joins
 |alignment=Vertical
 |structuredtext=Joining data enables you to pull together information about many aspects of your environment, enabling more powerful and nuanced predictions. When you join the data, the interaction dataset is the one containing joined fields. That is, the interaction dataset uploaded to the GPR application displays all its own fields, plus the fields from the joined dataset(s).
@@ Line 125: / Line 137: @@
 *'''skills'''=schema-agents-gim
 *'''START_TS'''=timestamp,created_at
 |Status=No
 }}{{Section
@@ Line 130: / Line 144: @@
 |anchor=advancedUploads
 |alignment=Vertical
 |structuredtext=In addition to the Agent Profile, Customer Profile, and interactions datasets described in the preceding sections, you might want to upload other data from your environment. This section presents examples showing how to upload data from additional sources.
@@ Line 182: / Line 198: @@
 *'''dataset-agents-cfgsrv'''
 *'''schema-agents-cfgsrv'''
 |Status=No
 }}{{Section
@@ Line 187: / Line 205: @@
 |anchor=createSQL
 |alignment=Vertical
 |structuredtext=Two default SQL queries are provided in the Data Loader installation package:
@@ Line 213: / Line 233: @@
 *The field names are case-sensitive.
 *Use of angle brackets to signify "not" is not supported. Genesys recommends that you use '''!=''' instead.
 |Status=No
 }}{{Section
@@ Line 218: / Line 240: @@
 |anchor=uploadTiming
 |alignment=Vertical
 |structuredtext=How often Data Loader uploads data from Genesys info Mart and how much data it uploads at once is controlled by two options, upload-period and chunk-size, that coordinate as described in this section.
 |Status=No
 }}
 }}

PE-GPR/9.0.0/Deployment/DL-CfgFile - Revision history

WikiSysop at 12:45, March 31, 2022

Lakshmi.krishnamurthy@genesys.com: Published

Vivian.hood@genesys.com: Published

Vivian.hood@genesys.com: Published

Vivian.hood@genesys.com: Published

Vivian.hood@genesys.com: Published

Vivian: Published

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

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

Vivian: Published

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

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