Documentation:GIM:Library:View-ADMIN AUDIT LOG:8.5DRAFT |
ADMIN_AUDIT_LOG |
|
[Show] This administrative view provides access to the data stored in the CTL_AUDIT_LOG table, which allows facts and dimensions to be described by data lineage attributes. Each row represents a logical transaction that is committed by Genesys Info Mart, identifying the ETL job that is involved in the transaction, including the minimum and maximum DATE_TIME values (which give a date-time range for the data that is committed in the transaction), and providing the processing status (an internal indicator of the kind of data that is processed). The columns in this view are identical to those in the underlying table.
|
|
|
|
|
|
?'"`UNIQ--source-00000004-QINU`"'? |
Documentation:GIM:Library:View-ADMIN AUDIT LOG:8.5PDMSource |
ADMIN_AUDIT_LOG |
|
[Show] This administrative view provides access to the data stored in the CTL_AUDIT_LOG table, which allows facts and dimensions to be described by data lineage attributes. Each row represents a logical transaction that is committed by Genesys Info Mart, identifying the ETL job that is involved in the transaction, including the minimum and maximum DATE_TIME values (which give a date-time range for the data that is committed in the transaction), and providing the processing status (an internal indicator of the kind of data that is processed). The columns in this view are identical to those in the underlying table.
|
|
|
|
|
|
?'"`UNIQ--source-00000004-QINU`"'? |
Documentation:GIM:Library:View-ADMIN AUDIT LOG:DRAFT |
ADMIN_AUDIT_LOG |
|
[Show] This administrative view provides access to the data stored in the CTL_AUDIT_LOG table, which allows facts and dimensions to be described by data lineage attributes. Each row represents a logical transaction that is committed by Genesys Info Mart, identifying the ETL job that is involved in the transaction, including the minimum and maximum DATE_TIME values (which give a date-time range for the data that is committed in the transaction), and providing the processing status (an internal indicator of the kind of data that is processed). The columns in this view are identical to those in the underlying table.
|
|
|
|
|
|
?'"`UNIQ--source-00000004-QINU`"'? |
Documentation:GIM:Library:View-ADMIN AUDIT LOG:PDMSource |
ADMIN_AUDIT_LOG |
|
[Show] This administrative view provides access to the data stored in the CTL_AUDIT_LOG table, which allows facts and dimensions to be described by data lineage attributes. Each row represents a logical transaction that is committed by Genesys Info Mart, identifying the ETL job that is involved in the transaction, including the minimum and maximum DATE_TIME values (which give a date-time range for the data that is committed in the transaction), and providing the processing status (an internal indicator of the kind of data that is processed). The columns in this view are identical to those in the underlying table.
|
|
|
|
|
|
?'"`UNIQ--source-00000003-QINU`"'? |
Documentation:GIM:Library:View-ADMIN ETL JOB HISTORY:8.5DRAFT |
ADMIN_ETL_JOB_HISTORY |
|
This view provides information about the execution of each ETL job. A row is added to this view after each ETL job completes. Currently running ETL jobs do not appear in this view. Rows in this view are written once and are not updated. |
|
|
|
|
|
?'"`UNIQ--source-00000004-QINU`"'? |
Documentation:GIM:Library:View-ADMIN ETL JOB HISTORY:8.5PDMSource |
ADMIN_ETL_JOB_HISTORY |
|
This view provides information about the execution of each ETL job. A row is added to this view after each ETL job completes. Currently running ETL jobs do not appear in this view. Rows in this view are written once and are not updated. |
|
|
|
|
|
?'"`UNIQ--source-00000004-QINU`"'? |
Documentation:GIM:Library:View-ADMIN ETL JOB HISTORY:DRAFT |
ADMIN_ETL_JOB_HISTORY |
|
This view provides information about the execution of each ETL job. A row is added to this view after each ETL job completes. Currently running ETL jobs do not appear in this view. Rows in this view are written once and are not updated. |
|
|
|
|
|
?'"`UNIQ--source-0000003F-QINU`"'? |
Documentation:GIM:Library:View-ADMIN ETL JOB HISTORY:PDMSource |
ADMIN_ETL_JOB_HISTORY |
|
This view provides information about the execution of each ETL job. A row is added to this view after each ETL job completes. Currently running ETL jobs do not appear in this view. Rows in this view are written once and are not updated. |
|
|
|
|
|
?'"`UNIQ--source-00000003-QINU`"'? |
Documentation:GIM:Library:View-ADMIN ETL JOB STATUS:8.5DRAFT |
ADMIN_ETL_JOB_STATUS |
|
This view provides information about the most recent execution of each ETL job. A row is added to this view after each ETL job starts and is updated as the job status changes. |
|
|
|
|
|
?'"`UNIQ--source-00000032-QINU`"'? |
Documentation:GIM:Library:View-ADMIN ETL JOB STATUS:8.5PDMSource |
ADMIN_ETL_JOB_STATUS |
|
This view provides information about the most recent execution of each ETL job. A row is added to this view after each ETL job starts and is updated as the job status changes. |
|
|
|
|
|
?'"`UNIQ--source-00000039-QINU`"'? |
Documentation:GIM:Library:View-ADMIN ETL JOB STATUS:DRAFT |
ADMIN_ETL_JOB_STATUS |
|
This view provides information about the most recent execution of each ETL job. A row is added to this view after each ETL job starts and is updated as the job status changes. |
|
|
|
|
|
?'"`UNIQ--source-00000041-QINU`"'? |
Documentation:GIM:Library:View-ADMIN ETL JOB STATUS:PDMSource |
ADMIN_ETL_JOB_STATUS |
|
This view provides information about the most recent execution of each ETL job. A row is added to this view after each ETL job starts and is updated as the job status changes. |
|
|
|
|
|
?'"`UNIQ--source-00000003-QINU`"'? |
Documentation:GIM:Library:View-ADMIN ETL STEP HISTORY:8.5DRAFT |
ADMIN_ETL_STEP_HISTORY |
|
[Show] This view provides information about the execution of each ETL job step. Rows are added to this view for completed ETL job steps only. As each ETL job completes, it adds rows for the completed steps of all currently running ETL jobs, including itself, that have not already been added to the view. Currently running ETL jobs may have steps that are in process or are waiting, and they do not yet appear in the view. Rows in this view are written once and are not updated.
|
|
|
|
|
|
?'"`UNIQ--source-00000004-QINU`"'? |
Documentation:GIM:Library:View-ADMIN ETL STEP HISTORY:8.5PDMSource |
ADMIN_ETL_STEP_HISTORY |
|
[Show] This view provides information about the execution of each ETL job step. Rows are added to this view for completed ETL job steps only. As each ETL job completes, it adds rows for the completed steps of all currently running ETL jobs, including itself, that have not already been added to the view. Currently running ETL jobs may have steps that are in process or are waiting, and they do not yet appear in the view. Rows in this view are written once and are not updated.
|
|
|
|
|
|
?'"`UNIQ--source-00000004-QINU`"'? |
Documentation:GIM:Library:View-ADMIN ETL STEP HISTORY:DRAFT |
ADMIN_ETL_STEP_HISTORY |
|
[Show] This view provides information about the execution of each ETL job step. Rows are added to this view for completed ETL job steps only. As each ETL job completes, it adds rows for the completed steps of all currently running ETL jobs, including itself, that have not already been added to the view. Currently running ETL jobs may have steps that are in process or are waiting, and they do not yet appear in the view. Rows in this view are written once and are not updated.
|
|
|
|
|
|
?'"`UNIQ--source-00000004-QINU`"'? |
Documentation:GIM:Library:View-ADMIN ETL STEP HISTORY:PDMSource |
ADMIN_ETL_STEP_HISTORY |
|
[Show] This view provides information about the execution of each ETL job step. Rows are added to this view for completed ETL job steps only. As each ETL job completes, it adds rows for the completed steps of all currently running ETL jobs, including itself, that have not already been added to the view. Currently running ETL jobs may have steps that are in process or are waiting, and they do not yet appear in the view. Rows in this view are written once and are not updated.
|
|
|
|
|
|
?'"`UNIQ--source-00000003-QINU`"'? |
Documentation:GIM:Library:View-ADMIN EXTRACT HISTORY:8.5DRAFT |
ADMIN_EXTRACT_HISTORY |
|
This view provides information about the data that is extracted from each source database table. A row is added to this view after Job_ExtractICON successfully completes extracting a source data table. Rows in this view are written once and are not updated. |
|
|
|
|
|
?'"`UNIQ--source-00000034-QINU`"'? |
Documentation:GIM:Library:View-ADMIN EXTRACT HISTORY:8.5PDMSource |
ADMIN_EXTRACT_HISTORY |
|
This view provides information about the data that is extracted from each source database table. A row is added to this view after Job_ExtractICON successfully completes extracting a source data table. Rows in this view are written once and are not updated. |
|
|
|
|
|
?'"`UNIQ--source-0000003B-QINU`"'? |
Documentation:GIM:Library:View-ADMIN EXTRACT HISTORY:DRAFT |
ADMIN_EXTRACT_HISTORY |
|
This view provides information about the data that is extracted from each source database table. A row is added to this view after Job_ExtractICON successfully completes extracting a source data table. Rows in this view are written once and are not updated. |
|
|
|
|
|
?'"`UNIQ--source-00000043-QINU`"'? |
Documentation:GIM:Library:View-ADMIN EXTRACT HISTORY:PDMSource |
ADMIN_EXTRACT_HISTORY |
|
This view provides information about the data that is extracted from each source database table. A row is added to this view after Job_ExtractICON successfully completes extracting a source data table. Rows in this view are written once and are not updated. |
|
|
|
|
|
?'"`UNIQ--source-0000000F-QINU`"'? |
Documentation:GIM:Library:View-CALLING LIST TO CAMP FACT:8.5DRAFT |
CALLING_LIST_TO_CAMP_FACT |
Describes the association of a calling list to an outbound campaign. |
Each row describes the association of a calling list to an outbound campaign. The grain of the fact is an accumulating snapshot that represents the duration of the association between a calling list and a campaign. |
|
|
|
Facts • Calling_List_To_Campaign |
yes |
?'"`UNIQ--source-00000005-QINU`"'? |
Documentation:GIM:Library:View-CALLING LIST TO CAMP FACT:8.5PDMSource |
CALLING_LIST_TO_CAMP_FACT |
Describes the association of a calling list to an outbound campaign. |
Each row describes the association of a calling list to an outbound campaign. The grain of the fact is an accumulating snapshot that represents the duration of the association between a calling list and a campaign. |
|
|
|
Facts • Calling_List_To_Campaign |
yes |
?'"`UNIQ--source-00000005-QINU`"'? |
Documentation:GIM:Library:View-CALLING LIST TO CAMP FACT:DRAFT |
CALLING_LIST_TO_CAMP_FACT |
Describes the association of a calling list to an outbound campaign. |
Each row describes the association of a calling list to an outbound campaign. The grain of the fact is an accumulating snapshot that represents the duration of the association between a calling list and a campaign. |
|
|
|
Facts • Calling_List_To_Campaign |
yes |
?'"`UNIQ--source-00000005-QINU`"'? |
Documentation:GIM:Library:View-CALLING LIST TO CAMP FACT:PDMSource |
CALLING_LIST_TO_CAMP_FACT |
Describes the association of a calling list to an outbound campaign. |
Each row describes the association of a calling list to an outbound campaign. The grain of the fact is an accumulating snapshot that represents the duration of the association between a calling list and a campaign. |
|
|
|
Facts • Calling_List_To_Campaign |
yes |
?'"`UNIQ--source-00000003-QINU`"'? |
Documentation:GIM:Library:View-CALLING LIST:8.5DRAFT |
CALLING_LIST |
Allows facts to be described based on attributes of an outbound campaign calling list. |
Allows facts to be described based on attributes of an outbound campaign calling list. Each row describes one calling list. |
|
|
|
|
|
?'"`UNIQ--source-00000007-QINU`"'? |
Documentation:GIM:Library:View-CALLING LIST:8.5DRAFT |
CALLING_LIST |
Allows facts to be described based on attributes of an outbound campaign calling list. |
Allows facts to be described based on attributes of an outbound campaign calling list. Each row describes one calling list. |
|
|
|
|
|
?'"`UNIQ--source-00000005-QINU`"'? |
Documentation:GIM:Library:View-CALLING LIST:8.5PDMSource |
CALLING_LIST |
Allows facts to be described based on attributes of an outbound campaign calling list. |
Allows facts to be described based on attributes of an outbound campaign calling list. Each row describes one calling list. |
|
|
|
|
|
?'"`UNIQ--source-0000002B-QINU`"'? |
Documentation:GIM:Library:View-CALLING LIST:DRAFT |
CALLING_LIST |
Allows facts to be described based on attributes of an outbound campaign calling list. |
Allows facts to be described based on attributes of an outbound campaign calling list. Each row describes one calling list. |
|
|
|
|
|
?'"`UNIQ--source-00000031-QINU`"'? |
Documentation:GIM:Library:View-CALLING LIST:PDMSource |
CALLING_LIST |
Allows facts to be described based on attributes of an outbound campaign calling list. |
Allows facts to be described based on attributes of an outbound campaign calling list. Each row describes one calling list. |
|
|
|
|
|
?'"`UNIQ--source-00000006-QINU`"'? |
Documentation:GIM:Library:View-CAMPAIGN:8.5DRAFT |
CAMPAIGN |
Allows facts to be described based on attributes of an outbound campaign. |
Allows facts to be described based on attributes of an outbound campaign. Each row describes one campaign. |
|
|
|
Calling_List_To_Campaign |
|
?'"`UNIQ--source-00000005-QINU`"'? |
Documentation:GIM:Library:View-CAMPAIGN:8.5PDMSource |
CAMPAIGN |
Allows facts to be described based on attributes of an outbound campaign. |
Allows facts to be described based on attributes of an outbound campaign. Each row describes one campaign. |
|
|
|
Calling_List_To_Campaign |
|
?'"`UNIQ--source-00000005-QINU`"'? |
Documentation:GIM:Library:View-CAMPAIGN:8.5PDMSource |
CAMPAIGN |
Allows facts to be described based on attributes of an outbound campaign. |
Allows facts to be described based on attributes of an outbound campaign. Each row describes one campaign. |
|
|
|
Calling_List_To_Campaign |
|
?'"`UNIQ--source-00000007-QINU`"'? |
Documentation:GIM:Library:View-CAMPAIGN:DRAFT |
CAMPAIGN |
Allows facts to be described based on attributes of an outbound campaign. |
Allows facts to be described based on attributes of an outbound campaign. Each row describes one campaign. |
|
|
|
Calling_List_To_Campaign |
|
?'"`UNIQ--source-00000005-QINU`"'? |
Documentation:GIM:Library:View-CAMPAIGN:PDMSource |
CAMPAIGN |
Allows facts to be described based on attributes of an outbound campaign. |
Allows facts to be described based on attributes of an outbound campaign. Each row describes one campaign. |
|
|
|
Calling_List_To_Campaign |
|
?'"`UNIQ--source-00000003-QINU`"'? |
Documentation:GIM:Library:View-CDR DATE TIME:8.5DRAFT |
CDR_DATE_TIME |
|
Reserved |
|
|
|
|
|
?'"`UNIQ--source-00000005-QINU`"'? |
Documentation:GIM:Library:View-CDR DATE TIME:8.5PDMSource |
CDR_DATE_TIME |
|
Reserved |
|
|
|
|
|
?'"`UNIQ--source-00000005-QINU`"'? |
Documentation:GIM:Library:View-CDR DATE TIME:DRAFT |
CDR_DATE_TIME |
|
Reserved |
|
|
|
|
|
?'"`UNIQ--source-00000005-QINU`"'? |
Documentation:GIM:Library:View-CDR DATE TIME:PDMSource |
CDR_DATE_TIME |
|
Reserved |
|
|
|
|
|
?'"`UNIQ--source-00000006-QINU`"'? |
Documentation:GIM:Library:View-CDR:8.5DRAFT |
CDR |
|
Reserved |
|
|
|
|
|
?'"`UNIQ--source-00000005-QINU`"'?
|
Documentation:GIM:Library:View-CDR:8.5PDMSource |
CDR |
|
Reserved |
|
|
|
|
|
?'"`UNIQ--source-00000005-QINU`"'?
|
Documentation:GIM:Library:View-CDR:DRAFT |
CDR |
|
Reserved |
|
|
|
|
|
?'"`UNIQ--source-00000005-QINU`"'?
|
Documentation:GIM:Library:View-CDR:PDMSource |
CDR |
|
Reserved |
|
|
|
|
|
?'"`UNIQ--source-00000005-QINU`"'?
|
Documentation:GIM:Library:View-CTL ETL HWM:8.5DRAFT |
CTL_ETL_HWM |
|
[Show] This view reflects processing progress for the data that is being transferred to the dimensional model tables, but for which certain interaction states are still in progress for the current time interval. In this release, the view is limited to the extracted configuration data and transformed multimedia data only.
|
|
|
|
|
|
?'"`UNIQ--source-00000005-QINU`"'? |
Documentation:GIM:Library:View-CTL ETL HWM:8.5PDMSource |
CTL_ETL_HWM |
|
[Show] This view reflects processing progress for the data that is being transferred to the dimensional model tables, but for which certain interaction states are still in progress for the current time interval. In this release, the view is limited to the extracted configuration data and transformed multimedia data only.
|
|
|
|
|
|
?'"`UNIQ--source-00000005-QINU`"'? |
Documentation:GIM:Library:View-CTL ETL HWM:DRAFT |
CTL_ETL_HWM |
|
[Show] This view reflects processing progress for the data that is being transferred to the dimensional model tables, but for which certain interaction states are still in progress for the current time interval. In this release, the view is limited to the extracted configuration data and transformed multimedia data only.
|
|
|
|
|
|
?'"`UNIQ--source-00000004-QINU`"'? |
Documentation:GIM:Library:View-CTL ETL HWM:PDMSource |
CTL_ETL_HWM |
|
[Show] This view reflects processing progress for the data that is being transferred to the dimensional model tables, but for which certain interaction states are still in progress for the current time interval. In this release, the view is limited to the extracted configuration data and transformed multimedia data only.
|
|
|
|
|
|
?'"`UNIQ--source-00000005-QINU`"'? |
Documentation:GIM:Library:View-GROUP TO CAMPAIGN FACT:8.5DRAFT |
GROUP_TO_CAMPAIGN_FACT |
Describes the association of an agent or place group to an outbound campaign. |
Each row describes the association of an agent or place group to an outbound campaign. The grain of the fact is an accumulating snapshot that represents the duration of the association between an agent or place group and a campaign. |
|
|
|
Facts • Campaign_Group_To_Campaign |
yes |
?'"`UNIQ--source-00000026-QINU`"'? |
Documentation:GIM:Library:View-GROUP TO CAMPAIGN FACT:8.5PDMSource |
GROUP_TO_CAMPAIGN_FACT |
Describes the association of an agent or place group to an outbound campaign. |
Each row describes the association of an agent or place group to an outbound campaign. The grain of the fact is an accumulating snapshot that represents the duration of the association between an agent or place group and a campaign. |
|
|
|
Facts • Campaign_Group_To_Campaign |
yes |
?'"`UNIQ--source-0000002D-QINU`"'? |
Documentation:GIM:Library:View-GROUP TO CAMPAIGN FACT:DRAFT |
GROUP_TO_CAMPAIGN_FACT |
Describes the association of an agent or place group to an outbound campaign. |
Each row describes the association of an agent or place group to an outbound campaign. The grain of the fact is an accumulating snapshot that represents the duration of the association between an agent or place group and a campaign. |
|
|
|
Facts • Campaign_Group_To_Campaign |
yes |
?'"`UNIQ--source-00000033-QINU`"'? |
Documentation:GIM:Library:View-GROUP TO CAMPAIGN FACT:PDMSource |
GROUP_TO_CAMPAIGN_FACT |
Describes the association of an agent or place group to an outbound campaign. |
Each row describes the association of an agent or place group to an outbound campaign. The grain of the fact is an accumulating snapshot that represents the duration of the association between an agent or place group and a campaign. |
|
|
|
Facts • Campaign_Group_To_Campaign |
yes |
?'"`UNIQ--source-00000003-QINU`"'? |
Documentation:GIM:Library:View-GROUP:8.5DRAFT |
GROUP_ |
Allows facts to be described based on the membership of resources in resource groups or membership of places in place groups. |
[Show] Allows facts to be described based on the membership of resources in resource groups or membership of places in place groups. Routing points, queues, and agents can belong to resource groups. Places can belong to place groups. Each row describes one place group or resource group. A new row is issued for each configured place group and resource group, which is identified by its ID in the contact center configuration. Changing a group name causes an update to an existing row. Deleting a group and re-creating it under the same name causes a new row to be issued. |
|
|
|
|
|
?'"`UNIQ--source-00000006-QINU`"'? |
Documentation:GIM:Library:View-GROUP:8.5PDMSource |
GROUP_ |
Allows facts to be described based on the membership of resources in resource groups or membership of places in place groups. |
[Show] Allows facts to be described based on the membership of resources in resource groups or membership of places in place groups. Routing points, queues, and agents can belong to resource groups. Places can belong to place groups. Each row describes one place group or resource group. A new row is issued for each configured place group and resource group, which is identified by its ID in the contact center configuration. Changing a group name causes an update to an existing row. Deleting a group and re-creating it under the same name causes a new row to be issued. |
|
|
|
|
|
?'"`UNIQ--source-00000006-QINU`"'? |
Documentation:GIM:Library:View-GROUP:DRAFT |
GROUP_ |
Allows facts to be described based on the membership of resources in resource groups or membership of places in place groups. |
[Show] Allows facts to be described based on the membership of resources in resource groups or membership of places in place groups. Routing points, queues, and agents can belong to resource groups. Places can belong to place groups. Each row describes one place group or resource group. A new row is issued for each configured place group and resource group, which is identified by its ID in the contact center configuration. Changing a group name causes an update to an existing row. Deleting a group and re-creating it under the same name causes a new row to be issued. |
|
|
|
|
|
?'"`UNIQ--source-00000005-QINU`"'? |
Documentation:GIM:Library:View-GROUP:PDMSource |
GROUP_ |
Allows facts to be described based on the membership of resources in resource groups or membership of places in place groups. |
[Show] Allows facts to be described based on the membership of resources in resource groups or membership of places in place groups. Routing points, queues, and agents can belong to resource groups. Places can belong to place groups. Each row describes one place group or resource group. A new row is issued for each configured place group and resource group, which is identified by its ID in the contact center configuration. Changing a group name causes an update to an existing row. Deleting a group and re-creating it under the same name causes a new row to be issued. |
|
|
|
|
|
?'"`UNIQ--source-0000000F-QINU`"'? |
Documentation:GIM:Library:View-PLACE GROUP FACT:8.5DRAFT |
PLACE_GROUP_FACT |
Describes the membership of places in place groups. |
Each row describes the membership of one place in one place group. The grain of the fact is an accumulating snapshot that represents the duration of the configured membership, which is identified by its ID in the Configuration Database. |
|
|
|
Facts • Place_Group |
yes |
?'"`UNIQ--source-0000002A-QINU`"'? |
Documentation:GIM:Library:View-PLACE GROUP FACT:8.5PDMSource |
PLACE_GROUP_FACT |
Describes the membership of places in place groups. |
Each row describes the membership of one place in one place group. The grain of the fact is an accumulating snapshot that represents the duration of the configured membership, which is identified by its ID in the Configuration Database. |
|
|
|
Facts • Place_Group |
yes |
?'"`UNIQ--source-00000031-QINU`"'? |
Documentation:GIM:Library:View-PLACE GROUP FACT:DRAFT |
PLACE_GROUP_FACT |
Describes the membership of places in place groups. |
Each row describes the membership of one place in one place group. The grain of the fact is an accumulating snapshot that represents the duration of the configured membership, which is identified by its ID in the Configuration Database. |
|
|
|
Facts • Place_Group |
yes |
?'"`UNIQ--source-00000037-QINU`"'? |
Documentation:GIM:Library:View-PLACE GROUP FACT:PDMSource |
PLACE_GROUP_FACT |
Describes the membership of places in place groups. |
Each row describes the membership of one place in one place group. The grain of the fact is an accumulating snapshot that represents the duration of the configured membership, which is identified by its ID in the Configuration Database. |
|
|
|
Facts • Place_Group |
yes |
?'"`UNIQ--source-000000E0-QINU`"'? |
Documentation:GIM:Library:View-PLACE:8.5DRAFT |
PLACE |
Allows facts to be described by the attributes of a place. |
[Show] Allows facts to be described by the attributes of a place. Each row describes one configured place, identified by its ID in the contact center configuration. Changing the place name causes an update to an existing row. Deleting a place and re-creating it under the same name causes a new row to be issued. |
|
|
|
|
|
?'"`UNIQ--source-00000005-QINU`"'? |
Documentation:GIM:Library:View-PLACE:8.5PDMSource |
PLACE |
Allows facts to be described by the attributes of a place. |
[Show] Allows facts to be described by the attributes of a place. Each row describes one configured place, identified by its ID in the contact center configuration. Changing the place name causes an update to an existing row. Deleting a place and re-creating it under the same name causes a new row to be issued. |
|
|
|
|
|
?'"`UNIQ--source-0000002F-QINU`"'? |
Documentation:GIM:Library:View-PLACE:DRAFT |
PLACE |
Allows facts to be described by the attributes of a place. |
[Show] Allows facts to be described by the attributes of a place. Each row describes one configured place, identified by its ID in the contact center configuration. Changing the place name causes an update to an existing row. Deleting a place and re-creating it under the same name causes a new row to be issued. |
|
|
|
|
|
?'"`UNIQ--source-00000035-QINU`"'? |
Documentation:GIM:Library:View-PLACE:PDMSource |
PLACE |
Allows facts to be described by the attributes of a place. |
[Show] Allows facts to be described by the attributes of a place. Each row describes one configured place, identified by its ID in the contact center configuration. Changing the place name causes an update to an existing row. Deleting a place and re-creating it under the same name causes a new row to be issued. |
|
|
|
|
|
?'"`UNIQ--source-00000005-QINU`"'? |
Documentation:GIM:Library:View-RESOURCE GROUP FACT:8.5DRAFT |
RESOURCE_GROUP_FACT |
Describes the membership of resources in resource groups. |
Each row describes the membership of one resource (routing point, queue, or agent) in one resource group. The grain of the fact is an accumulating snapshot that represents the duration of the configured membership, which is identified by its ID in the configuration database. |
|
|
|
Facts • Resource_Group |
yes |
?'"`UNIQ--source-0000002C-QINU`"'? |
Documentation:GIM:Library:View-RESOURCE GROUP FACT:8.5PDMSource |
RESOURCE_GROUP_FACT |
Describes the membership of resources in resource groups. |
Each row describes the membership of one resource (routing point, queue, or agent) in one resource group. The grain of the fact is an accumulating snapshot that represents the duration of the configured membership, which is identified by its ID in the configuration database. |
|
|
|
Facts • Resource_Group |
yes |
?'"`UNIQ--source-00000033-QINU`"'? |
Documentation:GIM:Library:View-RESOURCE GROUP FACT:DRAFT |
RESOURCE_GROUP_FACT |
Describes the membership of resources in resource groups. |
Each row describes the membership of one resource (routing point, queue, or agent) in one resource group. The grain of the fact is an accumulating snapshot that represents the duration of the configured membership, which is identified by its ID in the configuration database. |
|
|
|
Facts • Resource_Group |
yes |
?'"`UNIQ--source-00000039-QINU`"'? |
Documentation:GIM:Library:View-RESOURCE GROUP FACT:PDMSource |
RESOURCE_GROUP_FACT |
Describes the membership of resources in resource groups. |
Each row describes the membership of one resource (routing point, queue, or agent) in one resource group. The grain of the fact is an accumulating snapshot that represents the duration of the configured membership, which is identified by its ID in the configuration database. |
|
|
|
Facts • Resource_Group |
yes |
?'"`UNIQ--source-00000003-QINU`"'? |
Documentation:GIM:Library:View-RESOURCE SKILL FACT:8.5DRAFT |
RESOURCE_SKILL_FACT |
Describes an agent's skills and proficiency levels. |
Each row describes one skill at a particular proficiency level that one agent possesses. The grain of the fact is an accumulating snapshot that represents the duration of the configured skill and proficiency, which are identified by a unique ID in the configuration database. |
|
|
|
Facts • Resource_Skill |
yes |
?'"`UNIQ--source-0000002E-QINU`"'? |
Documentation:GIM:Library:View-RESOURCE SKILL FACT:8.5PDMSource |
RESOURCE_SKILL_FACT |
Describes an agent's skills and proficiency levels. |
Each row describes one skill at a particular proficiency level that one agent possesses. The grain of the fact is an accumulating snapshot that represents the duration of the configured skill and proficiency, which are identified by a unique ID in the configuration database. |
|
|
|
Facts • Resource_Skill |
yes |
?'"`UNIQ--source-00000035-QINU`"'? |
Documentation:GIM:Library:View-RESOURCE SKILL FACT:DRAFT |
RESOURCE_SKILL_FACT |
Describes an agent's skills and proficiency levels. |
Each row describes one skill at a particular proficiency level that one agent possesses. The grain of the fact is an accumulating snapshot that represents the duration of the configured skill and proficiency, which are identified by a unique ID in the configuration database. |
|
|
|
Facts • Resource_Skill |
yes |
?'"`UNIQ--source-0000003B-QINU`"'? |
Documentation:GIM:Library:View-RESOURCE SKILL FACT:PDMSource |
RESOURCE_SKILL_FACT |
Describes an agent's skills and proficiency levels. |
Each row describes one skill at a particular proficiency level that one agent possesses. The grain of the fact is an accumulating snapshot that represents the duration of the configured skill and proficiency, which are identified by a unique ID in the configuration database. |
|
|
|
Facts • Resource_Skill |
yes |
?'"`UNIQ--source-00000005-QINU`"'? |
Documentation:GIM:Library:View-SKILL:8.5DRAFT |
SKILL |
Allows facts to be described by the attributes of a skill. |
[Show] Allows facts to be described by the attributes of a skill. Each row describes one skill. A new row is issued for each configured skill, identified by its ID in the contact center configuration. Changing a skill name causes an update to an existing row. Deleting a skill and re-creating it under the same name causes a new row to be issued. |
|
|
|
|
|
?'"`UNIQ--source-00000030-QINU`"'? |
Documentation:GIM:Library:View-SKILL:8.5PDMSource |
SKILL |
Allows facts to be described by the attributes of a skill. |
[Show] Allows facts to be described by the attributes of a skill. Each row describes one skill. A new row is issued for each configured skill, identified by its ID in the contact center configuration. Changing a skill name causes an update to an existing row. Deleting a skill and re-creating it under the same name causes a new row to be issued. |
|
|
|
|
|
?'"`UNIQ--source-00000037-QINU`"'? |
Documentation:GIM:Library:View-SKILL:DRAFT |
SKILL |
Allows facts to be described by the attributes of a skill. |
[Show] Allows facts to be described by the attributes of a skill. Each row describes one skill. A new row is issued for each configured skill, identified by its ID in the contact center configuration. Changing a skill name causes an update to an existing row. Deleting a skill and re-creating it under the same name causes a new row to be issued. |
|
|
|
|
|
?'"`UNIQ--source-0000003D-QINU`"'? |
Documentation:GIM:Library:View-SKILL:PDMSource |
SKILL |
Allows facts to be described by the attributes of a skill. |
[Show] Allows facts to be described by the attributes of a skill. Each row describes one skill. A new row is issued for each configured skill, identified by its ID in the contact center configuration. Changing a skill name causes an update to an existing row. Deleting a skill and re-creating it under the same name causes a new row to be issued. |
|
|
|
|
|
?'"`UNIQ--source-00000003-QINU`"'? |
Documentation:GIM:Library:View-TENANT:8.5DRAFT |
TENANT |
Allows facts to be described based on attributes of a tenant. The TENANT dimension is used in a multi-tenant deployment to filter facts and dimensions into tenant-specific views--allowing each tenant to see only their own data. |
[Show] Allows facts to be described based on attributes of a tenant. The TENANT dimension is used in a multi-tenant deployment to filter facts and dimensions into tenant-specific views--allowing each tenant to see only their own data. In a single-tenant deployment, the Resources tenant is considered a tenant. In a multi-tenant deployment, the Environment tenant and the configured tenants are considered tenants. Each row describes one tenant. A new row is issued for each configured tenant, identified by its ID in the contact center configuration. Changing a tenant's name causes an update to the existing row. Deleting a tenant and re-creating it under the same name causes a new row to be issued.
|
|
|
|
|
|
?'"`UNIQ--source-00000005-QINU`"'? |
Documentation:GIM:Library:View-TENANT:8.5PDMSource |
TENANT |
Allows facts to be described based on attributes of a tenant. The TENANT dimension is used in a multi-tenant deployment to filter facts and dimensions into tenant-specific views--allowing each tenant to see only their own data. |
[Show] Allows facts to be described based on attributes of a tenant. The TENANT dimension is used in a multi-tenant deployment to filter facts and dimensions into tenant-specific views--allowing each tenant to see only their own data. In a single-tenant deployment, the Resources tenant is considered a tenant. In a multi-tenant deployment, the Environment tenant and the configured tenants are considered tenants. Each row describes one tenant. A new row is issued for each configured tenant, identified by its ID in the contact center configuration. Changing a tenant's name causes an update to the existing row. Deleting a tenant and re-creating it under the same name causes a new row to be issued.
|
|
|
|
|
|
?'"`UNIQ--source-00000005-QINU`"'? |
Documentation:GIM:Library:View-TENANT:DRAFT |
TENANT |
Allows facts to be described based on attributes of a tenant. The TENANT dimension is used in a multi-tenant deployment to filter facts and dimensions into tenant-specific views--allowing each tenant to see only their own data. |
[Show] Allows facts to be described based on attributes of a tenant. The TENANT dimension is used in a multi-tenant deployment to filter facts and dimensions into tenant-specific views--allowing each tenant to see only their own data. In a single-tenant deployment, the Resources tenant is considered a tenant. In a multi-tenant deployment, the Environment tenant and the configured tenants are considered tenants. Each row describes one tenant. A new row is issued for each configured tenant, identified by its ID in the contact center configuration. Changing a tenant's name causes an update to the existing row. Deleting a tenant and re-creating it under the same name causes a new row to be issued.
|
|
|
|
|
|
?'"`UNIQ--source-00000005-QINU`"'? |
Documentation:GIM:Library:View-TENANT:PDMSource |
TENANT |
Allows facts to be described based on attributes of a tenant. The TENANT dimension is used in a multi-tenant deployment to filter facts and dimensions into tenant-specific views--allowing each tenant to see only their own data. |
[Show] Allows facts to be described based on attributes of a tenant. The TENANT dimension is used in a multi-tenant deployment to filter facts and dimensions into tenant-specific views--allowing each tenant to see only their own data. In a single-tenant deployment, the Resources tenant is considered a tenant. In a multi-tenant deployment, the Environment tenant and the configured tenants are considered tenants. Each row describes one tenant. A new row is issued for each configured tenant, identified by its ID in the contact center configuration. Changing a tenant's name causes an update to the existing row. Deleting a tenant and re-creating it under the same name causes a new row to be issued.
|
|
|
|
|
|
?'"`UNIQ--source-00000003-QINU`"'? |
Documentation:PSAAS:RPRT:View-CALLING LIST:Julie |
CALLING_LIST |
Allows facts to be described based on attributes of an outbound campaign calling list. |
Allows facts to be described based on attributes of an outbound campaign calling list. Each row describes one calling list. |
|
|
|
|
|
?'"`UNIQ--source-00000003-QINU`"'? |
Documentation:PSAAS:RPRT:View-CAMPAIGN:Julie |
CAMPAIGN |
Allows facts to be described based on attributes of an outbound campaign. |
Allows facts to be described based on attributes of an outbound campaign. Each row describes one campaign. |
|
|
|
Calling_List_To_Campaign |
|
?'"`UNIQ--source-00000003-QINU`"'? |
Documentation:PSAAS:RPRT:View-CTL ETL HWM:Julie |
CTL_ETL_HWM |
|
[Show] This view reflects processing progress for the data that is being transferred to the dimensional model tables, but for which certain interaction states are still in progress for the current time interval. In this release, the view is limited to the extracted configuration data and transformed multimedia data only.
|
|
|
|
|
|
?'"`UNIQ--source-00000003-QINU`"'? |
Documentation:PSAAS:RPRT:View-GROUP TO CAMPAIGN FACT:Julie |
GROUP_TO_CAMPAIGN_FACT |
Describes the association of an agent or place group to an outbound campaign. |
Each row describes the association of an agent or place group to an outbound campaign. The grain of the fact is an accumulating snapshot that represents the duration of the association between an agent or place group and a campaign. |
|
|
|
Facts • Campaign_Group_To_Campaign |
yes |
?'"`UNIQ--source-00000003-QINU`"'? |
Documentation:PSAAS:RPRT:View-GROUP:Julie |
GROUP_ |
Allows facts to be described based on the membership of resources in resource groups or membership of places in place groups. |
[Show] Allows facts to be described based on the membership of resources in resource groups or membership of places in place groups. Routing points, queues, and agents can belong to resource groups. Places can belong to place groups. Each row describes one place group or resource group. A new row is issued for each configured place group and resource group, which is identified by its ID in the contact center configuration. Changing a group name causes an update to an existing row. Deleting a group and re-creating it under the same name causes a new row to be issued. |
|
|
|
|
|
?'"`UNIQ--source-00000004-QINU`"'? |
Documentation:PSAAS:RPRT:View-PLACE:Julie |
PLACE |
Allows facts to be described by the attributes of a place. |
[Show] Allows facts to be described by the attributes of a place. Each row describes one configured place, identified by its ID in the contact center configuration. Changing the place name causes an update to an existing row. Deleting a place and re-creating it under the same name causes a new row to be issued. |
|
|
|
|
|
?'"`UNIQ--source-00000003-QINU`"'? |
Documentation:PSAAS:RPRT:View-SKILL:Julie |
SKILL |
Allows facts to be described by the attributes of a skill. |
[Show] Allows facts to be described by the attributes of a skill. Each row describes one skill. A new row is issued for each configured skill, identified by its ID in the contact center configuration. Changing a skill name causes an update to an existing row. Deleting a skill and re-creating it under the same name causes a new row to be issued. |
|
|
|
|
|
?'"`UNIQ--source-00000003-QINU`"'? |
Documentation:PSAAS:RPRT:View-TENANT:Julie |
TENANT |
Allows facts to be described based on attributes of a tenant. The TENANT dimension is used in a multi-tenant deployment to filter facts and dimensions into tenant-specific views--allowing each tenant to see only their own data. |
[Show] Allows facts to be described based on attributes of a tenant. The TENANT dimension is used in a multi-tenant deployment to filter facts and dimensions into tenant-specific views--allowing each tenant to see only their own data. In a single-tenant deployment, the Resources tenant is considered a tenant. In a multi-tenant deployment, the Environment tenant and the configured tenants are considered tenants. Each row describes one tenant. A new row is issued for each configured tenant, identified by its ID in the contact center configuration. Changing a tenant's name causes an update to the existing row. Deleting a tenant and re-creating it under the same name causes a new row to be issued.
|
|
|
|
|
|
?'"`UNIQ--source-00000003-QINU`"'? |
Documentation:RAA:Library:View-AG2 AGENT CAMPAIGN HOUR:8.5DRAFT |
AG2_AGENT_CAMPAIGN_HOUR |
|
[Show] This view represents the disposition-based aggregate table AGT_AGENT_CAMPAIGN_HOUR, which provides a rollup of interaction-handling activities of agent resources who received interactions that originated from a particular campaign. Rollups are derived primarily from the CONTACT _ATTEMPT_FACT and INTERACTION_RESOURCE_FACT tables. This view includes two sets of measures:
- Nonconsult-related interactions
- Consult interactions
Where so indicated, the measures in this view include either warm consult interactions or simple consult interactions. Warm consult interactions, or warm consultations, refer to those consultations that result in a transfer to or conference with the agent. Simple consultations are consult interactions that begin and end in consult.
Counts and durations are attributed to the interval in which the agent was offered the interaction. For consultations, counts and durations are attributed to the interval in which the agent, who received the consultation request, was offered the interaction.
Interactions that occur at DNs that have no associated agent are excluded from this view, as are interactions that are received by unmonitored agents. Aggregation is performed along the TENANT, DATE_TIME, CAMPAIGN, MEDIA_TYPE, INTERACTION_DESCRIPTOR, INTERACTION_TYPE, RESOURCE_, RESOURCE_GROUP_COMBINATION, and USER_DATA_CUST_DIM dimensions.
The same columns and column descriptions apply to other AG2_AGENT_CAMPAIGN_* views.
|
|
|
|
|
|
|
Documentation:RAA:Library:View-AG2 AGENT CAMPAIGN HOUR:8.5PDMSource |
AG2_AGENT_CAMPAIGN_HOUR |
|
[Show] This view represents the disposition-based aggregate table AGT_AGENT_CAMPAIGN_HOUR, which provides a rollup of interaction-handling activities of agent resources who received interactions that originated from a particular campaign. Rollups are derived primarily from the CONTACT _ATTEMPT_FACT and INTERACTION_RESOURCE_FACT tables. This view includes two sets of measures:
- Nonconsult-related interactions
- Consult interactions
Where so indicated, the measures in this view include either warm consult interactions or simple consult interactions. Warm consult interactions, or warm consultations, refer to those consultations that result in a transfer to or conference with the agent. Simple consultations are consult interactions that begin and end in consult.
Counts and durations are attributed to the interval in which the agent was offered the interaction. For consultations, counts and durations are attributed to the interval in which the agent, who received the consultation request, was offered the interaction.
Interactions that occur at DNs that have no associated agent are excluded from this view, as are interactions that are received by unmonitored agents. Aggregation is performed along the TENANT, DATE_TIME, CAMPAIGN, MEDIA_TYPE, INTERACTION_DESCRIPTOR, INTERACTION_TYPE, RESOURCE_, RESOURCE_GROUP_COMBINATION, and USER_DATA_CUST_DIM dimensions.
The same columns and column descriptions apply to other AG2_AGENT_CAMPAIGN_* views.
|
|
|
|
|
|
|
Documentation:RAA:Library:View-AG2 AGENT GRP HOUR:8.5DRAFT |
AG2_AGENT_GRP_HOUR |
Agent group rollup of interaction handling based on key business attributes, such as customer segment, service type, and service subtype. |
[Show] This view represents the disposition-based aggregate table AGT_AGENT_GRP_HOUR, which provides a rollup of agent handling of interactions, based on key business attributes such as customer segment, service type, and service subtype. Rollups are derived primarily from the INTERACTION_RESOURCE_FACT table. An inner join to IRF_USER_DATA_GEN_1 provides aggregated data that is dimensioned by revenue and customer satisfaction. Within this view, these two sets of fields are stored as integers. Numeric data only should be written to these fields. In the source IRF_USER_DATA_GEN_1 table, they are stored in character format. Refer to “Check for Incorrect Data Type” in the Reporting and Analytics Aggregates User’s Guide to learn how to recover from situations where RAA attempts to aggregate nonnumeric data.
Where so indicated, the measures in this view include either warm consult or simple consult interactions. Warm consult interactions, or warm consultations, refer to those consultations that result in a transfer to or conference with the agent. Simple consultations are consult interactions that begin and end in consult.
Measures are attributed to the interval in which interactions were offered to agents belong to a particular agent group.
Interactions that occur at DNs that have no associated agent are excluded from this view. No consideration is made as to whether interactions were distributed from a queue or directly routed from the switch. Aggregation is performed along the TENANT, DATE_TIME, RESOURCE_, GROUP_, MEDIA_TYPE, INTERACTION_ TYPE, INTERACTION_DESCRIPTOR, and USER_DATA_CUST_DIM dimensions. The combination of keys to these dimensions uniquely identifies records in this view.
Group membership is determined by the moment at which the agent receives an interaction. If the agent belongs to more than one agent group, agent measures are attributed to all of the groups of which the agent was a member when s/he received the interaction.
The same columns and column descriptions apply to other AG2_AGENT_GRP_* views.
|
|
|
|
|
|
|
Documentation:RAA:Library:View-AG2 AGENT GRP HOUR:8.5PDMSource |
AG2_AGENT_GRP_HOUR |
Agent group rollup of interaction handling based on key business attributes, such as customer segment, service type, and service subtype. |
[Show] This view represents the disposition-based aggregate table AGT_AGENT_GRP_HOUR, which provides a rollup of agent handling of interactions, based on key business attributes such as customer segment, service type, and service subtype. Rollups are derived primarily from the INTERACTION_RESOURCE_FACT table. An inner join to IRF_USER_DATA_GEN_1 provides aggregated data that is dimensioned by revenue and customer satisfaction. Within this view, these two sets of fields are stored as integers. Numeric data only should be written to these fields. In the source IRF_USER_DATA_GEN_1 table, they are stored in character format. Refer to “Check for Incorrect Data Type” in the Reporting and Analytics Aggregates User’s Guide to learn how to recover from situations where RAA attempts to aggregate nonnumeric data.
Where so indicated, the measures in this view include either warm consult or simple consult interactions. Warm consult interactions, or warm consultations, refer to those consultations that result in a transfer to or conference with the agent. Simple consultations are consult interactions that begin and end in consult.
Measures are attributed to the interval in which interactions were offered to agents belong to a particular agent group.
Interactions that occur at DNs that have no associated agent are excluded from this view. No consideration is made as to whether interactions were distributed from a queue or directly routed from the switch. Aggregation is performed along the TENANT, DATE_TIME, RESOURCE_, GROUP_, MEDIA_TYPE, INTERACTION_ TYPE, INTERACTION_DESCRIPTOR, and USER_DATA_CUST_DIM dimensions. The combination of keys to these dimensions uniquely identifies records in this view.
Group membership is determined by the moment at which the agent receives an interaction. If the agent belongs to more than one agent group, agent measures are attributed to all of the groups of which the agent was a member when s/he received the interaction.
The same columns and column descriptions apply to other AG2_AGENT_GRP_* views.
|
|
|
|
|
|
|
Documentation:RAA:Library:View-AG2 AGENT HOUR:8.5DRAFT |
AG2_AGENT_HOUR |
|
[Show] This view represents the disposition-based aggregate table AGT_AGENT_HOUR, which provides a rollup of agent handling of interactions, based on key business attributes such as customer segment, service type, and service subtype. Rollups are derived primarily from the INTERACTION_RESOURCE_FACT table. An inner join to IRF_USER_DATA_GEN_1 provides aggregated data that is dimensioned by revenue and customer satisfaction. Note that within the AGT_AGENT_HOUR table, these two sets of fields are stored as integers. Numeric data only should be written to these fields. In the source IRF_USER_DATA_GEN_1 table, they are stored in character format. Refer to “Check for Incorrect Data Type” in the Reporting and Analytics Aggregates User’s Guide to learn how to recover from situations where RAA attempts to aggregate nonnumeric data. Where so indicated, the measures in this view include either warm consult interactions or simple consult interactions. Warm consult interactions, or warm consultations, refer to those consultations that result in a transfer
to or conference with the agent. Simple consultations are consult interactions that begin and end in consult.
Measures are attributed to the interval in which interactions were offered to the agent.
Interactions that occur at DNs that have no associated agent are excluded. No consideration is made as to whether interactions were distributed from a queue or directly routed from the switch. Aggregation is
performed along the TENANT, DATE_TIME, RESOURCE_, RESOURCE_GROUP_COMBINATION, MEDIA_ TYPE, INTERACTION_TYPE, INTERACTION_DESCRIPTOR, and USER_DATA_CUST_DIM dimensions. The combination of keys to these dimensions uniquely identifies records.
The same columns and column descriptions apply to other AG2_AGENT_* views.
|
|
|
|
|
|
|
Documentation:RAA:Library:View-AG2 AGENT HOUR:8.5PDMSource |
AG2_AGENT_HOUR |
|
[Show] This view represents the disposition-based aggregate table AGT_AGENT_HOUR, which provides a rollup of agent handling of interactions, based on key business attributes such as customer segment, service type, and service subtype. Rollups are derived primarily from the INTERACTION_RESOURCE_FACT table. An inner join to IRF_USER_DATA_GEN_1 provides aggregated data that is dimensioned by revenue and customer satisfaction. Note that within the AGT_AGENT_HOUR table, these two sets of fields are stored as integers. Numeric data only should be written to these fields. In the source IRF_USER_DATA_GEN_1 table, they are stored in character format. Refer to “Check for Incorrect Data Type” in the Reporting and Analytics Aggregates User’s Guide to learn how to recover from situations where RAA attempts to aggregate nonnumeric data. Where so indicated, the measures in this view include either warm consult interactions or simple consult interactions. Warm consult interactions, or warm consultations, refer to those consultations that result in a transfer
to or conference with the agent. Simple consultations are consult interactions that begin and end in consult.
Measures are attributed to the interval in which interactions were offered to the agent.
Interactions that occur at DNs that have no associated agent are excluded. No consideration is made as to whether interactions were distributed from a queue or directly routed from the switch. Aggregation is
performed along the TENANT, DATE_TIME, RESOURCE_, RESOURCE_GROUP_COMBINATION, MEDIA_ TYPE, INTERACTION_TYPE, INTERACTION_DESCRIPTOR, and USER_DATA_CUST_DIM dimensions. The combination of keys to these dimensions uniquely identifies records.
The same columns and column descriptions apply to other AG2_AGENT_* views.
|
|
|
|
|
|
|
Documentation:RAA:Library:View-AG2 AGENT QUEUE HOUR:8.5DRAFT |
AG2_AGENT_QUEUE_HOUR |
|
[Show] This view represents the disposition-based aggregate table AGT_AGENT_QUEUE_HOUR, which provides a rollup of interaction-handling activities of agent resources who received interactions that were distributed from the following queue types:- ACD queue
- Virtual queues
- Interaction queues
- Workbins
Rollups are derived primarily from the INTERACTION_RESOURCE_FACT and MEDIATION_SEGMENT_ FACT and tables. An inner join to IRF_USER_DATA_GEN_1 provides aggregated data that is dimensioned by revenue and customer satisfaction. Within this view these two sets of fields are stored as integers. Numeric data only should be written to these fields. In the source IRF_USER_DATA_GEN_1 table, they are stored in character format. Refer to “Check for Incorrect Data Type” in the Reporting and Analytics Aggregates User’s Guide to learn how to recover from situations where RAA attempts to aggregate nonnumeric data.
This view includes two sets of measures regarding interactions that were distributed from the preceding queue-type devices to agents-namely, measures for:
- Nonconsult-related interactions.
- Consult interactions.
Where so indicated, the measures in this view include either warm consult interactions or simple consult interactions. Warm consult interactions, or warm consultations, refer to those consultations that result in a transfer to or conference with the agent. Simple consultations are consult interactions that begin and end in consult.
Counts and durations are attributed to the interval in which the agent was offered the interaction. For consultations, counts and durations are attributed to the interval in which the agent, who received the consultation request, was offered the interaction.
Interactions that occur at DNs that have no associated agent are excluded from this view, as are interactions that are received by unmonitored agents. Aggregation is performed along the TENANT, DATE TIME, MEDIA_TYPE, INTERACTION_DESCRIPTOR, INTERACTION_TYPE, RESOURCE_, USER_DATA_CUST_DIM, and RESOURCE_GROUP_COMBINATION, and dimensions. Each of the latter two dimensions is referenced twice in this table, because both dimensions store agent- and queue-related information.
The same columns and column descriptions apply to other AG2_AGENT_QUEUE_* views.
|
|
|
|
|
|
|
Documentation:RAA:Library:View-AG2 AGENT QUEUE HOUR:8.5PDMSource |
AG2_AGENT_QUEUE_HOUR |
|
[Show] This view represents the disposition-based aggregate table AGT_AGENT_QUEUE_HOUR, which provides a rollup of interaction-handling activities of agent resources who received interactions that were distributed from the following queue types:- ACD queue
- Virtual queues
- Interaction queues
- Workbins
Rollups are derived primarily from the INTERACTION_RESOURCE_FACT and MEDIATION_SEGMENT_ FACT and tables. An inner join to IRF_USER_DATA_GEN_1 provides aggregated data that is dimensioned by revenue and customer satisfaction. Within this view these two sets of fields are stored as integers. Numeric data only should be written to these fields. In the source IRF_USER_DATA_GEN_1 table, they are stored in character format. Refer to “Check for Incorrect Data Type” in the Reporting and Analytics Aggregates User’s Guide to learn how to recover from situations where RAA attempts to aggregate nonnumeric data.
This view includes two sets of measures regarding interactions that were distributed from the preceding queue-type devices to agents-namely, measures for:
- Nonconsult-related interactions.
- Consult interactions.
Where so indicated, the measures in this view include either warm consult interactions or simple consult interactions. Warm consult interactions, or warm consultations, refer to those consultations that result in a transfer to or conference with the agent. Simple consultations are consult interactions that begin and end in consult.
Counts and durations are attributed to the interval in which the agent was offered the interaction. For consultations, counts and durations are attributed to the interval in which the agent, who received the consultation request, was offered the interaction.
Interactions that occur at DNs that have no associated agent are excluded from this view, as are interactions that are received by unmonitored agents. Aggregation is performed along the TENANT, DATE TIME, MEDIA_TYPE, INTERACTION_DESCRIPTOR, INTERACTION_TYPE, RESOURCE_, USER_DATA_CUST_DIM, and RESOURCE_GROUP_COMBINATION, and dimensions. Each of the latter two dimensions is referenced twice in this table, because both dimensions store agent- and queue-related information.
The same columns and column descriptions apply to other AG2_AGENT_QUEUE_* views.
|
|
|
|
|
|
|
Documentation:RAA:Library:View-AG2 CALLBACK HOUR:8.5DRAFT |
AG2_CALLBACK_HOUR |
Rollup of interactions associated with callbacks. |
[Show] This view represents the disposition-based aggregate AGT_CALLBACK_HOUR table, which provides a rollup of interactions associated with callbacks. Data is derived primarily from the CALLBACK_FACT table and IRF table. Aggregation is performed along the TENANT, DATE TIME, RESOURCE, CALLBACK_* dimensions.
The same columns and column descriptions apply to the AG2_CALLBACK_SUBHOUR, AG2_CALLBACK_DAY, AG2_CALLBACK_WEEK, AG2_CALLBACK_MONTH, AG2_CALLBACK_QRTR, and AG2_CALLBACK_YEAR views.
The same columns and column descriptions apply to other AG2_CALLBACK_* views.
|
|
|
|
|
|
|
Documentation:RAA:Library:View-AG2 CALLBACK HOUR:8.5PDMSource |
AG2_CALLBACK_HOUR |
Rollup of interactions associated with callbacks. |
[Show] This view represents the disposition-based aggregate AGT_CALLBACK_HOUR table, which provides a rollup of interactions associated with callbacks. Data is derived primarily from the CALLBACK_FACT table and IRF table. Aggregation is performed along the TENANT, DATE TIME, RESOURCE, CALLBACK_* dimensions.
The same columns and column descriptions apply to the AG2_CALLBACK_SUBHOUR, AG2_CALLBACK_DAY, AG2_CALLBACK_WEEK, AG2_CALLBACK_MONTH, AG2_CALLBACK_QRTR, and AG2_CALLBACK_YEAR views.
The same columns and column descriptions apply to other AG2_CALLBACK_* views.
|
|
|
|
|
|
|
Documentation:RAA:Library:View-AG2 CAMPAIGN HOUR:8.5DRAFT |
AG2_CAMPAIGN_HOUR |
|
[Show] This view represents the disposition-based aggregate AGT_CAMPAIGN_HOUR table, which provides a rollup of interactions generated by a particular campaign. Rollups are derived primarily from the CONTACT_ATTEMPT_FACT table with an inner join on CALL_RESULT. Counts and durations are attributed to the interval in which contact attempts were made. Aggregation is performed along the TENANT, DATE TIME, CAMPAIGN, MEDIA_TYPE, INTERACTION_ DESCRIPTOR, GROUP_ and USER_DATA_CUST_DIM dimensions.
The determination of special information tone (SIT) values in this view depends on the underlying signaling lines, capabilities of the CPD Server, and the dialer, which maps SIT classifications to Genesys enumeration. Refer to the Genesys Outbound Contact documentation set for more information.
The same columns and column descriptions apply to other AG2_CAMPAIGN_* views.
|
|
|
|
|
|
|
Documentation:RAA:Library:View-AG2 CAMPAIGN HOUR:8.5PDMSource |
AG2_CAMPAIGN_HOUR |
|
[Show] This view represents the disposition-based aggregate AGT_CAMPAIGN_HOUR table, which provides a rollup of interactions generated by a particular campaign. Rollups are derived primarily from the CONTACT_ATTEMPT_FACT table with an inner join on CALL_RESULT. Counts and durations are attributed to the interval in which contact attempts were made. Aggregation is performed along the TENANT, DATE TIME, CAMPAIGN, MEDIA_TYPE, INTERACTION_ DESCRIPTOR, GROUP_ and USER_DATA_CUST_DIM dimensions.
The determination of special information tone (SIT) values in this view depends on the underlying signaling lines, capabilities of the CPD Server, and the dialer, which maps SIT classifications to Genesys enumeration. Refer to the Genesys Outbound Contact documentation set for more information.
The same columns and column descriptions apply to other AG2_CAMPAIGN_* views.
|
|
|
|
|
|
|
Documentation:RAA:Library:View-AG2 I AGENT HOUR:8.5DRAFT |
AG2_I_AGENT_HOUR |
|
[Show] This view represents the interval-based aggregate AGT_I_AGENT_HOUR table, which provides a rollup of an agent’s handling of interactions. Rollups are derived primarily from the INTERACTION_RESOURCE_FACT (IRF) and IXN_RESOURCE_STATE_FACT tables. Interactions that occur at DNs that have no associated agent are excluded, as are interactions that are received by unmonitored agents. No consideration is made as to whether interactions were distributed from a
queue or directly routed from the switch. Aggregation is performed along the TENANT, DATE_TIME, MEDIA_ TYPE, RESOURCE_, INTERACTION_TYPE, and RESOURCE_GROUP_COMBINATION dimensions. The combination of keys to these dimensions uniquely identifies records in this view.
The same columns and column descriptions apply to other AG2_I_AGENT_* views.
|
|
|
|
|
|
|
Documentation:RAA:Library:View-AG2 I AGENT HOUR:8.5PDMSource |
AG2_I_AGENT_HOUR |
|
[Show] This view represents the interval-based aggregate AGT_I_AGENT_HOUR table, which provides a rollup of an agent’s handling of interactions. Rollups are derived primarily from the INTERACTION_RESOURCE_FACT (IRF) and IXN_RESOURCE_STATE_FACT tables. Interactions that occur at DNs that have no associated agent are excluded, as are interactions that are received by unmonitored agents. No consideration is made as to whether interactions were distributed from a
queue or directly routed from the switch. Aggregation is performed along the TENANT, DATE_TIME, MEDIA_ TYPE, RESOURCE_, INTERACTION_TYPE, and RESOURCE_GROUP_COMBINATION dimensions. The combination of keys to these dimensions uniquely identifies records in this view.
The same columns and column descriptions apply to other AG2_I_AGENT_* views.
|
|
|
|
|
|
|