Enterprise Intelligence Solutions

Custom Data Planner

Administration Guide
Version 11.2

Document Revision 1.00

Confidential and Proprietary Information of Verint Systems Inc.

© 1992–2015 Verint Systems Inc. All Rights Reserved Worldwide.
Confidential and Proprietary Information of Verint Systems Inc.

All materials (regardless of form and including, without limitation, software applications,
documentation, and any other information relating to Verint Systems, its products or services) are
the exclusive property of Verint Systems Inc. Only expressly authorized individuals under
obligations of confidentiality are permitted to review materials in this document. By reviewing
these materials, you agree to not disclose these materials to any third party unless expressly
authorized by Verint Systems, and to protect the materials as confidential and trade secret
information. Any unauthorized review, retransmission, dissemination or other use of these
materials is strictly prohibited. If you are not authorized to review these materials, please return
these materials (and any copies) from where they were obtained. All materials found herein are
provided “AS IS” and without warranty of any kind.
Verint Systems Inc. does not warrant, guarantee or make any representation regarding the use or
the results of the use of the information, links, tools, and materials in terms of the accuracy,
reliability, quality, validity, stability, completeness, currentness, or otherwise of its content or
products. The entire risk as to the use, results and performance of information, links, tools and
materials provided or referenced herein is assumed by the user. Verint Systems Inc. shall not be
liable for damages resulting from the use, misuse or unlawful use of the information, links, tools,
and materials contained or referenced herein.
Any third party technology that may be appropriate or necessary for use with the Verint Product is
licensed to you only for use with the Verint Product under the terms of the third party license
agreement specified in the Documentation, the Software or as provided online at
http://verint.com/thirdpartylicense. You may not take any action that would separate the third
party technology from the Verint Product. Unless otherwise permitted under the terms of the third
party license agreement, you agree to only use the third party technology in conjunction with the
Verint Product.
The Verint Systems Inc. products are protected by one or more U.S., European or International
Patents and other U.S. and International Patents and Patents Pending.

All marks referenced herein with the ® or ™ symbol are registered trademarks or trademarks of
Verint Systems Inc. or its subsidiaries. All rights reserved. All other marks are trademarks of their
respective owners.

Visit our website at www.verint.com/intellectualpropertynotice for updated information on Verint

Intellectual Property.

Document Revision 1.00

Published November 13, 2014
 Contents

About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1 Introduction to Custom Data Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

About Custom Data Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Installing the Custom Data Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2 Custom Data Planner Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Accessing the Custom Data Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Creating and Understanding a New Project . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Creating a New Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Understanding the Project Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Creating and Understanding a New Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
About Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
The Lock Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Creating a New Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Defining and Understanding Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
About Shared Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Defining a Custom Data Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Defining a Conditional Custom Data Field . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Populating a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
About Populating a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
About the Populate Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Errors and Feedback after Populating . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Exporting a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Importing a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Modifying and Deleting Projects, Sets and Fields . . . . . . . . . . . . . . . . . . . . . . . . 24
Modifying an Existing Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Modifying a Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Modifying an Existing Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Deleting a Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Deleting an Existing Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
 Preface

About this guide

This guide is intended as an aid in the installation and implementation of the Custom
Data Planner application using a logic for customized data that best serves customers’
lines of business.

Intended audience
This guide is designed to be used by:
 Verint and Business Partner professional services staff responsible for planning and
setting up systems.
 Customers’ IT staff responsible for system maintenance.
 Application Administrators
Preface About This Guide

Related documents
The following documents are related to this document:
 Interactions and Analytics Administration Guide

Documentation feedback
We strive to produce the highest quality documentation products and welcome your
feedback. If you have comments or suggestions about our guides or online help, you can
email us. Please include the following information with your feedback:
 Product name and version number
 Name of online help or guide
 Topic name and page number (if applicable)
 Brief description of content
 Your suggestion for correcting or improving the documentation
Please send your messages to userguides@verint.com.
The email address is only for documentation feedback. If you have a technical question,
please contact Technical Support.

