Jump to: navigation, search

Analyze Object

Release 8.1.400.15 of Interaction Routing Designer adds an Analyze object for enhanced content analysis. The Analyze object, available on IRD's Multimedia group of objects, combines the functionality of IRD's existing Classify and MultiScreen objects and adds new functionality. The Analyze object:

  • Visually presents screening rules under their applicable categories. The category name shows all roots so screening rules belonging to multiple categories can be selected in the same request.
  • Introduces two new attributes in the ESP Request: Service = Analyze and Method = ClassifyScreenUniversal.
  • Allows modified screening of ESP requests with the ability to specify a category/folder containing a subset of screening rules to screen against.

The example below shows the Financial Services Category, Unidentified Transaction_2 subcategory, associated with screening rules Wrong transaction amount_scrRule and Unidentified transaction_scrRule.

IRDAnalyze2.png

Configuring the Analyze Object

  1. From the Multimedia toolbar, click the Analyze object then click inside the Routing Design window to insert the object.
  2. Double-click the object to open its properties dialog box. A tree of the default Classification Server categories and screening rules appears below.
  3. From the Classification server drop-down list on the General tab, select a Classification Server from those in the Configuration Server database. If you leave this field empty, Interaction Server uses the first available Classification Server named in its Connections list.
  4. From the Language drop-down list, select the language of the incoming interaction. The categories and screening rules shown will be changed according to selected language. Only those roots associated (through their Annex property General/Language) with the selected language will be shown.
  5. From the Action drop-down list, select screen or classify. Only one Action can be configured. either screen or classify. For action classify, screening rules are not used so IRD hides screening rules in this case.
  6. If the classify Action is selected, opposite Relevancy Level, enter a percentage indicating the minimum relevancy (confidence) each category must have (greater or equal) in order for Classification Server to consider an interaction as belonging to that category (threshold). You have the option of changing the default but you cannot enter zero.
    • If Classification Server finds a category with the minimum specified relevancy, the results are processed based on the option you select in the Result tab and the interaction goes through the green port.
    • If an existing category cannot be found based on analyzing the interaction, the null result is attached to the interaction and the interaction also goes through the green port (the error is not retrievable through the current Error object). See Event3rdServerFault in the Universal Routing 8.1 Reference Manual.
  7. Under Get analyzing data from, enter a User Data key to search for data to be analyzed or enter a variable. If not specified, the data to be analyzed will be taken from the Universal Contact Server database.
  8. Under Categories and screening rules, you have the option of selecting a variable to contain the categories and/or screening rules to use. If variables are used, you cannot select screening rules or categories from the tree. You can either select from the tree or specify variables, but you cannot do both.
  9. Note the tree of categories/Screening Rules. If the identifiers do not sufficiently describe them, you can look up them up in Configuration Manager (Business Attributes) or Genesys Administrator or in eServices Knowledge Manager, where they were originally defined.
  10. The Subcategories using options (required) determine whether Classification Server should consider parent and child categories (ParentMode in Requests as shown in Samples below. There are three options.
    • To use all screening rules for a selected category, select All.
    • To use only the direct children of a selected category (excluding parents), select Direct.
    • To individually select categories and rules, select No.
  11. Continue to select categories/rules in this fashion until you have selected all the ones you want to use.
  12. Select the Parameters tab. If necessary, any additional parameters to the request can be added here. For additional information see eServices Knowledge Manager documentation.
  13. Select the Result tab. Specify what form the results should take. IRD uses the same Result tab for various Multimedia objects. When screening or classifying, the Do not use output value option does not apply.
  14. Complete the Result tab. If you write the results to a variable, the variable can be parsed by URS and attached to the interaction for further use in the strategy. You can also attach all the parameters to the interaction’s User Data. This enables you to analyze this User Data to make further routing decisions.
  15. Click OK.

For classification, The response will be either Event3rdServerResponse or Event3rdServerDefault. For detail on these responses as well as on using IRD for screening and classification, refer to the Universal Routing 8.1. Reference Manual.

Samples

[+] Analyze Action Classify

[+] Analyze Action Screen

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on April 14, 2016, at 09:38.