User variables in VM Pro

[lcorriveau]

Hello, I am have issues with user variables in VM Pro. As it seems, if I set a user variable in a call flow, let's say, Language, the value in the vriable is set to "English", but if I use the same variable in another call flow (We have about 30 call flows) well that Language variable is reset, and not trully associated with the call. It's more of a system variable.

Now, if I create a Language variable for each call flow, there is still the issue when 2 calls come into the same call flow, then again, overwriting the value of the varriable.

So, is there any other way to work arround with this then having to create a huge amout of variables ? Not to forget, the value of these variables are checked many times in the call flow for message prompts, voice mailbox, etc...

Thanks for your help.

Louis

 

[intrigrant]

User variables are not related to a call but these are public variables.
If you want to change the locale of a call use the "set language" option.
Each call has its own private set of variables called $CPx.
x is a value from 0 to 9 so there are ten variables you can use and these are relted to the call and will stay with the call during the lifetime of the call.
By default these have the value zero.
Iy you want to staore data in the variable the use the generic action and in the specific area give the variable a value with the following command: CP1:JohnnyEnglish.
During the lifetime of the call the value for $CP1 = JohnnyEnglish unless the value is overwritten in another calflow.
You can test the value with a compare action or within a condition.
Her you van find a example callflow which uses these variables for counting the number of times a person has passed a menu.

http://intrigrant.atspace.com/

 

[intrigrant]

User variables are not related to a call but these are public variables.
If you want to change the locale of a call use the "set language" option.
Each call has its own private set of variables called $CPx.
x is a value from 0 to 9 so there are ten variables you can use and these are relted to the call and will stay with the call during the lifetime of the call.
By default these have the value zero.
Iy you want to staore data in the variable the use the generic action and in the specific area give the variable a value with the following command: CP1:JohnnyEnglish.
During the lifetime of the call the value for $CP1 = JohnnyEnglish unless the value is overwritten in another calflow.
You can test the value with a compare action or within a condition.
Here you van find a example callflow which uses these variables for counting the number of times a person has passed a menu.

http://intrigrant.atspace.com/