[cisco-voip] IPCC Express Scripting - Subflow question

[Micah Bennett]

Hello all.  Looking for some confirmation on what I am seeing.  I hope
this makes sense.

I have been working on a subflow that we will add to all of our call
center IPCC scripts for the holiday period when we are closed.

Calls will come into their normal trigger, roll to their normal
application, and thus to their normal crs script path.  
My subflow script will do a date/time comparison between the current
date/time, a specified begin date/time and a specified end date/time.  
There are three paths that my subflow can take depending on the outcome
of this comparison. 

Path 1.  If the call date/time is BEFORE the specified closed range,
caller will hear a pre-holiday message (we will be closed .....) and
then be passed back to the main script for normal treatment.
Path 2.  If the call date/time is DURING the specified closed range,
caller will hear a closed message and be disconnected.
Path 3.  If the call date/time is AFTER the specified closed range,
caller will hear nothing from the subflow and be passed back to the main
script for normal treatment.

Setup of the subflow:
Current time is pulled from the server and stored as a variable.
Begin time is datafilled as a variable and set as a PARAMETER so it can
be edited at the Application level in CRS.
End time is datafilled as a variable and set as a PARAMETER so it can be
edited at the Application level in CRS.

>From my research I found the only way to test a subflow and actually
debug it was to assign a trigger and application to the subflow script.
This way it could be called independently and the logic / flow could be
tested and the variables / parameters could be verified separately from
the main script.  Testing the subflow by itself using the assigned
trigger works fine.  My variables are pulled, stored, and compared
accurately.  My paths all work based on the outcome.  When I test the
main script that calls the subflow I have found an issue.  

Issue:  
When I call the subflow independently of the main script, my PARAMETER
values for begin time and end time are populated correctly and
everything works at the subflow level.  
When I call the main script and roll to the subflow, my PARAMETER values
for the subflow are ignored and my treatment in the subflow is based off
the default values in my begin time variable and end time variable.  I
verified this by changing the default variable values and turning off
the option for them to be a PARAMETER.

Is it accurate to say that if I have a variable such as Begin Date/Time
or End Data/Time that will be referenced in a subflow and I need this
value to be editable at the application level in CRS as a PARAMETER,
this variable needs to be assigned in the main script and then passed to
the subflow.  It seems that since the application layer of the subflow
is not engaged when using the Call Subflow step, if the PARAMETER value
is set there, it is ignored and the default value of the variable in the
subflow script is used.    

Thanks.

Micah Bennett
Telecommunications Admin
Automated License Systems
3055 Lebanon Rd, Ste 2301
Nashville, TN  37214
Extension: 2357
Office: 615-263-4066
Mobile: 615-207-0318
Email: micah.bennett at als-xtn.com
Website: www.als-xtn.com
 









The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20071205/9e3d2a24/attachment.html