Technical support
Our goal at Verint Systems is to provide you with the best products backed by a high-
quality support network with a variety of resource options. Verint Systems Technical
Support services include email and telephone support.
To learn more about the support options that best suit your needs, visit us at
verint.com/EISsupport.

Verint University
In addition to documentation, online Help, and support services, Verint Systems also
offers both classroom-based and online learning alternatives to suit your specific needs.
To learn more about available training options from Verint Systems, visit us at
verint.com/training.

Custom Data Planner Administration Guide 5

Confidential and Proprietary Information of Verint Systems Inc.

 Chapter 1

Introduction to Custom Data

Planner

Topics
 About Custom Data Planner, page 7
 Installing the Custom Data Planner, page 10
Chapter 1 - Introduction to Custom Data Planner About Custom Data Planner

About Custom Data Planner

The Custom Data Planner is provided as a stand alone tool, to help customers plan their
customized sets. It is necessary to take into account the field attributes, importance,
and shared data field considerations. The output of this planning process can be
imported directly into the system. Using the CD Planner is mandatory when the
default set of Custom Data and Conditional Custom Data fields is not enough,
and you need customized data sets.
The customer has a single project where all their Data fields can be planned. Within this
project, there are a total of 75 Custom Data and 15 Conditional Custom Data fields. By
default, the system is deployed with one set of 25 Custom Data fields and 5 Conditional
Custom Data fields.
Each set within this project can contain a maximum of 25 Custom Data and 5
Conditional Custom Data fields.
Shared data fields allow the same data field to be defined in many sets. The data field is
defined once in a set and is then available for you to use in other sets.
After the sets are defined, the entire project is exported to an XML file and imported into
the Custom Data and Conditional Custom Data Managers.
It is in the Custom Data Manager and Conditional Custom Data Manager that rules and
values are assigned to the data fields.
The following example presents the type of sets an Insurance company might create:
Set 1 – Cars Sedan
Set 2 – Cars Coupe
Set 3 – Cars Hatchback
Set 4 – Health
Set 5 – Travel
Set 6 – Hospital
These sets are made up of specific Custom Data and Conditional Custom Data fields,
where each set can contain up to 25 Custom Data fields and 5 Conditional Custom Data
fields.
When you define a set, you can include up to 25 Custom Data and 5 Conditional Custom
Data fields, selected from the 75 Custom Data fields and 15 Conditional Custom Data
fields (physical fields) that are available for each project. Each physical field is mapped
to three logical field sets. Each data field has its own predefined types and properties.
The distribution of predefined Custom Data fields into the Logical field Sets is shown in
the following table:

Custom Data Planner Administration Guide 7

Confidential and Proprietary Information of Verint Systems Inc.

Chapter 1 - Introduction to Custom Data Planner About Custom Data Planner

Logical Logical Logical Field Type Indexed

Field Set 1 Field Set 2 Set 3

Custom 1 26 51 Varchar (128) Yes

Data
Field ID 2-8 27–33 52-58 Varchar (64) Yes
Number 9-16 34-41 59-66 Varchar (64) No

17-23 42-48 67-73 Varchar (32) No

24-25 49-50 74-75 Integer Yes

The distribution of Conditional Custom Data fields into the Logical field Sets are shown in
the following table:

Logical Logical Logica Type Indexed Used for

Field Field l Field Aggregation
Set 1 Set 2 Set 3

Condition 1 6 11 Varchar Yes Yes

al Custom (64)
Data Field
ID 2 7 12 Varchar Yes No
Number (64)

3 8 13 Varchar Yes No
(64)

4 9 14 Varchar Yes No
(64)

5 10 15 Varchar Yes No
(64)

Because there is a limit of 75 Custom Data fields per project, if you create a large
number of sets, some of the fields within each set must be shared fields (see “About
Shared Fields” on page 17), common to two or more sets.
The following table gives an example of how shared fields are used in different sets.

Data Field Customized Sets

Field ID Name

Cars - Cars - Cars Health Travel Hospital

