Skip to end of metadata
Go to start of metadata

Overview

Data management policies are very powerful tools for automated data management. Administrators can define rules that execute various actions based on customizable filtering criteria. The policies are executed by the Verba Storage Management Service and/or the Verba Import Service on either Verba Recording servers or Media Repositories.

Policy execution is turned off by default, it has to be enabled in the server configuration.

The system supports  the following data management policy types:

TypeDescriptionPolicies
Data RetentionData retention policies are responsible for managing the lifecycle of the data in the system. Retention policies allow moving data from one storage location to another, managing retention period or deleting/disposing of recordings.
Data ProcessingData processing policies can provide additional information by analyzing certain aspects of the data (e.g. transcribing speech to text), or convert recordings from one format to another.
Data ImportData import policies drive the data import process which allows ingesting different data into the system.

 

Enabling data management and processing policy execution on servers

Configured data management policies have to be enabled in the Verba Storage Management Service in order to run them. Please follow the steps below to enable the feature:

Step 1 - Login to the web interface with System administrator rights.

Step 2 - Navigate to the Configuration / Servers menu item and select the Media Repository server (or Single server) from the list.

Step 3 - Click on the Change Configuration Settings tab and find the Storage Management / Data Retention section.

Step 4 - Set the Enabled setting to Yes.

Step 5 - Configure the Schedule setting.

Step 6 - Save the changes by clicking on the  icon.

Step 7 - A notification banner will appear on the top. Click on the click here link, so you will be redirected to the Configuration Tasks tab. Click on the Execute button in order to execute the changes.

For further information on the configuration settings, check Storage management settings.

Enabling data import policy execution on servers

Step 1 - Login to the web interface with System administrator rights.

Step 2 - Navigate to the Configuration / Servers menu item and select the Media Repository server (or Single server) from the list.

Step 3 - Go to the Service Activation tab, then activate the Verba Import Service by clicking on the  icon.

Step 4 - Go to the Change Configuration Settings tab, configure the schedule settings under the CDR and Archived Content Importer \ CDR Import and Archive Import nodes.

Step 5 - Save the changes by clicking on the  icon.

Step 6 - A notification banner will appear on the top. Click on the click here link, so you will be redirected to the Configuration Tasks tab. Click on the Execute button in order to execute the changes.

Step 7 - Click on the Service Control tab.

Step 8 - Start the Verba Import Service by clicking on the  icon.

For further information on the configuration settings, check CDR and Archived Content Importer settings.

Find and list data management policies

Select the Data management / Data Management Policies menu item. You can use the search form below the title, to filter data retention policies: just select your filter and click Find.

When you click on a policy (or the Add New Data Management Policy button to create a new one), the Data Management Policy Configuration page opens.

Creating a data management policy

You can create a new data retention policy by clicking on the Add New Data Management Policy link on the Administration / Data Management Policies page. After selecting the link, the following page is opened.

The following table describes the policy settings that are common for all types of policies:

Setting

Description

Requirements

Name

The name of the data management policy.

Required field.
Minimum length: 3
Maximum length: 256
Must be unique in the system.

EnabledIndicates whether the policy is enabled or disabled. Only enabled policies are executed.Required field.
PriorityDefines the execution order of the policies. This should be an integer number. Higher priority policies are processed first if multiple policies apply to the same call.Required field.
Action

Defines the policy action. Some of the configuration options are only available with certain actions. The layout of the configuration page changes based on the selected action.

For more information on each of the actions and their specific configuration options refer to the individual description pages.

Required field.

Next, by adding filtering criteria, you will need to define the calls the policy should apply to.

Adding Data Management Filtering criteria

You can configure a filter that defines what calls should be included in your data management policy.

  • Conversations Older than (not available for upload and phonetic index related policy actions): This filtering option defines the age of the calls. Only calls older than the defined value will be handled for the policy during execution.
  • Conversations more recent than (only available for phonetic index related actions): This filtering option defines the age of the calls. Only calls more recent than the defined value will be handled for the policy during execution.

