Hi,

We've created two PureCloud data actions.  One is to lookup the number of agents listed as "on-queue" and that is performed by using the Queue ID.  The 2nd data action is going to lookup the Queue by name and return its ID.  You can see how the 2nd action feeds the first.

I have created the data actions and I'm able to to input String version of the Queue name and it works fine and successfully outputs the Queue ID when testing.

When I plug this into the In-queue architect flow it just gets an error when the step is reached.  No debug in in-queue flows. :(

The logic goes. .. Call hits in-queue -> assign a variable the "call.CurrentQueue" builtin (convert it to a string) -> plug that variable into my data actions input.



#Integrations
#Roadmap/NewFeatures

------------------------------
Tanner Albus
Realpage, Inc.
------------------------------

I usually throw a Play Audio action into my task and play back the new variable's value after it has been updated using the Speak each character option. That way I can hear if any leading characters are added or whatever. It will give you an idea as to whether the Call Data Action action is bringing back what you expect in Architect.

------------------------------
George Ganahl CCXP, GCP
Principal Technology Consultant
Genesys
------------------------------

Original Message:
Sent: 07-16-2019 14:03
From: Tanner Albus
Subject: "On Queue" Agents custom Data Action for in-Queue Flow

Hi,

We've created two PureCloud data actions.  One is to lookup the number of agents listed as "on-queue" and that is performed by using the Queue ID.  The 2nd data action is going to lookup the Queue by name and return its ID.  You can see how the 2nd action feeds the first.

I have created the data actions and I'm able to to input String version of the Queue name and it works fine and successfully outputs the Queue ID when testing.

When I plug this into the In-queue architect flow it just gets an error when the step is reached.  No debug in in-queue flows. :(

The logic goes. .. Call hits in-queue -> assign a variable the "call.CurrentQueue" builtin (convert it to a string) -> plug that variable into my data actions input.



#Integrations
#Roadmap/NewFeatures

------------------------------
Tanner Albus
Realpage, Inc.
------------------------------

Hi George,

Thank you for your reply.  I hadn't actually used the "Data" input function on the Audio scripting.  That was extremely helpful.  During that i found that the call.CurrentQueue.id was available and I was able to feed that into my other data action.  This eliminates my need for the other.  

I appreciate your reply!

------------------------------
Tanner Albus
Realpage, Inc.
------------------------------

Original Message:
Sent: 07-16-2019 14:21
From: George Ganahl
Subject: "On Queue" Agents custom Data Action for in-Queue Flow

I usually throw a Play Audio action into my task and play back the new variable's value after it has been updated using the Speak each character option. That way I can hear if any leading characters are added or whatever. It will give you an idea as to whether the Call Data Action action is bringing back what you expect in Architect.

------------------------------
George Ganahl CCXP, GCP
Principal Technology Consultant
Genesys

Original Message:
Sent: 07-16-2019 14:03
From: Tanner Albus
Subject: "On Queue" Agents custom Data Action for in-Queue Flow

Hi,

We've created two PureCloud data actions.  One is to lookup the number of agents listed as "on-queue" and that is performed by using the Queue ID.  The 2nd data action is going to lookup the Queue by name and return its ID.  You can see how the 2nd action feeds the first.

I have created the data actions and I'm able to to input String version of the Queue name and it works fine and successfully outputs the Queue ID when testing.

When I plug this into the In-queue architect flow it just gets an error when the step is reached.  No debug in in-queue flows. :(

The logic goes. .. Call hits in-queue -> assign a variable the "call.CurrentQueue" builtin (convert it to a string) -> plug that variable into my data actions input.



#Integrations
#Roadmap/NewFeatures

------------------------------
Tanner Albus
Realpage, Inc.
------------------------------

Excellent!

------------------------------
George Ganahl CCXP, GCP
Principal Technology Consultant
Genesys
------------------------------

Original Message:
Sent: 07-16-2019 16:28
From: Tanner Albus
Subject: "On Queue" Agents custom Data Action for in-Queue Flow

Hi George,

Thank you for your reply.  I hadn't actually used the "Data" input function on the Audio scripting.  That was extremely helpful.  During that i found that the call.CurrentQueue.id was available and I was able to feed that into my other data action.  This eliminates my need for the other.

I appreciate your reply!

------------------------------
Tanner Albus
Realpage, Inc.

Original Message:
Sent: 07-16-2019 14:21
From: George Ganahl
Subject: "On Queue" Agents custom Data Action for in-Queue Flow

I usually throw a Play Audio action into my task and play back the new variable's value after it has been updated using the Speak each character option. That way I can hear if any leading characters are added or whatever. It will give you an idea as to whether the Call Data Action action is bringing back what you expect in Architect.

------------------------------
George Ganahl CCXP, GCP
Principal Technology Consultant
Genesys

Original Message:
Sent: 07-16-2019 14:03
From: Tanner Albus
Subject: "On Queue" Agents custom Data Action for in-Queue Flow

Hi,

We've created two PureCloud data actions.  One is to lookup the number of agents listed as "on-queue" and that is performed by using the Queue ID.  The 2nd data action is going to lookup the Queue by name and return its ID.  You can see how the 2nd action feeds the first.

I have created the data actions and I'm able to to input String version of the Queue name and it works fine and successfully outputs the Queue ID when testing.

When I plug this into the In-queue architect flow it just gets an error when the step is reached.  No debug in in-queue flows. :(

The logic goes. .. Call hits in-queue -> assign a variable the "call.CurrentQueue" builtin (convert it to a string) -> plug that variable into my data actions input.



#Integrations
#Roadmap/NewFeatures

------------------------------
Tanner Albus
Realpage, Inc.
------------------------------