Sedan Coupe Hatchback

Custom Car Color Y Y Y

Data 3

Custom Age Y Y Y Y Y Y
Data 7 Category

Custom Data Planner Administration Guide 8

Confidential and Proprietary Information of Verint Systems Inc.

Chapter 1 - Introduction to Custom Data Planner About Custom Data Planner

Data Field Customized Sets

Field ID Name

Custom Type of Y Y Y
Data 14 Medical
Insurance

Custom City Y Y Y Y Y Y
Data 23

Custom Car Y Y Y
Data 35 Registratio
n Number

Custom Type of Y
Data 49 Operation

After all the sets within a project are defined, the project is populated (see “Populating a
Project” on page 20). The populate mechanism matches the fields according to the level
of priority set during the definition stage.
Once the project is populated, it is exported to an XML file. This XML file is imported (see
“Importing a Project” on page 23) into the Custom Data Manager and Conditional
Custom Data Manager.
Using these customized sets, the customer can then define the rules and values in either
the Custom Data Manager or the Conditional Custom Data Manager.

Related topics
Defining a Custom Data Field, page 17
Creating and Understanding a New Set, page 15

Custom Data Planner Administration Guide 9

Confidential and Proprietary Information of Verint Systems Inc.

Chapter 1 - Introduction to Custom Data Planner Installing the Custom Data Planner

Installing the Custom Data Planner

1 Obtain the Custom Data Planner setup file from the portal or from your customer
representative, and download it.
2 Click the link to the download location.
The Opening Mail Attachment dialog box opens.
3 Open the CDPlannerSetup.msi file.
The Open File dialog box opens.
4 Click Run.
The Custom Data Planner Setup Wizard opens.
5 Click Next.
The Select Installation Folder screen opens.
6 Select an installation folder location.
The default installation folder is Program Files\Impact360\I360 Custom Data
Planner.
7 Select the relevant usage option and click Next.
The Confirm Installation screen opens.
8 In the Confirm Installation screen, click Next.
The Installing Custom Data Planner screen appears, and tracks the progress of
the installation.
The Installation Complete screen appears at the end of the installation.
9 Click Close.

Custom Data Planner Administration Guide 10

Confidential and Proprietary Information of Verint Systems Inc.

 Chapter 2

Custom Data Planner

Workflow

Topics
 Accessing the Custom Data Planner, page 12
 Creating and Understanding a New Project, page 13
 Creating and Understanding a New Set, page 15
 Defining and Understanding Fields, page 17
 Populating a Project, page 20
 Exporting a Project, page 22
 Importing a Project, page 23
 Modifying and Deleting Projects, Sets and Fields, page 24
Chapter 2 - Custom Data Planner Workflow Accessing the Custom Data Planner

Accessing the Custom Data Planner

To access the Custom Data Planner, do one of the following:
 Click Custom Data Planner on the desktop.
 Select Custom Data Planner from Start > Programs > Impact360 >
Impact360 Custom Data Planner.
The Custom Data Planner application opens to a blank page, with the Project option
disabled.

Custom Data Planner Administration Guide 12

Confidential and Proprietary Information of Verint Systems Inc.

Chapter 2 - Custom Data Planner Workflow Creating and Understanding a New Project

Creating and Understanding a New Project

This topic covers the following:
 Creating a New Project, page 13
 Understanding the Project Page, page 13

Creating a New Project

1 Do one of the following:
 Click New File .
 From the Menu bar, select File > New.
The Custom Data Planner – New Project.cpd window opens.
2 Do one of the following:
 Click Save.
 From the Menu bar, select File > Save As.
The Save As dialog box opens.
3 Type the name of the new project, based on the customer’s name. For example,
AAA Insurance Company.
4 Click Save.
A confirmation message opens.
5 Click OK.
The Project page opens and displays the name of the new project at the top of the
Custom Data Planner window.
For information on the Project page see “Understanding the Project Page” on
page 13.
6 To save an existing project, do one of the following:
 Click Save in the application toolbar.
 From the menu, select File > Save.
