Creating a parent-child relationship between data sources
Parent and Child Phone Data Sources and Recorder Integration Service associations refer to the organizational structure and interaction In Speech Analytics, an interaction represents a single part of the contact between one employee and the same customer. In Text Analytics, an interaction is the communication session between one or more employees and the same customer with a unifying contextual element. between data sources and recording services.
Guidelines about parent and child phone data sources and Recorder Integration Service associations
-
If the parent and child data sources are of the type Phone, the child data source Third-party systems that provide data to the system, including employee and device states, and data change events. Typical data sources are phone switches, PBXs, or LANs. is automatically associated to the same Recorder Integration Service as the parent data source.
-
When you specify a parent data source for a child Phone data source, the Recorder Integration Service node specified for the child Phone data source is grayed out and cannot be changed. (As noted above, the Recorder Integration Service specified for the child data source is the same as that specified for the parent data source.)
-
If you select the No Parent option for the child phone data source, the data source is no longer a child data source. However, the former child data source remains associated to the same Recorder Integration Service that it was associated to when it was in the parent-child relationship.
Procedure
-
Create the Phone or Collection data source you want to act as the parent.
-
Create one or more child Phone data sources.
-
As the Data Source Parent, select the data source created in step 1 from the dropdown list.
-
Click Save.
A data source nested under Data Source Name on the left indicates a parent-child relationship between data sources.