Can I pass an argument to a CFD when called from IVR

[princer800]

Want to pass a parameter so I can cahnge my SQL lookup - based on which optin called CFD.
SAy press #2 for Dept X and press #3 for Dept Y.
So canuse same CFD to do lookup based on department. Otherwise have to duplicate CFD for each departmnet.

 

[edossantos]

No, you can't pass this information. Why don't you implement the entire IVR as a CFD app? You would not have this problem in that case.

 

[princer800]

No, you can't pass this information. Why don't you implement the entire IVR as a CFD app? You would not have this problem in that case.

Originally planned to do that - but then made more sense to use what is there first.
But I understand what you are saying and actually can do that for sure.
Can one CFD call another? That way it is more modular.

 

[edossantos]

Can one CFD call another? That way it is more modular.

Yes, you can transfer the call to a second CFD app, using the Transfer component and setting the destination to the CFD callflow name, for example "myproject.Main". However, this is probably not what you want. When you transfer a call, the caller might hear music on hold during a short time, and unnecessary delays... So, in order to keep the design modular, it's better to use User Defined Components. You can have all the user defined components that you want in your project, and call them just by dragging and dropping the component in the caller designer surface.