The Save icon is disabled until you make additional changes to the project.

Understanding the Project Page

The Project Page has the following tabs:
 Define Set Tab, page 14
 Fields Summary Tab, page 14
 Field Population Report Tab, page 14

Custom Data Planner Administration Guide 13

Confidential and Proprietary Information of Verint Systems Inc.

Chapter 2 - Custom Data Planner Workflow Define Set Tab

Define Set Tab

This tab is used to create and manage sets in this tab (see “Creating and Understanding
a New Set” on page 15).
The Define Set tab is divided the following sections:
 Customizing Set: To create, manage, and lock customized sets in this section.
 Custom Data Fields: To define Custom Data fields in this section.
 Conditional Custom Data Fields: To define Conditional Custom Data fields in this
section.
 Free Custom Data fields: Use the counters to track the number of available
Custom Data fields and when they were last modified.

Fields Summary Tab

This tab is used to see a summary of all the Custom Data and Conditional Custom Data
fields that are defined for a particular set in this tab.

Field Population Report Tab

This tab displays a report regarding the success or failure of the fields that are
populated in this tab (see “Defining a Custom Data Field” on page 17).

Related topics
Populating a Project, page 20
Defining a Custom Data Field, page 17

Custom Data Planner Administration Guide 14

Confidential and Proprietary Information of Verint Systems Inc.

Chapter 2 - Custom Data Planner Workflow Creating and Understanding a New Set

Creating and Understanding a New Set

This topic covers the following:
 About Sets, page 15
 The Lock Mechanism, page 15
 Creating a New Set, page 15

About Sets
The first step in creating a project is defining the first set. A set is a collection of Custom
Data and Conditional Custom Data fields. The Custom Data and Conditional Custom
Data fields are tagged to interactions according to customer's specific needs, typically
used for tagging interactions according to their Lines of Business.
After you define a set, you can allocate data fields to the set.
Users can define up to 100 sets in a project.
To add, edit, and delete Custom Data and Conditional Custom Data fields, select the
relevant Action Icon located in the toolbar in each section.

The Lock Mechanism

Sets and fields are locked after they are populated, to ensure that the fields are not
included in further populating procedures.
This is relevant when the set/field is already in use in the system and you do not want to
change it, or if you decide that the entity must be of a specific type.
It is possible to lock/unlock a set or a specific field.
If a set is locked, all the fields inside the set are locked as well. To edit the fields, you
must first unlock the set.
When an exporting process succeeds, by default, all the sets and fields are locked.

Creating a New Set

1 Do one of the following:
 In the Define Set tab, click the Manage button.
 From the menu bar, select Project > Manage Sets.
The Manage Sets screen opens.
2 At the bottom of the screen, click Add set to project .
A new active row for a set is added to the grid.
3 In the Name field, type the name of the set (Up to 128 characters).
4 In the Description field, type a description (Up to 1024 characters).

Custom Data Planner Administration Guide 15

Confidential and Proprietary Information of Verint Systems Inc.

Chapter 2 - Custom Data Planner Workflow Creating a New Set

5 If required, select the Locked check box. It is not possible to change the set
properties or the fields’ properties once a set is locked.
6 Click the Apply button to save the set and remain in the Manage Sets screen.
The Last Modified field shows the last time the set was updated.
7 To add additional sets, repeat steps 2 to 7 until all the sets are defined.
8 Click OK.
The following changes occur in the Define Set tab:
 In the Customizing Set section, the sets are available in the Select set list and
the description for each set is displayed below the list.
 The Custom Data Fields and Conditional Custom Data Fields sections are
empty.
 The Free Custom Data Fields and Free Conditional Custom Data Fields are
active. The number of free fields available for use per set is displayed next to the
field type.
 When no free fields of a specific type are available, users are unable to create
more fields of this type in this set and the option is removed from the combo
choices.
9 Save the project.

