Genesys CTI User Forum
Genesys CTI User Forum => Genesys-related Development => Topic started by: cavagnaro on March 02, 2015, 12:33:42 AM
-
Hi guys,
I was doing an idea on a project and faced an issue which tried to handle with root variables, but GVP resets the value to original one every time it changes scope. Meaning, if you update value on subcallflow it won't return to main callflow updated, main callflow will have the original value as was on the root.vxml file.
Wonder then, what is the point of having root variables then?
Tried then to work with sessions and another pain in the ass. Ended up doing it via DB...
Who has used root variables and a success case? Can't see the use of this if it doesn't allow the whole project to use the variable.
Ideas?
Thanks!
-
How are you using,declaring and passing the root variables to the another form?Could you attach "hello world" sample of your vxml app? It is working, but there are some pre-requisities according to the VXML definition.
-
On normal VXML should work I think, but I am talking about GVP specific implementation.
Updated values are not sent to main callflow or viceversa. If I'd use parameters for the subcallflows or return values would make no sense to have "root" variables, better use simple local variables.
-
So, you mean some specific attribute from extended Genesys namespace? If yes, which one? For data passing is not necessary to use extended namespaces.
-
Have you used this function before on GVP?
1. Create Main callflow
2. Declare Application Root file (sample.vxml with var a1 with initial value XXXXX for example on src folder )
3. Now you have a var a1 available (accessible by application.a1)
4. Call a sub callflow S1
5. Declare same Application Root file
6. Now you also have a1 variable available
7. On S1 update variable a1 to value YYYY (application.a1 = 'YYYY')
8. Return to main callflow
9. Check value (print, prompt, etc) of variable a1
10. a1 outputs XXXXX instead of YYYYY
-
[quote author=cavagnaro link=topic=8740.msg38817#msg38817 date=1425307802]
Have you used this function before on GVP?
1. Create Main callflow
2. Declare Application Root file (sample.vxml with var a1 with initial value XXXXX for example on src folder )
3. Now you have a var a1 available (accessible by application.a1)
4. Call a sub callflow S1
5. Declare same Application Root file
6. Now you also have a1 variable available
7. On S1 update variable a1 to value YYYY (application.a1 = 'YYYY')
8. Return to main callflow
9. Check value (print, prompt, etc) of variable a1
10. a1 outputs XXXXX instead of YYYYY
[/quote]
Were you able to find the solution of this issue? I am also trying to do the same in my sample application but it seems that I will also run into same issue while running the application.
-
Well I had to add the root file to ALL flows, no matter if variable was used or not.
-
[quote author=cavagnaro link=topic=8740.msg39099#msg39099 date=1428412246]
Well I had to add the root file to ALL flows, no matter if variable was used or not.
[/quote]
Got it!!! Thanks a lot.
-
Can you please confirm if below understanding is correct?
My understanding:
By using the concept of AppRoot in sub-callflows, the variables declared in AppRoot will be available in sub-callflow. If I change the value of these variables in sub callflow then the changed value of the variable will be available in main flow (or calling flow file).
Regards,
Ankur Khurana
-
As long as you use the root file on ALL (ALL) callflows (vxml) called. If you miss one, sequence will be lost.
http://voice.cs.vt.edu/docs/prm_files/rootdoc.html
-
Hi I am new to this forum,
I have worked with IVR Composer applications, You have to mention approot.vxml in every subcallflow but that will only let You use the root variable in the subcallflows it wont maintain the status from the parent callflow, one work around is to use GOTO instead of subdialog block. Another work around is to declare object in java script add all Your variables to the object and pass that as input and output to all the subcallflows. hope that helps.
-Raj.
-
Which Composer version you used?