Guest

Cisco Unified Contact Center Express

How Do I Setup an Enterprise Data Screen Pop?

Cisco - How Do I Setup an Enterprise Data Screen Pop?

Document ID: 46023

Updated: May 02, 2008

   Print

Introduction

This document describes the procedure to set up an enterprise data screen pop. This helps add specific steps to scripts that already exist.

Q. How do I setup an enterprise data screen pop?

A. The procedure to set up an enterprise data screen pop follows:

  1. Configure enterprise data as shown from page 2-3 through page 2-8 of the Cisco Desktop Administrator User Guide. This step adds a custom field to the Field List or edits a current custom field.

    Note: Predefined fields have index numbers of 231-255 and may not be edited. Custom fields may use index numbers 0-230 and may be edited.

  2. Run Cisco Response Applications Script Editor to modify the script which pops the enterprise data.

    Figure 1: The Script with One Set Enterprise Data Step

    QA-SetupScreenPOP-1.gif

  3. Add a label named "Op Q" before Select Resource, as shown in Figure 1 and Figure 2.

    Figure 2: Adding Label Step

    QA-SetupScreenPOP-2.gif

  4. Change the Select Resource step so it does not connect immediately . The selected output branch appears after you select the No radio button, see Figure 1 and Figure 3.

    Figure 3: Select Resource Step

    QA-SetupScreenPOP-3.gif

  5. Add the Set Enterprise Data step with the field index and the string variable that are set in step 1, shown in Figure 1 and Figure 4.

    Figure 4: Set Enterprise Server Data Step

    QA-SetupScreenPOP-4.gif

  6. To add additional Set Enterprise Data steps, repeat step 5 as needed.

  7. Add the Connect step with the ResourceID variable, shown in Figure 1 and Figure 5.

    Figure 5: Connect Step

    QA-SetupScreenPOP-5.gif

  8. In the failed step, under Connect, add a Goto step to goto "Op Q", as referenced in step 3, see Figure 1 and Figure 6.

    Figure 6: Goto Step

    QA-SetupScreenPOP-6.gif

Related Information

Updated: May 02, 2008
Document ID: 46023