Technical References

The Import Schedule (page 225) table defines import processes to be run automatically at specified
times.
The Import Log (page 216) table contains information about these import processes.
A schedule may recur daily, weekly, monthly, etc. The Recurring Schedule Map (page
270)describes a recurrence pattern for a schedule.
The Schedule Report (page 312) table describes the export report.
Script Tables - Database Rules
To see an illustration and a list of all tables in the Script category, click here (page 451).
The ICM/IPCC classifies each incoming call into a Call Type (page 74) based on a Dialed
Number Map (page 158). The mapping considers the dialed number, caller-entered digits, and
calling line ID. The calling line ID can be specified as a specific number, a wildcard, or a Region
(page 272) composed of Prefixes (page 274). Each routing client may have a Default Call Type
(page 154).
A script is a series of steps executed to determine the best route for a call or to perform periodic
administrative actions. You can create several versions of each script. General information about
each script is stored in the Master Scrip (page 232)t. Specific information about each version is
stored in the Script (page 317). The binary representation of the script version is stored in the
Script Data (page 319) table. Each Script version has a Cross Reference (page 318) for each
database entity that it references.
A Call Type Map (page 100) associates one or more routing scripts to the call type based on a
schedule of when each script is active. An Admin Script Schedule Map (page 13) schedules a
periodic administrative script. For each script version, Real Time (page 322) and Five-Minute
(page 320) data are produced. Also, Real-Time (page 101) data are produced for each call type.
You can define User Variables (page 431) that you can set and reference in scripts. Optionally,
you can define Persistent Variables (page 262) that retain their values between script invocations.
You can also define custom functions that are stored as User Formulas (page 426). The expression
associated with a custom function is stored in User Formula Equation (page 426).
With the optional Gateway feature, a script can communicate with an external application. An
Application Gateway (page 60) represents such an external application. Each side of the Central
Controller can maintain a separate Connection (page 61) for each Application Gateway.
ICM/IPCC software also maintains Global (page 63) default values for Application Gateway
connections. Half-hour (page 65) data are produced for each Application Gateway.
With the optional Gateway SQL feature, a script can query an external database. The tables that
can be accessed are stored in Script Table (page 317) and the specific columns in Script Table
Column (page 324).
The Script Queue Real Time (page 321)table contains data on how tasks are processed in a script
queue.
Database Schema Handbook Cisco ICM/IPCC Enterprise & Hosted Editions 7.2(2)
509
Chapter 5: Database Rules
Script Tables - Database Rules