Gregoire_SUAUD | 2020-04-14 16:05:34 UTC | #1
Hi, i'm new in the purecloud API explorer.
I'm actually working on a flow where i transfer the call to a secure flow at the end. In that first flow, I would like to get the internal partipant(s) name and/or email of the current interaction to also transfer this data to the secure flow.
I didnt find anything useful in the architect so I suppose that can be got from an action through a simple or json request.
Do you have any tips in that case ? And where could i find some help for the development code?
Thanks for your help !
MelissaBailey | 2020-04-14 16:55:31 UTC | #2
Call flows have a built-in variable for the conversation id, Call.ConversationId. It's available in the secure flow so you don't have to worry about passing it into the secure flow.
Scripter has built-int variables for the agent's name and email, you can set them in the Invoke Secure Flow's Flow Data Field. They will be available in the secure flow's built-in variable Flow.InvocationData. The field is a single string value, so since you want to pass 2 pieces of information you will need to append them in the script and split them in the flow. For this example, I appended them with a colon. In the flow make sure you set the value to assign to expression mode instead of literal.
Gregoire_SUAUD | 2020-04-15 06:56:42 UTC | #3
Hi, thanks a lot for those precious details, i appreciate ! However, i'm wondering one thing : How can i have the passed informations from the secure flow, in the flow performance data ?
For you to understand better what i want to do, it's a simple survey where the customer will be forwarded at the end of an interaction. I've got the results of the survey thanks to some Flow Outcomes and i want to match them with the agents name.
I've set up what you told me to do but how can i have the agent name variable as a results in the flow outcome?
Thanks for your consideration !
system | 2020-05-16 06:56:45 UTC | #4
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 7539