Related topics
Modifying a Set, page 25
Deleting a Set, page 26
Defining a Custom Data Field, page 17
Defining a Conditional Custom Data Field, page 18

Custom Data Planner Administration Guide 16

Confidential and Proprietary Information of Verint Systems Inc.

Chapter 2 - Custom Data Planner Workflow Defining and Understanding Fields

Defining and Understanding Fields

There are 75 Custom Data fields and 15 Conditional Custom Data fields available per
project. This topic describes:
 About Shared Fields, page 17
 Defining a Custom Data Field, page 17
 Defining a Conditional Custom Data Field, page 18

About Shared Fields

Once a field is defined in one set, the same field can be used in many other sets. This
field is marked as a Shared Field. It is possible to use the same Shared Fields in every
set that you create within a project. Therefore the same field, with the identical
properties, can be used up to 100 times, because a project can contain a maximum of
100 sets.
A field that is used only once is called a Unique field.
When you add a field that is already defined in another set, the Shared indicator for the
field is automatically checked in each set that includes the shared field. This indicator is
read only, and cannot be unchecked.
Rules and values that are defined in one Shared Field are included in all the relevant
related fields in all customized sets.
For all the field properties, except the Field Name, when you update a Shared Field in
one set, it is automatically updated in all other sets where it is defined. When you
change the Field Name of a shared field, you create a new Unique field. The original
Shared Field is not updated, and appears in the list of available fields, along with the
new field that has the same properties as the Shared Field you created it from. To edit
the name of a shared data field, you must go through each set that includes that field
and manually rename the CD field.

Defining a Custom Data Field

Up to 25 Custom Data fields can be defined per set. These 25 can be selected from a
pool of 75 Custom Data Fields available per project.
These can include Custom Data fields that are unique to a particular set, or shared
Custom Data fields that are included in many different sets.
Each Custom Data field has the following attributes:
 No
 Locked (true/false)
 Field Name (string 128)
 Shared (true/false)
 Populating Priority (high, medium, low)

Custom Data Planner Administration Guide 17

Confidential and Proprietary Information of Verint Systems Inc.

Chapter 2 - Custom Data Planner Workflow Defining a Conditional Custom Data Field

 Indexed (true/false)
 Type (string 128, string 64, string 32, integer)
 Status (populated, true/false)
 Description (string 1024)

To define a Custom Data Field:

1 Open the project and select the Define Set tab.
2 In the Customizing set section, select the set from the Select Set list.
3 In the Custom Data Fields section, click Add field to set .
A new active row is added to the grid.
4 In the Field Name column, do one of the following:
 Click the field and type a new name.
 Select a previously defined field from the list.
If you select a shared field, the Shared option is checked.
5 In the Description field, click the field. For a new field, type a new description.
When you select a shared field, the description parameter is already defined.
6 In the Populating Priority column, select a priority value from the list. See “Defining
a Custom Data Field” on page 17.
7 Select the field type for the Custom Data field. For a list of the types of fields
available, see “About Custom Data Planner” on page 7.
8 Select the Indexed option to create an indexed field.
The numbers of indexed and unindexed fields are predefined. For a list of the
indexed fields available, see “About Custom Data Planner” on page 7.
9 To lock the field, select the Locked option.
You cannot change a field if it is locked. To edit a locked field, you must first unlock
it.
10 Repeat steps 3 to 9 to add more fields to the set.
11 Click Save to save the new fields.
The number of remaining free Custom Data Fields is updated in the Free Custom
Data Fields section.

Defining a Conditional Custom Data Field

Up to 5 Conditional Custom Data fields can be defined per set. These 5 fields can be
selected from a pool of 15 Conditional Custom Data fields available per project.
These can include unique Conditional Custom Data fields that are unique to a particular
set, or shared Conditional Custom Data fields that are included in many sets.

Custom Data Planner Administration Guide 18

Confidential and Proprietary Information of Verint Systems Inc.

Chapter 2 - Custom Data Planner Workflow Defining a Conditional Custom Data Field

