Revision as of 16:19, December 19, 2019 by Vivian (talk | contribs)
Jump to: navigation, search

use-action-filters

Section: default-predictor
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately


Note: In a hybrid environment, this option should always be set to false.

  • true - URS uses a skill expression or Agent Group names taken from the action_filters field in the scoring request.
  • false - URS checks with the Stat Server for the target list of agents, as specified in the login-status-expression option, and adds the target Agent IDs to the scoring request.

Note: If [default-predictor].login-status-expression is set to &(loginStatus=4|loginStatus=9), indicating that the agents who are in the Ready state or ACW state (for voice calls) are the designated target agents, then the GetActionFilters subroutine uses a custom statistic called RStatGPRAgentsReadyOrACWvoice. This custom statistic is provided in the object.kvlt file in the URS Strategy Subroutines IP.

9.0.016.00

Predictive Routing - URS Strategy Subroutines Release Notes


Predictive Routing - URS Strategy Subroutines is part of 9.x starting in 9.0.006.00.
Release Date Release Type Restrictions AIX Linux Solaris Windows
12/20/19 General Under Shipping Control X

Helpful Links


What's New

This release includes the following new features and improvements:

  • Documentation for this and all subsequent releases has been moved to the following locations:
  • The URS Strategy Subroutines are now delivered as ZCF files. For more information and updated deployment instructions, see Deploy the URS Strategy Subroutines.
  • Genesys Predictive Routing (GPR) does not support custom subroutines in hybrid deployments (that is, deployments that combine components delivered in Genesys Engage Cloud and on-premises).
  • Action filtering is now done exclusively by URS. As a result, the use-action-filters configuration option must be set to false. See use-action-filters for more information.
  • The following new KVPs are now attached to user data and are stored in the Genesys info Mart database:
    • gpmVQDBID
    • gpmVQGUID
    In addition, the following KVPs are attached to EventUserEvent data if they are present, although they are not generated by GPR. See Integrate with Genesys reporting for all GPR KVPs.
    • CustomerID
    • ServiceType


Resolved Issues

This release contains The following resolved issues:


ITEM


ITEM



Upgrade Notes

No special procedure is required to upgrade to release 9.0.016.00.

Comments or questions about this documentation? Contact us for support!