![]() |
|
![]() ![]() ![]() |
CTI and IC Connectors > About the IC Connector > vdu and vdu_cache Variables | |
![]() |
vdu and vdu_cache Variables |
When you enable IC, Dialog Designer creates two complex variables, vdu and vdu_cache, which map to an EDU (Electronic Data Unit) on the IC system.
The vdu variable is created with one read-only variable field, labeled id. At runtime, when a call is initiated to the Dialog Designer application, the application sends a new call command to the IC system. The IC system then returns a unique EDU ID value, in the form of a vduid variable value, which is stored in the id field of the vdu variable in the Dialog Designer application.
The vdu_cache variable mimics the vdu variable, but fields cannot be added, deleted, or renamed from in it. As changes are made to the vdu variable, the vdu_cache variable will also reflect these changes. The vdu_cache does not go to the VOX server to get the data except for the first time you access it.
You can add other fields to the vdu variable and use them to:
To get values from or set values to the IC system, you must have variable fields in your vdu variable whose names exactly match the names of vdu fields on the IC system. There is no way to query the IC system for these field values, so you must be familiar enough with the workflows on the IC system to have the exact names of the fields whose values you want to use.
For more information about the use of the vdu or vdu_variable variable in Dialog Designer, see Invoke Workflow and Transfer Call.
For more information about variables in general, see Working with Variables.
![]() ![]() ![]() |
©2009, Avaya Inc. All rights reserved.
|