The Conditional Custom Data fields are named in the Custom Data Planner. The field
names are unique per project, however, in the case of shared items, the same field
name can appear in multiple sets.
Each Conditional Custom Data field has the following attributes:
 No
 Locked (true/false)
 Field Name (string 128)
 Shared (true/false)
 Populating Priority (high, medium, low)
 Aggregated (true/false)
 Status (populated, true/false)
 Description (string 1024)

To create a new Conditional Custom Data Field:

1 Open the project and select the Define Set tab.
2 In the Customizing set section, select the set from the Select Set list.
3 In the Conditional Custom Data Fields section, click Add field to set .
A new active row is added to the grid.
4 In the Field Name column, do one of the following:
 Click the field and type a new name.
 Select a previously defined field from the list.
If you select a shared field, the Shared option is checked.
5 In the Description field, click the field. For a new field, type a new description.
When you select a shared field, the description parameter is already defined.
6 In the Populating Priority column, select a priority value from the list. See
“Defining a Custom Data Field” on page 17.
7 To lock the field, select the Locked option.
You cannot change a field if it is locked. To edit a locked field, you must first unlock
it.
8 To aggregate the field, select the Aggregation option.
9 Repeat steps 3 to 8 to add more fields.
10 Click Save to save the fields.
The number of available Conditional Custom Data Fields is updated in the Free
Conditional Custom Data Fields section.

Custom Data Planner Administration Guide 19

Confidential and Proprietary Information of Verint Systems Inc.

Chapter 2 - Custom Data Planner Workflow Populating a Project

Populating a Project
This topic covers the following:
 About Populating a Project, page 20
 About the Populate Algorithm, page 20
 Errors and Feedback after Populating, page 21

About Populating a Project

A project needs to be repopulated after any changes are made to a set or data field.
Once fields have been assigned to different sets, they need to be populated. Fields are
populated in the order of the priority set.
When you click the Populate button, the process of verifying the sets and fields begins.
If the populate processes succeeds without any errors, a success message is displayed
in the report tab.
You can then export the outcome to an XML file, and then import into the Custom Data
manager and Conditional Custom Data Manager.
If errors are found, they are displayed in the report tab. You must fix these errors and
repopulate the project.

About the Populate Algorithm

The populate mechanism matches the fields according to the following priority rules:
 Locked fields do not participate in the populate procedure.
 The tool reviews all the fields from each set according to their importance.
 A field with a higher priority is always placed before a field with a lower priority.
 Shared fields (from all sets) are handled first.
 The following conditions must be met before it is possible to export the project to an
XML file:
 The fields with the highest priority are assigned to available physical data fields.
 All the errors are resolved.
 Type (for Custom Data only):
 The tool tries to match the requested size.
 If the same size is not available, the tool tries to match a longer string. In this
case, a message appears in the final report.
 Indexed (for Conditional Custom Data only): If the requested field is not indexed,
and all the not indexed fields of the same type are already assigned, the tool tries
to find an indexed field.

Custom Data Planner Administration Guide 20

Confidential and Proprietary Information of Verint Systems Inc.

Chapter 2 - Custom Data Planner Workflow Errors and Feedback after Populating

The same logic described in rules the 5 rules (above) applies to the aggregation of
Conditional Custom Data.
If the Populate process fails, the algorithm attempts to populate the fields according to
the following rules:
 By size: If there is no free field type of a specific size with the selected option
(Indexed/Aggregated), the algorithm attempts to populate a field of the same size,
without the option. If no field of the same size is available, the algorithm then
attempts to populate the field according to rule 2.
For example, if an indexed Varchar (64) string is requested and is not available, the
algorithm populates an unindexed Varchar (64) string.
 By option: If the requested field type is not available, and a field that matches rule
