deployment-type
Section: default
Default Value: hybrid
Valid Values: hybrid, cloud
Changes Take Effect: on initial startup of GPR
Introduced: 9.0.017.00
The URS Strategy Subroutines takes the value for this option to populate the gpmDeploymentType KVP, which is recorded in the GPR score log for internal reporting and monitoring purposes.
vq-for-reporting
Section: default
Default Value: No default value
Valid Values: Any valid virtual queue or DN name
Changes Take Effect: Immediately
This option is mandatory.
Indicates the virtual queue or DN where URS sends the Genesys Predictive Routing (GPR) user event data describing the routing decision made for the interaction. The user event data, in the form of key-value pairs, is attached to EventUserEvent in the AttributeUserData attribute. This should be the same value as AttributeThis DN in the EventUserEvent event.
NOTE: The values for VQ Number (on the VQ DN object General tab), VQ Alias (on the VQ DN object Advanced tab), and the value for the vq-for-reporting option should all be identical.
For more information on creating reports based on Predictive Routing data, see "Integrate with Genesys Reporting" in the Predictive Routing Deployment and Operations Guide.
proxy-password
Section: default
Default Value: No default value
Valid Values: any string
Changes Take Effect: on the next interaction processed by GPR
Introduced: 9.0.017.00
Related Options: proxy-host, proxy-port, proxy-username
Specifies the password to be used to connect to the HTTPS Proxy, if it requires client authentication to connect.
proxy-username
Section: default
Default Value: No default value
Valid Values: Any string
Changes Take Effect: on the next interaction processed by GPR
Introduced: 9.0.017.00
Related Options: proxy-host, proxy-port, proxy-password
Specifies the user name to be used to connect to HTTPS Proxy, if it requires client authentication to connect.
proxy-port
Section: default
Default Value: 0
Valid Values: Any positive integer
Changes Take Effect: on the next interaction processed by GPR
Introduced: 9.0.017.00
Related Options: proxy-host, proxy-username, proxy-password
Specifies the HTTPS Proxy port to which the GPR Subroutines should send the request to connect to the GPR Core Platform.
proxy-host
Section: default
Default Value: No default value
Valid Values: Any string
Changes Take Effect: On the next interaction processed by GPR
Introduced: 9.0.017.00
Related Options: proxy-port, proxy-username, proxy-password
Specifies the name of the HTTPS Proxy host to which the GPR Subroutines should send the request to connect to the GPR Core Platform.
9.0.017.00
Predictive Routing - URS Strategy Subroutines Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 04/17/20 | General | Under Shipping Control | X |
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release contains the following new features and enhancements:
- The Predictive Routing strategy subroutines now support the use of HTTP/HTTPS Proxy for requests sent to the GPR Core Platform from the URS Strategy Subroutines. Configure the following four options to activate this functionality:
- (PRR-6401)
- This release offers the option to specify a VQ name when calling the ActivatePredictiveRouting_v3 subroutine before Target selection or the Route Call block. To use this functionality, pass the desired VQ_name value in the default_skill_data parameter of the ActivatePredictiveRouting_v3 subroutine.
- ActivatePredictiveRouting_v3 stores this VQ value in the gpmVQNumber field in the URS global map. The GPRIxnCleanup subroutines then reads the gpmVQNumber value in URS global map and uses this to generate the value for the gpmVQDBID, which is required to be present in the GPM_FACT able for Genesys Info Mart reporting.
- If no VQ is passed to the ActivatePredictiveRouting_v3 subroutine or the GPRIxnClaenup subroutine cannot locate the value in the URS global map, GIM reporting uses the value configured in the vq-for-reporting option.
- Important: GPRIxnCleanup always sends EventUserEvent with VQ name configured in vq-for-reporting of Predictive_Route_DataCfg transaction list AttributeThisDN irrespective of value VQ on which the call is queued and routed.
- A new option, deployment-type, tells the GPR URS Strategy Subroutines to generate the new gpmDeploymentType KVP and pass it to the GPR score log for use by the GPR Core Platform. This option indicates whether GPR is deployed in hybrid or cloud-only mode. (PRR-6317)
- AB testing mode is activated when prr-mode in the predictor section is set to ab-test-time-sliced.
When ab-test-time-slice is set to 0 AB testing mode is activated, then IRD subroutine SetIdealAndReadyCondition uses a formula based on hour of day and day of year to determine whether particular interaction belongs to Group A or Group B regime.
When ab-test-time-slice is set to non-zero value and AB testing mode is activated, then IRD subroutine SetIdealAndReadyCondition uses a formula which is based on the configured time slice to determine whether particular interaction belongs to Group A or Group B regime.
- Note*: default value of ab-test-time-slice is changed to 0.
(PRR-6244)
- GPR subroutines now support premise anonymisation when account in GPR is configured to use Premise anonymization and Data Loader is deployed and started in premise environment before using the GPR subroutines.
* GPR subroutines will use the options anon-salt, anon-agent-id, anon-customer-id added by Data Loader in Predictive_Route_DataCfg transaction list object to perform the anonymization. * Agent ID's sent in the scoring request and score_log request will be anonymised only when anon-agent-id is set to true by Data Loader. * Context_id sent in the scoring request and score_log request will be anonymised only when anon-customer-id is set to true by Data Loader.
(PRR-6226)
Resolved Issues
This release contains the following resolved issues:
A new configuration option named *enable-log-suppression* is introduced to control log suppression in IRD subroutines.
Configured in default section of Predictive_Route_DataCfg transaction list object.
Valid values - true, false
Default value - true
Changes takes effect - For the next interaction
* When set to true, following subroutines suppress log messages to avoid the flooding of logs. ** GetActionFilters subroutine while builds a list of agent ID's to be scored ** ActivatePredictiveRouting_v3 subroutine while building the scoring request and also while parsing the scoring response before storing the returned agent scores in global map. ** ScoreIdealAgent subroutine while updating the values of default scored agent KVP's ** GPRIxnCleanup while building the score log request and also while generating the content for UserEvent. * When set to false, no log suppression will be done by subroutines and all messages will be printed in URS logs. (PRR-6265)
GPR subroutines will not send any scoring request in the following scenarios.
* When the GET Predictor API request tried in GetScoringContext subroutine fails and thus customer features cannot be obtained. * When the configured predictor has empty customer features. In real production mode, it is always expected to have predictors configured with atleast one customer feature which needs to be added in context of scoring request.
In both these scenarios, GPR subroutines will add gpmResult = 7 and gpmMessage = "Failed to build Scoring Context" KVP's sent to GIM and score_log. (PRR-6233)
Upgrade Notes
No special procedure is required to upgrade to release 9.0.017.00.