Guest

Cisco Unified Intelligent Contact Management Enterprise

Persistent and Non-persistent User Variable in ICM

Document ID: 63020

Updated: Oct 27, 2005

   Print

Introduction

This document describes the persistent and non-persistent user variable in a Cisco Intelligent Contact Management (ICM) environment.

Refer to the Conventions Used in Cisco Technical Tips for more information on document conventions.

Q. What is a Persistent User Variable in ICM?

A. The definitions of user variables are contained in the User_Variable table on the central database. The User Variable list tool is used to create, update, and delete user variables. Each user variable must meet this criteria:

  1. Have a name that begins with user.

  2. Be associated with an object type, for example, Service. (This enables ICM to maintain an instance of that variable for each object of that type in the system.)

  3. Be identified as a persistent (retains value across CallRouter restarts) or non-persistent (does not retain value across CallRouter restarts) variable. Figure 1 demonstrates the creation of a persistent user variable, where the name is user which is associated with Service.

    Figure 1—Create a Persistent User Variable

    qa-user-variable-1.gif

  4. Holds a value up to 40 characters long.

A user variable can be set and referenced within scripts. If a user variable is persistent, the value is stored in the Persistent_Variable table on the central database. Both a non-persistent user variable and persistent user variable can be passed between scripts.

Related Information

Updated: Oct 27, 2005
Document ID: 63020