Genesys CCPulse – Display UserData using Custom Stat and Filters

Previously, I wrote post about displaying user data in CCPulse using custom solution and user ‘‘ enquired about displaying user data using CCPulse application only.

I found two options to display user data in CCPulse

Option 1: Display User Data using Custom Stat


Step 1: Configure Custom Statistic as below

[CustomUserData]
Category = CurrentCustomValue
Formula = GetGlobalNumber(“Account”,-1)”
MainMask = *
Objects = Agent, Place, GroupAgents, GroupPlaces
Subject = DNAction

In CCPulse, configure template to display this custom statistic. Please note that this will work only if key value is numeric. To display string value, use option 2 below

Option 2: Display User Data using Filters


You need CCPulse 8.0.101.27 or higher to display user data using filters. Please find the CCPulse release notes below

CCPulse+ now displays by default only hardware or software reason codes, without User Data. A new CCPulse+ option, ReasonCodeData, in the [CustomStatistic] section enables you to control which values are displayed.

ReasonCodeData

Valid Values: Hardware; Software; Userdata
Separate with semicolons the values to be displayed. Enter all three values if you use User Data values with reason codes in Formulas or to display them in the Extended Status window or in a view.

[CustomStatistic]
ReasonCodeData=Userdata (optional values: Hardware; Software)

Previously, starting with release 8.0.000.41, CCPulse+ appended some values from User Data to the reason codes. (ER# 317914454)

To display user data ‘Account’, follow steps below

Step 1: Create Filter ‘Account = PairExist(“Account”, “*”) under [Filters] section in Stat Server

Step 2: Create statistical type [CustomAgentState] in Stat Server as below

[CustomAgentState]

Category=CurrentState
MainMask=*
Objects=Agent
Subject=DNAction

Step 3: Set CCPulse application options, set ‘ExtendedCurrentStatus’ to ‘true under [CustomStatistic]

Step 4: Add below formula to display

 

(Visited 136 times, 1 visits today)

Tagged: , , ,

Comments: 14

  1. Moshe Lezerovitz April 6, 2016 at 2:23 pm Reply

    thanks alot for the solution, will it also work with
    objects=RegDN ?
    i tried it with that and state.type is not equal to “AgentState” and it also alert me on the state.CallData.Filter(“”) says that the filter object is not exist

    • blakshmikanth April 6, 2016 at 4:58 pm Reply

      RegDN should work with ‘DNState’.

      • Moshe Lezerovitz April 10, 2016 at 12:41 pm Reply

        OK,
        now when i refer to Objects=Agent
        Subject=DNAction.
        when i’m putting the following in the script:
        var e = new Enumerator(state.CallData.Filter(“Key=Account”));
        result.Text = state.type;

        and try to validate i get the following error:
        “Error in formula: ‘state.CallData’ is null or not and object”

        • Moshe Lezerovitz April 11, 2016 at 2:11 pm Reply

          OK it works great for Objects=Agent 🙂
          but the problem is when i’m trying to do it on Objects = RegDN
          i always get ‘undefined’ on state.type
          any idea?

          • blakshmikanth April 11, 2016 at 2:19 pm

            Make sure that subject is set to ‘DNAction’ in your stat definition. If not, can you share your stat definition?

          • Moshe Lezerovitz April 12, 2016 at 6:43 am

            sure,

            Category=CurrentState

            MainMask=*

            Objects=RegDN

            Subject=DNAction

          • Moshe Lezerovitz April 26, 2016 at 9:22 am

            Hi,
            have you had the chance to look into it?

  2. Moshe Lezerovitz April 6, 2016 at 2:23 pm Reply

    thanks alot for the solution, will it also work with
    objects=RegDN ?
    i tried it with that and state.type is not equal to “AgentState” and it also alert me on the state.CallData.Filter(“”) says that the filter object is not exist

  3. jorge October 11, 2017 at 4:39 pm Reply

    Why state.type?

  4. jorge October 11, 2017 at 4:39 pm Reply

    Why state.type?

Leave a Reply

Your email address will not be published. Required fields are marked *