1 is not available, when possible, the algorithm attempts to populate the next
available free field type of a smaller size, with the same option.
For example, if an indexed Varchar (64) string is requested, if it is available, the
indexed Varchar (64) string is proposed.
If the requested field type is not available, and the algorithm cannot match rule 1
(that is, no unindexed Varchar (64) string is available), the algorithm proceeds to
rule 2, and attempts to populate an indexed Varchar (32) string.
The algorithm attempts to populate an unindexed Varchar (32) string only if no
indexed Varchar (32) string is available.

Errors and Feedback after Populating

If the populate fails, all the errors are displayed in the report tab. Each error is also
displayed near the relevant field in the Status column.
Each error starts with what the field looked for, and specifies the best solution.
Error examples:
1 Field XXX in set XXX looked for string 16. All string 16 fields were occupied so string
32 was chosen.
2 Field XXX in set XXX looked for indexed string 64. Only non indexed string 64 fields
are available.
3 Field XXX in set XXX looked for indexed string 64. Only non indexed string 32 fields
are available.
4 Field XXX in set XXX looked for integer. There are no integers left.
5 The following locked fields (Set XXX field XXX, Set YYY field XXX) prevent
populating field ZZZ from set ZZZ.

Custom Data Planner Administration Guide 21

Confidential and Proprietary Information of Verint Systems Inc.

Chapter 2 - Custom Data Planner Workflow Exporting a Project

Exporting a Project
After you define all the sets in the project and successfully populate them, the project
can be exported to an XML file. This XML file can then be imported into the Custom Data
Manager and Conditional Custom Data Manager.
A project can only be exported after all the data fields are successfully populated.

NOTE When you create a new project or make changes to an existing project,
you must export the project to an XML file and import it into the Custom
Data and Conditional Custom Data Manager.

To Export a Project:
1 Click Export.
A Save As dialog box opens.
2 Type the name of the file and save it with the .xml extension.
3 Click OK.

Custom Data Planner Administration Guide 22

Confidential and Proprietary Information of Verint Systems Inc.

Chapter 2 - Custom Data Planner Workflow Importing a Project

Importing a Project
Customized Sets are contained in a project. Once a project is defined in the Custom
Data Planner, it needs to be imported into both the Custom Data Manager and
Conditional Custom Data Manager. If the project is imported into Conditional Custom
Data Manager first, the names of the sets appear in the Custom Data Manager, but the
fields are not imported.
A project can only be imported after it has been populated and exported into an XML
file.
To Import a Project:
1 From the Custom Data Manager or the Conditional Custom Data Manager, click the
Import button.
The relevant Import Custom Data or the Import Conditional Custom Data -
web page dialog box opens.
2 Browse to the correct .xml file, select it, and click OK.
The following confirmation message is displayed: The file is successfully
imported.
3 Click Close.
The Customized sets are available for selection from the relevant Custom Data Sets
or Conditional Custom Data Sets list.

Custom Data Planner Administration Guide 23

Confidential and Proprietary Information of Verint Systems Inc.

Chapter 2 - Custom Data Planner Workflow Modifying and Deleting Projects, Sets and Fields

Modifying and Deleting Projects, Sets and

Fields
This section describes:
 Modifying an Existing Project, page 24
 Modifying a Set, page 25
 Modifying an Existing Field, page 25
 Deleting a Set, page 26
 Deleting an Existing Field, page 26

Modifying an Existing Project

Projects can be modified before or after they are exported to an XML file.

NOTE When you create a new project or make changes to an existing project,
you must export the project to an XML file and import it into the Custom
Data and Conditional Custom Data Manager.
If you need to add or modify sets within a project, take one of the actions
to ensure that you do not lose data:
 Make a backup of the original project before you begin.
 Save the modified project with a new name.

To save a project with a new name:

1 To open the project, do one of the following:
 Click Open File.
 From the Menu bar, select File > Open.
The Windows Open dialog box appears.
2 Select the file you want to open.
The project opens in the Custom Data Planner.
3 To save the project with a new name, select File Save.
The Save As dialog box opens.
4 Type the name of the new project.
5 Click Save.
A confirmation message opens, stating that the project is saved.
6 Click OK.
The project page opens with the name of the new project at the top of the Custom
Data Planner page.

