I am using Unified CCx Editor version 7.0(1.168). I created a script to be used instead of the system default script. According to the help file, "All script variables from the main script can initialize the default script variables, if the designer defines them using the same name and type". However, the variables in my default script are never initialized even though the same variables in the main script are changed before the main script terminates. I made sure they have the same name and type, but the values in the default script remain unchanged.
All the variables I am trying to pass are of type String, and initially they are all set to the empty string "" in both scripts.
I'm not sure I understand what you are asking, but will try telling you this to see if it makes things clearer:
Basically the variables in each script (i.e. each .aef file) are unique to the .aef, there is no way to change a variable in one and have it directly affect the state of a variable in another. Even if you are looking at two executions of the same .aef script, the variables are unique/distinct instances; there is no concept of 'static' variables.
Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
Thank you for your reply. However, I am not trying to pass variables between different scripts, not even differerent instances of the same script. I am talking about the default script which is executed when the main script is not terminated properly.
The help file states that the variables in the default script are populated with the values of the same name and type from the main script.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...