PDMViewColumnDPL
This template provides the DPL call to populate the Column List table on View pages. It does not use a phantom template for formatting.
{{#dpl:
|namespace=Documentation
|titlematch={{#switch:{{PONYDOCSSTATUS}}
|unreleased
|preview = {{#switch:{{#explode:{{FULLPAGENAME}}|:|1}}
|PSAAS=GIM:Library:{{anchorencode:{{#explode:{{FULLPAGENAME}}|:|3}}}}:8.5DRAFT
|GIM
|#default= {{#explode:{{FULLPAGENAME}}|:|1}}:Library:{{anchorencode:{{#explode:{{FULLPAGENAME}}|:|3}}}}:{{PONYDOCSVERSION}}}}
|released= {{#switch:{{#explode:{{FULLPAGENAME}}|:|1}}
|PSAAS=GIM:Library:{{anchorencode:{{#explode:{{FULLPAGENAME}}|:|3}}}}:8.5PDMSource
|GIM
|#default= {{#explode:{{FULLPAGENAME}}|:|1}}:Library:{{anchorencode:{{#explode:{{FULLPAGENAME}}|:|3}}}}:{{#sub:{{#explode:{{FULLPAGENAME}}|:|4}}|0|3}}PDMSource}}}}
|uses=Template:PDMViewColumn
|noresultsheader=No results
|include={PDMViewColumn}:colName:colDesc
|table=,-,'''Column''','''Description'''
|skipthispage=no
}}
| Column | Description |
|---|---|
| AUDIT_KEY | The primary key of this table and the surrogate key that is used to join this table to GIDB, merge tables, and dimensional model tables. |
| JOB_ID | ID that uniquely identifies the execution instance of the job. |
| CREATED | The date and time of row creation. |
| INSERTED | The UTC-equivalent date and time when the processing of the logical transaction described by this row was completed and the record was inserted into the database. |
| PROCESSING_STATUS_KEY | Reference to the CTL_PROCESSING_STATUS dimension. This field is reserved. |
| MIN_START_DATE_TIME_KEY | The minimum value of START_DATE_TIME_KEY that is committed in a transaction. If partitioning is enabled, this value helps to identify fact-table partition(s) in which data was inserted or updated. |
| MAX_START_DATE_TIME_KEY | The maximum value of START_DATE_TIME_KEY that is committed in a transaction. If partitioning is enabled, this value helps to identify fact-table partition(s) in which data was inserted or updated. |
| MAX_CHUNK_TS | The maximum value out of all timestamps that are stored for a particular chunk of data that is marked with the corresponding audit key. |
| DATA_SOURCE_KEY | The surrogate key that is used to join to the CTL_DS dimension. It specifies the data source server, such as T-Server, Interaction Server, Configuration Server, Outbound Contact Server (OCS), and Genesys Info Mart Server itself. |
| ROW_COUNT | The number of records that are marked with this audit key. |
| CREATED_TS | The UTC-equivalent value of the date and time of row creation. |
| AUDIT_KEY | The primary key of this table and the surrogate key that is used to join this table to GIDB, merge tables, and dimensional model tables. |
| JOB_ID | ID that uniquely identifies the execution instance of the job. |
| CREATED | The date and time of row creation. |
| INSERTED | The UTC-equivalent date and time when the processing of the logical transaction described by this row was completed and the record was inserted into the database. |
| PROCESSING_STATUS_KEY | Reference to the CTL_PROCESSING_STATUS dimension. This field is reserved. |
| MIN_START_DATE_TIME_KEY | The minimum value of START_DATE_TIME_KEY that is committed in a transaction. If partitioning is enabled, this value helps to identify fact-table partition(s) in which data was inserted or updated. |
| MAX_START_DATE_TIME_KEY | The maximum value of START_DATE_TIME_KEY that is committed in a transaction. If partitioning is enabled, this value helps to identify fact-table partition(s) in which data was inserted or updated. |
| MAX_CHUNK_TS | The maximum value out of all timestamps that are stored for a particular chunk of data that is marked with the corresponding audit key. |
| DATA_SOURCE_KEY | The surrogate key that is used to join to the CTL_DS dimension. It specifies the data source server, such as T-Server, Interaction Server, Configuration Server, Outbound Contact Server (OCS), and Genesys Info Mart Server itself. |
| ROW_COUNT | The number of records that are marked with this audit key. |
| CREATED_TS | The UTC-equivalent value of the date and time of row creation. |
| AUDIT_KEY | The primary key of this table and the surrogate key that is used to join this table to GIDB, merge tables, and dimensional model tables. |
| JOB_ID | ID that uniquely identifies the execution instance of the job. |
| CREATED | The date and time of row creation. |
| INSERTED | The UTC-equivalent date and time when the processing of the logical transaction described by this row was completed and the record was inserted into the database. |
| PROCESSING_STATUS_KEY | Reference to the CTL_PROCESSING_STATUS dimension. This field is reserved. |
| MIN_START_DATE_TIME_KEY | The minimum value of START_DATE_TIME_KEY that is committed in a transaction. If partitioning is enabled, this value helps to identify fact-table partition(s) in which data was inserted or updated. |
| MAX_START_DATE_TIME_KEY | The maximum value of START_DATE_TIME_KEY that is committed in a transaction. If partitioning is enabled, this value helps to identify fact-table partition(s) in which data was inserted or updated. |
| MAX_CHUNK_TS | The maximum value out of all timestamps that are stored for a particular chunk of data that is marked with the corresponding audit key. |
| DATA_SOURCE_KEY | The surrogate key that is used to join to the CTL_DS dimension. It specifies the data source server, such as T-Server, Interaction Server, Configuration Server, Outbound Contact Server (OCS), and Genesys Info Mart Server itself. |
| ROW_COUNT | The number of records that are marked with this audit key. |
| CREATED_TS | The UTC-equivalent value of the date and time of row creation. |
| AUDIT_KEY | The primary key of this table and the surrogate key that is used to join this table to GIDB, merge tables, and dimensional model tables. |
| JOB_ID | ID that uniquely identifies the execution instance of the job. |
| CREATED | The date and time of row creation. |
| INSERTED | The UTC-equivalent date and time when the processing of the logical transaction described by this row was completed and the record was inserted into the database. |
| PROCESSING_STATUS_KEY | Reference to the CTL_PROCESSING_STATUS dimension. This field is reserved. |
| MIN_START_DATE_TIME_KEY | The minimum value of START_DATE_TIME_KEY that is committed in a transaction. If partitioning is enabled, this value helps to identify fact-table partition(s) in which data was inserted or updated. |
| MAX_START_DATE_TIME_KEY | The maximum value of START_DATE_TIME_KEY that is committed in a transaction. If partitioning is enabled, this value helps to identify fact-table partition(s) in which data was inserted or updated. |
| MAX_CHUNK_TS | The maximum value out of all timestamps that are stored for a particular chunk of data that is marked with the corresponding audit key. |
| DATA_SOURCE_KEY | The surrogate key that is used to join to the CTL_DS dimension. It specifies the data source server, such as T-Server, Interaction Server, Configuration Server, Outbound Contact Server (OCS), and Genesys Info Mart Server itself. |
| ROW_COUNT | The number of records that are marked with this audit key. |
| CREATED_TS | The UTC-equivalent value of the date and time of row creation. |
| JOB_ID | ID that uniquely identifies the execution instance of the job. |
| JOB_NAME | The name of the job, such as Job_ExtractICON. |
| JOB_VERSION | The version of the job, such as 8.1.000.10. |
| START_TIME | The date and time at which the first step started (UTC time zone). |
| END_TIME | The date and time at which the last step ended (UTC time zone). |
| DURATION | The duration of the job, in seconds. |
| STATUS | The status of the step, such as COMPLETE or FAILED. |
| JOB_ID | ID that uniquely identifies the execution instance of the job. |
| JOB_NAME | The name of the job, such as Job_ExtractICON. |
| JOB_VERSION | The version of the job, such as 8.1.000.10. |
| START_TIME | The date and time at which the first step started (UTC time zone). |
| END_TIME | The date and time at which the last step ended (UTC time zone). |
| DURATION | The duration of the job, in seconds. |
| STATUS | The status of the step, such as COMPLETE or FAILED. |
| JOB_ID | ID that uniquely identifies the execution instance of the job. |
| JOB_NAME | The name of the job, such as Job_ExtractICON. |
| JOB_VERSION | The version of the job, such as 8.1.000.10. |
| START_TIME | The date and time at which the first step started (UTC time zone). |
| END_TIME | The date and time at which the last step ended (UTC time zone). |
| DURATION | The duration of the job, in seconds. |
| STATUS | The status of the step, such as COMPLETE or FAILED. |
| JOB_ID | ID that uniquely identifies the execution instance of the job. |
| JOB_NAME | The name of the job, such as Job_ExtractICON. |
| JOB_VERSION | The version of the job, such as 8.1.000.10. |
| START_TIME | The date and time at which the first step started (UTC time zone). |
| END_TIME | The date and time at which the last step ended (UTC time zone). |
| DURATION | The duration of the job, in seconds. |
| STATUS | The status of the step, such as COMPLETE or FAILED. |
| JOB_ID | ID that uniquely identifies the execution instance of the job. |
| JOB_NAME | The name of the job, such as Job_ExtractICON. |
| JOB_VERSION | The version of the job, such as 8.1.000.10. |
| START_TIME | The date and time at which the first step started (UTC time zone). |
| END_TIME | The date and time at which the last step ended (UTC time zone). |
| DURATION | The duration of the job, in seconds. |
| STATUS | The status of the step, such as COMPLETE or FAILED. |
| JOB_ID | ID that uniquely identifies the execution instance of the job. |
| JOB_NAME | The name of the job, such as Job_ExtractICON. |
| JOB_VERSION | The version of the job, such as 8.1.000.10. |
| START_TIME | The date and time at which the first step started (UTC time zone). |
| END_TIME | The date and time at which the last step ended (UTC time zone). |
| DURATION | The duration of the job, in seconds. |
| STATUS | The status of the step, such as COMPLETE or FAILED. |
| JOB_ID | ID that uniquely identifies the execution instance of the job. |
| JOB_NAME | The name of the job, such as Job_ExtractICON. |
| JOB_VERSION | The version of the job, such as 8.1.000.10. |
| START_TIME | The date and time at which the first step started (UTC time zone). |
| END_TIME | The date and time at which the last step ended (UTC time zone). |
| DURATION | The duration of the job, in seconds. |
| STATUS | The status of the step, such as COMPLETE or FAILED. |
| JOB_ID | ID that uniquely identifies the execution instance of the job. |
| JOB_NAME | The name of the job, such as Job_ExtractICON. |
| JOB_VERSION | The version of the job, such as 8.1.000.10. |
| START_TIME | The date and time at which the first step started (UTC time zone). |
| END_TIME | The date and time at which the last step ended (UTC time zone). |
| DURATION | The duration of the job, in seconds. |
| STATUS | The status of the step, such as COMPLETE or FAILED. |
| JOB_ID | ID that uniquely identifies the execution instance of the job. |
| JOB_NAME | The name of the job, such as Job_ExtractICON. |
| WORKFLOW_TYPE | The name of the ETL job step, such as Outbound. |
| JOB_VERSION | The version of the job, such as 8.1.000.10. |
| START_TIME | The date and time at which the first step started (UTC time zone). |
| END_TIME | The date and time at which the last step ended (UTC time zone). |
| DURATION | The duration of the job, in seconds. |
| STATUS | The status of the step, such as COMPLETE or FAILED. |
| JOB_ID | ID that uniquely identifies the execution instance of the job. |
| JOB_NAME | The name of the job, such as Job_ExtractICON. |
| WORKFLOW_TYPE | The name of the ETL job step, such as Outbound. |
| JOB_VERSION | The version of the job, such as 8.1.000.10. |
| START_TIME | The date and time at which the first step started (UTC time zone). |
| END_TIME | The date and time at which the last step ended (UTC time zone). |
| DURATION | The duration of the job, in seconds. |
| STATUS | The status of the step, such as COMPLETE or FAILED. |
| JOB_ID | ID that uniquely identifies the execution instance of the job. |
| JOB_NAME | The name of the job, such as Job_ExtractICON. |
| JOB_VERSION | The version of the job, such as 8.1.000.10. |
| START_TIME | The date and time at which the first step started (UTC time zone). |
| END_TIME | The date and time at which the last step ended (UTC time zone). |
| DURATION | The duration of the job, in seconds. |
| DBCONNECTION | The name of the Database Access Point (DAP) through which data was extracted. |
| ICON_DBID | ID that uniquely identifies the ICON application instance. Applies only to tables extracted by Job_ExtractICON. |
| TABLE_NAME | The name of the table from which data is extracted. |
| LATEST_DATA_TIME | Provides the highest timestamp value for the records that are extracted in a given extraction cycle. |
| ROW_COUNT | Provides the number of records that are extracted in a given extraction cycle. |
| JOB_ID | ID that uniquely identifies the execution instance of the job. |
| JOB_NAME | The name of the job, such as Job_ExtractICON. |
| JOB_VERSION | The version of the job, such as 8.1.000.10. |
| START_TIME | The date and time at which the first step started (UTC time zone). |
| END_TIME | The date and time at which the last step ended (UTC time zone). |
| DURATION | The duration of the job, in seconds. |
| DBCONNECTION | The name of the Database Access Point (DAP) through which data was extracted. |
| ICON_DBID | ID that uniquely identifies the ICON application instance. Applies only to tables extracted by Job_ExtractICON. |
| TABLE_NAME | The name of the table from which data is extracted. |
| LATEST_DATA_TIME | Provides the highest timestamp value for the records that are extracted in a given extraction cycle. |
| ROW_COUNT | Provides the number of records that are extracted in a given extraction cycle. |
| JOB_ID | ID that uniquely identifies the execution instance of the job. |
| JOB_NAME | The name of the job, such as Job_ExtractICON. |
| JOB_VERSION | The version of the job, such as 8.1.000.10. |
| START_TIME | The date and time at which the first step started (UTC time zone). |
| END_TIME | The date and time at which the last step ended (UTC time zone). |
| DURATION | The duration of the job, in seconds. |
| DBCONNECTION | The name of the Database Access Point (DAP) through which data was extracted. |
| ICON_DBID | ID that uniquely identifies the ICON application instance. Applies only to tables extracted by Job_ExtractICON. |
| TABLE_NAME | The name of the table from which data is extracted. |
| LATEST_DATA_TIME | Provides the highest timestamp value for the records that are extracted in a given extraction cycle. |
| ROW_COUNT | Provides the number of records that are extracted in a given extraction cycle. |
| JOB_ID | ID that uniquely identifies the execution instance of the job. |
| JOB_NAME | The name of the job, such as Job_ExtractICON. |
| JOB_VERSION | The version of the job, such as 8.1.000.10. |
| START_TIME | The date and time at which the first step started (UTC time zone). |
| END_TIME | The date and time at which the last step ended (UTC time zone). |
| DURATION | The duration of the job, in seconds. |
| DBCONNECTION | The name of the Database Access Point (DAP) through which data was extracted. |
| ICON_DBID | ID that uniquely identifies the ICON application instance. Applies only to tables extracted by Job_ExtractICON. |
| TABLE_NAME | The name of the table from which data is extracted. |
| LATEST_DATA_TIME | Provides the highest timestamp value for the records that are extracted in a given extraction cycle. |
| ROW_COUNT | Provides the number of records that are extracted in a given extraction cycle. |
| CALLING_LIST_KEY | The primary key of this view and the surrogate key that is used to join the CALLING_LIST dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| CALLING_LIST_NAME | The name of the calling list. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| DESCRIPTION | The description of the calling list. |
| CALLING_LIST_CFG_DBID | The calling list object identifier in the contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the calling list was added to IDB, which may differ from when the calling list was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the calling list was removed from contact center configuration. |
| CALLING_LIST_KEY | The primary key of this view and the surrogate key that is used to join the CALLING_LIST dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| CALLING_LIST_NAME | The name of the calling list. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| DESCRIPTION | The description of the calling list. |
| CALLING_LIST_CFG_DBID | The calling list object identifier in the contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the calling list was added to IDB, which may differ from when the calling list was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the calling list was removed from contact center configuration. |
| CALLING_LIST_KEY | The primary key of this view and the surrogate key that is used to join the CALLING_LIST dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| CALLING_LIST_NAME | The name of the calling list. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| DESCRIPTION | The description of the calling list. |
| CALLING_LIST_CFG_DBID | The calling list object identifier in the contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the calling list was added to IDB, which may differ from when the calling list was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the calling list was removed from contact center configuration. |
| CALLING_LIST_KEY | The primary key of this view and the surrogate key that is used to join the CALLING_LIST dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| CALLING_LIST_NAME | The name of the calling list. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| DESCRIPTION | The description of the calling list. |
| CALLING_LIST_CFG_DBID | The calling list object identifier in the contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the calling list was added to IDB, which may differ from when the calling list was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the calling list was removed from contact center configuration. |
| CALLING_LIST_TO_CAMP_FACT_KEY | The primary key of this view. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| CALLING_LIST_KEY | The surrogate key that is used to join the CALLING_LIST dimension to the fact tables. |
| CAMPAIGN_KEY | The surrogate key that is used to join the CAMPAIGN dimension to the fact tables. |
| START_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the calling list was added to the campaign. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the START_TS timestamp to an appropriate time zone. |
| END_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the calling list was removed from the campaign. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the END_TS timestamp to an appropriate time zone. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| START_TS | The UTC-equivalent value of the date and time when the calling list was added to the campaign in the contact center configuration. |
| END_TS | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, the UTC-equivalent value of the date and time when the calling list was removed from the campaign in the contact center configuration. For an active row, this value represents a UTC-equivalent value of the date and time far in the future, so that applications do not have to test for null. |
| TOTAL_DURATION | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, this value represents the total duration, in seconds, that the calling list was associated with the campaign. For an active row, this value represents the duration, in seconds, that the calling list was associated with the campaign, from start time to the time that the ETL last executed. |
| ACTIVE_FLAG | Indicates whether the association between the calling list and the campaign is still active: 0 = No, 1 = Yes. |
| PURGE_FLAG | This field is reserved. |
| CALLING_LIST_TO_CAMP_FACT_KEY | The primary key of this view. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| CALLING_LIST_KEY | The surrogate key that is used to join the CALLING_LIST dimension to the fact tables. |
| CAMPAIGN_KEY | The surrogate key that is used to join the CAMPAIGN dimension to the fact tables. |
| START_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the calling list was added to the campaign. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the START_TS timestamp to an appropriate time zone. |
| END_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the calling list was removed from the campaign. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the END_TS timestamp to an appropriate time zone. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| START_TS | The UTC-equivalent value of the date and time when the calling list was added to the campaign in the contact center configuration. |
| END_TS | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, the UTC-equivalent value of the date and time when the calling list was removed from the campaign in the contact center configuration. For an active row, this value represents a UTC-equivalent value of the date and time far in the future, so that applications do not have to test for null. |
| TOTAL_DURATION | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, this value represents the total duration, in seconds, that the calling list was associated with the campaign. For an active row, this value represents the duration, in seconds, that the calling list was associated with the campaign, from start time to the time that the ETL last executed. |
| ACTIVE_FLAG | Indicates whether the association between the calling list and the campaign is still active: 0 = No, 1 = Yes. |
| PURGE_FLAG | This field is reserved. |
| CALLING_LIST_TO_CAMP_FACT_KEY | The primary key of this view. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| CALLING_LIST_KEY | The surrogate key that is used to join the CALLING_LIST dimension to the fact tables. |
| CAMPAIGN_KEY | The surrogate key that is used to join the CAMPAIGN dimension to the fact tables. |
| START_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the calling list was added to the campaign. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the START_TS timestamp to an appropriate time zone. |
| END_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the calling list was removed from the campaign. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the END_TS timestamp to an appropriate time zone. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| START_TS | The UTC-equivalent value of the date and time when the calling list was added to the campaign in the contact center configuration. |
| END_TS | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, the UTC-equivalent value of the date and time when the calling list was removed from the campaign in the contact center configuration. For an active row, this value represents a UTC-equivalent value of the date and time far in the future, so that applications do not have to test for null. |
| TOTAL_DURATION | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, this value represents the total duration, in seconds, that the calling list was associated with the campaign. For an active row, this value represents the duration, in seconds, that the calling list was associated with the campaign, from start time to the time that the ETL last executed. |
| ACTIVE_FLAG | Indicates whether the association between the calling list and the campaign is still active: 0 = No, 1 = Yes. |
| PURGE_FLAG | This field is reserved. |
| CALLING_LIST_TO_CAMP_FACT_KEY | The primary key of this view. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| CALLING_LIST_KEY | The surrogate key that is used to join the CALLING_LIST dimension to the fact tables. |
| CAMPAIGN_KEY | The surrogate key that is used to join the CAMPAIGN dimension to the fact tables. |
| START_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the calling list was added to the campaign. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the START_TS timestamp to an appropriate time zone. |
| END_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the calling list was removed from the campaign. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the END_TS timestamp to an appropriate time zone. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| START_TS | The UTC-equivalent value of the date and time when the calling list was added to the campaign in the contact center configuration. |
| END_TS | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, the UTC-equivalent value of the date and time when the calling list was removed from the campaign in the contact center configuration. For an active row, this value represents a UTC-equivalent value of the date and time far in the future, so that applications do not have to test for null. |
| TOTAL_DURATION | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, this value represents the total duration, in seconds, that the calling list was associated with the campaign. For an active row, this value represents the duration, in seconds, that the calling list was associated with the campaign, from start time to the time that the ETL last executed. |
| ACTIVE_FLAG | Indicates whether the association between the calling list and the campaign is still active: 0 = No, 1 = Yes. |
| PURGE_FLAG | This field is reserved. |
| CAMPAIGN_KEY | The surrogate key that is used to join the CAMPAIGN dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| CAMPAIGN_NAME | The name of the campaign object in Configuration Server. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| DESCRIPTION | The description of the campaign. |
| CAMPAIGN_CFG_DBID | The campaign object identifier in contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the campaign was added to IDB, which may differ from when the campaign was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the campaign object was removed from contact center configuration. |
| CAMPAIGN_KEY | The surrogate key that is used to join the CAMPAIGN dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| CAMPAIGN_NAME | The name of the campaign object in Configuration Server. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| DESCRIPTION | The description of the campaign. |
| CAMPAIGN_CFG_DBID | The campaign object identifier in contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the campaign was added to IDB, which may differ from when the campaign was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the campaign object was removed from contact center configuration. |
| CAMPAIGN_KEY | The surrogate key that is used to join the CAMPAIGN dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| CAMPAIGN_NAME | The name of the campaign object in Configuration Server. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| DESCRIPTION | The description of the campaign. |
| CAMPAIGN_CFG_DBID | The campaign object identifier in contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the campaign was added to IDB, which may differ from when the campaign was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the campaign object was removed from contact center configuration. |
| CAMPAIGN_KEY | The surrogate key that is used to join the CAMPAIGN dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| CAMPAIGN_NAME | The name of the campaign object in Configuration Server. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| DESCRIPTION | The description of the campaign. |
| CAMPAIGN_CFG_DBID | The campaign object identifier in contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the campaign was added to IDB, which may differ from when the campaign was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the campaign object was removed from contact center configuration. |
| ID | |
| INTERACTION_ID | |
| MEDIA_TYPE | |
| INTERACTION_TYPE | |
| ORIGINATOR | |
| TARGET | |
| PARTY_TYPE | |
| PARTY_NAME | |
| STATUS | |
| START_TS | The UTC-equivalent value of the date and time when the calling list was added to IDB, which may differ from when the calling list was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the calling list was removed from contact center configuration. |
| TIME_ZONE_CODE | |
| START_DATE_TIME_STRING | |
| END_DATE_TIME_STRING | |
| FIRST_LEG_FLAG | |
| CONNECTED_FLAG | |
| ELAPSED_DURATION | |
| ENGAGE_DURATION | |
| CONFERENCE_ENGAGE_DURATION | |
| CONSULTATION_ENGAGE_DURATION | |
| HOLD_DURATION | |
| ORDINAL | |
| TECHNICAL_RESULT | |
| PARTY_ROLE | |
| TENANT_KEY | The surrogate key that is used to join to the TENANT dimension. |
| ID | |
| INTERACTION_ID | |
| MEDIA_TYPE | |
| INTERACTION_TYPE | |
| ORIGINATOR | |
| TARGET | |
| PARTY_TYPE | |
| PARTY_NAME | |
| STATUS | |
| START_TS | The UTC-equivalent value of the date and time when the calling list was added to IDB, which may differ from when the calling list was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the calling list was removed from contact center configuration. |
| TIME_ZONE_CODE | |
| START_DATE_TIME_STRING | |
| END_DATE_TIME_STRING | |
| FIRST_LEG_FLAG | |
| CONNECTED_FLAG | |
| ELAPSED_DURATION | |
| ENGAGE_DURATION | |
| CONFERENCE_ENGAGE_DURATION | |
| CONSULTATION_ENGAGE_DURATION | |
| HOLD_DURATION | |
| ORDINAL | |
| TECHNICAL_RESULT | |
| PARTY_ROLE | |
| TENANT_KEY | The surrogate key that is used to join to the TENANT dimension. |
| ID | |
| INTERACTION_ID | |
| MEDIA_TYPE | |
| INTERACTION_TYPE | |
| ORIGINATOR | |
| TARGET | |
| PARTY_TYPE | |
| PARTY_NAME | |
| STATUS | |
| START_TS | The UTC-equivalent value of the date and time when the calling list was added to IDB, which may differ from when the calling list was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the calling list was removed from contact center configuration. |
| TIME_ZONE_CODE | |
| START_DATE_TIME_STRING | |
| END_DATE_TIME_STRING | |
| FIRST_LEG_FLAG | |
| CONNECTED_FLAG | |
| ELAPSED_DURATION | |
| ENGAGE_DURATION | |
| CONFERENCE_ENGAGE_DURATION | |
| CONSULTATION_ENGAGE_DURATION | |
| HOLD_DURATION | |
| ORDINAL | |
| TECHNICAL_RESULT | |
| PARTY_ROLE | |
| TENANT_KEY | The surrogate key that is used to join to the TENANT dimension. |
| ID | |
| INTERACTION_ID | |
| MEDIA_TYPE | |
| INTERACTION_TYPE | |
| ORIGINATOR | |
| TARGET | |
| PARTY_TYPE | |
| PARTY_NAME | |
| STATUS | |
| START_TS | The UTC-equivalent value of the date and time when the calling list was added to IDB, which may differ from when the calling list was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the calling list was removed from contact center configuration. |
| TIME_ZONE_CODE | |
| START_DATE_TIME_STRING | |
| END_DATE_TIME_STRING | |
| FIRST_LEG_FLAG | |
| CONNECTED_FLAG | |
| ELAPSED_DURATION | |
| ENGAGE_DURATION | |
| CONFERENCE_ENGAGE_DURATION | |
| CONSULTATION_ENGAGE_DURATION | |
| HOLD_DURATION | |
| ORDINAL | |
| TECHNICAL_RESULT | |
| PARTY_ROLE | |
| TENANT_KEY | The surrogate key that is used to join to the TENANT dimension. |
| DATE_TIME_KEY | The primary key of this table. It is used to join a particular 15-minute interval in this table to the fact and aggregate tables. This field increases monotonically to facilitate the calculation of time interval ranges and is equal to the UTC-equivalent time at which the time interval started. |
| DATE_TIME_30MIN_KEY | The surrogate key that is used to join a particular 30-minute interval in this table to the fact and aggregate tables. Two rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the 30-minute interval. |
| DATE_TIME_HOUR_KEY | The surrogate key that is used to join a particular hour in this table to the fact and aggregate tables. Four rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the hour interval. |
| DATE_TIME_DAY_KEY | The surrogate key that is used to join a particular day in this table to the fact and aggregate tables. Ninety-six rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the day interval. |
| DATE_TIME_WEEK_KEY | The surrogate key that is used to join a particular week in this table to the fact and aggregate tables. Multiple rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the week interval. |
| DATE_TIME_MONTH_KEY | The surrogate key that is used to join a particular month in this table to the fact and aggregate tables. Multiple rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the month interval. |
| DATE_TIME_QUARTER_KEY | The surrogate key that is used to join a particular quarter in this table to the fact and aggregate tables. Multiple rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the quarter interval. |
| DATE_TIME_YEAR_KEY | The surrogate key that is used to join a particular year in this table to the fact and aggregate tables. Multiple rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the year interval. |
| DATE_TIME_NEXT_KEY | Points to the next record of this table. This value is DATE_TIME_KEY+1. |
| DATE_TIME_NEXT_30MIN_KEY | Points to the DATE_TIME_30MIN_KEY record that represents the next 30-minute period. |
| DATE_TIME_NEXT_HOUR_KEY | Points to the DATE_TIME_HOUR_KEY record that represents the next hour. |
| DATE_TIME_NEXT_DAY_KEY | Points to the DATE_TIME_DAY_KEY record that represents the next calendar day. |
| DATE_TIME_NEXT_WEEK_KEY | Points to the DATE_TIME_WEEK_KEY record that represents the next calendar week. |
| DATE_TIME_NEXT_MONTH_KEY | Points to the DATE_TIME_MONTH_KEY record that represents the next calendar month. |
| DATE_TIME_NEXT_QUARTER_KEY | Points to the DATE_TIME_QUARTER_KEY record that represents the next calendar quarter. |
| DATE_TIME_NEXT_YEAR_KEY | Points to the DATE_TIME_YEAR_KEY record that represents the next year. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| CAL_DATE | The date/time data type for a calendar date that is specific for this RDBMS. |
| CAL_DAY_NAME | The calendar day name — for example, "Sunday". |
| CAL_MONTH_NAME | The calendar month name — for example, "January". |
| CAL_DAY_NUM_IN_WEEK | The day number in a week. By default, the values start with 1 for Sunday and end with 7 for Saturday. If another day is configured as the first day of the week, the value 1 is populated for that day, the value 2 is populated for the subsequent day, and so forth. For example, if Monday is configured as the first day of the week (that is, the first-day-of-week configuration option is set to 2), the CAL_DAY_NUM_IN_WEEK values start with 1 for Monday and end with 7 for Sunday. |
| CAL_DAY_NUM_IN_MONTH | The day number in the calendar month, starting with 1 and ending with 28, 29, 30, or 31, depending on the month. |
| CAL_DAY_NUM_IN_YEAR | The day number in the calendar year, starting with 1 for January 1 and ending with 365 or 366 for December 31. |
| CAL_LAST_DAY_IN_WEEK | The indicator for the last day of the calendar week: 0 = No, 1 = Yes. For example, this value may be 0 for Wednesday records and 1 for Saturday records. |
| CAL_LAST_DAY_IN_MONTH | The indicator for the last day of the calendar month: 0 = No, 1 = Yes. For example, this value is set to 0 for January 16 and 1 for January 31. |
| CAL_WEEK_NUM_IN_YEAR | The week number in the calendar year, starting with 1 and ending with 53. The first week begins on the first day of the calendar year and may contain fewer than seven days. Likewise, the last week, ending with the last day of the year, may contain fewer than seven days. |
| WEEK_YEAR | The year number for the week to which this day belongs. By default, the week year matches the calendar year. If the week numbering is configured to differ from the simple week numbering (for example, for the purpose of financial reports), the year number that is stored for the first and last weeks differs from the year number of the calendar year. |
| CAL_WEEK_START_DATE | The start date of the calendar week to which this date belongs. All dates in the same calendar week share the same calendar week start date. For example, if a week starts on Sunday, this value is March 7, 2010 for all dates between March 7, 2010 and March 13, 2010. |
| CAL_WEEK_END_DATE | The end date of the calendar week to which this date belongs. All dates in the same calendar week share the same calendar week end date. For example, if a week starts on Sunday, this value is March 13, 2010 for all dates between March 7, 2010 and March 13, 2010. |
| CAL_MONTH_NUM_IN_YEAR | The month number in the calendar year, starting with 1 for January and ending with 12 for December. |
| CAL_QUARTER_NUM_IN_YEAR | The number of the quarter in the calendar year, starting with 1 for the first quarter (January 1 through March 31) and ending with 4 for the fourth quarter (October 1 through December 31). |
| CAL_HALF_NUM_IN_YEAR | The number of the half of the calendar year, starting with 1 for January 1 through June 30 and ending with 2 for July 1 through December 31. |
| CAL_YEAR_NUM | The Gregorian calendar year, expressed as a four-digit integer — for example, 2010. |
| CAL_HOUR_NUM_IN_DAY | The hour of the day, expressed as an integer from 1-12. This field is intended to be used in conjunction with the AMPM_INDICATOR field. |
| CAL_HOUR_24_NUM_IN_DAY | The hour of the day, as an integer from 00 to 23. |
| CAL_MINUTE_NUM_IN_HOUR | The 15-minute number of the hour. This field is set to one of the following values:
|
| CAL_30MINUTE_NUM_IN_HOUR | The 30-minute number of the hour. This field is set to one of the following values:
|
| LABEL_YYYY | The current date expressed as a string in YYYY format, where YYYY represents a four-digit year. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010". |
| LABEL_YYYY_QQ | The current date, expressed as a string in YYYY QQ format, where QQ represents the number of the quarter (1-4), followed by the letter "Q", which is not localizable. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010 1Q". |
| LABEL_YYYY_MM | The current date, expressed as a string in YYYY-MM format, where MM represents the two-digit month. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01". |
| LABEL_YYYY_WE | The current date, expressed as a string in YYYY-Www format, where Www represents the two-digit week number of the year, preceded by the letter "W". This field is useful when it is used as a label in report headers. For example, with simple week numbering, the label that this field stores for January 30, 2010, at 15:45 is "2010-W05" (January 30, 2010 fell in the fifth week of the year). |
| LABEL_YYYY_WE_D | The current date expressed as a string in YYYY-Www-D format, where Www represents the two-digit week number of the year, preceded by the letter "W", and D represents the day number in the week. This field is useful when used as a label in report headers. For example, with simple week numbering, the label that this field stores for January 30, 2010, at 15:45 is "2010-05-1" (January 30, 2010 fell in the fifth week of the year, and Sunday is the first day of the week). |
| LABEL_YYYY_MM_DD | The current date, expressed as a string in YYYY-MM-DD format, where DD represents the two-digit day of the month. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30". |
| LABEL_YYYY_MM_DD_HH | The current date, expressed as a string in YYYY-MM-DD HH format, where hour (HH) values range from 01 to 12. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 03". |
| LABEL_YYYY_MM_DD_HH24 | The current date, expressed as a string in YYYY-MM-DD HH format where hour (HH) values range from 01 to 24. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 15". |
| LABEL_YYYY_MM_DD_HH_30MI | The current date, expressed as a string in YYYY-MM-DD HH:mm format, where hour (HH) values range from 01 to 12 and mm represents the closest 30-minute period that is less than or equal to the actual minute. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 03:30". |
| LABEL_YYYY_MM_DD_HH24_30MI | The current date, expressed as a string in YYYY-MM-DD HH:mm format, where hour (HH) values range from 01 to 24 and mm represents the closest 30-minute period that is less than or equal to the actual minute. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 15:30". |
| LABEL_YYYY_MM_DD_HH_MI | The current date, expressed as a string in YYYY-MM-DD HH:mm format, where hour (HH) values range from 01 to 12 and mm represents the actual minute. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 03:45". |
| LABEL_YYYY_MM_DD_HH24_MI | The current date, expressed as a string in YYYY-MM-DD HH:mm format, where hour (HH) values range from 01 to 24 and mm represents the actual minute. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 15:45". |
| LABEL_YYYY_MM_DD_HH_15INT | The current date, expressed as a string in YYYY-MM-DD 15INT format, where 15INT represents the 15-minute interval within the day. Hour values range from 01 to 12. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 03:45-04:00". |
| LABEL_YYYY_MM_DD_HH24_15INT | The current date, expressed as a string in YYYY-MM-DD 15INT format, where 15INT represents the 15-minute interval within the day and includes the hour, in a range from 01 to 24. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 15:45-16:00". |
| LABEL_YYYY_MM_DD_HH_30INT | The current date, expressed as a string in YYYY-MM-DD 30INT format, where 30INT represents the 30-minute interval within the day and includes the hour, in a range from 01 to 12. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 03:30-04:00". |
| LABEL_YYYY_MM_DD_HH24_30INT | The current date, expressed as a string in YYYY-MM-DD 30INT format, where 30INT represents the 30-minute interval within the day and includes the hour, in a range from 01 to 24. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 15:30-16:00". |
| LABEL_QQ | A string representation of the current date, expressed in QQ format, where QQ represents the number of the quarter (1-4), followed by the letter "Q", which is not localizable. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "1Q". |
| LABEL_MM | A string representation of the current date, expressed in MM format, where MM represents the two-digit month. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "01". |
| LABEL_WE | A string representation of the current date, expressed in Www format, where Www represents the two-digit week number of the year, preceded by the letter "W". This field is useful when it is used as a label for report headers. For example, with simple week numbering, the label that this field stores for January 30, 2010, at 15:45 is "W05". (January 30, 2010 falls in the fifth week of the year.) |
| LABEL_DD | A string representation of the current date, expressed in DD format, where DD represents the two-digit day of the month. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "30". |
| LABEL_HH | A string representation of the current date, expressed in HH format, where hour (HH) values range from 01 to 12. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "03". |
| LABEL_HH24 | A string representation of the current date, expressed in HH format, where hour (HH) values range from 01 to 24. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "15". |
| LABEL_30MI | A string representation of the current date, expressed in mm format, where mm represents the closest 30-minute period that is less than or equal to the actual minute. For example, the label that this field stores for January 30, 2010, at 15:45 is "30". |
| LABEL_MI | A string representation of the current date, expressed in mm format, where mm represents the actual minute. For example, the label that this field stores for January 30, 2010, at 15:45 is "45". |
| LABEL_TZ | A string representation of the time zone designator, as defined in ISO 8601 standard. For the time zone in which the UTC offset is equal zero, the letter "Z" is stored as the time zone designator. The zone designator for other time zones is specified by the offset from UTC in the format ±HH:<mm>, where HH represents hours and mm represents minutes, if applicable. For example, if the time that is being described is one hour ahead of UTC, the stored value would be "+01". |
| AMPM_INDICATOR | Indicates the period between midnight and noon ("AM") or between noon and midnight ("PM"). |
| RUNNING_YEAR_NUM | The running year number, starting with 1 for the year that is populated as the first year in this calendar. The date-time-start-year configuration option controls the starting year. By default, the calendar starts with the year that precedes the DATE_TIME table initialization. For example, if the Genesys Info Mart database is initiated in year 2010, this field stores the value of 2 for rows that are generated for 2010 dates. |
| RUNNING_QUARTER_NUM | The running quarter number, starting with 1 as the first quarter of the first year that is populated for this calendar. Running values do not reset at the beginning of each year, so that this value is 1-4, respectively, for the four quarters of the first populated year (for example, 2009); 5-8, respectively, for the four quarters of the second populated year (in this example, 2010); and so forth. |
| RUNNING_MONTH_NUM | The running month number, starting with 1 as the first month of the first year that is populated for this calendar. Running values do not reset at the beginning of each year, so that this value is 1-12, respectively, for the 12 months of the first populated year (for example, 2009); 13-24, respectively, for the 12 months of the second populated year (in this example, 2010); and so forth. |
| RUNNING_WEEK_NUM | The running week number, starting with 1 as the first week of the first year that is populated for this calendar. Running values do not reset at the beginning of each year, so that, with simple week numbering, this value is 1-53, respectively, for the 53 weeks of the first populated year (for example, 2009); 54-107, respectively, for the 53 weeks of the second populated year (in this example, 2010); and so forth. |
| RUNNING_DAY_NUM | The running day number, starting with 1 as the first day of the first year that is populated for this calendar. Running values do not reset at the beginning of each year, so that this value is 1-365, respectively, for the 365 days of the first populated year (for example, 2009); 366-730, respectively, for the 365 days of the second populated year (in this example, 2010); and so forth. |
| RUNNING_HOUR_NUM | The running hour number, starting with 1 as the first hour of the first day of the first year that is populated for this calendar. Running hours do not reset at the beginning of each day, so that this value is 1-24, respectively, for the 24 hours of the first populated day (for example, 1/1/2009); 25-48, respectively, for the 24 hours of the second populated day (in this example, 1/2/2009); and so forth. |
| RUNNING_30MIN_NUM | The running 30-minute number, starting with 1 as the first 30-minute interval of the first hour of the first day of the first year that is populated for this calendar. Running 30-minute periods do not reset at the beginning of each hour, so that this value is 1-2, respectively, for the two 30-minute intervals of the first hour of 1/1/2009, if 2009 is the first year populated for this calendar; 3-4, respectively, for the two 30-minute intervals in the second hour of this day; and so forth. |
| DATE_TIME_KEY | The primary key of this table. It is used to join a particular 15-minute interval in this table to the fact and aggregate tables. This field increases monotonically to facilitate the calculation of time interval ranges and is equal to the UTC-equivalent time at which the time interval started. |
| DATE_TIME_30MIN_KEY | The surrogate key that is used to join a particular 30-minute interval in this table to the fact and aggregate tables. Two rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the 30-minute interval. |
| DATE_TIME_HOUR_KEY | The surrogate key that is used to join a particular hour in this table to the fact and aggregate tables. Four rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the hour interval. |
| DATE_TIME_DAY_KEY | The surrogate key that is used to join a particular day in this table to the fact and aggregate tables. Ninety-six rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the day interval. |
| DATE_TIME_WEEK_KEY | The surrogate key that is used to join a particular week in this table to the fact and aggregate tables. Multiple rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the week interval. |
| DATE_TIME_MONTH_KEY | The surrogate key that is used to join a particular month in this table to the fact and aggregate tables. Multiple rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the month interval. |
| DATE_TIME_QUARTER_KEY | The surrogate key that is used to join a particular quarter in this table to the fact and aggregate tables. Multiple rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the quarter interval. |
| DATE_TIME_YEAR_KEY | The surrogate key that is used to join a particular year in this table to the fact and aggregate tables. Multiple rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the year interval. |
| DATE_TIME_NEXT_KEY | Points to the next record of this table. This value is DATE_TIME_KEY+1. |
| DATE_TIME_NEXT_30MIN_KEY | Points to the DATE_TIME_30MIN_KEY record that represents the next 30-minute period. |
| DATE_TIME_NEXT_HOUR_KEY | Points to the DATE_TIME_HOUR_KEY record that represents the next hour. |
| DATE_TIME_NEXT_DAY_KEY | Points to the DATE_TIME_DAY_KEY record that represents the next calendar day. |
| DATE_TIME_NEXT_WEEK_KEY | Points to the DATE_TIME_WEEK_KEY record that represents the next calendar week. |
| DATE_TIME_NEXT_MONTH_KEY | Points to the DATE_TIME_MONTH_KEY record that represents the next calendar month. |
| DATE_TIME_NEXT_QUARTER_KEY | Points to the DATE_TIME_QUARTER_KEY record that represents the next calendar quarter. |
| DATE_TIME_NEXT_YEAR_KEY | Points to the DATE_TIME_YEAR_KEY record that represents the next year. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| CAL_DATE | The date/time data type for a calendar date that is specific for this RDBMS. |
| CAL_DAY_NAME | The calendar day name — for example, "Sunday". |
| CAL_MONTH_NAME | The calendar month name — for example, "January". |
| CAL_DAY_NUM_IN_WEEK | The day number in a week. By default, the values start with 1 for Sunday and end with 7 for Saturday. If another day is configured as the first day of the week, the value 1 is populated for that day, the value 2 is populated for the subsequent day, and so forth. For example, if Monday is configured as the first day of the week (that is, the first-day-of-week configuration option is set to 2), the CAL_DAY_NUM_IN_WEEK values start with 1 for Monday and end with 7 for Sunday. |
| CAL_DAY_NUM_IN_MONTH | The day number in the calendar month, starting with 1 and ending with 28, 29, 30, or 31, depending on the month. |
| CAL_DAY_NUM_IN_YEAR | The day number in the calendar year, starting with 1 for January 1 and ending with 365 or 366 for December 31. |
| CAL_LAST_DAY_IN_WEEK | The indicator for the last day of the calendar week: 0 = No, 1 = Yes. For example, this value may be 0 for Wednesday records and 1 for Saturday records. |
| CAL_LAST_DAY_IN_MONTH | The indicator for the last day of the calendar month: 0 = No, 1 = Yes. For example, this value is set to 0 for January 16 and 1 for January 31. |
| CAL_WEEK_NUM_IN_YEAR | The week number in the calendar year, starting with 1 and ending with 53. The first week begins on the first day of the calendar year and may contain fewer than seven days. Likewise, the last week, ending with the last day of the year, may contain fewer than seven days. |
| WEEK_YEAR | The year number for the week to which this day belongs. By default, the week year matches the calendar year. If the week numbering is configured to differ from the simple week numbering (for example, for the purpose of financial reports), the year number that is stored for the first and last weeks differs from the year number of the calendar year. |
| CAL_WEEK_START_DATE | The start date of the calendar week to which this date belongs. All dates in the same calendar week share the same calendar week start date. For example, if a week starts on Sunday, this value is March 7, 2010 for all dates between March 7, 2010 and March 13, 2010. |
| CAL_WEEK_END_DATE | The end date of the calendar week to which this date belongs. All dates in the same calendar week share the same calendar week end date. For example, if a week starts on Sunday, this value is March 13, 2010 for all dates between March 7, 2010 and March 13, 2010. |
| CAL_MONTH_NUM_IN_YEAR | The month number in the calendar year, starting with 1 for January and ending with 12 for December. |
| CAL_QUARTER_NUM_IN_YEAR | The number of the quarter in the calendar year, starting with 1 for the first quarter (January 1 through March 31) and ending with 4 for the fourth quarter (October 1 through December 31). |
| CAL_HALF_NUM_IN_YEAR | The number of the half of the calendar year, starting with 1 for January 1 through June 30 and ending with 2 for July 1 through December 31. |
| CAL_YEAR_NUM | The Gregorian calendar year, expressed as a four-digit integer — for example, 2010. |
| CAL_HOUR_NUM_IN_DAY | The hour of the day, expressed as an integer from 1-12. This field is intended to be used in conjunction with the AMPM_INDICATOR field. |
| CAL_HOUR_24_NUM_IN_DAY | The hour of the day, as an integer from 00 to 23. |
| CAL_MINUTE_NUM_IN_HOUR | The 15-minute number of the hour. This field is set to one of the following values:
|
| CAL_30MINUTE_NUM_IN_HOUR | The 30-minute number of the hour. This field is set to one of the following values:
|
| LABEL_YYYY | The current date expressed as a string in YYYY format, where YYYY represents a four-digit year. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010". |
| LABEL_YYYY_QQ | The current date, expressed as a string in YYYY QQ format, where QQ represents the number of the quarter (1-4), followed by the letter "Q", which is not localizable. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010 1Q". |
| LABEL_YYYY_MM | The current date, expressed as a string in YYYY-MM format, where MM represents the two-digit month. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01". |
| LABEL_YYYY_WE | The current date, expressed as a string in YYYY-Www format, where Www represents the two-digit week number of the year, preceded by the letter "W". This field is useful when it is used as a label in report headers. For example, with simple week numbering, the label that this field stores for January 30, 2010, at 15:45 is "2010-W05" (January 30, 2010 fell in the fifth week of the year). |
| LABEL_YYYY_WE_D | The current date expressed as a string in YYYY-Www-D format, where Www represents the two-digit week number of the year, preceded by the letter "W", and D represents the day number in the week. This field is useful when used as a label in report headers. For example, with simple week numbering, the label that this field stores for January 30, 2010, at 15:45 is "2010-05-1" (January 30, 2010 fell in the fifth week of the year, and Sunday is the first day of the week). |
| LABEL_YYYY_MM_DD | The current date, expressed as a string in YYYY-MM-DD format, where DD represents the two-digit day of the month. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30". |
| LABEL_YYYY_MM_DD_HH | The current date, expressed as a string in YYYY-MM-DD HH format, where hour (HH) values range from 01 to 12. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 03". |
| LABEL_YYYY_MM_DD_HH24 | The current date, expressed as a string in YYYY-MM-DD HH format where hour (HH) values range from 01 to 24. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 15". |
| LABEL_YYYY_MM_DD_HH_30MI | The current date, expressed as a string in YYYY-MM-DD HH:mm format, where hour (HH) values range from 01 to 12 and mm represents the closest 30-minute period that is less than or equal to the actual minute. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 03:30". |
| LABEL_YYYY_MM_DD_HH24_30MI | The current date, expressed as a string in YYYY-MM-DD HH:mm format, where hour (HH) values range from 01 to 24 and mm represents the closest 30-minute period that is less than or equal to the actual minute. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 15:30". |
| LABEL_YYYY_MM_DD_HH_MI | The current date, expressed as a string in YYYY-MM-DD HH:mm format, where hour (HH) values range from 01 to 12 and mm represents the actual minute. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 03:45". |
| LABEL_YYYY_MM_DD_HH24_MI | The current date, expressed as a string in YYYY-MM-DD HH:mm format, where hour (HH) values range from 01 to 24 and mm represents the actual minute. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 15:45". |
| LABEL_YYYY_MM_DD_HH_15INT | The current date, expressed as a string in YYYY-MM-DD 15INT format, where 15INT represents the 15-minute interval within the day. Hour values range from 01 to 12. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 03:45-04:00". |
| LABEL_YYYY_MM_DD_HH24_15INT | The current date, expressed as a string in YYYY-MM-DD 15INT format, where 15INT represents the 15-minute interval within the day and includes the hour, in a range from 01 to 24. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 15:45-16:00". |
| LABEL_YYYY_MM_DD_HH_30INT | The current date, expressed as a string in YYYY-MM-DD 30INT format, where 30INT represents the 30-minute interval within the day and includes the hour, in a range from 01 to 12. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 03:30-04:00". |
| LABEL_YYYY_MM_DD_HH24_30INT | The current date, expressed as a string in YYYY-MM-DD 30INT format, where 30INT represents the 30-minute interval within the day and includes the hour, in a range from 01 to 24. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 15:30-16:00". |
| LABEL_QQ | A string representation of the current date, expressed in QQ format, where QQ represents the number of the quarter (1-4), followed by the letter "Q", which is not localizable. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "1Q". |
| LABEL_MM | A string representation of the current date, expressed in MM format, where MM represents the two-digit month. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "01". |
| LABEL_WE | A string representation of the current date, expressed in Www format, where Www represents the two-digit week number of the year, preceded by the letter "W". This field is useful when it is used as a label for report headers. For example, with simple week numbering, the label that this field stores for January 30, 2010, at 15:45 is "W05". (January 30, 2010 falls in the fifth week of the year.) |
| LABEL_DD | A string representation of the current date, expressed in DD format, where DD represents the two-digit day of the month. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "30". |
| LABEL_HH | A string representation of the current date, expressed in HH format, where hour (HH) values range from 01 to 12. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "03". |
| LABEL_HH24 | A string representation of the current date, expressed in HH format, where hour (HH) values range from 01 to 24. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "15". |
| LABEL_30MI | A string representation of the current date, expressed in mm format, where mm represents the closest 30-minute period that is less than or equal to the actual minute. For example, the label that this field stores for January 30, 2010, at 15:45 is "30". |
| LABEL_MI | A string representation of the current date, expressed in mm format, where mm represents the actual minute. For example, the label that this field stores for January 30, 2010, at 15:45 is "45". |
| LABEL_TZ | A string representation of the time zone designator, as defined in ISO 8601 standard. For the time zone in which the UTC offset is equal zero, the letter "Z" is stored as the time zone designator. The zone designator for other time zones is specified by the offset from UTC in the format ±HH:<mm>, where HH represents hours and mm represents minutes, if applicable. For example, if the time that is being described is one hour ahead of UTC, the stored value would be "+01". |
| AMPM_INDICATOR | Indicates the period between midnight and noon ("AM") or between noon and midnight ("PM"). |
| RUNNING_YEAR_NUM | The running year number, starting with 1 for the year that is populated as the first year in this calendar. The date-time-start-year configuration option controls the starting year. By default, the calendar starts with the year that precedes the DATE_TIME table initialization. For example, if the Genesys Info Mart database is initiated in year 2010, this field stores the value of 2 for rows that are generated for 2010 dates. |
| RUNNING_QUARTER_NUM | The running quarter number, starting with 1 as the first quarter of the first year that is populated for this calendar. Running values do not reset at the beginning of each year, so that this value is 1-4, respectively, for the four quarters of the first populated year (for example, 2009); 5-8, respectively, for the four quarters of the second populated year (in this example, 2010); and so forth. |
| RUNNING_MONTH_NUM | The running month number, starting with 1 as the first month of the first year that is populated for this calendar. Running values do not reset at the beginning of each year, so that this value is 1-12, respectively, for the 12 months of the first populated year (for example, 2009); 13-24, respectively, for the 12 months of the second populated year (in this example, 2010); and so forth. |
| RUNNING_WEEK_NUM | The running week number, starting with 1 as the first week of the first year that is populated for this calendar. Running values do not reset at the beginning of each year, so that, with simple week numbering, this value is 1-53, respectively, for the 53 weeks of the first populated year (for example, 2009); 54-107, respectively, for the 53 weeks of the second populated year (in this example, 2010); and so forth. |
| RUNNING_DAY_NUM | The running day number, starting with 1 as the first day of the first year that is populated for this calendar. Running values do not reset at the beginning of each year, so that this value is 1-365, respectively, for the 365 days of the first populated year (for example, 2009); 366-730, respectively, for the 365 days of the second populated year (in this example, 2010); and so forth. |
| RUNNING_HOUR_NUM | The running hour number, starting with 1 as the first hour of the first day of the first year that is populated for this calendar. Running hours do not reset at the beginning of each day, so that this value is 1-24, respectively, for the 24 hours of the first populated day (for example, 1/1/2009); 25-48, respectively, for the 24 hours of the second populated day (in this example, 1/2/2009); and so forth. |
| RUNNING_30MIN_NUM | The running 30-minute number, starting with 1 as the first 30-minute interval of the first hour of the first day of the first year that is populated for this calendar. Running 30-minute periods do not reset at the beginning of each hour, so that this value is 1-2, respectively, for the two 30-minute intervals of the first hour of 1/1/2009, if 2009 is the first year populated for this calendar; 3-4, respectively, for the two 30-minute intervals in the second hour of this day; and so forth. |
| DATE_TIME_KEY | The primary key of this table. It is used to join a particular 15-minute interval in this table to the fact and aggregate tables. This field increases monotonically to facilitate the calculation of time interval ranges and is equal to the UTC-equivalent time at which the time interval started. |
| DATE_TIME_30MIN_KEY | The surrogate key that is used to join a particular 30-minute interval in this table to the fact and aggregate tables. Two rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the 30-minute interval. |
| DATE_TIME_HOUR_KEY | The surrogate key that is used to join a particular hour in this table to the fact and aggregate tables. Four rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the hour interval. |
| DATE_TIME_DAY_KEY | The surrogate key that is used to join a particular day in this table to the fact and aggregate tables. Ninety-six rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the day interval. |
| DATE_TIME_WEEK_KEY | The surrogate key that is used to join a particular week in this table to the fact and aggregate tables. Multiple rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the week interval. |
| DATE_TIME_MONTH_KEY | The surrogate key that is used to join a particular month in this table to the fact and aggregate tables. Multiple rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the month interval. |
| DATE_TIME_QUARTER_KEY | The surrogate key that is used to join a particular quarter in this table to the fact and aggregate tables. Multiple rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the quarter interval. |
| DATE_TIME_YEAR_KEY | The surrogate key that is used to join a particular year in this table to the fact and aggregate tables. Multiple rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the year interval. |
| DATE_TIME_NEXT_KEY | Points to the next record of this table. This value is DATE_TIME_KEY+1. |
| DATE_TIME_NEXT_30MIN_KEY | Points to the DATE_TIME_30MIN_KEY record that represents the next 30-minute period. |
| DATE_TIME_NEXT_HOUR_KEY | Points to the DATE_TIME_HOUR_KEY record that represents the next hour. |
| DATE_TIME_NEXT_DAY_KEY | Points to the DATE_TIME_DAY_KEY record that represents the next calendar day. |
| DATE_TIME_NEXT_WEEK_KEY | Points to the DATE_TIME_WEEK_KEY record that represents the next calendar week. |
| DATE_TIME_NEXT_MONTH_KEY | Points to the DATE_TIME_MONTH_KEY record that represents the next calendar month. |
| DATE_TIME_NEXT_QUARTER_KEY | Points to the DATE_TIME_QUARTER_KEY record that represents the next calendar quarter. |
| DATE_TIME_NEXT_YEAR_KEY | Points to the DATE_TIME_YEAR_KEY record that represents the next year. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| CAL_DATE | The date/time data type for a calendar date that is specific for this RDBMS. |
| CAL_DAY_NAME | The calendar day name — for example, "Sunday". |
| CAL_MONTH_NAME | The calendar month name — for example, "January". |
| CAL_DAY_NUM_IN_WEEK | The day number in a week. By default, the values start with 1 for Sunday and end with 7 for Saturday. If another day is configured as the first day of the week, the value 1 is populated for that day, the value 2 is populated for the subsequent day, and so forth. For example, if Monday is configured as the first day of the week (that is, the first-day-of-week configuration option is set to 2), the CAL_DAY_NUM_IN_WEEK values start with 1 for Monday and end with 7 for Sunday. |
| CAL_DAY_NUM_IN_MONTH | The day number in the calendar month, starting with 1 and ending with 28, 29, 30, or 31, depending on the month. |
| CAL_DAY_NUM_IN_YEAR | The day number in the calendar year, starting with 1 for January 1 and ending with 365 or 366 for December 31. |
| CAL_LAST_DAY_IN_WEEK | The indicator for the last day of the calendar week: 0 = No, 1 = Yes. For example, this value may be 0 for Wednesday records and 1 for Saturday records. |
| CAL_LAST_DAY_IN_MONTH | The indicator for the last day of the calendar month: 0 = No, 1 = Yes. For example, this value is set to 0 for January 16 and 1 for January 31. |
| CAL_WEEK_NUM_IN_YEAR | The week number in the calendar year, starting with 1 and ending with 53. The first week begins on the first day of the calendar year and may contain fewer than seven days. Likewise, the last week, ending with the last day of the year, may contain fewer than seven days. |
| WEEK_YEAR | The year number for the week to which this day belongs. By default, the week year matches the calendar year. If the week numbering is configured to differ from the simple week numbering (for example, for the purpose of financial reports), the year number that is stored for the first and last weeks differs from the year number of the calendar year. |
| CAL_WEEK_START_DATE | The start date of the calendar week to which this date belongs. All dates in the same calendar week share the same calendar week start date. For example, if a week starts on Sunday, this value is March 7, 2010 for all dates between March 7, 2010 and March 13, 2010. |
| CAL_WEEK_END_DATE | The end date of the calendar week to which this date belongs. All dates in the same calendar week share the same calendar week end date. For example, if a week starts on Sunday, this value is March 13, 2010 for all dates between March 7, 2010 and March 13, 2010. |
| CAL_MONTH_NUM_IN_YEAR | The month number in the calendar year, starting with 1 for January and ending with 12 for December. |
| CAL_QUARTER_NUM_IN_YEAR | The number of the quarter in the calendar year, starting with 1 for the first quarter (January 1 through March 31) and ending with 4 for the fourth quarter (October 1 through December 31). |
| CAL_HALF_NUM_IN_YEAR | The number of the half of the calendar year, starting with 1 for January 1 through June 30 and ending with 2 for July 1 through December 31. |
| CAL_YEAR_NUM | The Gregorian calendar year, expressed as a four-digit integer — for example, 2010. |
| CAL_HOUR_NUM_IN_DAY | The hour of the day, expressed as an integer from 1-12. This field is intended to be used in conjunction with the AMPM_INDICATOR field. |
| CAL_HOUR_24_NUM_IN_DAY | The hour of the day, as an integer from 00 to 23. |
| CAL_MINUTE_NUM_IN_HOUR | The 15-minute number of the hour. This field is set to one of the following values:
|
| CAL_30MINUTE_NUM_IN_HOUR | The 30-minute number of the hour. This field is set to one of the following values:
|
| LABEL_YYYY | The current date expressed as a string in YYYY format, where YYYY represents a four-digit year. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010". |
| LABEL_YYYY_QQ | The current date, expressed as a string in YYYY QQ format, where QQ represents the number of the quarter (1-4), followed by the letter "Q", which is not localizable. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010 1Q". |
| LABEL_YYYY_MM | The current date, expressed as a string in YYYY-MM format, where MM represents the two-digit month. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01". |
| LABEL_YYYY_WE | The current date, expressed as a string in YYYY-Www format, where Www represents the two-digit week number of the year, preceded by the letter "W". This field is useful when it is used as a label in report headers. For example, with simple week numbering, the label that this field stores for January 30, 2010, at 15:45 is "2010-W05" (January 30, 2010 fell in the fifth week of the year). |
| LABEL_YYYY_WE_D | The current date expressed as a string in YYYY-Www-D format, where Www represents the two-digit week number of the year, preceded by the letter "W", and D represents the day number in the week. This field is useful when used as a label in report headers. For example, with simple week numbering, the label that this field stores for January 30, 2010, at 15:45 is "2010-05-1" (January 30, 2010 fell in the fifth week of the year, and Sunday is the first day of the week). |
| LABEL_YYYY_MM_DD | The current date, expressed as a string in YYYY-MM-DD format, where DD represents the two-digit day of the month. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30". |
| LABEL_YYYY_MM_DD_HH | The current date, expressed as a string in YYYY-MM-DD HH format, where hour (HH) values range from 01 to 12. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 03". |
| LABEL_YYYY_MM_DD_HH24 | The current date, expressed as a string in YYYY-MM-DD HH format where hour (HH) values range from 01 to 24. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 15". |
| LABEL_YYYY_MM_DD_HH_30MI | The current date, expressed as a string in YYYY-MM-DD HH:mm format, where hour (HH) values range from 01 to 12 and mm represents the closest 30-minute period that is less than or equal to the actual minute. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 03:30". |
| LABEL_YYYY_MM_DD_HH24_30MI | The current date, expressed as a string in YYYY-MM-DD HH:mm format, where hour (HH) values range from 01 to 24 and mm represents the closest 30-minute period that is less than or equal to the actual minute. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 15:30". |
| LABEL_YYYY_MM_DD_HH_MI | The current date, expressed as a string in YYYY-MM-DD HH:mm format, where hour (HH) values range from 01 to 12 and mm represents the actual minute. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 03:45". |
| LABEL_YYYY_MM_DD_HH24_MI | The current date, expressed as a string in YYYY-MM-DD HH:mm format, where hour (HH) values range from 01 to 24 and mm represents the actual minute. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 15:45". |
| LABEL_YYYY_MM_DD_HH_15INT | The current date, expressed as a string in YYYY-MM-DD 15INT format, where 15INT represents the 15-minute interval within the day. Hour values range from 01 to 12. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 03:45-04:00". |
| LABEL_YYYY_MM_DD_HH24_15INT | The current date, expressed as a string in YYYY-MM-DD 15INT format, where 15INT represents the 15-minute interval within the day and includes the hour, in a range from 01 to 24. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 15:45-16:00". |
| LABEL_YYYY_MM_DD_HH_30INT | The current date, expressed as a string in YYYY-MM-DD 30INT format, where 30INT represents the 30-minute interval within the day and includes the hour, in a range from 01 to 12. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 03:30-04:00". |
| LABEL_YYYY_MM_DD_HH24_30INT | The current date, expressed as a string in YYYY-MM-DD 30INT format, where 30INT represents the 30-minute interval within the day and includes the hour, in a range from 01 to 24. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 15:30-16:00". |
| LABEL_QQ | A string representation of the current date, expressed in QQ format, where QQ represents the number of the quarter (1-4), followed by the letter "Q", which is not localizable. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "1Q". |
| LABEL_MM | A string representation of the current date, expressed in MM format, where MM represents the two-digit month. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "01". |
| LABEL_WE | A string representation of the current date, expressed in Www format, where Www represents the two-digit week number of the year, preceded by the letter "W". This field is useful when it is used as a label for report headers. For example, with simple week numbering, the label that this field stores for January 30, 2010, at 15:45 is "W05". (January 30, 2010 falls in the fifth week of the year.) |
| LABEL_DD | A string representation of the current date, expressed in DD format, where DD represents the two-digit day of the month. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "30". |
| LABEL_HH | A string representation of the current date, expressed in HH format, where hour (HH) values range from 01 to 12. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "03". |
| LABEL_HH24 | A string representation of the current date, expressed in HH format, where hour (HH) values range from 01 to 24. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "15". |
| LABEL_30MI | A string representation of the current date, expressed in mm format, where mm represents the closest 30-minute period that is less than or equal to the actual minute. For example, the label that this field stores for January 30, 2010, at 15:45 is "30". |
| LABEL_MI | A string representation of the current date, expressed in mm format, where mm represents the actual minute. For example, the label that this field stores for January 30, 2010, at 15:45 is "45". |
| LABEL_TZ | A string representation of the time zone designator, as defined in ISO 8601 standard. For the time zone in which the UTC offset is equal zero, the letter "Z" is stored as the time zone designator. The zone designator for other time zones is specified by the offset from UTC in the format ±HH:<mm>, where HH represents hours and mm represents minutes, if applicable. For example, if the time that is being described is one hour ahead of UTC, the stored value would be "+01". |
| AMPM_INDICATOR | Indicates the period between midnight and noon ("AM") or between noon and midnight ("PM"). |
| RUNNING_YEAR_NUM | The running year number, starting with 1 for the year that is populated as the first year in this calendar. The date-time-start-year configuration option controls the starting year. By default, the calendar starts with the year that precedes the DATE_TIME table initialization. For example, if the Genesys Info Mart database is initiated in year 2010, this field stores the value of 2 for rows that are generated for 2010 dates. |
| RUNNING_QUARTER_NUM | The running quarter number, starting with 1 as the first quarter of the first year that is populated for this calendar. Running values do not reset at the beginning of each year, so that this value is 1-4, respectively, for the four quarters of the first populated year (for example, 2009); 5-8, respectively, for the four quarters of the second populated year (in this example, 2010); and so forth. |
| RUNNING_MONTH_NUM | The running month number, starting with 1 as the first month of the first year that is populated for this calendar. Running values do not reset at the beginning of each year, so that this value is 1-12, respectively, for the 12 months of the first populated year (for example, 2009); 13-24, respectively, for the 12 months of the second populated year (in this example, 2010); and so forth. |
| RUNNING_WEEK_NUM | The running week number, starting with 1 as the first week of the first year that is populated for this calendar. Running values do not reset at the beginning of each year, so that, with simple week numbering, this value is 1-53, respectively, for the 53 weeks of the first populated year (for example, 2009); 54-107, respectively, for the 53 weeks of the second populated year (in this example, 2010); and so forth. |
| RUNNING_DAY_NUM | The running day number, starting with 1 as the first day of the first year that is populated for this calendar. Running values do not reset at the beginning of each year, so that this value is 1-365, respectively, for the 365 days of the first populated year (for example, 2009); 366-730, respectively, for the 365 days of the second populated year (in this example, 2010); and so forth. |
| RUNNING_HOUR_NUM | The running hour number, starting with 1 as the first hour of the first day of the first year that is populated for this calendar. Running hours do not reset at the beginning of each day, so that this value is 1-24, respectively, for the 24 hours of the first populated day (for example, 1/1/2009); 25-48, respectively, for the 24 hours of the second populated day (in this example, 1/2/2009); and so forth. |
| RUNNING_30MIN_NUM | The running 30-minute number, starting with 1 as the first 30-minute interval of the first hour of the first day of the first year that is populated for this calendar. Running 30-minute periods do not reset at the beginning of each hour, so that this value is 1-2, respectively, for the two 30-minute intervals of the first hour of 1/1/2009, if 2009 is the first year populated for this calendar; 3-4, respectively, for the two 30-minute intervals in the second hour of this day; and so forth. |
| DATE_TIME_KEY | The primary key of this table. It is used to join a particular 15-minute interval in this table to the fact and aggregate tables. This field increases monotonically to facilitate the calculation of time interval ranges and is equal to the UTC-equivalent time at which the time interval started. |
| DATE_TIME_30MIN_KEY | The surrogate key that is used to join a particular 30-minute interval in this table to the fact and aggregate tables. Two rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the 30-minute interval. |
| DATE_TIME_HOUR_KEY | The surrogate key that is used to join a particular hour in this table to the fact and aggregate tables. Four rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the hour interval. |
| DATE_TIME_DAY_KEY | The surrogate key that is used to join a particular day in this table to the fact and aggregate tables. Ninety-six rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the day interval. |
| DATE_TIME_WEEK_KEY | The surrogate key that is used to join a particular week in this table to the fact and aggregate tables. Multiple rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the week interval. |
| DATE_TIME_MONTH_KEY | The surrogate key that is used to join a particular month in this table to the fact and aggregate tables. Multiple rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the month interval. |
| DATE_TIME_QUARTER_KEY | The surrogate key that is used to join a particular quarter in this table to the fact and aggregate tables. Multiple rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the quarter interval. |
| DATE_TIME_YEAR_KEY | The surrogate key that is used to join a particular year in this table to the fact and aggregate tables. Multiple rows in this table share the same value, which is the DATE_TIME_KEY that represents the start of the year interval. |
| DATE_TIME_NEXT_KEY | Points to the next record of this table. This value is DATE_TIME_KEY+1. |
| DATE_TIME_NEXT_30MIN_KEY | Points to the DATE_TIME_30MIN_KEY record that represents the next 30-minute period. |
| DATE_TIME_NEXT_HOUR_KEY | Points to the DATE_TIME_HOUR_KEY record that represents the next hour. |
| DATE_TIME_NEXT_DAY_KEY | Points to the DATE_TIME_DAY_KEY record that represents the next calendar day. |
| DATE_TIME_NEXT_WEEK_KEY | Points to the DATE_TIME_WEEK_KEY record that represents the next calendar week. |
| DATE_TIME_NEXT_MONTH_KEY | Points to the DATE_TIME_MONTH_KEY record that represents the next calendar month. |
| DATE_TIME_NEXT_QUARTER_KEY | Points to the DATE_TIME_QUARTER_KEY record that represents the next calendar quarter. |
| DATE_TIME_NEXT_YEAR_KEY | Points to the DATE_TIME_YEAR_KEY record that represents the next year. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| CAL_DATE | The date/time data type for a calendar date that is specific for this RDBMS. |
| CAL_DAY_NAME | The calendar day name — for example, "Sunday". |
| CAL_MONTH_NAME | The calendar month name — for example, "January". |
| CAL_DAY_NUM_IN_WEEK | The day number in a week. By default, the values start with 1 for Sunday and end with 7 for Saturday. If another day is configured as the first day of the week, the value 1 is populated for that day, the value 2 is populated for the subsequent day, and so forth. For example, if Monday is configured as the first day of the week (that is, the first-day-of-week configuration option is set to 2), the CAL_DAY_NUM_IN_WEEK values start with 1 for Monday and end with 7 for Sunday. |
| CAL_DAY_NUM_IN_MONTH | The day number in the calendar month, starting with 1 and ending with 28, 29, 30, or 31, depending on the month. |
| CAL_DAY_NUM_IN_YEAR | The day number in the calendar year, starting with 1 for January 1 and ending with 365 or 366 for December 31. |
| CAL_LAST_DAY_IN_WEEK | The indicator for the last day of the calendar week: 0 = No, 1 = Yes. For example, this value may be 0 for Wednesday records and 1 for Saturday records. |
| CAL_LAST_DAY_IN_MONTH | The indicator for the last day of the calendar month: 0 = No, 1 = Yes. For example, this value is set to 0 for January 16 and 1 for January 31. |
| CAL_WEEK_NUM_IN_YEAR | The week number in the calendar year, starting with 1 and ending with 53. The first week begins on the first day of the calendar year and may contain fewer than seven days. Likewise, the last week, ending with the last day of the year, may contain fewer than seven days. |
| WEEK_YEAR | The year number for the week to which this day belongs. By default, the week year matches the calendar year. If the week numbering is configured to differ from the simple week numbering (for example, for the purpose of financial reports), the year number that is stored for the first and last weeks differs from the year number of the calendar year. |
| CAL_WEEK_START_DATE | The start date of the calendar week to which this date belongs. All dates in the same calendar week share the same calendar week start date. For example, if a week starts on Sunday, this value is March 7, 2010 for all dates between March 7, 2010 and March 13, 2010. |
| CAL_WEEK_END_DATE | The end date of the calendar week to which this date belongs. All dates in the same calendar week share the same calendar week end date. For example, if a week starts on Sunday, this value is March 13, 2010 for all dates between March 7, 2010 and March 13, 2010. |
| CAL_MONTH_NUM_IN_YEAR | The month number in the calendar year, starting with 1 for January and ending with 12 for December. |
| CAL_QUARTER_NUM_IN_YEAR | The number of the quarter in the calendar year, starting with 1 for the first quarter (January 1 through March 31) and ending with 4 for the fourth quarter (October 1 through December 31). |
| CAL_HALF_NUM_IN_YEAR | The number of the half of the calendar year, starting with 1 for January 1 through June 30 and ending with 2 for July 1 through December 31. |
| CAL_YEAR_NUM | The Gregorian calendar year, expressed as a four-digit integer — for example, 2010. |
| CAL_HOUR_NUM_IN_DAY | The hour of the day, expressed as an integer from 1-12. This field is intended to be used in conjunction with the AMPM_INDICATOR field. |
| CAL_HOUR_24_NUM_IN_DAY | The hour of the day, as an integer from 00 to 23. |
| CAL_MINUTE_NUM_IN_HOUR | The 15-minute number of the hour. This field is set to one of the following values:
|
| CAL_30MINUTE_NUM_IN_HOUR | The 30-minute number of the hour. This field is set to one of the following values:
|
| LABEL_YYYY | The current date expressed as a string in YYYY format, where YYYY represents a four-digit year. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010". |
| LABEL_YYYY_QQ | The current date, expressed as a string in YYYY QQ format, where QQ represents the number of the quarter (1-4), followed by the letter "Q", which is not localizable. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010 1Q". |
| LABEL_YYYY_MM | The current date, expressed as a string in YYYY-MM format, where MM represents the two-digit month. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01". |
| LABEL_YYYY_WE | The current date, expressed as a string in YYYY-Www format, where Www represents the two-digit week number of the year, preceded by the letter "W". This field is useful when it is used as a label in report headers. For example, with simple week numbering, the label that this field stores for January 30, 2010, at 15:45 is "2010-W05" (January 30, 2010 fell in the fifth week of the year). |
| LABEL_YYYY_WE_D | The current date expressed as a string in YYYY-Www-D format, where Www represents the two-digit week number of the year, preceded by the letter "W", and D represents the day number in the week. This field is useful when used as a label in report headers. For example, with simple week numbering, the label that this field stores for January 30, 2010, at 15:45 is "2010-05-1" (January 30, 2010 fell in the fifth week of the year, and Sunday is the first day of the week). |
| LABEL_YYYY_MM_DD | The current date, expressed as a string in YYYY-MM-DD format, where DD represents the two-digit day of the month. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30". |
| LABEL_YYYY_MM_DD_HH | The current date, expressed as a string in YYYY-MM-DD HH format, where hour (HH) values range from 01 to 12. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 03". |
| LABEL_YYYY_MM_DD_HH24 | The current date, expressed as a string in YYYY-MM-DD HH format where hour (HH) values range from 01 to 24. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 15". |
| LABEL_YYYY_MM_DD_HH_30MI | The current date, expressed as a string in YYYY-MM-DD HH:mm format, where hour (HH) values range from 01 to 12 and mm represents the closest 30-minute period that is less than or equal to the actual minute. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 03:30". |
| LABEL_YYYY_MM_DD_HH24_30MI | The current date, expressed as a string in YYYY-MM-DD HH:mm format, where hour (HH) values range from 01 to 24 and mm represents the closest 30-minute period that is less than or equal to the actual minute. This field is useful when it is used as a label in report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 15:30". |
| LABEL_YYYY_MM_DD_HH_MI | The current date, expressed as a string in YYYY-MM-DD HH:mm format, where hour (HH) values range from 01 to 12 and mm represents the actual minute. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 03:45". |
| LABEL_YYYY_MM_DD_HH24_MI | The current date, expressed as a string in YYYY-MM-DD HH:mm format, where hour (HH) values range from 01 to 24 and mm represents the actual minute. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 15:45". |
| LABEL_YYYY_MM_DD_HH_15INT | The current date, expressed as a string in YYYY-MM-DD 15INT format, where 15INT represents the 15-minute interval within the day. Hour values range from 01 to 12. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 03:45-04:00". |
| LABEL_YYYY_MM_DD_HH24_15INT | The current date, expressed as a string in YYYY-MM-DD 15INT format, where 15INT represents the 15-minute interval within the day and includes the hour, in a range from 01 to 24. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 15:45-16:00". |
| LABEL_YYYY_MM_DD_HH_30INT | The current date, expressed as a string in YYYY-MM-DD 30INT format, where 30INT represents the 30-minute interval within the day and includes the hour, in a range from 01 to 12. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 03:30-04:00". |
| LABEL_YYYY_MM_DD_HH24_30INT | The current date, expressed as a string in YYYY-MM-DD 30INT format, where 30INT represents the 30-minute interval within the day and includes the hour, in a range from 01 to 24. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "2010-01-30 15:30-16:00". |
| LABEL_QQ | A string representation of the current date, expressed in QQ format, where QQ represents the number of the quarter (1-4), followed by the letter "Q", which is not localizable. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "1Q". |
| LABEL_MM | A string representation of the current date, expressed in MM format, where MM represents the two-digit month. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "01". |
| LABEL_WE | A string representation of the current date, expressed in Www format, where Www represents the two-digit week number of the year, preceded by the letter "W". This field is useful when it is used as a label for report headers. For example, with simple week numbering, the label that this field stores for January 30, 2010, at 15:45 is "W05". (January 30, 2010 falls in the fifth week of the year.) |
| LABEL_DD | A string representation of the current date, expressed in DD format, where DD represents the two-digit day of the month. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "30". |
| LABEL_HH | A string representation of the current date, expressed in HH format, where hour (HH) values range from 01 to 12. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "03". |
| LABEL_HH24 | A string representation of the current date, expressed in HH format, where hour (HH) values range from 01 to 24. This field is useful when it is used as a label for report headers. For example, the label that this field stores for January 30, 2010, at 15:45 is "15". |
| LABEL_30MI | A string representation of the current date, expressed in mm format, where mm represents the closest 30-minute period that is less than or equal to the actual minute. For example, the label that this field stores for January 30, 2010, at 15:45 is "30". |
| LABEL_MI | A string representation of the current date, expressed in mm format, where mm represents the actual minute. For example, the label that this field stores for January 30, 2010, at 15:45 is "45". |
| LABEL_TZ | A string representation of the time zone designator, as defined in ISO 8601 standard. For the time zone in which the UTC offset is equal zero, the letter "Z" is stored as the time zone designator. The zone designator for other time zones is specified by the offset from UTC in the format ±HH:<mm>, where HH represents hours and mm represents minutes, if applicable. For example, if the time that is being described is one hour ahead of UTC, the stored value would be "+01". |
| AMPM_INDICATOR | Indicates the period between midnight and noon ("AM") or between noon and midnight ("PM"). |
| RUNNING_YEAR_NUM | The running year number, starting with 1 for the year that is populated as the first year in this calendar. The date-time-start-year configuration option controls the starting year. By default, the calendar starts with the year that precedes the DATE_TIME table initialization. For example, if the Genesys Info Mart database is initiated in year 2010, this field stores the value of 2 for rows that are generated for 2010 dates. |
| RUNNING_QUARTER_NUM | The running quarter number, starting with 1 as the first quarter of the first year that is populated for this calendar. Running values do not reset at the beginning of each year, so that this value is 1-4, respectively, for the four quarters of the first populated year (for example, 2009); 5-8, respectively, for the four quarters of the second populated year (in this example, 2010); and so forth. |
| RUNNING_MONTH_NUM | The running month number, starting with 1 as the first month of the first year that is populated for this calendar. Running values do not reset at the beginning of each year, so that this value is 1-12, respectively, for the 12 months of the first populated year (for example, 2009); 13-24, respectively, for the 12 months of the second populated year (in this example, 2010); and so forth. |
| RUNNING_WEEK_NUM | The running week number, starting with 1 as the first week of the first year that is populated for this calendar. Running values do not reset at the beginning of each year, so that, with simple week numbering, this value is 1-53, respectively, for the 53 weeks of the first populated year (for example, 2009); 54-107, respectively, for the 53 weeks of the second populated year (in this example, 2010); and so forth. |
| RUNNING_DAY_NUM | The running day number, starting with 1 as the first day of the first year that is populated for this calendar. Running values do not reset at the beginning of each year, so that this value is 1-365, respectively, for the 365 days of the first populated year (for example, 2009); 366-730, respectively, for the 365 days of the second populated year (in this example, 2010); and so forth. |
| RUNNING_HOUR_NUM | The running hour number, starting with 1 as the first hour of the first day of the first year that is populated for this calendar. Running hours do not reset at the beginning of each day, so that this value is 1-24, respectively, for the 24 hours of the first populated day (for example, 1/1/2009); 25-48, respectively, for the 24 hours of the second populated day (in this example, 1/2/2009); and so forth. |
| RUNNING_30MIN_NUM | The running 30-minute number, starting with 1 as the first 30-minute interval of the first hour of the first day of the first year that is populated for this calendar. Running 30-minute periods do not reset at the beginning of each hour, so that this value is 1-2, respectively, for the two 30-minute intervals of the first hour of 1/1/2009, if 2009 is the first year populated for this calendar; 3-4, respectively, for the two 30-minute intervals in the second hour of this day; and so forth. |
| NAME | A combination of the job name and an abbreviated data type for the processed data. Either of the following values:
|
| LAST_TS | Provides a UTC equivalent of the date and time up to which the data has been processed. |
| GROUP_KEY | The primary key of this view that is used to join the GROUP_ dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| GROUP_NAME | The group name. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| GROUP_TYPE | The group type. This field is set to one of the following values:
This value can change with localization. |
| GROUP_TYPE_CODE | The group type code. This field is set to one of the following values:
This value does not change with localization. |
| GROUP_CFG_DBID | The group object identifier in the contact center configuration. |
| GROUP_CFG_TYPE_ID | The contact center configuration integer type that is associated with the DN or agent group object. |
| START_TS | The UTC-equivalent value of the date and time when the group was added to IDB, which may differ from when the group was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the group was removed from contact center configuration. |
| GROUP_KEY | The primary key of this view that is used to join the GROUP_ dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| GROUP_NAME | The group name. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| GROUP_TYPE | The group type. This field is set to one of the following values:
This value can change with localization. |
| GROUP_TYPE_CODE | The group type code. This field is set to one of the following values:
This value does not change with localization. |
| GROUP_CFG_DBID | The group object identifier in the contact center configuration. |
| GROUP_CFG_TYPE_ID | The contact center configuration integer type that is associated with the DN or agent group object. |
| START_TS | The UTC-equivalent value of the date and time when the group was added to IDB, which may differ from when the group was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the group was removed from contact center configuration. |
| GROUP_KEY | The primary key of this view that is used to join the GROUP_ dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| GROUP_NAME | The group name. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| GROUP_TYPE | The group type. This field is set to one of the following values:
This value can change with localization. |
| GROUP_TYPE_CODE | The group type code. This field is set to one of the following values:
This value does not change with localization. |
| GROUP_CFG_DBID | The group object identifier in the contact center configuration. |
| GROUP_CFG_TYPE_ID | The contact center configuration integer type that is associated with the DN or agent group object. |
| START_TS | The UTC-equivalent value of the date and time when the group was added to IDB, which may differ from when the group was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the group was removed from contact center configuration. |
| GROUP_KEY | The primary key of this view that is used to join the GROUP_ dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| GROUP_NAME | The group name. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| GROUP_TYPE | The group type. This field is set to one of the following values:
This value can change with localization. |
| GROUP_TYPE_CODE | The group type code. This field is set to one of the following values:
This value does not change with localization. |
| GROUP_CFG_DBID | The group object identifier in the contact center configuration. |
| GROUP_CFG_TYPE_ID | The contact center configuration integer type that is associated with the DN or agent group object. |
| START_TS | The UTC-equivalent value of the date and time when the group was added to IDB, which may differ from when the group was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the group was removed from contact center configuration. |
| GROUP_TO_CAMPAIGN_FACT_KEY | The primary key of this view. |
| GROUP_KEY | The surrogate key that is used to join the GROUP_ dimension to the fact tables. |
| CAMPAIGN_KEY | The surrogate key that is used to join the CAMPAIGN dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| START_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the agent group or place group was added to the campaign in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the START_TS timestamp to an appropriate time zone. |
| END_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the agent group or place group was removed from the campaign in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the END_TS timestamp to an appropriate time zone. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| START_TS | The UTC-equivalent value of the date and time when the agent group or place group was added to the campaign in the contact center configuration. |
| END_TS | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, the UTC-equivalent value of the date and time when the agent group or place group was removed from the campaign in the contact center configuration. For an active row, this value represents a UTC-equivalent value of the date and time far in the future, so that applications do not have to test for null. |
| TOTAL_DURATION | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, this value represents the total duration, in seconds, that the agent group or place group was associated with the campaign. For an active row, this value represents the duration, in seconds, that the agent group or place group was associated with the campaign, from start time to the time that the ETL last executed. |
| ACTIVE_FLAG | Indicates whether the association between the agent group or place group and the campaign is still active: 0 = No, 1 = Yes. |
| PURGE_FLAG | This field is reserved. |
| GROUP_TO_CAMPAIGN_FACT_KEY | The primary key of this view. |
| GROUP_KEY | The surrogate key that is used to join the GROUP_ dimension to the fact tables. |
| CAMPAIGN_KEY | The surrogate key that is used to join the CAMPAIGN dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| START_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the agent group or place group was added to the campaign in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the START_TS timestamp to an appropriate time zone. |
| END_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the agent group or place group was removed from the campaign in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the END_TS timestamp to an appropriate time zone. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| START_TS | The UTC-equivalent value of the date and time when the agent group or place group was added to the campaign in the contact center configuration. |
| END_TS | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, the UTC-equivalent value of the date and time when the agent group or place group was removed from the campaign in the contact center configuration. For an active row, this value represents a UTC-equivalent value of the date and time far in the future, so that applications do not have to test for null. |
| TOTAL_DURATION | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, this value represents the total duration, in seconds, that the agent group or place group was associated with the campaign. For an active row, this value represents the duration, in seconds, that the agent group or place group was associated with the campaign, from start time to the time that the ETL last executed. |
| ACTIVE_FLAG | Indicates whether the association between the agent group or place group and the campaign is still active: 0 = No, 1 = Yes. |
| PURGE_FLAG | This field is reserved. |
| GROUP_TO_CAMPAIGN_FACT_KEY | The primary key of this view. |
| GROUP_KEY | The surrogate key that is used to join the GROUP_ dimension to the fact tables. |
| CAMPAIGN_KEY | The surrogate key that is used to join the CAMPAIGN dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| START_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the agent group or place group was added to the campaign in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the START_TS timestamp to an appropriate time zone. |
| END_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the agent group or place group was removed from the campaign in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the END_TS timestamp to an appropriate time zone. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| START_TS | The UTC-equivalent value of the date and time when the agent group or place group was added to the campaign in the contact center configuration. |
| END_TS | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, the UTC-equivalent value of the date and time when the agent group or place group was removed from the campaign in the contact center configuration. For an active row, this value represents a UTC-equivalent value of the date and time far in the future, so that applications do not have to test for null. |
| TOTAL_DURATION | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, this value represents the total duration, in seconds, that the agent group or place group was associated with the campaign. For an active row, this value represents the duration, in seconds, that the agent group or place group was associated with the campaign, from start time to the time that the ETL last executed. |
| ACTIVE_FLAG | Indicates whether the association between the agent group or place group and the campaign is still active: 0 = No, 1 = Yes. |
| PURGE_FLAG | This field is reserved. |
| GROUP_TO_CAMPAIGN_FACT_KEY | The primary key of this view. |
| GROUP_KEY | The surrogate key that is used to join the GROUP_ dimension to the fact tables. |
| CAMPAIGN_KEY | The surrogate key that is used to join the CAMPAIGN dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| START_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the agent group or place group was added to the campaign in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the START_TS timestamp to an appropriate time zone. |
| END_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the agent group or place group was removed from the campaign in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the END_TS timestamp to an appropriate time zone. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| START_TS | The UTC-equivalent value of the date and time when the agent group or place group was added to the campaign in the contact center configuration. |
| END_TS | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, the UTC-equivalent value of the date and time when the agent group or place group was removed from the campaign in the contact center configuration. For an active row, this value represents a UTC-equivalent value of the date and time far in the future, so that applications do not have to test for null. |
| TOTAL_DURATION | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, this value represents the total duration, in seconds, that the agent group or place group was associated with the campaign. For an active row, this value represents the duration, in seconds, that the agent group or place group was associated with the campaign, from start time to the time that the ETL last executed. |
| ACTIVE_FLAG | Indicates whether the association between the agent group or place group and the campaign is still active: 0 = No, 1 = Yes. |
| PURGE_FLAG | This field is reserved. |
| PLACE_KEY | The primary key of this view and the surrogate key that is used to join the PLACE dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join to the TENANT dimension. |
| PLACE_NAME | The place name. |
| PLACE_CFG_DBID | The place object identifier in the contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the place object was added to IDB, which may differ from when the place was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the place object was removed from contact center configuration. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| PLACE_KEY | The primary key of this view and the surrogate key that is used to join the PLACE dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join to the TENANT dimension. |
| PLACE_NAME | The place name. |
| PLACE_CFG_DBID | The place object identifier in the contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the place object was added to IDB, which may differ from when the place was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the place object was removed from contact center configuration. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| PLACE_KEY | The primary key of this view and the surrogate key that is used to join the PLACE dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join to the TENANT dimension. |
| PLACE_NAME | The place name. |
| PLACE_CFG_DBID | The place object identifier in the contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the place object was added to IDB, which may differ from when the place was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the place object was removed from contact center configuration. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| PLACE_KEY | The primary key of this view and the surrogate key that is used to join the PLACE dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join to the TENANT dimension. |
| PLACE_NAME | The place name. |
| PLACE_CFG_DBID | The place object identifier in the contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the place object was added to IDB, which may differ from when the place was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the place object was removed from contact center configuration. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| PLACE_GROUP_FACT_KEY | The primary key of this view. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| PLACE_KEY | The surrogate key that is used to join the PLACE dimension to the fact tables. |
| GROUP_KEY | The surrogate key that is used to join the GROUP_ dimension to the fact tables. |
| START_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the place was added to the place group in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the START_TS timestamp to an appropriate time zone. |
| END_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the place was removed from the place group in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the END_TS timestamp to an appropriate time zone. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| START_TS | The UTC-equivalent value of the date and time when the place was added to the place group in the contact center configuration. |
| END_TS | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, the UTC-equivalent value of the date and time when the place was removed from the place group in the contact center configuration. For an active row, this value represents a UTC-equivalent value of the date and time far in the future, so that applications do not have to test for null. |
| TOTAL_DURATION | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, this value represents the total duration, in seconds, that the place was a member of the place group. For an active row, this value represents the duration, in seconds, that the place has been a member of the place group, from start time to the time that the ETL last executed. |
| ACTIVE_FLAG | Indicates whether the place is currently a member of the place group: 0 = No, 1 = Yes. |
| PURGE_FLAG | This field is reserved. |
| PLACE_GROUP_FACT_KEY | The primary key of this view. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| PLACE_KEY | The surrogate key that is used to join the PLACE dimension to the fact tables. |
| GROUP_KEY | The surrogate key that is used to join the GROUP_ dimension to the fact tables. |
| START_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the place was added to the place group in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the START_TS timestamp to an appropriate time zone. |
| END_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the place was removed from the place group in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the END_TS timestamp to an appropriate time zone. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| START_TS | The UTC-equivalent value of the date and time when the place was added to the place group in the contact center configuration. |
| END_TS | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, the UTC-equivalent value of the date and time when the place was removed from the place group in the contact center configuration. For an active row, this value represents a UTC-equivalent value of the date and time far in the future, so that applications do not have to test for null. |
| TOTAL_DURATION | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, this value represents the total duration, in seconds, that the place was a member of the place group. For an active row, this value represents the duration, in seconds, that the place has been a member of the place group, from start time to the time that the ETL last executed. |
| ACTIVE_FLAG | Indicates whether the place is currently a member of the place group: 0 = No, 1 = Yes. |
| PURGE_FLAG | This field is reserved. |
| PLACE_GROUP_FACT_KEY | The primary key of this view. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| PLACE_KEY | The surrogate key that is used to join the PLACE dimension to the fact tables. |
| GROUP_KEY | The surrogate key that is used to join the GROUP_ dimension to the fact tables. |
| START_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the place was added to the place group in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the START_TS timestamp to an appropriate time zone. |
| END_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the place was removed from the place group in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the END_TS timestamp to an appropriate time zone. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| START_TS | The UTC-equivalent value of the date and time when the place was added to the place group in the contact center configuration. |
| END_TS | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, the UTC-equivalent value of the date and time when the place was removed from the place group in the contact center configuration. For an active row, this value represents a UTC-equivalent value of the date and time far in the future, so that applications do not have to test for null. |
| TOTAL_DURATION | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, this value represents the total duration, in seconds, that the place was a member of the place group. For an active row, this value represents the duration, in seconds, that the place has been a member of the place group, from start time to the time that the ETL last executed. |
| ACTIVE_FLAG | Indicates whether the place is currently a member of the place group: 0 = No, 1 = Yes. |
| PURGE_FLAG | This field is reserved. |
| PLACE_GROUP_FACT_KEY | The primary key of this view. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| PLACE_KEY | The surrogate key that is used to join the PLACE dimension to the fact tables. |
| GROUP_KEY | The surrogate key that is used to join the GROUP_ dimension to the fact tables. |
| START_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the place was added to the place group in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the START_TS timestamp to an appropriate time zone. |
| END_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the place was removed from the place group in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the END_TS timestamp to an appropriate time zone. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| START_TS | The UTC-equivalent value of the date and time when the place was added to the place group in the contact center configuration. |
| END_TS | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, the UTC-equivalent value of the date and time when the place was removed from the place group in the contact center configuration. For an active row, this value represents a UTC-equivalent value of the date and time far in the future, so that applications do not have to test for null. |
| TOTAL_DURATION | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, this value represents the total duration, in seconds, that the place was a member of the place group. For an active row, this value represents the duration, in seconds, that the place has been a member of the place group, from start time to the time that the ETL last executed. |
| ACTIVE_FLAG | Indicates whether the place is currently a member of the place group: 0 = No, 1 = Yes. |
| PURGE_FLAG | This field is reserved. |
| RESOURCE_GROUP_FACT_KEY | The primary key of this view. |
| START_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the resource was added to the resource group in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the START_TS timestamp to an appropriate time zone. |
| END_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the resource was removed from the resource group in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the END_TS timestamp to an appropriate time zone. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| RESOURCE_KEY | The surrogate key that is used to join the RESOURCE_ dimension to the fact tables. |
| GROUP_KEY | The surrogate key that is used to join the GROUP_ dimension to the fact tables. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| START_TS | The UTC-equivalent value of the date and time when the resource was added to the resource group in the contact center configuration. |
| END_TS | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, the UTC-equivalent value of the date and time when the resource was removed from the resource group in the contact center configuration. For an active row, this value represents a UTC-equivalent value of the date and time far in the future, so that applications do not have to test for null. |
| TOTAL_DURATION | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, this value represents the total duration, in seconds, that the resource was a member of the resource group. For an active row, this value represents the duration, in seconds, that the resource has been a member of the resource group, from start time to the time that the ETL last executed. |
| ACTIVE_FLAG | Indicates whether the resource is currently a member of the resource group: 0 = No, 1 = Yes. |
| PURGE_FLAG | This field is reserved. |
| RESOURCE_GROUP_FACT_KEY | The primary key of this view. |
| START_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the resource was added to the resource group in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the START_TS timestamp to an appropriate time zone. |
| END_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the resource was removed from the resource group in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the END_TS timestamp to an appropriate time zone. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| RESOURCE_KEY | The surrogate key that is used to join the RESOURCE_ dimension to the fact tables. |
| GROUP_KEY | The surrogate key that is used to join the GROUP_ dimension to the fact tables. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| START_TS | The UTC-equivalent value of the date and time when the resource was added to the resource group in the contact center configuration. |
| END_TS | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, the UTC-equivalent value of the date and time when the resource was removed from the resource group in the contact center configuration. For an active row, this value represents a UTC-equivalent value of the date and time far in the future, so that applications do not have to test for null. |
| TOTAL_DURATION | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, this value represents the total duration, in seconds, that the resource was a member of the resource group. For an active row, this value represents the duration, in seconds, that the resource has been a member of the resource group, from start time to the time that the ETL last executed. |
| ACTIVE_FLAG | Indicates whether the resource is currently a member of the resource group: 0 = No, 1 = Yes. |
| PURGE_FLAG | This field is reserved. |
| RESOURCE_GROUP_FACT_KEY | The primary key of this view. |
| START_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the resource was added to the resource group in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the START_TS timestamp to an appropriate time zone. |
| END_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the resource was removed from the resource group in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the END_TS timestamp to an appropriate time zone. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| RESOURCE_KEY | The surrogate key that is used to join the RESOURCE_ dimension to the fact tables. |
| GROUP_KEY | The surrogate key that is used to join the GROUP_ dimension to the fact tables. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| START_TS | The UTC-equivalent value of the date and time when the resource was added to the resource group in the contact center configuration. |
| END_TS | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, the UTC-equivalent value of the date and time when the resource was removed from the resource group in the contact center configuration. For an active row, this value represents a UTC-equivalent value of the date and time far in the future, so that applications do not have to test for null. |
| TOTAL_DURATION | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, this value represents the total duration, in seconds, that the resource was a member of the resource group. For an active row, this value represents the duration, in seconds, that the resource has been a member of the resource group, from start time to the time that the ETL last executed. |
| ACTIVE_FLAG | Indicates whether the resource is currently a member of the resource group: 0 = No, 1 = Yes. |
| PURGE_FLAG | This field is reserved. |
| RESOURCE_GROUP_FACT_KEY | The primary key of this view. |
| START_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the resource was added to the resource group in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the START_TS timestamp to an appropriate time zone. |
| END_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the resource was removed from the resource group in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the END_TS timestamp to an appropriate time zone. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| RESOURCE_KEY | The surrogate key that is used to join the RESOURCE_ dimension to the fact tables. |
| GROUP_KEY | The surrogate key that is used to join the GROUP_ dimension to the fact tables. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| START_TS | The UTC-equivalent value of the date and time when the resource was added to the resource group in the contact center configuration. |
| END_TS | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, the UTC-equivalent value of the date and time when the resource was removed from the resource group in the contact center configuration. For an active row, this value represents a UTC-equivalent value of the date and time far in the future, so that applications do not have to test for null. |
| TOTAL_DURATION | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, this value represents the total duration, in seconds, that the resource was a member of the resource group. For an active row, this value represents the duration, in seconds, that the resource has been a member of the resource group, from start time to the time that the ETL last executed. |
| ACTIVE_FLAG | Indicates whether the resource is currently a member of the resource group: 0 = No, 1 = Yes. |
| PURGE_FLAG | This field is reserved. |
| RESOURCE_SKILL_FACT_KEY | The primary key of this view. |
| START_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the skill at the specified level was added to the resource in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the START_TS timestamp to an appropriate time zone. |
| END_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the skill at the specified level was removed from the resource in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts related to the same interval and/or convert the END_TS timestamp to an appropriate time zone. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| RESOURCE_KEY | The surrogate key that is used to join the RESOURCE_ dimension to the fact tables. |
| SKILL_KEY | The surrogate key that is used to join the SKILL dimension to the fact tables. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| START_TS | The UTC-equivalent value of the date and time when the skill, at the specified level, was added to the resource in the contact center configuration. |
| END_TS | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, the UTC-equivalent value of the date and time when the skill, at the specified level, was removed from the resource in contact center configuration. For an active row, this value represents a UTC-equivalent value of the date and time far in the future, so that applications do not have to test for null. |
| TOTAL_DURATION | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, this field represents the total duration, in seconds, that the resource had the skill at the specified level. For an active row, this field represents the duration, in seconds, that the resource has had the skill at the specified level, from start time to the time that the ETL last executed. |
| ACTIVE_FLAG | Indicates whether the resource currently has the skill at the specified level: 0 = No, 1 = Yes. |
| SKILL_LEVEL | The skill level or proficiency. |
| PURGE_FLAG | This field is reserved. |
| RESOURCE_SKILL_FACT_KEY | The primary key of this view. |
| START_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the skill at the specified level was added to the resource in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the START_TS timestamp to an appropriate time zone. |
| END_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the skill at the specified level was removed from the resource in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts related to the same interval and/or convert the END_TS timestamp to an appropriate time zone. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| RESOURCE_KEY | The surrogate key that is used to join the RESOURCE_ dimension to the fact tables. |
| SKILL_KEY | The surrogate key that is used to join the SKILL dimension to the fact tables. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| START_TS | The UTC-equivalent value of the date and time when the skill, at the specified level, was added to the resource in the contact center configuration. |
| END_TS | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, the UTC-equivalent value of the date and time when the skill, at the specified level, was removed from the resource in contact center configuration. For an active row, this value represents a UTC-equivalent value of the date and time far in the future, so that applications do not have to test for null. |
| TOTAL_DURATION | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, this field represents the total duration, in seconds, that the resource had the skill at the specified level. For an active row, this field represents the duration, in seconds, that the resource has had the skill at the specified level, from start time to the time that the ETL last executed. |
| ACTIVE_FLAG | Indicates whether the resource currently has the skill at the specified level: 0 = No, 1 = Yes. |
| SKILL_LEVEL | The skill level or proficiency. |
| PURGE_FLAG | This field is reserved. |
| RESOURCE_SKILL_FACT_KEY | The primary key of this view. |
| START_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the skill at the specified level was added to the resource in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the START_TS timestamp to an appropriate time zone. |
| END_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the skill at the specified level was removed from the resource in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts related to the same interval and/or convert the END_TS timestamp to an appropriate time zone. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| RESOURCE_KEY | The surrogate key that is used to join the RESOURCE_ dimension to the fact tables. |
| SKILL_KEY | The surrogate key that is used to join the SKILL dimension to the fact tables. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| START_TS | The UTC-equivalent value of the date and time when the skill, at the specified level, was added to the resource in the contact center configuration. |
| END_TS | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, the UTC-equivalent value of the date and time when the skill, at the specified level, was removed from the resource in contact center configuration. For an active row, this value represents a UTC-equivalent value of the date and time far in the future, so that applications do not have to test for null. |
| TOTAL_DURATION | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, this field represents the total duration, in seconds, that the resource had the skill at the specified level. For an active row, this field represents the duration, in seconds, that the resource has had the skill at the specified level, from start time to the time that the ETL last executed. |
| ACTIVE_FLAG | Indicates whether the resource currently has the skill at the specified level: 0 = No, 1 = Yes. |
| SKILL_LEVEL | The skill level or proficiency. |
| PURGE_FLAG | This field is reserved. |
| RESOURCE_SKILL_FACT_KEY | The primary key of this view. |
| START_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the skill at the specified level was added to the resource in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the START_TS timestamp to an appropriate time zone. |
| END_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the skill at the specified level was removed from the resource in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts related to the same interval and/or convert the END_TS timestamp to an appropriate time zone. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| RESOURCE_KEY | The surrogate key that is used to join the RESOURCE_ dimension to the fact tables. |
| SKILL_KEY | The surrogate key that is used to join the SKILL dimension to the fact tables. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| START_TS | The UTC-equivalent value of the date and time when the skill, at the specified level, was added to the resource in the contact center configuration. |
| END_TS | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, the UTC-equivalent value of the date and time when the skill, at the specified level, was removed from the resource in contact center configuration. For an active row, this value represents a UTC-equivalent value of the date and time far in the future, so that applications do not have to test for null. |
| TOTAL_DURATION | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, this field represents the total duration, in seconds, that the resource had the skill at the specified level. For an active row, this field represents the duration, in seconds, that the resource has had the skill at the specified level, from start time to the time that the ETL last executed. |
| ACTIVE_FLAG | Indicates whether the resource currently has the skill at the specified level: 0 = No, 1 = Yes. |
| SKILL_LEVEL | The skill level or proficiency. |
| PURGE_FLAG | This field is reserved. |
| SKILL_KEY | The primary key of this view and the surrogate key that is used to join the SKILL dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| SKILL_NAME | The skill name. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| SKILL_CFG_DBID | The skill object identifier in the contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the skill was added to IDB, which may differ from when the skill was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the skill was removed from contact center configuration. |
| SKILL_KEY | The primary key of this view and the surrogate key that is used to join the SKILL dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| SKILL_NAME | The skill name. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| SKILL_CFG_DBID | The skill object identifier in the contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the skill was added to IDB, which may differ from when the skill was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the skill was removed from contact center configuration. |
| SKILL_KEY | The primary key of this view and the surrogate key that is used to join the SKILL dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| SKILL_NAME | The skill name. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| SKILL_CFG_DBID | The skill object identifier in the contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the skill was added to IDB, which may differ from when the skill was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the skill was removed from contact center configuration. |
| SKILL_KEY | The primary key of this view and the surrogate key that is used to join the SKILL dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| SKILL_NAME | The skill name. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| SKILL_CFG_DBID | The skill object identifier in the contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the skill was added to IDB, which may differ from when the skill was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the skill was removed from contact center configuration. |
| TENANT_KEY | The primary key of this view and the surrogate key that is used to join the TENANT dimension to the fact tables. |
| TENANT_NAME | The tenant name. |
| TENANT_CFG_DBID | The tenant object identifier in the contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the tenant was added to IDB, which may differ from when the tenant was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the tenant was removed from contact center configuration. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| TENANT_KEY | The primary key of this view and the surrogate key that is used to join the TENANT dimension to the fact tables. |
| TENANT_NAME | The tenant name. |
| TENANT_CFG_DBID | The tenant object identifier in the contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the tenant was added to IDB, which may differ from when the tenant was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the tenant was removed from contact center configuration. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| TENANT_KEY | The primary key of this view and the surrogate key that is used to join the TENANT dimension to the fact tables. |
| TENANT_NAME | The tenant name. |
| TENANT_CFG_DBID | The tenant object identifier in the contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the tenant was added to IDB, which may differ from when the tenant was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the tenant was removed from contact center configuration. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| TENANT_KEY | The primary key of this view and the surrogate key that is used to join the TENANT dimension to the fact tables. |
| TENANT_NAME | The tenant name. |
| TENANT_CFG_DBID | The tenant object identifier in the contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the tenant was added to IDB, which may differ from when the tenant was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the tenant was removed from contact center configuration. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| CALLING_LIST_KEY | The primary key of this view and the surrogate key that is used to join the CALLING_LIST dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| CALLING_LIST_NAME | The name of the calling list. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| DESCRIPTION | The description of the calling list. |
| CALLING_LIST_CFG_DBID | The calling list object identifier in the contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the calling list was added to IDB, which may differ from when the calling list was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the calling list was removed from contact center configuration. |
| CAMPAIGN_KEY | The surrogate key that is used to join the CAMPAIGN dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| CAMPAIGN_NAME | The name of the campaign object in Configuration Server. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| DESCRIPTION | The description of the campaign. |
| CAMPAIGN_CFG_DBID | The campaign object identifier in contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the campaign was added to IDB, which may differ from when the campaign was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the campaign object was removed from contact center configuration. |
| NAME | A combination of the job name and an abbreviated data type for the processed data. Either of the following values:
|
| LAST_TS | Provides a UTC equivalent of the date and time up to which the data has been processed. |
| GROUP_KEY | The primary key of this view that is used to join the GROUP_ dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| GROUP_NAME | The group name. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| GROUP_TYPE | The group type. This field is set to one of the following values:
This value can change with localization. |
| GROUP_TYPE_CODE | The group type code. This field is set to one of the following values:
This value does not change with localization. |
| GROUP_CFG_DBID | The group object identifier in the contact center configuration. |
| GROUP_CFG_TYPE_ID | The contact center configuration integer type that is associated with the DN or agent group object. |
| START_TS | The UTC-equivalent value of the date and time when the group was added to IDB, which may differ from when the group was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the group was removed from contact center configuration. |
| GROUP_TO_CAMPAIGN_FACT_KEY | The primary key of this view. |
| GROUP_KEY | The surrogate key that is used to join the GROUP_ dimension to the fact tables. |
| CAMPAIGN_KEY | The surrogate key that is used to join the CAMPAIGN dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| START_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the agent group or place group was added to the campaign in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the START_TS timestamp to an appropriate time zone. |
| END_DATE_TIME_KEY | Identifies the start of a 15-minute interval in which the agent group or place group was removed from the campaign in the contact center configuration. Use this value as a key to join the fact tables to any configured DATE_TIME dimension, in order to group the facts that are related to the same interval and/or convert the END_TS timestamp to an appropriate time zone. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| START_TS | The UTC-equivalent value of the date and time when the agent group or place group was added to the campaign in the contact center configuration. |
| END_TS | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, the UTC-equivalent value of the date and time when the agent group or place group was removed from the campaign in the contact center configuration. For an active row, this value represents a UTC-equivalent value of the date and time far in the future, so that applications do not have to test for null. |
| TOTAL_DURATION | The meaning depends on the value of ACTIVE_FLAG. For an inactive row, this value represents the total duration, in seconds, that the agent group or place group was associated with the campaign. For an active row, this value represents the duration, in seconds, that the agent group or place group was associated with the campaign, from start time to the time that the ETL last executed. |
| ACTIVE_FLAG | Indicates whether the association between the agent group or place group and the campaign is still active: 0 = No, 1 = Yes. |
| PURGE_FLAG | This field is reserved. |
| PLACE_KEY | The primary key of this view and the surrogate key that is used to join the PLACE dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join to the TENANT dimension. |
| PLACE_NAME | The place name. |
| PLACE_CFG_DBID | The place object identifier in the contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the place object was added to IDB, which may differ from when the place was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the place object was removed from contact center configuration. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| SKILL_KEY | The primary key of this view and the surrogate key that is used to join the SKILL dimension to the fact tables. |
| TENANT_KEY | The surrogate key that is used to join the TENANT dimension to the fact tables. |
| SKILL_NAME | The skill name. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| SKILL_CFG_DBID | The skill object identifier in the contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the skill was added to IDB, which may differ from when the skill was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the skill was removed from contact center configuration. |
| TENANT_KEY | The primary key of this view and the surrogate key that is used to join the TENANT dimension to the fact tables. |
| TENANT_NAME | The tenant name. |
| TENANT_CFG_DBID | The tenant object identifier in the contact center configuration. |
| START_TS | The UTC-equivalent value of the date and time when the tenant was added to IDB, which may differ from when the tenant was actually added to contact center configuration. |
| END_TS | The UTC-equivalent value of the date and time when the tenant was removed from contact center configuration. |
| CREATE_AUDIT_KEY | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data. |
| UPDATE_AUDIT_KEY | The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data. |
| DATE_TIME_KEY | The surrogate key that is used to join this aggregate table to the DATE_TIME dimension table to identify the calendar date and 15-minute interval at which the agent’s participation in the interaction began. |
| GROUP_KEY | The surrogate key that is used to join this aggregate table to the GROUP_ view to identify the specific queue group of which the queue was a member when the interaction entered the queue. |
| INTERACTION_DESCRIPTOR_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_DESCRIPTOR dimension table to identify the business attributes that have been assigned to the interaction. |
| TENANT_KEY | The surrogate key that is used to join this aggregate table to the TENANT view to identify a specific tenant. |
| MEDIA_TYPE_KEY | The surrogate key that is used to join this aggregate table to the MEDIA_TYPE dimension table. |
| INTERACTION_TYPE_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_TYPE dimension table. |
| USER_DATA_KEY1 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction.
If you engage the social-media feature, RAA maps this field to GEN_ES_KEY in the IRF_USER_DATA_KEYS table. |
| USER_DATA_KEY2 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction. |
| POST_CALL_SURVEY_KEY1 | The surrogate key that is used to join this aggregate table to the POST_CALL_SURVEY dimension table. |
| POST_CALL_SURVEY_KEY2 | The surrogate key that is used to join this aggregate table to the POST_CALL_SURVEY dimension table. |
| ACCEPTED_THREAD | The total number of customer-interaction threads that were accepted, initiated, or pulled for the first time by agents who belong to this agent group. This measure includes an agent's first participation in outbound replies to inbound interactions and yields the same values as ACCEPTED_UNIQUE for media other than e-mail. |
| ACCEPTED_UNIQUE | The total number of logical interactions that were accepted, initiated, or pulled by agents who belong to this agent group. This measure includes an agent's first participation in outbound replies to inbound interactions. |
| ACCEPTED | The total number of times that customer interactions or warm consultations were accepted, answered, pulled, or initiated by agents who belong to this agent group.
For voice media, this measure is identical to RESPONSES. |
| NOTACCEPTED | The total number of times that customer interactions were redirected to another resource upon no answer by agents who belong to this agent group or were otherwise not accepted or answered by such agents. This measure includes interactions that the customer abandoned while they were alerting at the agent. |
| OFFERED | The total number of times that interactions were received or initiated by agents who belong to this agent group. The count includes interactions that were abandoned while inviting, handling attempts that the agent rejected, and warm consultations and conferences that the agent received. This count excludes simple consultations, whether they were initiated or received. |
| RESPONDED_UNIQUE | The total number of first-time outbound replies in which agents, who belong to this agent group, participated in response to customer interactions. Any number of replies could be prepared in response to a customer interaction. This measure attributes only the first-connected reply to this agent, regardless of whether the reply was sent. This measure excludes outbound replies to consultations, outbound replies that the agent pulled from his/her personal workbin or rejected, and system-generated responses. |
| RESPONSES | For voice and chat media, this measure represents the total number of times that customer interactions or warm consultations were answered or accepted by agents who belong to this agent group. For voice media, this measure is identical to ACCEPTED; it returns positive values when agents initiate calls.
For e-mail, this measure represents the total number of times that agents who belong to this agent group prepared an outbound reply. |
| ABANDONED_INVITE | The total number of times that customer interactions were abandoned or dropped for any reason while the interactions were alerting or ringing at agents who belong to this agent group. |
| REJECTED | The total number of times that customer interactions alerted at an agent that belong to this agent group and were not accepted or answered. |
| INVITE | The total number of customer interactions that alerted or rang at agents who belong to this agent group before the interactions were accepted, answered, or pulled plus the total number of dials that agents performed, where the calls were successfully established. This measure is attributed to the interval in which the alerting/dialing first occurred.
The dialing component of this measure applies to voice media only. |
| INVITE_TIME | The total amount of time, in seconds, that customer interactions alerted at agents who belong to this agent group plus the total duration of the dialing that the agents performed. For the alerting component of this measure, interactions do not have to be established for this measure to be incremented. For the dialing component, dial duration is measured for established calls only. This measure is attributed to the interval in which the alerting/dialing first occurred. |
| ENGAGE_TIME | The total amount of time, in seconds, that agents who belong to this agent group were engaged with customers on interactions that the agents received. This measure excludes other interaction-related durations, such as hold time, ACW (Wrap) time, alert (ring) time, and time that is spent in collaboration or consultation. |
| ENGAGE | The total number of interactions in which agents, who belong to this agent group, were engaged with customers for interactions that the agents received. This measure excludes other interaction-related counts, such as holds, instances of ACW, and collaborations and consultations that the agent received. |
| SHORT | The total number of times that customer interactions were accepted by agents who belong to this agent group and then released, transferred, or stopped within the short-engagement threshold.
This measure relies on the value of short-engagement (short-talk) as configured in the [agg-gim-thld-AGENT-IXN] section. |
| HOLD_TIME | The total amount of time, in seconds, that agents, who belong to this agent group, had customer interactions on hold. |
| HOLD | The total number of customer interactions that agents, who belong to this agent group, had on hold. |
| WRAP_TIME | The total amount of time, in seconds, that agents who belong to this agent group spent in ACW state for customer interactions that the agents received. This measure is attributed to the interval in which the agent was offered the interaction for which ACW was invoked. |
| WRAP | The total number of times that agents who belong to this agent group were in ACW state for customer interactions that the agents received. This measure is attributed to the interval in which the agent was offered the interactions for which ACW was invoked. |
| CONSULT_RECEIVED_ENGAGE_TIME | The total amount of time, in seconds, that agents who belong to this agent group were engaged in collaborations or simple consultations where the agents were the recipients of the collaboration/consultation requests and the collaborations/consultations were associated with customer interactions. |
| CONSULT_RECEIVED_ACCEPTED | The total number of times that agents who belong to this agent group received and accepted collaborations or simple consultations that were associated with customer interactions. |
| CONSULT_RESPONSES | For e-mail, the total number of collaboration replies that were initiated by agents who belong to this agent group. For voice, this measure is the same as CONSULT_RECEIVED_ACCEPTED. |
| CONSULT_RECEIVED_HOLD_TIME | The total amount of time, in seconds, that agents who belong to this agent group had collaborations or simple consultations on hold where the collaborations/consultations were associated with customer interactions and the agents were the recipients of the collaboration/consultation requests. |
| CONSULT_RECEIVED_HOLD | The total number of times that agents from this agent group were on hold during simple consultations that they received where the consultations were associated with customer interactions. |
| CONSULT_RECEIVED_WRAP_TIME | The total amount of time, in seconds, that agents who belong to this agent group were in ACW state after simple consultations that the agents accepted, where the consultations were associated with customer calls. This duration does not stop if the agents received or made calls while in ACW state. This measure is attributed to the interval in which this agent was offered the consult interaction for which ACW was invoked. |
| CONSULT_RECEIVED_WRAP | The total number of times that agents who belong to this agent group were in ACW state after requests for simple consultation that they accepted where the consultations were associated with customer interactions. |
| CONSULT_RCV_WARM_ENGAGE_TIME | The total amount of time, in seconds, that agents, who belong to this agent group, were engaged in collaborations or consultations where the collaborations/consultations were associated with customer interactions and the interactions were transferred to or conferenced with the agents. |
| CONSULT_RCV_ACC_WARM | The total number of times that agents who belong to this agent group participated in consultations that the agents received, where the consultations were associated with customer interactions that were transferred to or conferenced with the agents. |
| CONSULT_RCV_WARM_HOLD_TIME | The total number of consultations that agents, who belong to this agent group, had on hold where the consultations were associated with customer interactions, the agents were the recipients of the consultation requests, and the interactions were transferred to or conferenced with the agents. |
| CONSULT_RCV_WARM_HOLD | The total number of consultations that agents, who belong to this agent group, had on hold where the consultations were associated with customer interactions, the agents were the recipients of the consultation requests, and the interactions were transferred to or conferenced with the agents. |
| CONSULT_RCV_WARM_WRAP_TIME | The total amount of time, in seconds, that agents from this agent group spent in ACW state following consultations that the agents requested and received, where the consultations were associated with customer interactions that were transferred to or conferenced with the agents.
This measure includes:
In common call-flow scenarios, this measure yields a value of zero. |
| CONSULT_RCV_WARM_WRAP | The total number of times that agents, who belong to this agent group were in ACW state following consultations that the agents requested and received, where the consultations were associated with customer interactions, and the interactions were transferred to or conferenced with the agents.
This measure includes:
In common call-flow scenarios, this measure yields a value of zero. |
| CONSULT_INITIATED | The total number of times that agents who belong to this agent group, initiated requests for collaboration or simple consultation, where the collaborations/consultations were established and associated with customer interactions. |
| CONSULT_INITIATED_TIME | The total amount of time, in seconds, that agents who belong to this agent group were engaged in collaborations or simple consultations that the agents requested where the collaborations/consultations were associated with customer interactions. |
| CONFERENCE_RECEIVED_ACCEPTED | The total number of times that agents from this agent group joined conferences to participate in customer interactions. |
| CONFERENCE_INITIATED | The total number of times that agents who belong to this agent group initiated conferences for customer interactions that the agent received, where the conferences were established. The count includes the number of established conferences that were initiated for transferred interactions that the agent received. |
| TRANSFER_INIT_AGENT | The total number of times that agents, who belong to this agent group, transferred customer interactions. Both warm and blind transfers are reflected in this measure. |
| XFER_RECEIVED_ACCEPTED | The total number of times that agents who belong to this agent group, received customer interactions that were successfully transferred to the agents. Both warm and blind transfers are reflected in this measure. |
| SATISFACTION_OFFERED | The total number of customer interactions handled by agents who belong with this agent group for which customer-satisfaction scores were recorded. |
| SATISFACTION | The sum of numerical scores of customer satisfaction that were attributed to customer interactions handled by agents who belong to this agent group. |
| REVENUE_OFFERED | The total number of customer interactions that entered or began within the contact center, were handled by agents who belong to this agent group, and had associated revenue. |
| REVENUE | The total revenue that is generated during the interval by customer interactions handled by agents who belong to this agent group. |
| AGENT_DISCONNECT_FIRST | The total number of times during the reporting interval that agents from this agent group released customer interactions before the other party did. The tally is incremented only when the system (such as the switch) provides such information. |
| ACTIONABILITY_OFFERED | The total number of customer interactions that were offered to, pulled, or initiated by agents belonging to this agent group for which an actionability score was attached. Actionability scores measure the degree to which interactions required agent attention. |
| ACTIONABILITY | The sum of actionability scores attached to customer interactions that were handled by agents who belong to this agent group. |
| SENTIMENT_OFFERED | The total number of customer interactions that were offered to, pulled, or initiated by agents belonging to this agent group for which a sentiment score was attached. Sentiment scores reflect the attitude expressed by customers. |
| SENTIMENT | The sum of sentiment scores attached to customer interactions that were handled by agents belonging to this agent group. |
| INFLUENCE_OFFERED | The total number of customer interactions that were offered to, pulled, or initiated by agents belonging to this agent group for which an influence score was attached. Influence scores represent the clout that the customer amassed on social networks. |
| INFLUENCE | The sum of influence scores attached to customer interactions that were handled by agents belonging to this agent group. |
| DATE_TIME_KEY | The surrogate key that is used to join this aggregate table to the DATE_TIME dimension table to identify the calendar date and 15-minute interval at which the agent’s participation in the interaction began. |
| GROUP_KEY | The surrogate key that is used to join this aggregate table to the GROUP_ view to identify the specific queue group of which the queue was a member when the interaction entered the queue. |
| INTERACTION_DESCRIPTOR_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_DESCRIPTOR dimension table to identify the business attributes that have been assigned to the interaction. |
| TENANT_KEY | The surrogate key that is used to join this aggregate table to the TENANT view to identify a specific tenant. |
| MEDIA_TYPE_KEY | The surrogate key that is used to join this aggregate table to the MEDIA_TYPE dimension table. |
| INTERACTION_TYPE_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_TYPE dimension table. |
| USER_DATA_KEY1 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction.
If you engage the social-media feature, RAA maps this field to GEN_ES_KEY in the IRF_USER_DATA_KEYS table. |
| USER_DATA_KEY2 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction. |
| POST_CALL_SURVEY_KEY1 | The surrogate key that is used to join this aggregate table to the POST_CALL_SURVEY dimension table. |
| POST_CALL_SURVEY_KEY2 | The surrogate key that is used to join this aggregate table to the POST_CALL_SURVEY dimension table. |
| ACCEPTED_THREAD | The total number of customer-interaction threads that were accepted, initiated, or pulled for the first time by agents who belong to this agent group. This measure includes an agent's first participation in outbound replies to inbound interactions and yields the same values as ACCEPTED_UNIQUE for media other than e-mail. |
| ACCEPTED_UNIQUE | The total number of logical interactions that were accepted, initiated, or pulled by agents who belong to this agent group. This measure includes an agent's first participation in outbound replies to inbound interactions. |
| ACCEPTED | The total number of times that customer interactions or warm consultations were accepted, answered, pulled, or initiated by agents who belong to this agent group.
For voice media, this measure is identical to RESPONSES. |
| NOTACCEPTED | The total number of times that customer interactions were redirected to another resource upon no answer by agents who belong to this agent group or were otherwise not accepted or answered by such agents. This measure includes interactions that the customer abandoned while they were alerting at the agent. |
| OFFERED | The total number of times that interactions were received or initiated by agents who belong to this agent group. The count includes interactions that were abandoned while inviting, handling attempts that the agent rejected, and warm consultations and conferences that the agent received. This count excludes simple consultations, whether they were initiated or received. |
| RESPONDED_UNIQUE | The total number of first-time outbound replies in which agents, who belong to this agent group, participated in response to customer interactions. Any number of replies could be prepared in response to a customer interaction. This measure attributes only the first-connected reply to this agent, regardless of whether the reply was sent. This measure excludes outbound replies to consultations, outbound replies that the agent pulled from his/her personal workbin or rejected, and system-generated responses. |
| RESPONSES | For voice and chat media, this measure represents the total number of times that customer interactions or warm consultations were answered or accepted by agents who belong to this agent group. For voice media, this measure is identical to ACCEPTED; it returns positive values when agents initiate calls.
For e-mail, this measure represents the total number of times that agents who belong to this agent group prepared an outbound reply. |
| ABANDONED_INVITE | The total number of times that customer interactions were abandoned or dropped for any reason while the interactions were alerting or ringing at agents who belong to this agent group. |
| REJECTED | The total number of times that customer interactions alerted at an agent that belong to this agent group and were not accepted or answered. |
| INVITE | The total number of customer interactions that alerted or rang at agents who belong to this agent group before the interactions were accepted, answered, or pulled plus the total number of dials that agents performed, where the calls were successfully established. This measure is attributed to the interval in which the alerting/dialing first occurred.
The dialing component of this measure applies to voice media only. |
| INVITE_TIME | The total amount of time, in seconds, that customer interactions alerted at agents who belong to this agent group plus the total duration of the dialing that the agents performed. For the alerting component of this measure, interactions do not have to be established for this measure to be incremented. For the dialing component, dial duration is measured for established calls only. This measure is attributed to the interval in which the alerting/dialing first occurred. |
| ENGAGE_TIME | The total amount of time, in seconds, that agents who belong to this agent group were engaged with customers on interactions that the agents received. This measure excludes other interaction-related durations, such as hold time, ACW (Wrap) time, alert (ring) time, and time that is spent in collaboration or consultation. |
| ENGAGE | The total number of interactions in which agents, who belong to this agent group, were engaged with customers for interactions that the agents received. This measure excludes other interaction-related counts, such as holds, instances of ACW, and collaborations and consultations that the agent received. |
| SHORT | The total number of times that customer interactions were accepted by agents who belong to this agent group and then released, transferred, or stopped within the short-engagement threshold.
This measure relies on the value of short-engagement (short-talk) as configured in the [agg-gim-thld-AGENT-IXN] section. |
| HOLD_TIME | The total amount of time, in seconds, that agents, who belong to this agent group, had customer interactions on hold. |
| HOLD | The total number of customer interactions that agents, who belong to this agent group, had on hold. |
| WRAP_TIME | The total amount of time, in seconds, that agents who belong to this agent group spent in ACW state for customer interactions that the agents received. This measure is attributed to the interval in which the agent was offered the interaction for which ACW was invoked. |
| WRAP | The total number of times that agents who belong to this agent group were in ACW state for customer interactions that the agents received. This measure is attributed to the interval in which the agent was offered the interactions for which ACW was invoked. |
| CONSULT_RECEIVED_ENGAGE_TIME | The total amount of time, in seconds, that agents who belong to this agent group were engaged in collaborations or simple consultations where the agents were the recipients of the collaboration/consultation requests and the collaborations/consultations were associated with customer interactions. |
| CONSULT_RECEIVED_ACCEPTED | The total number of times that agents who belong to this agent group received and accepted collaborations or simple consultations that were associated with customer interactions. |
| CONSULT_RESPONSES | For e-mail, the total number of collaboration replies that were initiated by agents who belong to this agent group. For voice, this measure is the same as CONSULT_RECEIVED_ACCEPTED. |
| CONSULT_RECEIVED_HOLD_TIME | The total amount of time, in seconds, that agents who belong to this agent group had collaborations or simple consultations on hold where the collaborations/consultations were associated with customer interactions and the agents were the recipients of the collaboration/consultation requests. |
| CONSULT_RECEIVED_HOLD | The total number of times that agents from this agent group were on hold during simple consultations that they received where the consultations were associated with customer interactions. |
| CONSULT_RECEIVED_WRAP_TIME | The total amount of time, in seconds, that agents who belong to this agent group were in ACW state after simple consultations that the agents accepted, where the consultations were associated with customer calls. This duration does not stop if the agents received or made calls while in ACW state. This measure is attributed to the interval in which this agent was offered the consult interaction for which ACW was invoked. |
| CONSULT_RECEIVED_WRAP | The total number of times that agents who belong to this agent group were in ACW state after requests for simple consultation that they accepted where the consultations were associated with customer interactions. |
| CONSULT_RCV_WARM_ENGAGE_TIME | The total amount of time, in seconds, that agents, who belong to this agent group, were engaged in collaborations or consultations where the collaborations/consultations were associated with customer interactions and the interactions were transferred to or conferenced with the agents. |
| CONSULT_RCV_ACC_WARM | The total number of times that agents who belong to this agent group participated in consultations that the agents received, where the consultations were associated with customer interactions that were transferred to or conferenced with the agents. |
| CONSULT_RCV_WARM_HOLD_TIME | The total number of consultations that agents, who belong to this agent group, had on hold where the consultations were associated with customer interactions, the agents were the recipients of the consultation requests, and the interactions were transferred to or conferenced with the agents. |
| CONSULT_RCV_WARM_HOLD | The total number of consultations that agents, who belong to this agent group, had on hold where the consultations were associated with customer interactions, the agents were the recipients of the consultation requests, and the interactions were transferred to or conferenced with the agents. |
| CONSULT_RCV_WARM_WRAP_TIME | The total amount of time, in seconds, that agents from this agent group spent in ACW state following consultations that the agents requested and received, where the consultations were associated with customer interactions that were transferred to or conferenced with the agents.
This measure includes:
In common call-flow scenarios, this measure yields a value of zero. |
| CONSULT_RCV_WARM_WRAP | The total number of times that agents, who belong to this agent group were in ACW state following consultations that the agents requested and received, where the consultations were associated with customer interactions, and the interactions were transferred to or conferenced with the agents.
This measure includes:
In common call-flow scenarios, this measure yields a value of zero. |
| CONSULT_INITIATED | The total number of times that agents who belong to this agent group, initiated requests for collaboration or simple consultation, where the collaborations/consultations were established and associated with customer interactions. |
| CONSULT_INITIATED_TIME | The total amount of time, in seconds, that agents who belong to this agent group were engaged in collaborations or simple consultations that the agents requested where the collaborations/consultations were associated with customer interactions. |
| CONFERENCE_RECEIVED_ACCEPTED | The total number of times that agents from this agent group joined conferences to participate in customer interactions. |
| CONFERENCE_INITIATED | The total number of times that agents who belong to this agent group initiated conferences for customer interactions that the agent received, where the conferences were established. The count includes the number of established conferences that were initiated for transferred interactions that the agent received. |
| TRANSFER_INIT_AGENT | The total number of times that agents, who belong to this agent group, transferred customer interactions. Both warm and blind transfers are reflected in this measure. |
| XFER_RECEIVED_ACCEPTED | The total number of times that agents who belong to this agent group, received customer interactions that were successfully transferred to the agents. Both warm and blind transfers are reflected in this measure. |
| SATISFACTION_OFFERED | The total number of customer interactions handled by agents who belong with this agent group for which customer-satisfaction scores were recorded. |
| SATISFACTION | The sum of numerical scores of customer satisfaction that were attributed to customer interactions handled by agents who belong to this agent group. |
| REVENUE_OFFERED | The total number of customer interactions that entered or began within the contact center, were handled by agents who belong to this agent group, and had associated revenue. |
| REVENUE | The total revenue that is generated during the interval by customer interactions handled by agents who belong to this agent group. |
| AGENT_DISCONNECT_FIRST | The total number of times during the reporting interval that agents from this agent group released customer interactions before the other party did. The tally is incremented only when the system (such as the switch) provides such information. |
| ACTIONABILITY_OFFERED | The total number of customer interactions that were offered to, pulled, or initiated by agents belonging to this agent group for which an actionability score was attached. Actionability scores measure the degree to which interactions required agent attention. |
| ACTIONABILITY | The sum of actionability scores attached to customer interactions that were handled by agents who belong to this agent group. |
| SENTIMENT_OFFERED | The total number of customer interactions that were offered to, pulled, or initiated by agents belonging to this agent group for which a sentiment score was attached. Sentiment scores reflect the attitude expressed by customers. |
| SENTIMENT | The sum of sentiment scores attached to customer interactions that were handled by agents belonging to this agent group. |
| INFLUENCE_OFFERED | The total number of customer interactions that were offered to, pulled, or initiated by agents belonging to this agent group for which an influence score was attached. Influence scores represent the clout that the customer amassed on social networks. |
| INFLUENCE | The sum of influence scores attached to customer interactions that were handled by agents belonging to this agent group. |
| DATE_TIME_KEY | The surrogate key that is used to join this aggregate table to the DATE_TIME dimension table to identify the calendar date and 15-minute interval at which the agent’s participation in the interaction began. |
| GROUP_COMBINATION_KEY | The surrogate key that is used to join records in this aggregate table to the RESOURCE_GROUP_ COMBINATION dimension table to identify a specific combination of queue groups of which the queue was a member when the interaction entered the queue. |
| RESOURCE_KEY | The surrogate key that is used to join this aggregate table to the RESOURCE_ dimension table. |
| INTERACTION_DESCRIPTOR_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_DESCRIPTOR dimension table to identify the business attributes that have been assigned to the interaction. |
| TENANT_KEY | The surrogate key that is used to join this aggregate table to the TENANT view to identify a specific tenant. |
| MEDIA_TYPE_KEY | The surrogate key that is used to join this aggregate table to the MEDIA_TYPE dimension table. |
| INTERACTION_TYPE_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_TYPE dimension table. |
| USER_DATA_KEY1 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction.
If you engage the social-media feature, RAA maps this field to GEN_ES_KEY in the IRF_USER_DATA_KEYS table. |
| USER_DATA_KEY2 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction. |
| POST_CALL_SURVEY_KEY1 | The surrogate key that is used to join this aggregate table to the POST_CALL_SURVEY dimension table. |
| POST_CALL_SURVEY_KEY2 | The surrogate key that is used to join this aggregate table to the POST_CALL_SURVEY dimension table. |
| ACCEPTED_THREAD | The total number of customer-interaction threads that were accepted, initiated, or pulled for the first time by this agent. This measure includes an agent's first participation in outbound replies to inbound interactions and yields the same values as ACCEPTED_UNIQUE for media other than e-mail. |
| ACCEPTED_UNIQUE | The total number of logical interactions that were accepted, initiated, or pulled by this agent. This measure includes an agent's first participation in outbound replies to inbound interactions. |
| ACCEPTED | The total number of times that customer interactions or warm consultations were accepted, answered, pulled, or initiated by this agent.
For voice media, this measure is identical to RESPONSES. |
| NOTACCEPTED | The total number of times that customer interactions were redirected to another resource upon no answer by this agent or were otherwise not accepted or answered by this agent. This measure includes interactions that the customer abandoned while they were alerting at the agent. |
| OFFERED | The total number of times that interactions were received or initiated by an agent. The count includes interactions that were abandoned while inviting, handling attempts that the agent rejected, and warm consultations and conferences that the agent received. This count excludes simple consultations, whether they were initiated or received. |
| RESPONDED_THREAD | The total number of customer-interaction threads for which a first-time response was created by this agent. This measure includes an agent's first participation in outbound replies to inbound interactions. |
| RESPONDED_UNIQUE | The total number of first-time outbound replies in which this agent participated in response to customer interactions. Any number of replies could be prepared in response to a customer interaction. This measure attributes only the first-connected reply to this agent, regardless of whether the reply was sent. This measure excludes outbound replies to consultations, outbound replies that the agent pulled from his/her personal workbin or rejected, and system-generated responses. |
| RESPONSES | For voice and chat media, this measure represents the total number of times that customer interactions or warm consultations were answered or accepted by this agent. For voice media, this measure is identical to ACCEPTED; it returns positive values when agents initiate calls.
For e-mail, this measure represents the total number of times that the agent prepared an outbound reply. |
| ABANDONED_INVITE | The total number of times that customer interactions were abandoned or dropped for any reason while the interactions were alerting or ringing at this agent. |
| REJECTED | The total number of times that customer interactions alerted at an agent that belong to this agent group and were not accepted or answered. |
| INVITE | The total number of customer interactions that alerted or rang at this agent before the interactions were accepted, answered, or pulled plus the total number of dials that the agent performed, where the calls were successfully established. This measure is attributed to the interval in which the alerting/dialing first occurred.
The dialing component of this measure applies to voice media only. |
| INVITE_TIME | The total amount of time, in seconds, that customer interactions alerted at this agent plus the total duration of the dialing that the agent performed. For the alerting component of this measure, interactions do not have to be established for this measure to be incremented. For the dialing component, dial duration is measured for established calls only. This measure is attributed to the interval in which the alerting/dialing first occurred. |
| ENGAGE_TIME | The total amount of time, in seconds, that this agent was engaged with customers on interactions that the agent received. This measure excludes other interaction-related durations, such as hold time, ACW (Wrap) time, alert (ring) time, and time that is spent in collaboration or consultation. |
| ENGAGE | The total number of interactions for which this agent was engaged with customers for interactions that the agent received. This measure excludes other interaction-related counts, such as holds, instances of ACW, and collaborations and consultations that the agent received. |
| SHORT | The total number of times that customer interactions were accepted by this agent and then released, transferred, or stopped within the short-engagement threshold. This measure relies on the value of short-engagement (short-talk) as configured in the [agg-gim-thld-AGENT-IXN] section. |
| HOLD_TIME | The total amount of time, in seconds, that this agent had customer interactions on hold. |
| HOLD | The total number of customer interactions that this agent had on hold. |
| WRAP_TIME | The total amount of time, in seconds, that this agent was in ACW state for customer interactions that the agent received. This measure is attributed to the interval in which the agent was offered the interaction for which ACW was invoked. |
| WRAP | The total number of times that this agent was in ACW state for customer interactions that the agent received. This measure is attributed to the interval in which the agent was offered the interactions for which ACW was invoked. |
| CONSULT_RECEIVED_ENGAGE_TIME | The total amount of time, in seconds, that this agent was engaged in collaborations or simple consultations where the agents were the recipients of the collaboration/consultation requests and the collaborations/consultations were associated with customer interactions. |
| CONSULT_RECEIVED_ACCEPTED | The total number of times that this agent received and accepted collaborations or simple consultations that were associated with customer interactions. |
| CONSULT_RESPONSES | For e-mail, the total number of collaboration replies that were initiated by this agent. For voice, this measure is the same as CONSULT_RECEIVED_ACCEPTED. |
| CONSULT_RECEIVED_HOLD_TIME | The total amount of time, in seconds, that this agent had collaborations or simple consultations on hold, where the collaborations/consultations were associated with customer interactions and the agent was the recipient of the collaboration/consultation requests. |
| CONSULT_RECEIVED_HOLD | The total number of times that this agent was on hold during simple consultations that the agent received where the consultations were associated with customer interactions. |
| CONSULT_RECEIVED_WRAP_TIME | The total amount of time, in seconds, that this agent was in ACW (Wrap) state after simple consultations that the agent accepted, where the consultations were associated with customer calls. This duration does not stop if the agents received or made calls while in ACW state. This measure is attributed to the interval in which this agent was offered the consult interaction for which ACW was invoked. |
| CONSULT_RECEIVED_WRAP | The total number of times that this agent was in ACW state after requests for simple consultation that the agent accepted where the consultations were associated with customer interactions. |
| CONSULT_RCV_WARM_ENGAGE_TIME | The total amount of time, in seconds, that this agent was engaged in consultations that the agent received where the consultations were associated with customer interactions and the interactions were transferred to or conferenced with this agent. |
| CONSULT_RCV_ACC_WARM | The total number of times that this agent participated in consultations that the agent received, where the consultations were associated with customer interactions that were transferred to or conferenced with the agent. |
| CONSULT_RCV_WARM_HOLD_TIME | The total amount of time, in seconds, that this agent had consultations on hold where the consultations were associated with customer interactions, the agent was the recipient of the consultation requests, and the interactions were transferred to or conferenced with the agent. |
| CONSULT_RCV_WARM_HOLD | The total number of consultations that this agent had on hold where the consultations were associated with customer interactions, the agent was the recipient of the consultation requests, and the interactions were transferred to or conferenced with the agent. |
| CONSULT_RCV_WARM_WRAP_TIME | The total amount of time, in seconds, that this agent spent in ACW state following consultations that the agent requested and received, where the consultations were associated with customer interactions that were transferred to or conferenced with this agent.
In common call-flow scenarios, this measure yields a value of zero. |
| CONSULT_RCV_WARM_WRAP | The total number of times that this agent was in ACW state following consultations that the agent requested and received, where the consultations were associated with customer interactions and the interactions were transferred to or conferenced with the agent. This measure includes:
In common call-flow scenarios, this measure yields a value of zero. |
| CONSULT_INITIATED | The total number of times that this agent initiated requests for collaboration or simple consultation, where the collaborations/consultations were established and associated with customer interactions. |
| CONSULT_INITIATED_TIME | The total amount of time, in seconds, that this agent was engaged in collaborations or simple consultations that the agent requested, where the collaborations/consultations were associated with customer interactions. |
| CONFERENCE_INITIATED | The total number of times that this agent initiated conferences for customer interactions that the agent received, where the conferences were established. The count includes the number of established conferences that were initiated for transferred interactions that the agent received. |
| CONFERENCE_RECEIVED_ACCEPTED | The total number of times that this agent received and accepted collaborations or simple consultations that were associated with customer interactions. |
| TRANSFER_INIT_AGENT | The total number of times that this agent transferred customer interactions. Both warm and blind transfers are reflected in this measure. |
| XFER_RECEIVED_ACCEPTED | The total number of times that this agent received customer interactions that were successfully transferred to the agent. Both warm and blind transfers are reflected in this measure. |
| SATISFACTION_OFFERED | The total number of customer interactions handled by this agent for which customer-satisfaction scores were recorded. |
| SATISFACTION | The sum of numerical scores of customer satisfaction that were attributed to customer interactions handled by this agent. |
| REVENUE_OFFERED | The total number of customer interactions that entered or began within the contact center, were handled by this agent, and had associated revenue. |
| REVENUE | The total revenue that is generated during the interval by customer interactions handled by this agent. |
| AGENT_DISCONNECT_FIRST | The total number of times during the reporting interval that this agent released customer interactions before the other party did. The tally is incremented only when the system (such as the switch) provides such information. |
| ACTIONABILITY_OFFERED | The total number of customer interactions that were offered to, pulled, or initiated by this agent for whom an actionability score was attached. Actionability scores measure the degree to which interactions required agent attention. |
| ACTIONABILITY | The sum of actionability scores attached to customer interactions that were handled by this agent. |
| SENTIMENT_OFFERED | The total number of customer interactions that were offered to, pulled, or initiated by this agent for whom a sentiment score was attached. Sentiment scores reflect the attitude expressed by customers. |
| SENTIMENT | The sum of sentiment scores attached to customer interactions that were handled by this agent. |
| INFLUENCE_OFFERED | The total number of customer interactions that were offered to, pulled, or initiated by this agent for whom an influence score was attached. Influence scores represent the clout that the customer amassed on social networks. |
| INFLUENCE | The sum of influence scores attached to customer interactions that were handled by this agent. |
| DATE_TIME_KEY | The surrogate key that is used to join this aggregate table to the DATE_TIME dimension table to identify the calendar date and 15-minute interval at which the agent’s participation in the interaction began. |
| GROUP_COMBINATION_KEY | The surrogate key that is used to join records in this aggregate table to the RESOURCE_GROUP_ COMBINATION dimension table to identify a specific combination of queue groups of which the queue was a member when the interaction entered the queue. |
| RESOURCE_KEY | The surrogate key that is used to join this aggregate table to the RESOURCE_ dimension table. |
| INTERACTION_DESCRIPTOR_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_DESCRIPTOR dimension table to identify the business attributes that have been assigned to the interaction. |
| TENANT_KEY | The surrogate key that is used to join this aggregate table to the TENANT view to identify a specific tenant. |
| MEDIA_TYPE_KEY | The surrogate key that is used to join this aggregate table to the MEDIA_TYPE dimension table. |
| INTERACTION_TYPE_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_TYPE dimension table. |
| USER_DATA_KEY1 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction.
If you engage the social-media feature, RAA maps this field to GEN_ES_KEY in the IRF_USER_DATA_KEYS table. |
| USER_DATA_KEY2 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction. |
| POST_CALL_SURVEY_KEY1 | The surrogate key that is used to join this aggregate table to the POST_CALL_SURVEY dimension table. |
| POST_CALL_SURVEY_KEY2 | The surrogate key that is used to join this aggregate table to the POST_CALL_SURVEY dimension table. |
| ACCEPTED_THREAD | The total number of customer-interaction threads that were accepted, initiated, or pulled for the first time by this agent. This measure includes an agent's first participation in outbound replies to inbound interactions and yields the same values as ACCEPTED_UNIQUE for media other than e-mail. |
| ACCEPTED_UNIQUE | The total number of logical interactions that were accepted, initiated, or pulled by this agent. This measure includes an agent's first participation in outbound replies to inbound interactions. |
| ACCEPTED | The total number of times that customer interactions or warm consultations were accepted, answered, pulled, or initiated by this agent.
For voice media, this measure is identical to RESPONSES. |
| NOTACCEPTED | The total number of times that customer interactions were redirected to another resource upon no answer by this agent or were otherwise not accepted or answered by this agent. This measure includes interactions that the customer abandoned while they were alerting at the agent. |
| OFFERED | The total number of times that interactions were received or initiated by an agent. The count includes interactions that were abandoned while inviting, handling attempts that the agent rejected, and warm consultations and conferences that the agent received. This count excludes simple consultations, whether they were initiated or received. |
| RESPONDED_THREAD | The total number of customer-interaction threads for which a first-time response was created by this agent. This measure includes an agent's first participation in outbound replies to inbound interactions. |
| RESPONDED_UNIQUE | The total number of first-time outbound replies in which this agent participated in response to customer interactions. Any number of replies could be prepared in response to a customer interaction. This measure attributes only the first-connected reply to this agent, regardless of whether the reply was sent. This measure excludes outbound replies to consultations, outbound replies that the agent pulled from his/her personal workbin or rejected, and system-generated responses. |
| RESPONSES | For voice and chat media, this measure represents the total number of times that customer interactions or warm consultations were answered or accepted by this agent. For voice media, this measure is identical to ACCEPTED; it returns positive values when agents initiate calls.
For e-mail, this measure represents the total number of times that the agent prepared an outbound reply. |
| ABANDONED_INVITE | The total number of times that customer interactions were abandoned or dropped for any reason while the interactions were alerting or ringing at this agent. |
| REJECTED | The total number of times that customer interactions alerted at an agent that belong to this agent group and were not accepted or answered. |
| INVITE | The total number of customer interactions that alerted or rang at this agent before the interactions were accepted, answered, or pulled plus the total number of dials that the agent performed, where the calls were successfully established. This measure is attributed to the interval in which the alerting/dialing first occurred.
The dialing component of this measure applies to voice media only. |
| INVITE_TIME | The total amount of time, in seconds, that customer interactions alerted at this agent plus the total duration of the dialing that the agent performed. For the alerting component of this measure, interactions do not have to be established for this measure to be incremented. For the dialing component, dial duration is measured for established calls only. This measure is attributed to the interval in which the alerting/dialing first occurred. |
| ENGAGE_TIME | The total amount of time, in seconds, that this agent was engaged with customers on interactions that the agent received. This measure excludes other interaction-related durations, such as hold time, ACW (Wrap) time, alert (ring) time, and time that is spent in collaboration or consultation. |
| ENGAGE | The total number of interactions for which this agent was engaged with customers for interactions that the agent received. This measure excludes other interaction-related counts, such as holds, instances of ACW, and collaborations and consultations that the agent received. |
| SHORT | The total number of times that customer interactions were accepted by this agent and then released, transferred, or stopped within the short-engagement threshold. This measure relies on the value of short-engagement (short-talk) as configured in the [agg-gim-thld-AGENT-IXN] section. |
| HOLD_TIME | The total amount of time, in seconds, that this agent had customer interactions on hold. |
| HOLD | The total number of customer interactions that this agent had on hold. |
| WRAP_TIME | The total amount of time, in seconds, that this agent was in ACW state for customer interactions that the agent received. This measure is attributed to the interval in which the agent was offered the interaction for which ACW was invoked. |
| WRAP | The total number of times that this agent was in ACW state for customer interactions that the agent received. This measure is attributed to the interval in which the agent was offered the interactions for which ACW was invoked. |
| CONSULT_RECEIVED_ENGAGE_TIME | The total amount of time, in seconds, that this agent was engaged in collaborations or simple consultations where the agents were the recipients of the collaboration/consultation requests and the collaborations/consultations were associated with customer interactions. |
| CONSULT_RECEIVED_ACCEPTED | The total number of times that this agent received and accepted collaborations or simple consultations that were associated with customer interactions. |
| CONSULT_RESPONSES | For e-mail, the total number of collaboration replies that were initiated by this agent. For voice, this measure is the same as CONSULT_RECEIVED_ACCEPTED. |
| CONSULT_RECEIVED_HOLD_TIME | The total amount of time, in seconds, that this agent had collaborations or simple consultations on hold, where the collaborations/consultations were associated with customer interactions and the agent was the recipient of the collaboration/consultation requests. |
| CONSULT_RECEIVED_HOLD | The total number of times that this agent was on hold during simple consultations that the agent received where the consultations were associated with customer interactions. |
| CONSULT_RECEIVED_WRAP_TIME | The total amount of time, in seconds, that this agent was in ACW (Wrap) state after simple consultations that the agent accepted, where the consultations were associated with customer calls. This duration does not stop if the agents received or made calls while in ACW state. This measure is attributed to the interval in which this agent was offered the consult interaction for which ACW was invoked. |
| CONSULT_RECEIVED_WRAP | The total number of times that this agent was in ACW state after requests for simple consultation that the agent accepted where the consultations were associated with customer interactions. |
| CONSULT_RCV_WARM_ENGAGE_TIME | The total amount of time, in seconds, that this agent was engaged in consultations that the agent received where the consultations were associated with customer interactions and the interactions were transferred to or conferenced with this agent. |
| CONSULT_RCV_ACC_WARM | The total number of times that this agent participated in consultations that the agent received, where the consultations were associated with customer interactions that were transferred to or conferenced with the agent. |
| CONSULT_RCV_WARM_HOLD_TIME | The total amount of time, in seconds, that this agent had consultations on hold where the consultations were associated with customer interactions, the agent was the recipient of the consultation requests, and the interactions were transferred to or conferenced with the agent. |
| CONSULT_RCV_WARM_HOLD | The total number of consultations that this agent had on hold where the consultations were associated with customer interactions, the agent was the recipient of the consultation requests, and the interactions were transferred to or conferenced with the agent. |
| CONSULT_RCV_WARM_WRAP_TIME | The total amount of time, in seconds, that this agent spent in ACW state following consultations that the agent requested and received, where the consultations were associated with customer interactions that were transferred to or conferenced with this agent.
In common call-flow scenarios, this measure yields a value of zero. |
| CONSULT_RCV_WARM_WRAP | The total number of times that this agent was in ACW state following consultations that the agent requested and received, where the consultations were associated with customer interactions and the interactions were transferred to or conferenced with the agent. This measure includes:
In common call-flow scenarios, this measure yields a value of zero. |
| CONSULT_INITIATED | The total number of times that this agent initiated requests for collaboration or simple consultation, where the collaborations/consultations were established and associated with customer interactions. |
| CONSULT_INITIATED_TIME | The total amount of time, in seconds, that this agent was engaged in collaborations or simple consultations that the agent requested, where the collaborations/consultations were associated with customer interactions. |
| CONFERENCE_INITIATED | The total number of times that this agent initiated conferences for customer interactions that the agent received, where the conferences were established. The count includes the number of established conferences that were initiated for transferred interactions that the agent received. |
| CONFERENCE_RECEIVED_ACCEPTED | The total number of times that this agent received and accepted collaborations or simple consultations that were associated with customer interactions. |
| TRANSFER_INIT_AGENT | The total number of times that this agent transferred customer interactions. Both warm and blind transfers are reflected in this measure. |
| XFER_RECEIVED_ACCEPTED | The total number of times that this agent received customer interactions that were successfully transferred to the agent. Both warm and blind transfers are reflected in this measure. |
| SATISFACTION_OFFERED | The total number of customer interactions handled by this agent for which customer-satisfaction scores were recorded. |
| SATISFACTION | The sum of numerical scores of customer satisfaction that were attributed to customer interactions handled by this agent. |
| REVENUE_OFFERED | The total number of customer interactions that entered or began within the contact center, were handled by this agent, and had associated revenue. |
| REVENUE | The total revenue that is generated during the interval by customer interactions handled by this agent. |
| AGENT_DISCONNECT_FIRST | The total number of times during the reporting interval that this agent released customer interactions before the other party did. The tally is incremented only when the system (such as the switch) provides such information. |
| ACTIONABILITY_OFFERED | The total number of customer interactions that were offered to, pulled, or initiated by this agent for whom an actionability score was attached. Actionability scores measure the degree to which interactions required agent attention. |
| ACTIONABILITY | The sum of actionability scores attached to customer interactions that were handled by this agent. |
| SENTIMENT_OFFERED | The total number of customer interactions that were offered to, pulled, or initiated by this agent for whom a sentiment score was attached. Sentiment scores reflect the attitude expressed by customers. |
| SENTIMENT | The sum of sentiment scores attached to customer interactions that were handled by this agent. |
| INFLUENCE_OFFERED | The total number of customer interactions that were offered to, pulled, or initiated by this agent for whom an influence score was attached. Influence scores represent the clout that the customer amassed on social networks. |
| INFLUENCE | The sum of influence scores attached to customer interactions that were handled by this agent. |
| DATE_TIME_KEY | The surrogate key that is used to join this aggregate table to the DATE_TIME dimension table to identify the calendar date and 15-minute interval that correspond to the start of the aggregated interval. |
| AGENT_GROUP_COMBINATION_KEY | The surrogate key that is used to join this aggregate table to a specific combination of agent groups in the RESOURCE_GROUP_COMBINATION dimension table. This field identifies the combination of groups of which the agent was a member when the agent was offered the interaction. |
| AGENT_RESOURCE_KEY | The surrogate key that is used to join this aggregate table to the RESOURCE_ dimension table to identify a specific agent. |
| INTERACTION_DESCRIPTOR_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_DESCRIPTOR dimension table to identify the business attributes that have been assigned to the interaction. |
| TENANT_KEY | The surrogate key that is used to join this aggregate table to the TENANT view to identify a specific tenant. |
| QUEUE_GROUP_COMBINATION_KEY | The surrogate key that is used to join this aggregate table to a specific combination of queue groups in the RESOURCE_GROUP_COMBINATION dimension table. This field identifies the groups of which the queue was a member when the agent was offered the interaction. |
| QUEUE_RESOURCE_KEY | The surrogate key that is used to join this aggregate table to the RESOURCE_ dimension table to identify a specific queue. |
| MEDIA_TYPE_KEY | The surrogate key that is used to join this aggregate table to the MEDIA_TYPE dimension table. |
| INTERACTION_TYPE_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_TYPE dimension table. |
| USER_DATA_KEY1 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction.
If you engage the social-media feature, RAA maps this field to GEN_ES_KEY in the IRF_USER_DATA_KEYS table. |
| USER_DATA_KEY2 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction. |
| POST_CALL_SURVEY_KEY1 | The surrogate key that is used to join this aggregate table to the POST_CALL_SURVEY dimension table. |
| POST_CALL_SURVEY_KEY2 | The surrogate key that is used to join this aggregate table to the POST_CALL_SURVEY dimension table. |
| ACCEPTED_THREAD | The total number of customer-interaction threads that were accepted, initiated, or pulled from this queue for the first time by this agent. This measure includes an agent's first participation in outbound replies to inbound interactions and yields the same values as ACCEPTED_UNIQUE for media other than e-mail. |
| ACCEPTED_UNIQUE | The total number of logical interactions that were accepted, initiated, or pulled from this queue by this agent. This measure includes an agent's first participation in outbound replies to inbound interactions. |
| ACCEPTED | The total number of times that customer interactions or warm consultations that were distributed from this queue were accepted, answered, or pulled by this agent.
For voice media, this measure is identical to RESPONSES. |
| NOTACCEPTED | The total number of times that customer interactions, that were distributed from this queue were redirected to another resource upon no answer by this agent or were otherwise not accepted or answered by the agent. This measure includes interactions that the customer abandoned while they were alerting at the agent. |
| OFFERED | The total number of times that interactions, distributed or pulled from this queue, were received or initiated by this agent excluding interactions that were abandoned within the short-abandoned threshold. The count includes interactions that were abandoned while inviting, handling attempts that the agent rejected, and warm consultations and conferences that the agent received. This count excludes simple consultations, whether they were initiated or received.
This measure relies on the value of the short-abandoned threshold as configured in the [agg-gim-thld-ID-IXN] section. |
| RESPONDED_UNIQUE | The total number of first-time outbound replies made by this agent in response to customer interactions that were pulled or transferred from this queue. Any number of replies could be prepared in response to a customer interaction. This measure attributes only the first-connected reply to this agent, regardless of whether the reply was sent. This measure excludes outbound replies to consultations, outbound replies that the agent pulled from his/her personal workbin or rejected, and system-generated responses. |
| RESPONSES | For voice and chat media, this measure represents the total number of times that customer interactions or warm consultations were distributed or pulled from this queue and answered or accepted by this agent. For voice media, this measure is identical to ACCEPTED; it returns positive values when agents initiate calls.
For e-mail, this measure represents the total number of times that the agent created an outbound reply for interactions that were distributed or pulled from this interaction queue or workbin. |
| ABANDONED_INVITE | The total number of times that customer interactions that were distributed or pulled from this queue, were abandoned or dropped for any reason while the interactions were alerting at this agent. |
| REJECTED | The total number of times that customer interactions were distributed from this queue, alerted at this agent, and were not accepted or answered. |
| INVITE | The total number of customer interactions that were distributed from this queue that alerted or rang at this agent before the interactions were accepted, answered, or pulled plus the total number of dials that the agent performed, where the calls were successfully established. This measure is attributed to the interval in which the alerting/dialing first occurred.
The dialing component of this measure applies to voice media only. |
| INVITE_TIME | The total amount of time, in seconds, that customer interactions alerted at this agent plus the total duration of the dialing that the agent performed for calls that were distributed or pulled from this queue. For the alerting component of this measure, interactions do not have to be established for this measure to be incremented. For the dialing component, dial duration is measured for established calls only. This measure is attributed to the interval in which the alerting/dialing first occurred. |
| ENGAGE_TIME | For interactions that were distributed or pulled from this queue, the total amount of time, in seconds, that this agent was engaged with customers on interactions that the agent received. This measure excludes other interaction-related durations, such as hold time, ACW (Wrap) time, alert (ring) time, and time that is spent in collaboration or consultation. |
| ENGAGE | For interactions that were distributed or pulled from this queue, the total number of interactions in which this agent was engaged with customers for interactions that the agent received. This measure excludes other interaction-related counts, such as holds, instances of ACW, and collaborations and consultations that the agent received. |
| SHORT | The total number of times that customer interactions were distributed or pulled from this queue, accepted by this agent, and then released, transferred, or stopped within the short-engagement threshold.
This measure relies on the value of short-engagement (short-talk) as configured in the [agg-gim-thld-AGENT-IXN] section. |
| HOLD_TIME | The total amount of time, in seconds, that this agent had customer interactions, distributed from this queue, on hold. |
| HOLD | The total number of customer interactions that were distributed from this queue that this agent had on hold. |
| WRAP_TIME | The total amount of time, in seconds, that this agent was in ACW state for customer interactions that the agent received from this queue. This measure is attributed to the interval in which the agent was offered the interaction for which ACW was invoked. |
| WRAP | The total number of times that this agent was in ACW state for customer interactions that the agent received from this queue. This measure is attributed to the interval in which the agent was offered the interactions for which ACW was invoked. |
| CONSULT_RECEIVED_ENGAGE_TIME | The total amount time, in seconds, that this agent was engaged in collaborations and simple consultations that were distributed or pulled from this queue where the collaborations/consultations were associated with customer interactions and the agent was the recipient of the collaboration/consultation requests. |
| CONSULT_RECEIVED_ACCEPTED | The total number of times that this agent received and accepted collaborations or simple consultations that were distributed or pulled from this queue and associated with customer interactions. |
| CONSULT_RESPONSES | For e-mail, the total number of collaboration replies that were initiated by this agent for customer interactions that were distributed from this queue. For voice, this measure is the same as CONSULT_RECEIVED_ACCEPTED. |
| CONSULT_RECEIVED_HOLD_TIME | The total amount time, in seconds, that this agent had collaborations or simple consultations on hold where the collaborations/consultations were distributed or pulled from this queue and associated with customer interactions and the agent was the recipient of the collaboration/consultation requests. |
| CONSULT_RECEIVED_HOLD | The total number of times that this agent was on hold during simple consultations that the agent received where the consultations were associated with customer interactions and were distributed from this queue. |
| CONSULT_RECEIVED_WRAP_TIME | The total amount of time, in seconds, that this agent spent in ACW state after simple consultations that the agent accepted, where the consultations were distributed from this queue and were associated with customer calls. This duration does not stop if the agents received or made calls while in ACW state. This measure is attributed to the interval in which this agent was offered the consult interaction for which ACW was invoked. |
| CONSULT_RECEIVED_WRAP | The total number of times that this agent was in ACW state after requests for simple consultation that the agent accepted and that were distributed from this queue where the consultations were associated with customer interactions. |
| CONSULT_RCV_WARM_ENGAGE_TIME | The total amount of time, in seconds, that this agent was engaged in consultations that were distributed or pulled from this queue where the consultations were associated with customer interactions, the agent was the recipient of the consultation requests, and the interactions were transferred to or conferenced with the agent. |
| CONSULT_RCV_ACC_WARM | The total number of times that this agent participated in consultations that the agent received, where the consultations were distributed or pulled from this queue, associated with customer interactions, and transferred to or conferenced with the agent. |
| CONSULT_RCV_WARM_HOLD_TIME | The total amount of time, in seconds, that this agent had consultations on hold where the consultations were distributed or pulled from this queue and associated with customer interactions, the agent was the recipient of the consultation requests, and the interactions were transferred to or conferenced with the agent. |
| CONSULT_RCV_WARM_HOLD | The total number of consultations distributed from this queue that this agent had on hold where the consultations were associated with customer interactions, the agent was the recipient of the consultation requests, and the interactions were transferred to or conferenced with the agent. |
| CONSULT_RCV_WARM_WRAP_TIME | The total amount of time, in seconds, that this agent spent in ACW state following consultations that the agent requested and received, where the consultations were distributed from this queue and were associated with customer interactions that were transferred to or conferenced with the agent.
This measure includes:
In common call-flow scenarios, this measure yields a value of zero. |
| CONSULT_RCV_WARM_WRAP | The total number of times that this agent was in ACW state following consultations that were distributed from this queue and that the agent requested and received, where the consultations were associated with customer interactions, and the interactions were transferred to or conferenced with the agent.
This measure includes:
In common call-flow scenarios, this measure yields a value of zero. |
| CONSULT_INITIATED | The total number of times that this agent initiated requests for collaboration or simple consultation, where the collaborations/consultations were established, distributed or pulled from this queue, and associated with customer interactions. |
| CONSULT_INITIATED_TIME | The total amount of time, in seconds, that this agent was engaged in collaborations or simple consultations that the agent requested, where the collaborations/consultations were associated with customer interactions that were distributed or pulled from this queue. |
| CONFERENCE_INITIATED | The total number of times that this agent initiated conferences for customer interactions that the agent received, where the interactions were distributed or pulled from this queue and, where the conferences were established. The count includes the number of established conferences that were initiated for transferred interactions that the agent received. |
| CONFERENCE_RECEIVED_ACCEPTED | The total number of times that this agent joined conferences to participate in interactions that were distributed or pulled from this queue. |
| TRANSFER_INIT_AGENT | The total number of times that this agent transferred customer interactions that were distributed or pulled from this queue. Both warm and blind transfers are reflected in this measure. |
| XFER_RECEIVED_ACCEPTED | The total number of times that this agent received customer interactions that were distributed or pulled from this queue that were successfully transferred to the agent. Both warm and blind transfers are reflected in this measure. |
| SATISFACTION_OFFERED | The total number of customer interactions that were distributed from this queue and handled by this agent for which customer-satisfaction scores were recorded. |
| SATISFACTION | The sum of numerical scores of customer satisfaction that were attributed to customer interactions that were distributed from this queue and handled by this agent. |
| REVENUE_OFFERED | The total number of customer interactions that entered or began within the contact center, were distributed from this queue, had associated revenue, and were handled by this agent. |
| REVENUE | The total revenue that is generated during the interval by customer interactions that were distributed from this queue and handled by this agent. |
| AGENT_DISCONNECT_FIRST | The total number of times during the reporting interval that this agent released customer interactions, distributed from this queue, before the other party did. The tally is incremented only when the system (such as the switch) provides such information. |
| ACTIONABILITY_OFFERED | The total number of customer interactions that were offered to this agent and distributed from this queue for which an actionability score was attached. Actionability scores measure the degree to which interactions required agent attention. |
| ACTIONABILITY | The sum of actionability scores attached to customer interactions that were handled this agent and distributed from this queue. |
| SENTIMENT_OFFERED | The total number of customer interactions that were offered to this agent and distributed from this queue for which a sentiment score was attached. Sentiment scores reflect the attitude expressed by customers. |
| SENTIMENT | The sum of sentiment scores attached to customer interactions that were handled by this agent and distributed from this queue. |
| INFLUENCE_OFFERED | The total number of customer interactions that were offered to this agent and distributed from this queue for which an influence score was attached. Influence scores represent the clout that the customer amassed on social networks. |
| INFLUENCE | The sum of influence scores attached to customer interactions that were handled by this agent and distributed from this queue. |
| DATE_TIME_KEY | The surrogate key that is used to join this aggregate table to the DATE_TIME dimension table to identify the calendar date and 15-minute interval that correspond to the start of the aggregated interval. |
| AGENT_GROUP_COMBINATION_KEY | The surrogate key that is used to join this aggregate table to a specific combination of agent groups in the RESOURCE_GROUP_COMBINATION dimension table. This field identifies the combination of groups of which the agent was a member when the agent was offered the interaction. |
| AGENT_RESOURCE_KEY | The surrogate key that is used to join this aggregate table to the RESOURCE_ dimension table to identify a specific agent. |
| INTERACTION_DESCRIPTOR_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_DESCRIPTOR dimension table to identify the business attributes that have been assigned to the interaction. |
| TENANT_KEY | The surrogate key that is used to join this aggregate table to the TENANT view to identify a specific tenant. |
| QUEUE_GROUP_COMBINATION_KEY | The surrogate key that is used to join this aggregate table to a specific combination of queue groups in the RESOURCE_GROUP_COMBINATION dimension table. This field identifies the groups of which the queue was a member when the agent was offered the interaction. |
| QUEUE_RESOURCE_KEY | The surrogate key that is used to join this aggregate table to the RESOURCE_ dimension table to identify a specific queue. |
| MEDIA_TYPE_KEY | The surrogate key that is used to join this aggregate table to the MEDIA_TYPE dimension table. |
| INTERACTION_TYPE_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_TYPE dimension table. |
| USER_DATA_KEY1 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction.
If you engage the social-media feature, RAA maps this field to GEN_ES_KEY in the IRF_USER_DATA_KEYS table. |
| USER_DATA_KEY2 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction. |
| POST_CALL_SURVEY_KEY1 | The surrogate key that is used to join this aggregate table to the POST_CALL_SURVEY dimension table. |
| POST_CALL_SURVEY_KEY2 | The surrogate key that is used to join this aggregate table to the POST_CALL_SURVEY dimension table. |
| ACCEPTED_THREAD | The total number of customer-interaction threads that were accepted, initiated, or pulled from this queue for the first time by this agent. This measure includes an agent's first participation in outbound replies to inbound interactions and yields the same values as ACCEPTED_UNIQUE for media other than e-mail. |
| ACCEPTED_UNIQUE | The total number of logical interactions that were accepted, initiated, or pulled from this queue by this agent. This measure includes an agent's first participation in outbound replies to inbound interactions. |
| ACCEPTED | The total number of times that customer interactions or warm consultations that were distributed from this queue were accepted, answered, or pulled by this agent.
For voice media, this measure is identical to RESPONSES. |
| NOTACCEPTED | The total number of times that customer interactions, that were distributed from this queue were redirected to another resource upon no answer by this agent or were otherwise not accepted or answered by the agent. This measure includes interactions that the customer abandoned while they were alerting at the agent. |
| OFFERED | The total number of times that interactions, distributed or pulled from this queue, were received or initiated by this agent excluding interactions that were abandoned within the short-abandoned threshold. The count includes interactions that were abandoned while inviting, handling attempts that the agent rejected, and warm consultations and conferences that the agent received. This count excludes simple consultations, whether they were initiated or received.
This measure relies on the value of the short-abandoned threshold as configured in the [agg-gim-thld-ID-IXN] section. |
| RESPONDED_UNIQUE | The total number of first-time outbound replies made by this agent in response to customer interactions that were pulled or transferred from this queue. Any number of replies could be prepared in response to a customer interaction. This measure attributes only the first-connected reply to this agent, regardless of whether the reply was sent. This measure excludes outbound replies to consultations, outbound replies that the agent pulled from his/her personal workbin or rejected, and system-generated responses. |
| RESPONSES | For voice and chat media, this measure represents the total number of times that customer interactions or warm consultations were distributed or pulled from this queue and answered or accepted by this agent. For voice media, this measure is identical to ACCEPTED; it returns positive values when agents initiate calls.
For e-mail, this measure represents the total number of times that the agent created an outbound reply for interactions that were distributed or pulled from this interaction queue or workbin. |
| ABANDONED_INVITE | The total number of times that customer interactions that were distributed or pulled from this queue, were abandoned or dropped for any reason while the interactions were alerting at this agent. |
| REJECTED | The total number of times that customer interactions were distributed from this queue, alerted at this agent, and were not accepted or answered. |
| INVITE | The total number of customer interactions that were distributed from this queue that alerted or rang at this agent before the interactions were accepted, answered, or pulled plus the total number of dials that the agent performed, where the calls were successfully established. This measure is attributed to the interval in which the alerting/dialing first occurred.
The dialing component of this measure applies to voice media only. |
| INVITE_TIME | The total amount of time, in seconds, that customer interactions alerted at this agent plus the total duration of the dialing that the agent performed for calls that were distributed or pulled from this queue. For the alerting component of this measure, interactions do not have to be established for this measure to be incremented. For the dialing component, dial duration is measured for established calls only. This measure is attributed to the interval in which the alerting/dialing first occurred. |
| ENGAGE_TIME | For interactions that were distributed or pulled from this queue, the total amount of time, in seconds, that this agent was engaged with customers on interactions that the agent received. This measure excludes other interaction-related durations, such as hold time, ACW (Wrap) time, alert (ring) time, and time that is spent in collaboration or consultation. |
| ENGAGE | For interactions that were distributed or pulled from this queue, the total number of interactions in which this agent was engaged with customers for interactions that the agent received. This measure excludes other interaction-related counts, such as holds, instances of ACW, and collaborations and consultations that the agent received. |
| SHORT | The total number of times that customer interactions were distributed or pulled from this queue, accepted by this agent, and then released, transferred, or stopped within the short-engagement threshold.
This measure relies on the value of short-engagement (short-talk) as configured in the [agg-gim-thld-AGENT-IXN] section. |
| HOLD_TIME | The total amount of time, in seconds, that this agent had customer interactions, distributed from this queue, on hold. |
| HOLD | The total number of customer interactions that were distributed from this queue that this agent had on hold. |
| WRAP_TIME | The total amount of time, in seconds, that this agent was in ACW state for customer interactions that the agent received from this queue. This measure is attributed to the interval in which the agent was offered the interaction for which ACW was invoked. |
| WRAP | The total number of times that this agent was in ACW state for customer interactions that the agent received from this queue. This measure is attributed to the interval in which the agent was offered the interactions for which ACW was invoked. |
| CONSULT_RECEIVED_ENGAGE_TIME | The total amount time, in seconds, that this agent was engaged in collaborations and simple consultations that were distributed or pulled from this queue where the collaborations/consultations were associated with customer interactions and the agent was the recipient of the collaboration/consultation requests. |
| CONSULT_RECEIVED_ACCEPTED | The total number of times that this agent received and accepted collaborations or simple consultations that were distributed or pulled from this queue and associated with customer interactions. |
| CONSULT_RESPONSES | For e-mail, the total number of collaboration replies that were initiated by this agent for customer interactions that were distributed from this queue. For voice, this measure is the same as CONSULT_RECEIVED_ACCEPTED. |
| CONSULT_RECEIVED_HOLD_TIME | The total amount time, in seconds, that this agent had collaborations or simple consultations on hold where the collaborations/consultations were distributed or pulled from this queue and associated with customer interactions and the agent was the recipient of the collaboration/consultation requests. |
| CONSULT_RECEIVED_HOLD | The total number of times that this agent was on hold during simple consultations that the agent received where the consultations were associated with customer interactions and were distributed from this queue. |
| CONSULT_RECEIVED_WRAP_TIME | The total amount of time, in seconds, that this agent spent in ACW state after simple consultations that the agent accepted, where the consultations were distributed from this queue and were associated with customer calls. This duration does not stop if the agents received or made calls while in ACW state. This measure is attributed to the interval in which this agent was offered the consult interaction for which ACW was invoked. |
| CONSULT_RECEIVED_WRAP | The total number of times that this agent was in ACW state after requests for simple consultation that the agent accepted and that were distributed from this queue where the consultations were associated with customer interactions. |
| CONSULT_RCV_WARM_ENGAGE_TIME | The total amount of time, in seconds, that this agent was engaged in consultations that were distributed or pulled from this queue where the consultations were associated with customer interactions, the agent was the recipient of the consultation requests, and the interactions were transferred to or conferenced with the agent. |
| CONSULT_RCV_ACC_WARM | The total number of times that this agent participated in consultations that the agent received, where the consultations were distributed or pulled from this queue, associated with customer interactions, and transferred to or conferenced with the agent. |
| CONSULT_RCV_WARM_HOLD_TIME | The total amount of time, in seconds, that this agent had consultations on hold where the consultations were distributed or pulled from this queue and associated with customer interactions, the agent was the recipient of the consultation requests, and the interactions were transferred to or conferenced with the agent. |
| CONSULT_RCV_WARM_HOLD | The total number of consultations distributed from this queue that this agent had on hold where the consultations were associated with customer interactions, the agent was the recipient of the consultation requests, and the interactions were transferred to or conferenced with the agent. |
| CONSULT_RCV_WARM_WRAP_TIME | The total amount of time, in seconds, that this agent spent in ACW state following consultations that the agent requested and received, where the consultations were distributed from this queue and were associated with customer interactions that were transferred to or conferenced with the agent.
This measure includes:
In common call-flow scenarios, this measure yields a value of zero. |
| CONSULT_RCV_WARM_WRAP | The total number of times that this agent was in ACW state following consultations that were distributed from this queue and that the agent requested and received, where the consultations were associated with customer interactions, and the interactions were transferred to or conferenced with the agent.
This measure includes:
In common call-flow scenarios, this measure yields a value of zero. |
| CONSULT_INITIATED | The total number of times that this agent initiated requests for collaboration or simple consultation, where the collaborations/consultations were established, distributed or pulled from this queue, and associated with customer interactions. |
| CONSULT_INITIATED_TIME | The total amount of time, in seconds, that this agent was engaged in collaborations or simple consultations that the agent requested, where the collaborations/consultations were associated with customer interactions that were distributed or pulled from this queue. |
| CONFERENCE_INITIATED | The total number of times that this agent initiated conferences for customer interactions that the agent received, where the interactions were distributed or pulled from this queue and, where the conferences were established. The count includes the number of established conferences that were initiated for transferred interactions that the agent received. |
| CONFERENCE_RECEIVED_ACCEPTED | The total number of times that this agent joined conferences to participate in interactions that were distributed or pulled from this queue. |
| TRANSFER_INIT_AGENT | The total number of times that this agent transferred customer interactions that were distributed or pulled from this queue. Both warm and blind transfers are reflected in this measure. |
| XFER_RECEIVED_ACCEPTED | The total number of times that this agent received customer interactions that were distributed or pulled from this queue that were successfully transferred to the agent. Both warm and blind transfers are reflected in this measure. |
| SATISFACTION_OFFERED | The total number of customer interactions that were distributed from this queue and handled by this agent for which customer-satisfaction scores were recorded. |
| SATISFACTION | The sum of numerical scores of customer satisfaction that were attributed to customer interactions that were distributed from this queue and handled by this agent. |
| REVENUE_OFFERED | The total number of customer interactions that entered or began within the contact center, were distributed from this queue, had associated revenue, and were handled by this agent. |
| REVENUE | The total revenue that is generated during the interval by customer interactions that were distributed from this queue and handled by this agent. |
| AGENT_DISCONNECT_FIRST | The total number of times during the reporting interval that this agent released customer interactions, distributed from this queue, before the other party did. The tally is incremented only when the system (such as the switch) provides such information. |
| ACTIONABILITY_OFFERED | The total number of customer interactions that were offered to this agent and distributed from this queue for which an actionability score was attached. Actionability scores measure the degree to which interactions required agent attention. |
| ACTIONABILITY | The sum of actionability scores attached to customer interactions that were handled this agent and distributed from this queue. |
| SENTIMENT_OFFERED | The total number of customer interactions that were offered to this agent and distributed from this queue for which a sentiment score was attached. Sentiment scores reflect the attitude expressed by customers. |
| SENTIMENT | The sum of sentiment scores attached to customer interactions that were handled by this agent and distributed from this queue. |
| INFLUENCE_OFFERED | The total number of customer interactions that were offered to this agent and distributed from this queue for which an influence score was attached. Influence scores represent the clout that the customer amassed on social networks. |
| INFLUENCE | The sum of influence scores attached to customer interactions that were handled by this agent and distributed from this queue. |
| DATE_TIME_KEY | The surrogate key that is used to join this aggregate table to the DATE_TIME dimension table to identify the calendar date and 15-minute interval that correspond to the start of the aggregated interval. |
| INTERACTION_DESCRIPTOR_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_DESCRIPTOR dimension table to identify the business attributes that have been assigned to the interaction. |
| TENANT_KEY | The surrogate key that is used to join this aggregate table to the TENANT view to identify a specific tenant. |
| MEDIA_TYPE_KEY | The surrogate key that is used to join this aggregate table to the GROUP_ view to identify the specific queue group of which the queue was a member when the interaction entered the queue. |
| INTERACTION_TYPE_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_TYPE dimension table. |
| USER_DATA_KEY1 | The surrogate key that is used to join this aggregate table to a custom user-data dimension table to identify attached data that has been assigned to the interaction. |
| USER_DATA_KEY2 | The surrogate key that is used to join this aggregate table to a custom user-data dimension table to identify attached data that has been assigned to the interaction. |
| GPM_PREDICTOR_KEY | The name of the predictor in the Journey Optimization Platform (JOP). If an error is encountered, the section name in the PredictorsCfg Transaction List object is used as the predictor name. |
| GPM_MODEL_KEY | The surrogate key that is used to join the GPM_MODEL dimension to the fact table, to identify the model used to calculate agent scores for the interaction. |
| GPM_RESULT_KEY | The surrogate key that is used to join the GPM_RESULT dimension to the fact table, to identify the result of the Predictive Routing attempt. |
| ACCEPTED | The total number of customer interactions of this business attribute that were accepted, answered, or pulled by a handling resource. |
| ACCEPTED_FCR | The total number of customer interactions of this business attribute that were accepted, answered, or pulled by a handling resource, and which were subsequently resolved during the first customer attempt. An issue is considered to be resolved on the first attempt if there are no subsequent customer interactions from the same CUSTOMER_ID for the same SERVICE-TYPE within 7 days. |
| ACCEPTED_CUSTID | The number of customer interactions with the indicated Customer ID that were accepted, answered, or pulled. |
| DATE_TIME_KEY | The surrogate key that is used to join this aggregate table to the DATE_TIME dimension table to identify the calendar date and 15-minute interval corresponding to the start of the aggregated interval. |
| INTERACTION_DESCRIPTOR_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_DESCRIPTOR dimension table to identify the business attributes assigned to the interaction. |
| TENANT_KEY | The surrogate key that is used to join this aggregate table to the TENANT view to identify a specific tenant. |
| MEDIA_TYPE_KEY | The surrogate key that is used to join this aggregate table to the MEDIA_TYPE dimension table. |
| INTERACTION_TYPE_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_TYPE dimension table. |
| USER_DATA_KEY1 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction.
If you engage the social-media feature, RAA maps this field to GEN_ES_KEY in the IRF_USER_DATA_KEYS table. |
| USER_DATA_KEY2 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction. |
| POST_CALL_SURVEY_KEY1 | The surrogate key that is used to join this aggregate table to the POST_CALL_SURVEY dimension table. |
| POST_CALL_SURVEY_KEY2 | The surrogate key that is used to join this aggregate table to the POST_CALL_SURVEY dimension table. |
| ENTERED | The total number of customer interactions that entered or began within the contact center and were assigned this business attribute. This count includes abandoned interactions. |
| ENTERED_THREAD | The total number of unique threads of customer interactions of this business attribute that entered or began within the contact center. This measure is attributed to the first interval of the thread. |
| ENTERED_OBJ_RES | The total number of customer interactions that entered or began within the contact center, were assigned this business attribute, and either had a baseline service objective or a response threshold that was greater than zero.
This measure relies on the value of the response threshold as configured in the [agg-gim-thld-ID-IXN] section. |
| ABANDONED | The total number of customer interactions of this business attribute that were abandoned or stopped for any reason while the interactions were waiting for the first handling resource. The count includes customer interactions that were abandoned while they were ringing at the agent’s desktop or alerting at the handling resource as well as short-abandoned interactions. |
| DEFERRED | The total number of customer interactions of this business attribute that were deferred while the interactions were waiting for the first handling resource. |
| ABANDONED_INVITE | The total number of customer interactions of this business attribute that were abandoned or dropped for any reason while they were alerting or ringing at the first handling resource. This count includes short-abandoned interactions. |
| SHORT_ABANDONED | The total number of customer interactions of this business attribute that were abandoned or dropped for any reason within the threshold while they were waiting for the first handling resource.
This measure relies on the value of the short-abandoned threshold as configured in the [agg-gim-thld-ID-IXN] section. |
| ACCEPTED_THREAD | The total number of customer-interaction threads that were accepted, initiated, or pulled by handling resources. This measure includes a handling resource’s first participation in outbound replies to inbound interactions. |
| ACCEPTED | The total number of customer interactions of this business attribute that were accepted, answered, or pulled by a handling resource. |
| ACCEPT_TIME | The total amount of time, in seconds, that customer interactions of this business attribute were queued and/or alerting or ringing before the interactions were accepted, answered, or pulled by the first-handling resource. Duration starts when the interaction enters or begins within the contact center and ends when the interaction is accepted, answered, or pulled by the handling resource. This measure includes alert (ring) time. |
| ACCEPTED_THR | The total number of times that customer interactions or established warm consultations of this business attribute that were accepted, answered, or pulled by a handling resource within the acceptance threshold.
This measure relies on the value of the acceptance threshold as configured in the [agg-gim-thld-ID-IXN] section. |
| RESPONSES | For voice and chat media, the total number of customer interactions of this business attribute that were accepted, answered, or pulled by handling resources.
For e-mail, this measure represents the total number times that resources (e.g., agents) created outbound replies that might or might not have been sent. One handling resource can create multiple replies; this measure’s value reflects each reply. The value of this measure is greater than or equal to RESPONDED. |
| RESPONDED | For voice and chat media, the total number of customer interactions of this business attribute that had been answered by a handling resource.
For e mail, this measure represents the total number interactions that had a response that had been sent to a customer. One handling resource can send multiple replies; however, this measure’s value is either 0 or 1 for each interaction. The value of this measure is less than or equal to RESPONSES. |
| RESPONDED_THR | The total number of customer interactions of this business attribute for which a response was created within the service time threshold configured by service-related key-value pairs in the attached user-data mapping.
For online media, a response is considered to have been created when the interaction was accepted. For offline media, the first reply to a given interaction must be sent out in order to increment this measure. This measure excludes interactions that were routed to and accepted, answered, or pulled by unmonitored resources. This measure relies on the value of the response threshold as configured in the [agg-gim-thld-ID-IXN] section. |
| FIRST_RESPONSE_TIME | The total amount of time, in seconds, including mediation duration that elapsed before a first response to a customer interaction, that was assigned this business attribute was created.
For online media, a response is considered to have been created when the interaction was accepted by a handling resource. For offline media, the first reply to a given interaction must be sent in order to increment this measure. The business-attribute assignment can occur at any moment during the interaction’s lifetime for this measure to be tallied. |
| ACCEPTED_AGENT | The total number of customer interactions of this business attribute that were accepted, answered, or pulled by an agent. |
| ACCEPTED_AGENT_TIME | The total amount of time, in seconds, that customer interactions of this business attribute were queued and/or alerting or ringing at agent resources before the interactions were accepted, answered, or pulled by the first-handling agent. Duration starts when an interaction enters or begins within the contact center and ends when the interaction is accepted, answered, or pulled by an agent—thereby, including alert time or ring time. |
| ACCEPT_TIME_AGENT_MAX | The longest amount of time, in seconds, that customer interactions of this business attribute spent in a queue before the interactions were accepted by the first handling resource. The duration starts when the interaction enters or begins within the contact center and ends when the interaction is accepted, answered, or pulled. This measure includes alert (ring) time. |
| ABANDONED_TIME | The total amount of time, in seconds, associated with customer interactions of this business attribute that were abandoned or dropped for any reason. This time includes the duration of customer interactions that were abandoned within the short-abandoned threshold. |
| ABANDONED_STANDARD_TIME | The total amount of time, in seconds, that is associated with interactions of this business attribute that were abandoned by the customer or dropped for any reason before the interactions could be established. This time excludes the duration of customer interactions that were abandoned within the short-abandoned threshold.
This measure relies on the value of the short-abandoned threshold as configured in the [agg-gim-thld-ID-IXN] section. |
| ABANDONED_TIME_MAX | The maximum amount of time, in seconds, that customer interactions that entered or began within the contact center and were assigned this business attribute spent in a queue and/or alerting/ringing at the first target before the interactions were abandoned or stopped for any reason. |
| ENGAGE_TIME | The total amount of time, in seconds, that agents were engaged with customers for interactions that were assigned this business attribute. This measure excludes engagement time that is associated with collaborations, simple consultations, and other interaction-related durations, such as hold time, ACW time, and alert (ring) time. |
| ENGAGE | The total number of interactions for which agents were engaged with customers for interactions that the agents received and that were assigned this business attribute. This measure excludes other interaction-related counts, such as holds, instances of ACW, and collaborations and consultations that the agents received. |
| HOLD_TIME | The total amount of time, in seconds, that agents had customers on hold for interactions assigned this business attribute. |
| HOLD | The total number of customer interactions of this business attribute that agents had on hold. |
| WRAP_TIME | The total amount of time, in seconds, that resources spent in ACW state for customer interactions that were received of this business attribute. |
| WRAP | The total number of times that agents entered ACW state for customer interactions that the agents received of this business attribute. |
| INVITE | The total number of customer interactions of this business attribute that alerted or rang at agents before the interactions were accepted, answered, or pulled plus the total number of dials that agents performed, where the interactions were successfully established. This measure is attributed to the interval in which the alerting/dialing first occurred.
The dialing component of this measure applies only to voice media. |
| INVITE_TIME | The total amount of time, in seconds, that customer interactions of this business attribute alerted at agents plus the total duration of dialing performed by agents.
For the alerting component of this measure, interactions do not have to be established for this measure to be incremented. For the dialing component, dial duration is measured for established interactions only and is applicable only to voice media. This measure is attributed to the interval in which the alerting/dialing first occurred. |
| CONSULT_RECEIVED_ACCEPTED | The total number of interactions of this business attribute that included requests for collaboration or consultation where the collaborations/consultations were associated with customer interactions.
For voice, this measure is the same as CONSULT_RESPONSES. |
| CONSULT_RESPONSES | For e-mail, the total number of collaboration replies that were initiated within the contact center. For voice, this measure is the same as CONSULT_RECEIVED_ACCEPTED. |
| CONSULT_RECEIVED_INVITE | The total number of simple consult interactions of this business attribute that alerted or rang at agent resources before the agents accepted, answered, or pulled the interactions. |
| CONSULT_RECEIVED_INVITE_TIME | The total amount of time, in seconds, that simple consult interactions of this attribute alerted or rang at agent resources. Consultations do not have to be established for this measure to be incremented. |
| CONSULT_RECEIVED_ENGAGE_TIME | The total amount of time, in seconds, that agents were engaged in collaborations or simple consultations where the collaborations/consultations were associated with customer interactions of this business attribute and the agents were the recipients of the collaboration/consultations requests. |
| CONSULT_RECEIVED_HOLD_TIME | The total amount time, in seconds, that agents had simple consultations on hold where the consultations were associated with customer interactions of this business attributes and the agents were the recipients of the consultation requests. |
| CONSULT_RECEIVED_HOLD | The total number of simple consultations that agents had on hold where the interactions were associated with customer interactions of this business attribute and the agents were the recipients of the consultation requests. |
| CONSULT_RECEIVED_WRAP_TIME | The total amount of time, in seconds, that agents spent in ACW state after consult calls that the agents accepted, where the consultations were associated with customer interactions that were assigned this business attribute. |
| CONSULT_RECEIVED_WRAP | The total number of simple consultations for which agents entered ACW state where the consultations were associated with customer interactions of this business attribute and the agents were the recipients of the consultation requests. |
| CONSULT_RCV_WARM_ENGAGE_TIME | The total amount of time, in seconds, that agents were engaged in consultations where the agents were the recipients of the consultation requests and the interactions were transferred to or conferenced with the agents. |
| CONSULT_RCV_WARM_INVITE | The total number of warm consult interactions of this business attribute that rang at agent resources before the agents answered the calls. |
| CONSULT_RCV_WARM_INVITE_TIME | The total amount of time, in seconds, that warm consult interactions of this business attribute that alerted or rang at agents. |
| CONSULT_RCV_ACC_WARM | The total number of interactions of this business attribute that included requests for collaboration or consultation where the collaborations/consultations were transferred to or conferenced with the agents who accepted them. |
| CONSULT_RCV_WARM_HOLD_TIME | The total amount time, in seconds, that agents had consultations on hold where the interactions were associated with customer interactions of this business attribute, the agents were the recipients of the consultation requests, and the interactions were transferred to or conferenced with the agents. |
| CONSULT_RCV_WARM_HOLD | The total number of consultations that agents had on hold where the consultations were associated with customer interactions of this business attribute, the agents were the recipients of the consultation requests, and the interactions were transferred to or conferenced with the agents. |
| CONSULT_RCV_WARM_WRAP_TIME | The total amount of time, in seconds, that agents spent in ACW state following consultations that the agents requested and received, where the consultations were associated with customer interactions that were assigned this business attribute and the interactions were transferred to or conferenced with the agents.
This measure includes:
In common call-flow scenarios, this measure yields a value of zero. |
| CONSULT_RCV_WARM_WRAP | The total number of consultations that agents received for which agents entered ACW state where the consultations were associated with customer interactions of this attribute, and the interactions were transferred to or conferenced with the agents.
In common call-flow scenarios, this measure yields a value of zero. |
| CONFERENCE_INIT_AGENT | The total number of times that agents initiated conferences for customer interactions that the agents received where the interactions were established and were of this business attribute. |
| TRANSFER_INIT_AGENT | The total number of customer interactions of this business attribute that agents transferred. Both warm and blind transfers are reflected in this measure. |
| FINISHED_RESPONSE | The total number of completed customer interactions that were assigned this business attribute and for which non-acknowledgement responses were sent by the system. |
| FINISH_RESPONSE_TIME | The total duration, in seconds, of completed customer interactions that were assigned this business attribute and for which non-acknowledgement responses were sent by the system. The responses can be auto-responses that are generated by system handling resources or responses that are generated by agents. (For synchronous media, a response is counted upon acceptance of the interaction.) This duration includes the entire lifespan of the interaction: processing, queuing, and handling. |
| FINISHED | The total number of completed customer interactions that were assigned this business attribute. This measure is equivalent to ENTERED when there are no remaining active interactions during the interval. |
| FINISHED_THR | The total number of customer interactions of this business attribute that were completed within the finish threshold.
This measure relies on the value of the finish threshold as configured in the [agg-gim-thld-ID-IXN] section. |
| FINISH_TIME | The total amount of time, in seconds, that it took to complete customer interactions that were assigned this business attribute. Duration is measured as the end time of a completed interaction minus its start time. Active interactions do not contribute to this measure. |
| SATISFACTION_ENTERED | The total number of times that customer-satisfaction scores were recorded for customer interactions of this business attribute.
This measure might yield results that are greater than the total number of interactions that entered or began within the contact center if customer satisfaction scores were attributed more than once to the same interaction. |
| SATISFACTION | The sum of numerical scores of customer satisfaction that were attributed to customer interactions assigned this business attribute. |
| REVENUE_ENTERED | The total number of customer interactions that entered or began within the contact center, were assigned this business attribute, and had associated revenue.
Unlike SATISFACTTION_ENTERED, this measure never yields results that are greater than the total number of interactions that entered or began within the contact center. If more than one agent handled the same interaction, revenue is attributed to the first-handling agent only. |
| REVENUE | The total revenue generated during the interval by customer interactions assigned this business attribute. |
| ACTIONABILITY_ENTERED | The total number of times that actionability scores were recorded for customer interactions of this business attribute. |
| ACTIONABILITY | The sum of actionability scores attached to customer interactions that were handled by this agent. |
| SENTIMENT_ENTERED | The total number of times that sentiment scores were recorded for customer interactions of this business attribute. |
| SENTIMENT | The sum of sentiment scores attached to customer interactions that were handled by this agent. |
| INFLUENCE_ENTERED | The total number of times that influence scores were recorded for customer interactions of this business attribute. |
| INFLUENCE | The sum of influence scores attached to customer interactions that were handled by this agent. |
| GPM_RESULT_KEY | The surrogate key that is used to join the GPM_RESULT dimension to the fact table, to identify the result of the Predictive Routing attempt. |
| GPM_PREDICTOR_KEY | The name of the predictor in the Journey Optimization Platform (JOP). If an error is encountered, the section name in the PredictorsCfg Transaction List object is used as the predictor name. |
| GPM_MODEL_KEY | The surrogate key that is used to join the GPM_MODEL dimension to the fact table, to identify the model used to calculate agent scores for the interaction. |
| GPM_AGENT_SCORE | The score of the agent to whom the interaction was routed. |
| GPM_ACTIVE | The total number of interactions in which Genesys Predictive Routing (GPR) was active. Calculated as the total number of times that GPM_RESULT.GPM_USE contains a result other than 'null'. |
| GPM_ERROR | The total number of interactions that were processed by Genesys Predictive Routing (GPR) that resulted in an error. Calculated as the total number of times that GPM_RESULT.GPM_USE contains an 'unknown' result. |
| GPM_WAIT_TIME | The amount of time, in seconds, that the interaction spent in the queue used for Predictive Routing decision-making. |
| DATE_TIME_KEY | The surrogate key that is used to join this aggregate table to the DATE_TIME dimension table to identify the calendar date and 15-minute interval corresponding to the start of the aggregated interval. |
| INTERACTION_DESCRIPTOR_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_DESCRIPTOR dimension table to identify the business attributes assigned to the interaction. |
| TENANT_KEY | The surrogate key that is used to join this aggregate table to the TENANT view to identify a specific tenant. |
| MEDIA_TYPE_KEY | The surrogate key that is used to join this aggregate table to the MEDIA_TYPE dimension table. |
| INTERACTION_TYPE_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_TYPE dimension table. |
| USER_DATA_KEY1 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction.
If you engage the social-media feature, RAA maps this field to GEN_ES_KEY in the IRF_USER_DATA_KEYS table. |
| USER_DATA_KEY2 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction. |
| POST_CALL_SURVEY_KEY1 | The surrogate key that is used to join this aggregate table to the POST_CALL_SURVEY dimension table. |
| POST_CALL_SURVEY_KEY2 | The surrogate key that is used to join this aggregate table to the POST_CALL_SURVEY dimension table. |
| ENTERED | The total number of customer interactions that entered or began within the contact center and were assigned this business attribute. This count includes abandoned interactions. |
| ENTERED_THREAD | The total number of unique threads of customer interactions of this business attribute that entered or began within the contact center. This measure is attributed to the first interval of the thread. |
| ENTERED_OBJ_RES | The total number of customer interactions that entered or began within the contact center, were assigned this business attribute, and either had a baseline service objective or a response threshold that was greater than zero.
This measure relies on the value of the response threshold as configured in the [agg-gim-thld-ID-IXN] section. |
| ABANDONED | The total number of customer interactions of this business attribute that were abandoned or stopped for any reason while the interactions were waiting for the first handling resource. The count includes customer interactions that were abandoned while they were ringing at the agent’s desktop or alerting at the handling resource as well as short-abandoned interactions. |
| DEFERRED | The total number of customer interactions of this business attribute that were deferred while the interactions were waiting for the first handling resource. |
| ABANDONED_INVITE | The total number of customer interactions of this business attribute that were abandoned or dropped for any reason while they were alerting or ringing at the first handling resource. This count includes short-abandoned interactions. |
| SHORT_ABANDONED | The total number of customer interactions of this business attribute that were abandoned or dropped for any reason within the threshold while they were waiting for the first handling resource.
This measure relies on the value of the short-abandoned threshold as configured in the [agg-gim-thld-ID-IXN] section. |
| ACCEPTED_THREAD | The total number of customer-interaction threads that were accepted, initiated, or pulled by handling resources. This measure includes a handling resource’s first participation in outbound replies to inbound interactions. |
| ACCEPTED | The total number of customer interactions of this business attribute that were accepted, answered, or pulled by a handling resource. |
| ACCEPT_TIME | The total amount of time, in seconds, that customer interactions of this business attribute were queued and/or alerting or ringing before the interactions were accepted, answered, or pulled by the first-handling resource. Duration starts when the interaction enters or begins within the contact center and ends when the interaction is accepted, answered, or pulled by the handling resource. This measure includes alert (ring) time. |
| ACCEPTED_THR | The total number of times that customer interactions or established warm consultations of this business attribute that were accepted, answered, or pulled by a handling resource within the acceptance threshold.
This measure relies on the value of the acceptance threshold as configured in the [agg-gim-thld-ID-IXN] section. |
| RESPONSES | For voice and chat media, the total number of customer interactions of this business attribute that were accepted, answered, or pulled by handling resources.
For e-mail, this measure represents the total number times that resources (e.g., agents) created outbound replies that might or might not have been sent. One handling resource can create multiple replies; this measure’s value reflects each reply. The value of this measure is greater than or equal to RESPONDED. |
| RESPONDED | For voice and chat media, the total number of customer interactions of this business attribute that had been answered by a handling resource.
For e mail, this measure represents the total number interactions that had a response that had been sent to a customer. One handling resource can send multiple replies; however, this measure’s value is either 0 or 1 for each interaction. The value of this measure is less than or equal to RESPONSES. |
| RESPONDED_THR | The total number of customer interactions of this business attribute for which a response was created within the service time threshold configured by service-related key-value pairs in the attached user-data mapping.
For online media, a response is considered to have been created when the interaction was accepted. For offline media, the first reply to a given interaction must be sent out in order to increment this measure. This measure excludes interactions that were routed to and accepted, answered, or pulled by unmonitored resources. This measure relies on the value of the response threshold as configured in the [agg-gim-thld-ID-IXN] section. |
| FIRST_RESPONSE_TIME | The total amount of time, in seconds, including mediation duration that elapsed before a first response to a customer interaction, that was assigned this business attribute was created.
For online media, a response is considered to have been created when the interaction was accepted by a handling resource. For offline media, the first reply to a given interaction must be sent in order to increment this measure. The business-attribute assignment can occur at any moment during the interaction’s lifetime for this measure to be tallied. |
| ACCEPTED_AGENT | The total number of customer interactions of this business attribute that were accepted, answered, or pulled by an agent. |
| ACCEPTED_AGENT_TIME | The total amount of time, in seconds, that customer interactions of this business attribute were queued and/or alerting or ringing at agent resources before the interactions were accepted, answered, or pulled by the first-handling agent. Duration starts when an interaction enters or begins within the contact center and ends when the interaction is accepted, answered, or pulled by an agent—thereby, including alert time or ring time. |
| ACCEPT_TIME_AGENT_MAX | The longest amount of time, in seconds, that customer interactions of this business attribute spent in a queue before the interactions were accepted by the first handling resource. The duration starts when the interaction enters or begins within the contact center and ends when the interaction is accepted, answered, or pulled. This measure includes alert (ring) time. |
| ABANDONED_TIME | The total amount of time, in seconds, associated with customer interactions of this business attribute that were abandoned or dropped for any reason. This time includes the duration of customer interactions that were abandoned within the short-abandoned threshold. |
| ABANDONED_STANDARD_TIME | The total amount of time, in seconds, that is associated with interactions of this business attribute that were abandoned by the customer or dropped for any reason before the interactions could be established. This time excludes the duration of customer interactions that were abandoned within the short-abandoned threshold.
This measure relies on the value of the short-abandoned threshold as configured in the [agg-gim-thld-ID-IXN] section. |
| ABANDONED_TIME_MAX | The maximum amount of time, in seconds, that customer interactions that entered or began within the contact center and were assigned this business attribute spent in a queue and/or alerting/ringing at the first target before the interactions were abandoned or stopped for any reason. |
| ENGAGE_TIME | The total amount of time, in seconds, that agents were engaged with customers for interactions that were assigned this business attribute. This measure excludes engagement time that is associated with collaborations, simple consultations, and other interaction-related durations, such as hold time, ACW time, and alert (ring) time. |
| ENGAGE | The total number of interactions for which agents were engaged with customers for interactions that the agents received and that were assigned this business attribute. This measure excludes other interaction-related counts, such as holds, instances of ACW, and collaborations and consultations that the agents received. |
| HOLD_TIME | The total amount of time, in seconds, that agents had customers on hold for interactions assigned this business attribute. |
| HOLD | The total number of customer interactions of this business attribute that agents had on hold. |
| WRAP_TIME | The total amount of time, in seconds, that resources spent in ACW state for customer interactions that were received of this business attribute. |
| WRAP | The total number of times that agents entered ACW state for customer interactions that the agents received of this business attribute. |
| INVITE | The total number of customer interactions of this business attribute that alerted or rang at agents before the interactions were accepted, answered, or pulled plus the total number of dials that agents performed, where the interactions were successfully established. This measure is attributed to the interval in which the alerting/dialing first occurred.
The dialing component of this measure applies only to voice media. |
| INVITE_TIME | The total amount of time, in seconds, that customer interactions of this business attribute alerted at agents plus the total duration of dialing performed by agents.
For the alerting component of this measure, interactions do not have to be established for this measure to be incremented. For the dialing component, dial duration is measured for established interactions only and is applicable only to voice media. This measure is attributed to the interval in which the alerting/dialing first occurred. |
| CONSULT_RECEIVED_ACCEPTED | The total number of interactions of this business attribute that included requests for collaboration or consultation where the collaborations/consultations were associated with customer interactions.
For voice, this measure is the same as CONSULT_RESPONSES. |
| CONSULT_RESPONSES | For e-mail, the total number of collaboration replies that were initiated within the contact center. For voice, this measure is the same as CONSULT_RECEIVED_ACCEPTED. |
| CONSULT_RECEIVED_INVITE | The total number of simple consult interactions of this business attribute that alerted or rang at agent resources before the agents accepted, answered, or pulled the interactions. |
| CONSULT_RECEIVED_INVITE_TIME | The total amount of time, in seconds, that simple consult interactions of this attribute alerted or rang at agent resources. Consultations do not have to be established for this measure to be incremented. |
| CONSULT_RECEIVED_ENGAGE_TIME | The total amount of time, in seconds, that agents were engaged in collaborations or simple consultations where the collaborations/consultations were associated with customer interactions of this business attribute and the agents were the recipients of the collaboration/consultations requests. |
| CONSULT_RECEIVED_HOLD_TIME | The total amount time, in seconds, that agents had simple consultations on hold where the consultations were associated with customer interactions of this business attributes and the agents were the recipients of the consultation requests. |
| CONSULT_RECEIVED_HOLD | The total number of simple consultations that agents had on hold where the interactions were associated with customer interactions of this business attribute and the agents were the recipients of the consultation requests. |
| CONSULT_RECEIVED_WRAP_TIME | The total amount of time, in seconds, that agents spent in ACW state after consult calls that the agents accepted, where the consultations were associated with customer interactions that were assigned this business attribute. |
| CONSULT_RECEIVED_WRAP | The total number of simple consultations for which agents entered ACW state where the consultations were associated with customer interactions of this business attribute and the agents were the recipients of the consultation requests. |
| CONSULT_RCV_WARM_ENGAGE_TIME | The total amount of time, in seconds, that agents were engaged in consultations where the agents were the recipients of the consultation requests and the interactions were transferred to or conferenced with the agents. |
| CONSULT_RCV_WARM_INVITE | The total number of warm consult interactions of this business attribute that rang at agent resources before the agents answered the calls. |
| CONSULT_RCV_WARM_INVITE_TIME | The total amount of time, in seconds, that warm consult interactions of this business attribute that alerted or rang at agents. |
| CONSULT_RCV_ACC_WARM | The total number of interactions of this business attribute that included requests for collaboration or consultation where the collaborations/consultations were transferred to or conferenced with the agents who accepted them. |
| CONSULT_RCV_WARM_HOLD_TIME | The total amount time, in seconds, that agents had consultations on hold where the interactions were associated with customer interactions of this business attribute, the agents were the recipients of the consultation requests, and the interactions were transferred to or conferenced with the agents. |
| CONSULT_RCV_WARM_HOLD | The total number of consultations that agents had on hold where the consultations were associated with customer interactions of this business attribute, the agents were the recipients of the consultation requests, and the interactions were transferred to or conferenced with the agents. |
| CONSULT_RCV_WARM_WRAP_TIME | The total amount of time, in seconds, that agents spent in ACW state following consultations that the agents requested and received, where the consultations were associated with customer interactions that were assigned this business attribute and the interactions were transferred to or conferenced with the agents.
This measure includes:
In common call-flow scenarios, this measure yields a value of zero. |
| CONSULT_RCV_WARM_WRAP | The total number of consultations that agents received for which agents entered ACW state where the consultations were associated with customer interactions of this attribute, and the interactions were transferred to or conferenced with the agents.
In common call-flow scenarios, this measure yields a value of zero. |
| CONFERENCE_INIT_AGENT | The total number of times that agents initiated conferences for customer interactions that the agents received where the interactions were established and were of this business attribute. |
| TRANSFER_INIT_AGENT | The total number of customer interactions of this business attribute that agents transferred. Both warm and blind transfers are reflected in this measure. |
| FINISHED_RESPONSE | The total number of completed customer interactions that were assigned this business attribute and for which non-acknowledgement responses were sent by the system. |
| FINISH_RESPONSE_TIME | The total duration, in seconds, of completed customer interactions that were assigned this business attribute and for which non-acknowledgement responses were sent by the system. The responses can be auto-responses that are generated by system handling resources or responses that are generated by agents. (For synchronous media, a response is counted upon acceptance of the interaction.) This duration includes the entire lifespan of the interaction: processing, queuing, and handling. |
| FINISHED | The total number of completed customer interactions that were assigned this business attribute. This measure is equivalent to ENTERED when there are no remaining active interactions during the interval. |
| FINISHED_THR | The total number of customer interactions of this business attribute that were completed within the finish threshold.
This measure relies on the value of the finish threshold as configured in the [agg-gim-thld-ID-IXN] section. |
| FINISH_TIME | The total amount of time, in seconds, that it took to complete customer interactions that were assigned this business attribute. Duration is measured as the end time of a completed interaction minus its start time. Active interactions do not contribute to this measure. |
| SATISFACTION_ENTERED | The total number of times that customer-satisfaction scores were recorded for customer interactions of this business attribute.
This measure might yield results that are greater than the total number of interactions that entered or began within the contact center if customer satisfaction scores were attributed more than once to the same interaction. |
| SATISFACTION | The sum of numerical scores of customer satisfaction that were attributed to customer interactions assigned this business attribute. |
| REVENUE_ENTERED | The total number of customer interactions that entered or began within the contact center, were assigned this business attribute, and had associated revenue.
Unlike SATISFACTTION_ENTERED, this measure never yields results that are greater than the total number of interactions that entered or began within the contact center. If more than one agent handled the same interaction, revenue is attributed to the first-handling agent only. |
| REVENUE | The total revenue generated during the interval by customer interactions assigned this business attribute. |
| ACTIONABILITY_ENTERED | The total number of times that actionability scores were recorded for customer interactions of this business attribute. |
| ACTIONABILITY | The sum of actionability scores attached to customer interactions that were handled by this agent. |
| SENTIMENT_ENTERED | The total number of times that sentiment scores were recorded for customer interactions of this business attribute. |
| SENTIMENT | The sum of sentiment scores attached to customer interactions that were handled by this agent. |
| INFLUENCE_ENTERED | The total number of times that influence scores were recorded for customer interactions of this business attribute. |
| INFLUENCE | The sum of influence scores attached to customer interactions that were handled by this agent. |
| DATE_TIME_KEY | The surrogate key that is used to join this aggregate table to the DATE_TIME dimension table to identify the calendar date and 15-minute interval that correspond to the start of the aggregated interval. |
| GROUP_COMBINATION_KEY | The surrogate key that is used to join records in this aggregate table to the RESOURCE_GROUP_ COMBINATION dimension table to identify a specific combination of queue groups of which the queue was a member when the interaction entered the queue |
| RESOURCE_KEY | The surrogate key that is used to join this aggregate table to the RESOURCE_ dimension table. |
| INTERACTION_DESCRIPTOR_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_DESCRIPTOR dimension table to identify the business attributes that have been assigned to the interaction. |
| TENANT_KEY | The surrogate key that is used to join this aggregate table to the TENANT view to identify a specific tenant. |
| WORKBIN_KEY | In MEDIATION_SEGMENT_FACT (MSF) records that are created as a result of workbin time that is considered to be mediation, this field is the surrogate key that is used to join this table to the WORKBIN dimension, to identify the type of resource that is associated with the workbin and the specific resource that is associated with the mediation. For MSF records that are not associated with workbin mediation, this field is populated with the specified default value (-2).
For a summary of the conditions under which workbin time is considered to be mediation, see the description of the populate-workbin-as-hold configuration option in the Genesys Info Mart Configuration Options Reference. |
| TIME_RANGE_KEY | The surrogate key that is used to join this aggregate table to the TIME_RANGE dimension table. |
| MEDIA_TYPE_KEY | The surrogate key that is used to join this aggregate table to the MEDIA_TYPE dimension table. |
| INTERACTION_TYPE_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_TYPE dimension table. |
| USER_DATA_KEY1 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction. |
| USER_DATA_KEY2 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction. |
| ABANDONED | The total number of times that interactions entered this queue and were abandoned or dropped for any reason before the interactions could be established. The count includes short-abandoned interactions and excludes interactions that were abandoned following distribution, such as abandoned-while-inviting interactions. |
| ABANDONED_STI_1 | The total number of times that interactions entered this queue and were subsequently abandoned prior to the first abandon threshold. If the first abandon threshold is not configured, this measure uses no limit as the upper boundary of the abandon interval. |
| ABANDONED_STI_2 through ABANDONED_STI_19 | The total number of times that interactions entered this queue and were subsequently abandoned within the time interval that is bound by the nth and (n+1)th abandon thresholds. If the (n+1)th abandon threshold is not configured, this measure uses no limit as the upper boundary of the abandon interval. If the nth abandon threshold is not configured, this measure returns 0.
Abandon thresholds are defined within the [agg-gim-thld-QUEUE-ABN] section. |
| ABANDONED_STI_20 | The total number of times that interactions entered this queue and were subsequently abandoned beyond the nineteenth abandon threshold. If the nineteenth abandon threshold is not configured, this measure returns 0. |
| DATE_TIME_KEY | The surrogate key that is used to join this aggregate table to the DATE_TIME dimension table to identify the calendar date and 15-minute interval that correspond to the start of the aggregated interval. |
| GROUP_COMBINATION_KEY | The surrogate key that is used to join records in this aggregate table to the RESOURCE_GROUP_ COMBINATION dimension table to identify a specific combination of queue groups of which the queue was a member when the interaction entered the queue |
| RESOURCE_KEY | The surrogate key that is used to join this aggregate table to the RESOURCE_ dimension table. |
| INTERACTION_DESCRIPTOR_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_DESCRIPTOR dimension table to identify the business attributes that have been assigned to the interaction. |
| TENANT_KEY | The surrogate key that is used to join this aggregate table to the TENANT view to identify a specific tenant. |
| WORKBIN_KEY | In MEDIATION_SEGMENT_FACT (MSF) records that are created as a result of workbin time that is considered to be mediation, this field is the surrogate key that is used to join this table to the WORKBIN dimension, to identify the type of resource that is associated with the workbin and the specific resource that is associated with the mediation. For MSF records that are not associated with workbin mediation, this field is populated with the specified default value (-2).
For a summary of the conditions under which workbin time is considered to be mediation, see the description of the populate-workbin-as-hold configuration option in the Genesys Info Mart Configuration Options Reference. |
| TIME_RANGE_KEY | The surrogate key that is used to join this aggregate table to the TIME_RANGE dimension table. |
| MEDIA_TYPE_KEY | The surrogate key that is used to join this aggregate table to the MEDIA_TYPE dimension table. |
| INTERACTION_TYPE_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_TYPE dimension table. |
| USER_DATA_KEY1 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction. |
| USER_DATA_KEY2 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction. |
| ABANDONED | The total number of times that interactions entered this queue and were abandoned or dropped for any reason before the interactions could be established. The count includes short-abandoned interactions and excludes interactions that were abandoned following distribution, such as abandoned-while-inviting interactions. |
| ABANDONED_STI_1 | The total number of times that interactions entered this queue and were subsequently abandoned prior to the first abandon threshold. If the first abandon threshold is not configured, this measure uses no limit as the upper boundary of the abandon interval. |
| ABANDONED_STI_2 through ABANDONED_STI_19 | The total number of times that interactions entered this queue and were subsequently abandoned within the time interval that is bound by the nth and (n+1)th abandon thresholds. If the (n+1)th abandon threshold is not configured, this measure uses no limit as the upper boundary of the abandon interval. If the nth abandon threshold is not configured, this measure returns 0.
Abandon thresholds are defined within the [agg-gim-thld-QUEUE-ABN] section. |
| ABANDONED_STI_20 | The total number of times that interactions entered this queue and were subsequently abandoned beyond the nineteenth abandon threshold. If the nineteenth abandon threshold is not configured, this measure returns 0. |
| DATE_TIME_KEY | The surrogate key that is used to join this aggregate table to the DATE_TIME dimension table to identify the calendar date and 15-minute interval that correspond to the start of the aggregated interval. |
| GROUP_COMBINATION_KEY | The surrogate key that is used to join records in this aggregate table to the RESOURCE_GROUP_ COMBINATION dimension table to identify a specific combination of queue groups of which the queue was a member when the interaction entered the queue. |
| RESOURCE_KEY | The surrogate key that is used to join this aggregate table to the RESOURCE_ dimension table. |
| INTERACTION_DESCRIPTOR_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_DESCRIPTOR dimension table to identify the business attributes that have been assigned to the interaction. |
| TENANT_KEY | The surrogate key that is used to join this aggregate table to the TENANT view to identify a specific tenant. |
| WORKBIN_KEY | In MEDIATION_SEGMENT_FACT (MSF) records that are created as a result of workbin time that is considered to be mediation, this field is the surrogate key that is used to join this table to the WORKBIN dimension, to identify the type of resource that is associated with the workbin and the specific resource that is associated with the mediation. For MSF records that are not associated with workbin mediation, this field is populated with the specified default value (-2).
For a summary of the conditions under which workbin time is considered to be mediation, see the description of the populate-workbin-as-hold configuration option in the Genesys Info Mart Configuration Options Reference. |
| TIME_RANGE_KEY | The surrogate key that is used to join this aggregate table to the TIME_RANGE dimension table. |
| MEDIA_TYPE_KEY | The surrogate key that is used to join this aggregate table to the MEDIA_TYPE dimension table. |
| INTERACTION_TYPE_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_TYPE dimension table. |
| USER_DATA_KEY1 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction. |
| USER_DATA_KEY2 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction. |
| ACCEPTED_AGENT | The total number of times that customer interactions or warm consultations distributed from this queue were accepted, answered, or pulled by an agent. |
| ACCEPTED_AGENT_STI_1 | The total number of times that interactions entered this queue and were subsequently distributed and accepted, answered, or pulled by an agent prior to the first service time service time interval threshold. If the first service time threshold is not defined, this measure uses no limit as the upper boundary of the service time interval. |
| ACCEPTED_AGENT_STI_2 through ACCEPTED_AGENT_STI_19 | The total number of times that interactions entered this queue and were subsequently distributed and accepted, answered, or pulled by an agent within the service time interval that is bound by the nth and (n+1)th service time thresholds. If the (n+1)th service time threshold is not defined, this measure uses no limit as the upper boundary of the service time interval. If the nth service time threshold is not defined, this measure returns 0.
Speed-of-accept thresholds are defined within the [agg-gim-thld-QUEUE-ACC] section. |
| ACCEPTED_AGENT_STI_20 | The total number of times that interactions entered this queue and were subsequently distributed and accepted, answered, or pulled by an agent beyond the nineteenth service time interval. If the nineteenth service time threshold is not defined, this measure returns 0. |
| DATE_TIME_KEY | The surrogate key that is used to join this aggregate table to the DATE_TIME dimension table to identify the calendar date and 15-minute interval that correspond to the start of the aggregated interval. |
| GROUP_COMBINATION_KEY | The surrogate key that is used to join records in this aggregate table to the RESOURCE_GROUP_ COMBINATION dimension table to identify a specific combination of queue groups of which the queue was a member when the interaction entered the queue. |
| RESOURCE_KEY | The surrogate key that is used to join this aggregate table to the RESOURCE_ dimension table. |
| INTERACTION_DESCRIPTOR_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_DESCRIPTOR dimension table to identify the business attributes that have been assigned to the interaction. |
| TENANT_KEY | The surrogate key that is used to join this aggregate table to the TENANT view to identify a specific tenant. |
| WORKBIN_KEY | In MEDIATION_SEGMENT_FACT (MSF) records that are created as a result of workbin time that is considered to be mediation, this field is the surrogate key that is used to join this table to the WORKBIN dimension, to identify the type of resource that is associated with the workbin and the specific resource that is associated with the mediation. For MSF records that are not associated with workbin mediation, this field is populated with the specified default value (-2).
For a summary of the conditions under which workbin time is considered to be mediation, see the description of the populate-workbin-as-hold configuration option in the Genesys Info Mart Configuration Options Reference. |
| TIME_RANGE_KEY | The surrogate key that is used to join this aggregate table to the TIME_RANGE dimension table. |
| MEDIA_TYPE_KEY | The surrogate key that is used to join this aggregate table to the MEDIA_TYPE dimension table. |
| INTERACTION_TYPE_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_TYPE dimension table. |
| USER_DATA_KEY1 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction. |
| USER_DATA_KEY2 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction. |
| ACCEPTED_AGENT | The total number of times that customer interactions or warm consultations distributed from this queue were accepted, answered, or pulled by an agent. |
| ACCEPTED_AGENT_STI_1 | The total number of times that interactions entered this queue and were subsequently distributed and accepted, answered, or pulled by an agent prior to the first service time service time interval threshold. If the first service time threshold is not defined, this measure uses no limit as the upper boundary of the service time interval. |
| ACCEPTED_AGENT_STI_2 through ACCEPTED_AGENT_STI_19 | The total number of times that interactions entered this queue and were subsequently distributed and accepted, answered, or pulled by an agent within the service time interval that is bound by the nth and (n+1)th service time thresholds. If the (n+1)th service time threshold is not defined, this measure uses no limit as the upper boundary of the service time interval. If the nth service time threshold is not defined, this measure returns 0.
Speed-of-accept thresholds are defined within the [agg-gim-thld-QUEUE-ACC] section. |
| ACCEPTED_AGENT_STI_20 | The total number of times that interactions entered this queue and were subsequently distributed and accepted, answered, or pulled by an agent beyond the nineteenth service time interval. If the nineteenth service time threshold is not defined, this measure returns 0. |
| DATE_TIME_KEY | The surrogate key that is used to join this aggregate table to the DATE_TIME dimension table to identify the calendar date and 15-minute interval that correspond to the start of the aggregated interval. |
| GROUP_COMBINATION_KEY | The surrogate key that is used to join records in this aggregate table to the RESOURCE_GROUP_ COMBINATION dimension table to identify a specific combination of queue groups of which the queue was a member when the interaction entered the queue. |
| RESOURCE_KEY | The surrogate key that is used to join this aggregate table to the RESOURCE_ dimension table to identify a specific queue. |
| INTERACTION_DESCRIPTOR_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_DESCRIPTOR dimension table to identify the business attributes that have been assigned to the interaction. |
| TENANT_KEY | The surrogate key that is used to join this aggregate table to the TENANT view to identify a specific tenant. |
| WORKBIN_KEY | In MEDIATION_SEGMENT_FACT (MSF) records that are created as a result of workbin time that is considered to be mediation, this field is the surrogate key that is used to join this table to the WORKBIN dimension, to identify the type of resource that is associated with the workbin and the specific resource that is associated with the mediation.
For MSF records that are not associated with workbin mediation, this field is populated with the specified default value (-2). For a summary of the conditions under which workbin time is considered to be mediation, see the description of the populate-workbin-as-hold configuration option in the Genesys Info Mart Configuration Options Reference. |
| MEDIA_TYPE_KEY | The surrogate key that is used to join this aggregate table to the MEDIA_TYPE dimension table. |
| INTERACTION_TYPE_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_TYPE dimension table. |
| USER_DATA_KEY1 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction. |
| USER_DATA_KEY2 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction. |
| ENTERED | The total number of times that customer interactions or established warm consultations entered this queue. If the same interaction enters this queue more than once, this measure counts each entrance separately. |
| CLEARED | The total number of times that customer interactions were cleared from this virtual queue, workbin, or interaction queue.
Clearing involves any of the following:
Clearing excludes:
|
| CLEARED_TIME | The total duration, in seconds, that customer interactions spent in a queue before they were cleared from this virtual queue, workbin, or interaction queue. |
| CLEARED_TIME_MAX | The longest amount of time, in seconds, that customer interactions spent in a queue before they were cleared from this virtual queue, workbin, or interaction queue. |
| CLEARED_STUCK | The total number of times that customer interactions were cleared from this virtual queue, workbin, or interaction queue because they were identified as being stuck (having a technical result of StuckCall). |
| ABANDONED | The total number of times that customer interactions entered this queue and were abandoned or dropped for any reason before the interactions could be distributed. The count includes short-abandoned interactions and excludes interactions that were abandoned after distribution, such as abandoned-while-inviting interactions. |
| ABANDONED_TIME | The total amount of time, in seconds, that customer interactions waited in this queue before they were abandoned or dropped for any reason and before the interactions could be distributed. The duration starts the moment at which the interaction entered this queue and ends the moment at which the interaction was abandoned or stopped. The measurement includes short-abandoned interactions and excludes interactions that were abandoned after distribution. |
| ABANDONED_TIME_MAX | The longest amount of time, in seconds, that customers waited at this queue before abandoning the interactions and before the interactions could be distributed. |
| ABANDONED_SHORT | The total number of times that customer interactions entered this queue and were abandoned within the short-abandoned threshold. The count excludes interactions that were abandoned after distribution.
This measure relies on the value of the short-abandoned threshold as configured in the [agg-gim-thld-QUEUE-IXN] section. |
| ABANDONED_STANDARD | The total number of customer interactions that entered this queue and were abandoned or dropped for any reason beyond the short-abandoned threshold and before the interactions could be established. This measure excludes interactions that were abandoned while they were alerting at a handling resource.
This measure relies on the value of the short-abandoned threshold as configured in the [agg-gim-thld-QUEUE-IXN] section. |
| ABANDONED_STANDARD_TIME | The total amount of time, in seconds, that is associated with interactions that entered this queue and were abandoned or dropped for any reason before the interactions could be distributed. This time excludes the duration of customer interactions that were abandoned within the short-abandoned threshold as well as abandoned-while-alerting interactions.
This measure relies on the value of the short-abandoned threshold as configured in the [agg-gim-thld-QUEUE-IXN] section. |
| ABANDONED_INVITE | The total number of times that customer interactions that were distributed or pulled from this queue were abandoned or dropped for any reason while the interactions were alerting or ringing at an agent. |
| DISTRIBUTED_ | The total number of times that customer interactions or established warm consultations were distributed or pulled from this queue.
Distribution includes the interactions that were:
If the interaction passes through more than one queue before it was distributed, the count is increased only for that device from which the interaction was distributed or pulled. |
| DISTRIBUTED_TIME | The time, in seconds, from the moment at which customer interactions or warm consultations entered this queue to the moment at which they were distributed or pulled from this queue. |
| DISTRIBUTED_TIME_MAX | The longest amount of time, in seconds, that customer interactions or warm consultations spent in this queue before they were distributed. |
| REDIRECTED | he total number of times that customer interactions entered this queue, rang at a routing target, and were redirected upon no acceptance/answer by an agent. |
| ROUTED_OTHER | The total number of times that customer interactions entered this queue and were subsequently routed either to other mediation DNs or to unmonitored resources. |
| ACCEPTED | The total number of times that customer interactions and warm consultations that were distributed from this queue, were accepted, answered, or pulled by an agent, voice-treatment port, IVR port, or non-agent-associated DN (such as contact center resources that can alert). |
| ACCEPTED_THR | The total number of times that customer interactions or established warm consultations that were distributed from this queue were accepted, answered, or pulled by a handling resource within the acceptance threshold.
This measure relies on the value of the acceptance threshold as configured in the [agg-gim-thld-QUEUE-IXN] section. |
| ACCEPTED_AGENT | The total number of times that customer interactions or warm consultations that were distributed from this queue, were accepted, answered, or pulled by an agent. |
| ACCEPTED_AGENT_TIME | The total amount of time, in seconds, that customer interactions waited in this queue before they were accepted, answered, or pulled by agents. Duration starts when the interaction enters the queue and ends when the interaction is accepted, answered, or pulled by an agent—thereby, including alert (ring) time. |
| ACCEPTED_AGENT_THR | The total number of times that customer interactions or established warm consultations that were distributed from this queue were accepted, answered, or pulled by an agent within the acceptance threshold.
This measure relies on the value of the accepted-by-agent threshold as configured in the [agg-gim-thld-QUEUE-IXN] section. |
| TRANSFER_INIT_AGENT | The total number of times that agents transferred customer interactions that were distributed or pulled from this queue. Both warm and blind transfers are reflected in this measure. |
| INVITE | The total number of customer interactions (that were distributed from this queue) that alerted or rang at agent resources before the agents accepted, answered, or pulled the interactions plus the total number of dials that agents performed, where the calls were successfully established and were distributed from this queue. |
| INVITE_TIME | The total amount of time, in seconds, that customer interactions distributed from this queue alerted or rang at agents plus the total duration of the dialing that agents performed. For the alerting component of this measure, interactions do not have to be established for this measure to be incremented. For the dialing component, dial duration is measured for established calls only. |
| ENGAGE_TIME | For customer interactions that were distributed or pulled from this queue, the total amount of time, in seconds, that agents were engaged with customers. This measure excludes other interaction-related durations, such as hold time, ACW (Wrap) time, alert (ring) time and the time that is associated with consultations and collaborations that the agent received. |
| WRAP | The total number of times that agents entered or were in ACW state upon handling customer interactions that were distributed from this queue. |
| WRAP_TIME | The total amount of time, in seconds, that agents spent performing after-call work for customer interactions that were distributed from this queue. |
| HOLD | The total number of times that agents had customer interactions, distributed from this queue, on hold. This count attributes only one hold instance per distribution per agent, even if the same interaction was placed on hold more than once by the agent. |
| HOLD_TIME | The total amount of time, in seconds, that agents had customer interactions that were distributed from this queue on hold. This time starts when the interaction is placed on hold and ends when it is retrieved, dropped, transferred, or completed. |
| CONSULT_ENTERED | The total number of times that simple consultation requests entered this queue where the collaborations/consultations were associated with customer interactions. |
| CONSULT_CLEARED | The total number of times that simple consult interactions were cleared from this virtual queue, workbin, or interaction queue. |
| CONSULT_CLEARED_TIME | The total duration, in seconds, that simple consult interactions spent in a queue before they were cleared from this virtual queue, workbin, or interaction queue. |
| CONSULT_CLEARED_TIME_MAX | The longest amount of time, in seconds, that simple consult interactions spent in a queue before they were cleared from this virtual queue, workbin, or interaction queue. |
| CONSULT_CLEARED_STUCK | The total number of times that simple consult interactions were cleared from this virtual queue, workbin, or interaction queue because they were identified as being stuck (that is, having a technical result of StuckCall). |
| CONSULT_ABANDONED | The total number of times that simple consultations entered this queue and were abandoned before they could be established inside the short-abandoned threshold, where the consultations were associated with customer interactions.
This measure relies on the value of the short-abandoned threshold as configured in the [agg-gim-thld-QUEUE-IXN] section. |
| CONSULT_ABANDONED_TIME | The total amount of time, in seconds, that simple consult interactions waited in this queue before they were abandoned or dropped for any reason and before the interactions could be established. The duration starts the moment at which the consultation entered this queue and ends the moment at which the interaction was abandoned or stopped. The measurement includes short-abandoned interactions and excludes interactions that were abandoned after distribution. |
| CONSULT_ABANDONED_TIME_MAX | The longest amount of time, in seconds, that agents waited at this queue before they abandoned their simple consult interactions. Interactions that were abandoned after they were offered to a resource (that is, abandoned-while-alerting/abandoned-while-ringing interactions) are excluded from consideration. |
| CONSULT_ABANDONED_SHORT | The total number of times that requests for consultation entered this queue and were abandoned within the short-abandoned threshold where the consultations were associated with customer interactions. The count excludes collaborations and consultations that were abandoned after distribution.
This measure relies on the value of the short-abandoned threshold as configured in the [agg-gim-thld-QUEUE-IXN] section. |
| CONSULT_ABANDONED_STANDARD | The total number of simple consult interactions that entered this queue and were abandoned or dropped for any reason beyond the short-abandoned threshold and before the consultations could be established. This measure excludes consultations that were abandoned while they were alerting at a handling resource.
This measure relies on the value of the short-abandoned threshold as configured in the [agg-gim-thld-QUEUE-IXN] section. |
| CONSULT_ABN_STANDARD_TIME | The total amount of time, in seconds, that is associated with simple consult interactions that entered this queue and were abandoned by the agent or dropped for any reason before the consultations could be established. The duration starts when the consultation enters the queue and ends when the consultation is abandoned or dropped, but only after the short-abandoned threshold has elapsed. This measure also excludes the time that is associated with consultations that were abandoned while they were alerting at a handling resource.
This measure relies on the value of the short-abandoned threshold as configured in the [agg-gim-thld-QUEUE-IXN] section. |
| CONSULT_ABANDONED_INVITE | The total number of times that consult interactions that were distributed or pulled from this queue were abandoned or dropped for any reason while the interactions were alerting or ringing at an agent. |
| CONSULT_DISTRIBUTED | The total number of times that simple consult interactions were distributed or pulled from this queue. |
| CONSULT_DISTRIBUTED_TIME | The time, in seconds, from the moment at which simple consult interactions entered this queue to the moment at which they were distributed or pulled from this queue. |
| CONSULT_DISTRIBUTED_TIME_MAX | The longest amount of time, in seconds, that customer interactions spent in this queue before they were distributed. |
| CONSULT_REDIRECTED | The total number of times that collaborations or simple consult interactions entered this queue, rang at a routing target, and were redirected upon no acceptance/answer by an agent. |
| CONSULT_ROUTED_OTHER | The total number of times that consult interactions entered this queue and were subsequently routed either to other mediation DNs or to unmonitored resources. |
| CONSULT_ACCEPTED | The total number of times that simple consult interactions, that were distributed from this queue, were accepted, answered, or pulled by an agent, voice-treatment port, IVR port, or non-agent-associated DN (such as contact center resources that can alert). |
| CONSULT_ACCEPTED_TIME | The total amount of time, in seconds, that simple consult interactions waited in this queue before they were accepted, answered, or pulled by handling resources. The duration starts when consultations enter the queue and ends when the consultations are accepted by the target resource—thereby, including alert (ring) time. |
| CONSULT_ACCEPTED_TIME_MAX | The longest amount of time, in seconds, that simple consult interactions that were distributed from this queue spent in a queue before they were accepted, answered, or pulled by the target resource. Duration starts when the consultation enters the member queue and ends when the consultation is accepted, answered, or pulled—thereby, including alert (ring) time. |
| CONSULT_ACCEPTED_THR | The total number of times that simple consult interactions that were distributed from this queue were accepted, answered, or pulled by a handling resource within the acceptance threshold.
This measure relies on the value of the acceptance threshold as configured in the [agg-gim-thld-QUEUE-IXN] section. |
| CONSULT_ACCEPTED_AGENT_TIME | The total amount of time, in seconds, that consult interactions waited in this queue before they were accepted, answered, or pulled by agents. Duration starts when the interaction enters the queue and ends when the interaction is accepted, answered, or pulled by an agent—thereby, including alert (ring) time. |
| CONSULT_ACCEPTED_AGENT_THR | The total number of times that simple consult interactions that were distributed from this queue were accepted, answered, or pulled by an agent within the acceptance threshold.
This measure relies on the value of the acceptance threshold as configured in the [agg-gim-thld-QUEUE-IXN] section. |
| CONSULT_TRANSFER_INIT_AGENT | The total number of times that agents transferred simple consult interactions that were distributed or pulled from this queue. |
| CONSULT_RECEIVED_ACCEPTED | The total number of times that agents received collaborations or simple consultations that were distributed or pulled from this queue and associated with customer interactions. |
| CONSULT_RECEIVED_INVITE | The total number of simple consult interactions that were distributed from this queue that alerted or rang at agent resources before the agents accepted, answered, or pulled the interactions. |
| CONSULT_RECEIVED_INVITE_TIME | The total amount of time, in seconds, that simple consult interactions that were distributed from this queue alerted or rang at agents. Consultations do not have to be established for this measure to be incremented. |
| CONSULT_RECEIVED_ENGAGE_TIME | The total amount of time, in seconds, that agents were engaged in collaborations or simple consultations that were distributed or pulled from this queue where the collaborations/consultations were associated with customer interactions and the agents were the recipients of the collaboration/consultations requests. |
| CONSULT_RECEIVED_WRAP | The total number of simple consultations for which agents entered ACW state where the consultations were distributed or pulled from this queue and associated with customer interactions and the agents were the recipients of the consultation requests. |
| CONSULT_RECEIVED_WRAP_TIME | The total amount of time, in seconds, that agents were in ACW state after simple consultations that the agents accepted, where the consultations were distributed from this queue and were associated with customer interactions. |
| CONSULT_RECEIVED_HOLD | The total number of simple consultations that agents had on hold where the interactions were distributed or pulled from this queue and associated with customer interactions and the agents were the recipients of the consultation requests. |
| CONSULT_RECEIVED_HOLD_TIME | The total amount time, in seconds, that agents had simple consultations on hold where the consultations were distributed or pulled from this queue and associated with customer interactions and the agents were the recipients of the consultation requests. |
| CONSULT_RCV_ACC_WARM | The total number of times that agents participated in consultations that the agents received, where the consultations were distributed or pulled from this queue, associated with customer interactions, and transferred to or conferenced with the agents. |
| CONSULT_RCV_ACC_WARM_TIME | The total amount time, in seconds, that others spent waiting for an agent to respond to the requests for warm consultation that the agent received, where the warm consult interactions were distributed or pulled from this queue. |
| CONSULT_RCV_WARM_INVITE | The total number of warm consultations that were distributed from this queue that rang at agent resources before the agents answered the calls. |
| CONSULT_RCV_WARM_INVITE_TIME | The total amount of time, in seconds, that warm consult interactions distributed from this queue alerted or rang at agents. By definition, warm interactions must be established for this measure to be incremented. |
| CONSULT_RCV_WARM_ENGAGE_TIME | The total amount of time, in seconds, that agents were engaged in consultations that were distributed or pulled from this queue and associated with customer interactions, the agents were the recipients of the consultation requests, and the interactions were transferred to or conferenced with agents. |
| CONSULT_RCV_WARM_HOLD_TIME | The total amount time, in seconds, that agents had consultations on hold where the interactions were distributed or pulled from this queue and associated with customer interactions, the agents were the recipients of the consultation requests, and the interactions were transferred to or conferenced with the agents. |
| CONSULT_RCV_WARM_HOLD | The total number of consultations distributed from this queue that agents had on hold where the consultations were associated with customer interactions, the agents were the recipients of the consultation requests, and the interactions were transferred to or conferenced with the agents. |
| CONSULT_RCV_WARM_WRAP | The total number of consultations that agents received for which agents entered ACW state where the consultations were distributed from this queue and were associated with customer interactions, and the interactions were transferred to or conferenced with the agents.
This measure includes:
In common call-flow scenarios, this measure yields a value of zero. |
| CONSULT_RCV_WARM_WRAP_TIME | The total amount of time, in seconds, that agents spent in ACW state following consultations that the agents requested and received, where the consultations were distributed from this queue and were associated with customer interactions, and the interactions were transferred to or conferenced with the agents.
This measure includes:
In common call-flow scenarios, this measure yields a value of zero. |
| CONFERENCE_INIT_AGENT | The total number of times that agents initiated conferences for customer interactions that the agents received where the interactions were distributed or pulled from this queue and the conferences were established. The count includes the number of established conferences that were initiated for transferred interactions that agents received. |
| ACCEPTED_TIME | The total amount of time, in seconds, that customer interactions waited in this queue before they were accepted, answered, or pulled by handling resources. The duration starts when interactions enter the queue and ends when the interactions are accepted by the target resource—thereby, including alert (ring) time. |
| ACCEPTED_TIME_MAX | The longest amount of time, in seconds, that customer interactions that were distributed from this queue spent in a queue before they were accepted, answered, or pulled by the target resource. Duration starts when the interaction enters the member queue and ends when the interaction is accepted, answered, or pulled—thereby, including alert (ring) time. |
| GPM_RESULT_KEY | The surrogate key that is used to join the GPM_RESULT dimension to the fact table, to identify the result of the Predictive Routing attempt. |
| GPM_PREDICTOR_KEY | The name of the predictor in the Journey Optimization Platform (JOP). If an error is encountered, the section name in the PredictorsCfg Transaction List object is used as the predictor name. |
| GPM_MODEL_KEY | The surrogate key that is used to join the GPM_MODEL dimension to the fact table, to identify the model used to calculate agent scores for the interaction. |
| GPM_AGENT_SCORE | The score of the agent to whom the interaction was routed. |
| GPM_ACTIVE | The total number of interactions in which Genesys Predictive Routing (GPR) was active. Calculated as the total number of times that GPM_RESULT.GPM_USE contains a result other than 'null'. |
| GPM_ERROR | The total number of interactions that were processed by Genesys Predictive Routing (GPR) that resulted in an error. Calculated as the total number of times that GPM_RESULT.GPM_USE contains an 'unknown' result. |
| DATE_TIME_KEY | The surrogate key that is used to join this aggregate table to the DATE_TIME dimension table to identify the calendar date and 15-minute interval that correspond to the start of the aggregated interval. |
| GROUP_COMBINATION_KEY | The surrogate key that is used to join records in this aggregate table to the RESOURCE_GROUP_ COMBINATION dimension table to identify a specific combination of queue groups of which the queue was a member when the interaction entered the queue. |
| RESOURCE_KEY | The surrogate key that is used to join this aggregate table to the RESOURCE_ dimension table to identify a specific queue. |
| INTERACTION_DESCRIPTOR_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_DESCRIPTOR dimension table to identify the business attributes that have been assigned to the interaction. |
| TENANT_KEY | The surrogate key that is used to join this aggregate table to the TENANT view to identify a specific tenant. |
| WORKBIN_KEY | In MEDIATION_SEGMENT_FACT (MSF) records that are created as a result of workbin time that is considered to be mediation, this field is the surrogate key that is used to join this table to the WORKBIN dimension, to identify the type of resource that is associated with the workbin and the specific resource that is associated with the mediation.
For MSF records that are not associated with workbin mediation, this field is populated with the specified default value (-2). For a summary of the conditions under which workbin time is considered to be mediation, see the description of the populate-workbin-as-hold configuration option in the Genesys Info Mart Configuration Options Reference. |
| MEDIA_TYPE_KEY | The surrogate key that is used to join this aggregate table to the MEDIA_TYPE dimension table. |
| INTERACTION_TYPE_KEY | The surrogate key that is used to join this aggregate table to the INTERACTION_TYPE dimension table. |
| USER_DATA_KEY1 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction. |
| USER_DATA_KEY2 | The surrogate key that is used to join this aggregate table to a custom user data dimension table to identify attached data that has been assigned to the interaction. |
| ENTERED | The total number of times that customer interactions or established warm consultations entered this queue. If the same interaction enters this queue more than once, this measure counts each entrance separately. |
| CLEARED | The total number of times that customer interactions were cleared from this virtual queue, workbin, or interaction queue.
Clearing involves any of the following:
Clearing excludes:
|
| CLEARED_TIME | The total duration, in seconds, that customer interactions spent in a queue before they were cleared from this virtual queue, workbin, or interaction queue. |
| CLEARED_TIME_MAX | The longest amount of time, in seconds, that customer interactions spent in a queue before they were cleared from this virtual queue, workbin, or interaction queue. |
| CLEARED_STUCK | The total number of times that customer interactions were cleared from this virtual queue, workbin, or interaction queue because they were identified as being stuck (having a technical result of StuckCall). |
| ABANDONED | The total number of times that customer interactions entered this queue and were abandoned or dropped for any reason before the interactions could be distributed. The count includes short-abandoned interactions and excludes interactions that were abandoned after distribution, such as abandoned-while-inviting interactions. |
| ABANDONED_TIME | The total amount of time, in seconds, that customer interactions waited in this queue before they were abandoned or dropped for any reason and before the interactions could be distributed. The duration starts the moment at which the interaction entered this queue and ends the moment at which the interaction was abandoned or stopped. The measurement includes short-abandoned interactions and excludes interactions that were abandoned after distribution. |
| ABANDONED_TIME_MAX | The longest amount of time, in seconds, that customers waited at this queue before abandoning the interactions and before the interactions could be distributed. |
| ABANDONED_SHORT | The total number of times that customer interactions entered this queue and were abandoned within the short-abandoned threshold. The count excludes interactions that were abandoned after distribution.
This measure relies on the value of the short-abandoned threshold as configured in the [agg-gim-thld-QUEUE-IXN] section. |
| ABANDONED_STANDARD | The total number of customer interactions that entered this queue and were abandoned or dropped for any reason beyond the short-abandoned threshold and before the interactions could be established. This measure excludes interactions that were abandoned while they were alerting at a handling resource.
This measure relies on the value of the short-abandoned threshold as configured in the [agg-gim-thld-QUEUE-IXN] section. |
| ABANDONED_STANDARD_TIME | The total amount of time, in seconds, that is associated with interactions that entered this queue and were abandoned or dropped for any reason before the interactions could be distributed. This time excludes the duration of customer interactions that were abandoned within the short-abandoned threshold as well as abandoned-while-alerting interactions.
This measure relies on the value of the short-abandoned threshold as configured in the [agg-gim-thld-QUEUE-IXN] section. |
| ABANDONED_INVITE | The total number of times that customer interactions that were distributed or pulled from this queue were abandoned or dropped for any reason while the interactions were alerting or ringing at an agent. |
| DISTRIBUTED_ | The total number of times that customer interactions or established warm consultations were distributed or pulled from this queue.
Distribution includes the interactions that were:
If the interaction passes through more than one queue before it was distributed, the count is increased only for that device from which the interaction was distributed or pulled. |
| DISTRIBUTED_TIME | The time, in seconds, from the moment at which customer interactions or warm consultations entered this queue to the moment at which they were distributed or pulled from this queue. |
| DISTRIBUTED_TIME_MAX | The longest amount of time, in seconds, that customer interactions or warm consultations spent in this queue before they were distributed. |
| REDIRECTED | he total number of times that customer interactions entered this queue, rang at a routing target, and were redirected upon no acceptance/answer by an agent. |
| ROUTED_OTHER | The total number of times that customer interactions entered this queue and were subsequently routed either to other mediation DNs or to unmonitored resources. |
| ACCEPTED | The total number of times that customer interactions and warm consultations that were distributed from this queue, were accepted, answered, or pulled by an agent, voice-treatment port, IVR port, or non-agent-associated DN (such as contact center resources that can alert). |
| ACCEPTED_THR | The total number of times that customer interactions or established warm consultations that were distributed from this queue were accepted, answered, or pulled by a handling resource within the acceptance threshold.
This measure relies on the value of the acceptance threshold as configured in the [agg-gim-thld-QUEUE-IXN] section. |
| ACCEPTED_AGENT | The total number of times that customer interactions or warm consultations that were distributed from this queue, were accepted, answered, or pulled by an agent. |
| ACCEPTED_AGENT_TIME | The total amount of time, in seconds, that customer interactions waited in this queue before they were accepted, answered, or pulled by agents. Duration starts when the interaction enters the queue and ends when the interaction is accepted, answered, or pulled by an agent—thereby, including alert (ring) time. |
| ACCEPTED_AGENT_THR | The total number of times that customer interactions or established warm consultations that were distributed from this queue were accepted, answered, or pulled by an agent within the acceptance threshold.
This measure relies on the value of the accepted-by-agent threshold as configured in the [agg-gim-thld-QUEUE-IXN] section. |
| TRANSFER_INIT_AGENT | The total number of times that agents transferred customer interactions that were distributed or pulled from this queue. Both warm and blind transfers are reflected in this measure. |
| INVITE | The total number of customer interactions (that were distributed from this queue) that alerted or rang at agent resources before the agents accepted, answered, or pulled the interactions plus the total number of dials that agents performed, where the calls were successfully established and were distributed from this queue. |
| INVITE_TIME | The total amount of time, in seconds, that customer interactions distributed from this queue alerted or rang at agents plus the total duration of the dialing that agents performed. For the alerting component of this measure, interactions do not have to be established for this measure to be incremented. For the dialing component, dial duration is measured for established calls only. |
| ENGAGE_TIME | For customer interactions that were distributed or pulled from this queue, the total amount of time, in seconds, that agents were engaged with customers. This measure excludes other interaction-related durations, such as hold time, ACW (Wrap) time, alert (ring) time and the time that is associated with consultations and collaborations that the agent received. |
| WRAP | The total number of times that agents entered or were in ACW state upon handling customer interactions that were distributed from this queue. |
| WRAP_TIME | The total amount of time, in seconds, that agents spent performing after-call work for customer interactions that were distributed from this queue. |
| HOLD | The total number of times that agents had customer interactions, distributed from this queue, on hold. This count attributes only one hold instance per distribution per agent, even if the same interaction was placed on hold more than once by the agent. |
| HOLD_TIME | The total amount of time, in seconds, that agents had customer interactions that were distributed from this queue on hold. This time starts when the interaction is placed on hold and ends when it is retrieved, dropped, transferred, or completed. |
| CONSULT_ENTERED | The total number of times that simple consultation requests entered this queue where the collaborations/consultations were associated with customer interactions. |
| CONSULT_CLEARED | The total number of times that simple consult interactions were cleared from this virtual queue, workbin, or interaction queue. |
| CONSULT_CLEARED_TIME | The total duration, in seconds, that simple consult interactions spent in a queue before they were cleared from this virtual queue, workbin, or interaction queue. |
| CONSULT_CLEARED_TIME_MAX | The longest amount of time, in seconds, that simple consult interactions spent in a queue before they were cleared from this virtual queue, workbin, or interaction queue. |
| CONSULT_CLEARED_STUCK | The total number of times that simple consult interactions were cleared from this virtual queue, workbin, or interaction queue because they were identified as being stuck (that is, having a technical result of StuckCall). |
| CONSULT_ABANDONED | The total number of times that simple consultations entered this queue and were abandoned before they could be established inside the short-abandoned threshold, where the consultations were associated with customer interactions.
This measure relies on the value of the short-abandoned threshold as configured in the [agg-gim-thld-QUEUE-IXN] section. |
| CONSULT_ABANDONED_TIME | The total amount of time, in seconds, that simple consult interactions waited in this queue before they were abandoned or dropped for any reason and before the interactions could be established. The duration starts the moment at which the consultation entered this queue and ends the moment at which the interaction was abandoned or stopped. The measurement includes short-abandoned interactions and excludes interactions that were abandoned after distribution. |
| CONSULT_ABANDONED_TIME_MAX | The longest amount of time, in seconds, that agents waited at this queue before they abandoned their simple consult interactions. Interactions that were abandoned after they were offered to a resource (that is, abandoned-while-alerting/abandoned-while-ringing interactions) are excluded from consideration. |
| CONSULT_ABANDONED_SHORT | The total number of times that requests for consultation entered this queue and were abandoned within the short-abandoned threshold where the consultations were associated with customer interactions. The count excludes collaborations and consultations that were abandoned after distribution.
This measure relies on the value of the short-abandoned threshold as configured in the [agg-gim-thld-QUEUE-IXN] section. |
| CONSULT_ABANDONED_STANDARD | The total number of simple consult interactions that entered this queue and were abandoned or dropped for any reason beyond the short-abandoned threshold and before the consultations could be established. This measure excludes consultations that were abandoned while they were alerting at a handling resource.
This measure relies on the value of the short-abandoned threshold as configured in the [agg-gim-thld-QUEUE-IXN] section. |
| CONSULT_ABN_STANDARD_TIME | The total amount of time, in seconds, that is associated with simple consult interactions that entered this queue and were abandoned by the agent or dropped for any reason before the consultations could be established. The duration starts when the consultation enters the queue and ends when the consultation is abandoned or dropped, but only after the short-abandoned threshold has elapsed. This measure also excludes the time that is associated with consultations that were abandoned while they were alerting at a handling resource.
This measure relies on the value of the short-abandoned threshold as configured in the [agg-gim-thld-QUEUE-IXN] section. |
| CONSULT_ABANDONED_INVITE | The total number of times that consult interactions that were distributed or pulled from this queue were abandoned or dropped for any reason while the interactions were alerting or ringing at an agent. |
| CONSULT_DISTRIBUTED | The total number of times that simple consult interactions were distributed or pulled from this queue. |
| CONSULT_DISTRIBUTED_TIME | The time, in seconds, from the moment at which simple consult interactions entered this queue to the moment at which they were distributed or pulled from this queue. |
| CONSULT_DISTRIBUTED_TIME_MAX | The longest amount of time, in seconds, that customer interactions spent in this queue before they were distributed. |
| CONSULT_REDIRECTED | The total number of times that collaborations or simple consult interactions entered this queue, rang at a routing target, and were redirected upon no acceptance/answer by an agent. |
| CONSULT_ROUTED_OTHER | The total number of times that consult interactions entered this queue and were subsequently routed either to other mediation DNs or to unmonitored resources. |
| CONSULT_ACCEPTED | The total number of times that simple consult interactions, that were distributed from this queue, were accepted, answered, or pulled by an agent, voice-treatment port, IVR port, or non-agent-associated DN (such as contact center resources that can alert). |
| CONSULT_ACCEPTED_TIME | The total amount of time, in seconds, that simple consult interactions waited in this queue before they were accepted, answered, or pulled by handling resources. The duration starts when consultations enter the queue and ends when the consultations are accepted by the target resource—thereby, including alert (ring) time. |
| CONSULT_ACCEPTED_TIME_MAX | The longest amount of time, in seconds, that simple consult interactions that were distributed from this queue spent in a queue before they were accepted, answered, or pulled by the target resource. Duration starts when the consultation enters the member queue and ends when the consultation is accepted, answered, or pulled—thereby, including alert (ring) time. |
| CONSULT_ACCEPTED_THR | The total number of times that simple consult interactions that were distributed from this queue were accepted, answered, or pulled by a handling resource within the acceptance threshold.
This measure relies on the value of the acceptance threshold as configured in the [agg-gim-thld-QUEUE-IXN] section. |
| CONSULT_ACCEPTED_AGENT_TIME | The total amount of time, in seconds, that consult interactions waited in this queue before they were accepted, answered, or pulled by agents. Duration starts when the interaction enters the queue and ends when the interaction is accepted, answered, or pulled by an agent—thereby, including alert (ring) time. |
| CONSULT_ACCEPTED_AGENT_THR | The total number of times that simple consult interactions that were distributed from this queue were accepted, answered, or pulled by an agent within the acceptance threshold.
This measure relies on the value of the acceptance threshold as configured in the [agg-gim-thld-QUEUE-IXN] section. |
| CONSULT_TRANSFER_INIT_AGENT | The total number of times that agents transferred simple consult interactions that were distributed or pulled from this queue. |
| CONSULT_RECEIVED_ACCEPTED | The total number of times that agents received collaborations or simple consultations that were distributed or pulled from this queue and associated with customer interactions. |
| CONSULT_RECEIVED_INVITE | The total number of simple consult interactions that were distributed from this queue that alerted or rang at agent resources before the agents accepted, answered, or pulled the interactions. |
| CONSULT_RECEIVED_INVITE_TIME | The total amount of time, in seconds, that simple consult interactions that were distributed from this queue alerted or rang at agents. Consultations do not have to be established for this measure to be incremented. |
| CONSULT_RECEIVED_ENGAGE_TIME | The total amount of time, in seconds, that agents were engaged in collaborations or simple consultations that were distributed or pulled from this queue where the collaborations/consultations were associated with customer interactions and the agents were the recipients of the collaboration/consultations requests. |
| CONSULT_RECEIVED_WRAP | The total number of simple consultations for which agents entered ACW state where the consultations were distributed or pulled from this queue and associated with customer interactions and the agents were the recipients of the consultation requests. |
| CONSULT_RECEIVED_WRAP_TIME | The total amount of time, in seconds, that agents were in ACW state after simple consultations that the agents accepted, where the consultations were distributed from this queue and were associated with customer interactions. |
| CONSULT_RECEIVED_HOLD | The total number of simple consultations that agents had on hold where the interactions were distributed or pulled from this queue and associated with customer interactions and the agents were the recipients of the consultation requests. |
| CONSULT_RECEIVED_HOLD_TIME | The total amount time, in seconds, that agents had simple consultations on hold where the consultations were distributed or pulled from this queue and associated with customer interactions and the agents were the recipients of the consultation requests. |
| CONSULT_RCV_ACC_WARM | The total number of times that agents participated in consultations that the agents received, where the consultations were distributed or pulled from this queue, associated with customer interactions, and transferred to or conferenced with the agents. |
| CONSULT_RCV_ACC_WARM_TIME | The total amount time, in seconds, that others spent waiting for an agent to respond to the requests for warm consultation that the agent received, where the warm consult interactions were distributed or pulled from this queue. |
| CONSULT_RCV_WARM_INVITE | The total number of warm consultations that were distributed from this queue that rang at agent resources before the agents answered the calls. |
| CONSULT_RCV_WARM_INVITE_TIME | The total amount of time, in seconds, that warm consult interactions distributed from this queue alerted or rang at agents. By definition, warm interactions must be established for this measure to be incremented. |
| CONSULT_RCV_WARM_ENGAGE_TIME | The total amount of time, in seconds, that agents were engaged in consultations that were distributed or pulled from this queue and associated with customer interactions, the agents were the recipients of the consultation requests, and the interactions were transferred to or conferenced with agents. |
| CONSULT_RCV_WARM_HOLD_TIME | The total amount time, in seconds, that agents had consultations on hold where the interactions were distributed or pulled from this queue and associated with customer interactions, the agents were the recipients of the consultation requests, and the interactions were transferred to or conferenced with the agents. |
| CONSULT_RCV_WARM_HOLD | The total number of consultations distributed from this queue that agents had on hold where the consultations were associated with customer interactions, the agents were the recipients of the consultation requests, and the interactions were transferred to or conferenced with the agents. |
| CONSULT_RCV_WARM_WRAP | The total number of consultations that agents received for which agents entered ACW state where the consultations were distributed from this queue and were associated with customer interactions, and the interactions were transferred to or conferenced with the agents.
This measure includes:
In common call-flow scenarios, this measure yields a value of zero. |
| CONSULT_RCV_WARM_WRAP_TIME | The total amount of time, in seconds, that agents spent in ACW state following consultations that the agents requested and received, where the consultations were distributed from this queue and were associated with customer interactions, and the interactions were transferred to or conferenced with the agents.
This measure includes:
In common call-flow scenarios, this measure yields a value of zero. |
| CONFERENCE_INIT_AGENT | The total number of times that agents initiated conferences for customer interactions that the agents received where the interactions were distributed or pulled from this queue and the conferences were established. The count includes the number of established conferences that were initiated for transferred interactions that agents received. |
| ACCEPTED_TIME | The total amount of time, in seconds, that customer interactions waited in this queue before they were accepted, answered, or pulled by handling resources. The duration starts when interactions enter the queue and ends when the interactions are accepted by the target resource—thereby, including alert (ring) time. |
| ACCEPTED_TIME_MAX | The longest amount of time, in seconds, that customer interactions that were distributed from this queue spent in a queue before they were accepted, answered, or pulled by the target resource. Duration starts when the interaction enters the member queue and ends when the interaction is accepted, answered, or pulled—thereby, including alert (ring) time. |
This page was last edited on March 30, 2017, at 14:39.
Comments or questions about this documentation? Contact us for support!