Custom Data Planner Administration Guide 24

Confidential and Proprietary Information of Verint Systems Inc.

Chapter 2 - Custom Data Planner Workflow Modifying a Set

NOTE Do not change the name of your project in Windows Explorer. This
changes only the file name, and not the project name.

What do you want to do?

Creating and Understanding a New Set, page 15
Modifying a Set, page 25
Deleting a Set, page 26

Modifying a Set
To modify the set name or description:
If the set is locked, you must first unlock the set in the Define Set tab by deselecting
the Locked option (See “The Lock Mechanism” on page 15).
1 Do one of the following:
 Click the Manage button in the Define Set tab.
 From the menu bar, select Project > Manage Sets.
The Manage Sets screen opens.
2 Modify the name or the description of the required set.
3 Click OK.
The Manage Sets screen closes and you return to the Define Sets tab.
4 Save the project.

Related topics
Deleting a Set, page 26
Defining a Custom Data Field, page 17
Defining a Conditional Custom Data Field, page 18

Modifying an Existing Field

It is possible to update the properties of an existing field. However it is not possible to
update a locked field.
A shared field that is modified will be updated in all sets.
To modify a data field:
1 Open the project and select the Define Set tab.
2 In the Customizing set section, select the set from the Select Set list.
3 In the Custom Data Fields or the Conditional Custom Data Fields section,
select the data field you want to modify.

Custom Data Planner Administration Guide 25

Confidential and Proprietary Information of Verint Systems Inc.

Chapter 2 - Custom Data Planner Workflow Deleting a Set

4 Click the field you want to edit and make the necessary changes.
5 Click OK as required.
6 Click Update field .
7 Click Save.

Deleting a Set
NOTE Deleting a set deletes the set from the project, including the definitions of
the fields that are defined for the set. These fields are not deleted from
the pool of available fields. Make sure you have selected the correct set to
delete, before you continue.

To delete a data set:

1 Do one of the following:
 Click the Manage button in the Define Set tab.
 From the menu bar, select Project > Manage Sets.
The Manage Sets screen opens.
2 To select the set, click the empty cell at the start of the row in the grid.
A triangle appears in the cell and the row is highlighted.
3 To remove the set from the project, click Remove set from project .
The following message appears, asking you to confirm the action: This action will
permanently delete the set from the project. Do you want to continue?
4 Click Yes.
5 Repeat steps 2 and 4 to remove more sets.
6 Click OK.
The Manage Sets screen closes and you return to the Define Set tab.
7 Save the project.

Deleting an Existing Field

NOTE It is not possible to delete a locked field.
Deleting a shared field only deletes it from the current set.

To Delete a Data Field:

1 Open the project and select the Define Set tab.
2 In the Customizing set section, select the set from the Select Set list.

Custom Data Planner Administration Guide 26

Confidential and Proprietary Information of Verint Systems Inc.

Chapter 2 - Custom Data Planner Workflow Deleting an Existing Field

3 To select the data field to delete, in the Custom Data Fields or the Conditional
Custom Data Fields section, click the empty cell at the start of the field row in the
grid.
A triangle appears in the cell and the row is highlighted.
4 To delete the field, click Remove set from set .
5 The following message appears, asking you to confirm the action: This action will
delete this Custom Data (or Conditional Custom Data) field from this set. Do you
want to continue?
6 Click Yes.
7 Repeat steps 2 and 5 to remove more sets.
8 Save the project.

Custom Data Planner Administration Guide 27

Confidential and Proprietary Information of Verint Systems Inc.

Verint Global Headquarters
330 South Service Road
Melville, NY 11747 USA

info@verint.com
1-800-4VERINT

www.verint.com

© 2015 Verint Systems Inc.

All Rights Reserved Worldwide.
Confidential and Proprietary Information of Verint Systems Inc.

The contents of this material are confidential and proprietary to Verint Systems Inc.
and may not be reproduced, published, or disclosed to others without express
authorization of Verint Systems Inc.