Click on the + icon to add a new filtering option. You can add as many policies as you want. Multiple field filters are used with 'AND' operator.

The rest of the filtering options are based on various metadata or CDR (Call Detail Record) information that is stored in the database for each conversation. The table below contains a list of potentially available filtering options including custom metadata fields.

Field NameDescription
FromFilters based on the number of the caller party in the call.
From InfoFilters based on the number of the called party in the call.
From (digits)Filters based on the number of digits in the phone number of the initiator of the conversation.
From Device IDFilters based on the device ID if the initiator of the conversation.
From IPFilters based on the IP address of the caller party in the call.
ToFilters based on the name of the caller party in the call.
To InfoFilters based on the name of the called party in the call.
To (digits)Filters based on the number of digits in the phone number of the target of the conversation.
To Device IDFilters based on the device ID if the target of the conversation.
To IPFilters based on the IP address of the called party in the call.
Both To or FromFilters based on the number of any party participating in the call.
Both To or From InfoFilters based on the name of any party participating in the call.
UserFilters based on the user to whom the call belongs.
ExtensionFilters based on the extension numbers in a call.
Provides a selection list of your configured extensions, otherwise similar to the 'Any party number' field below.
GroupFilters based on the group where a call belongs.
Agent IDFilters based on the Agent ID (if present, obtained from contact center systems as extra metadata)
Start TimeFilters based on the start time of the conversation.
DirectionFilters based on the direction of the call.
Duration IntervalFilters based on length of the call.
Conversation Type

Filters based on the type of the conversation. Available options:

  • Voice
  • Video
  • Instant Messaging
  • Desktop Screen
  • Screen & Application Share (Lync/SfB)
  • Whiteboard (Lync/SfB)
  • Poll / Q&A (Lync/SfB)
  • File Share (Lync/SfB)
OndemandFilters based on whether a call was recorded as on-demand.
Marked for recordingFilters based on whether an on-demand call was marked for recording.
ProtectedFilters based on the protected flag. This flag can be applied to conversations by usersonaperconversationbasisthroughtheconversation search interface.
LabelFilters based on labels applied to the conversation.
Silence ratioFilters based on the silence ratio in a conversation.
Talkover ratioFiltersbasedonthetalkoverratiooftheconversation.
Longest SilenceFilters based on the longest silence present in a conversation.
Recording ServerFilters based on the name of the server that recorded the call.
Media file nameFilters based on the name of the stored media file.
Storage targetFilters based on which storage folder a call is currently stored in.
Source PlatformFilters based on which Telephony/Unified Communications system the conversation was recorded in (Cisco,Sfb, Avaya, etc.)
Phone XML listFilters based on a custom user-created metadata field (the name of the field is customizable).
Text1Filters based on a custom user-created metadata field (the name of the field is customizable).
TextArea1Filters based on a custom user-created metadata field (the name of the field is customizable).
PrivateFilters based on the Private flag on a conversation.
Important

Filters based on the Important flag on a conversation.

 

 

If you do not want a Delete policy to delete protected conversations, you have to explicitly add a 'Protected' = 'No' filter.
After filling out the form, click the Save button to save the data retention policy into the database.

Custom Schedules

You can set up a custom schedule for each policy.

Under Period Settings you can configure the frequency, by clicking on the ... button at the end of the line.
The Configuration wizard will appear, here you can set the desired value.
 

If you leave the Custom Schedule option unchecked, then the central settings will take effect.
By setting a custom schedule, you overwrite the central configuration for this policy.

Modifying and deleting data management policies

To edit a data retention entry, you have to click on the desired row of the list showing registered data management policies. After clicking on the row, a new page opens automatically. 

To make changes effective, push the Save button. All conditions, which are described in the previous part, have to be met.

You can delete the data management policy by clicking on the Delete button.

Alerts

The system sends notification alerts when a data management policy is created, updated or deleted.