View table: PDMColumn
Table structure:
- colName - String
- dataType_Ora - String
- dataType_MSSQL - String
- dataType_Postgre - String
- dataType_DB2 - String
- primaryKey - String
- mandatoryKey - String
- foreignKey - String
- defaultValue - String
- colDesc - Wikitext
- introduced - Wikitext
- modified - List of Wikitext
- discontinued - Wikitext
- KVP - String
- xpath - String
- mandatoryForGIM - String
- transformDefault - String
This table has 3,423 rows altogether.
| Page | colName | dataType Ora | dataType MSSQL | dataType Postgre | dataType DB2 | primaryKey | mandatoryKey | foreignKey | defaultValue | colDesc | introduced | modified | discontinued | KVP | xpath | mandatoryForGIM | transformDefault |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL AUDIT LOG | AUDIT_KEY | NUMBER(19) | numeric(19) | numeric(19) | yes | yes | 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. | ||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL AUDIT LOG | CREATED | TIMESTAMP(3) | datetime | timestamp(3) | yes | The date and time of row creation. | |||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL AUDIT LOG | CREATED_TS | NUMBER(10) | int | integer | yes | The UTC-equivalent value of the date and time of row creation. | |||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL AUDIT LOG | DATA_SOURCE_KEY | NUMBER(10) | int | integer | 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. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL AUDIT LOG | INSERTED | TIMESTAMP(3) | datetime | timestamp(3) | 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. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL AUDIT LOG | JOB_ID | VARCHAR2(64 CHAR) | varchar(64) | varchar(64) | yes | ID that uniquely identifies the execution instance of the job. | |||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL AUDIT LOG | MAX_CHUNK_TS | NUMBER(10) | int | integer | The maximum value out of all timestamps that are stored for a particular chunk of data that is marked with the corresponding audit key. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL AUDIT LOG | MAX_START_DATE_TIME_KEY | NUMBER(10) | int | integer | yes | 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. | |||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL AUDIT LOG | MIN_START_DATE_TIME_KEY | NUMBER(10) | int | integer | yes | 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. | |||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL AUDIT LOG | PROCESSING_STATUS_KEY | NUMBER(10) | int | integer | yes | Reference to the CTL_PROCESSING_STATUS dimension. This field is reserved. | |||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL AUDIT LOG | PRODUCER_INFO_KEY | NUMBER(19) | numeric(19) | numeric(19) | Reference to the CTL_PRODUCER_INFO dimension, to identify the version of the upstream application or service that produced Kafka data. | 8.5.116.12 | |||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL AUDIT LOG | ROW_COUNT | NUMBER(10) | int | integer | The number of records that are marked with this audit key. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL ETL HISTORY | CREATED_TS | NUMBER(10) | int | integer | yes | The UTC-equivalent value of the date and time at which the job started. | |||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL ETL HISTORY | DURATION | NUMBER(10) | int | integer | The duration of the job, in seconds. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL ETL HISTORY | GMT_END_TIME | TIMESTAMP(3) | datetime | timestamp(3) | The date and time the last step of the job ended (in GMT time zone). | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL ETL HISTORY | GMT_START_TIME | TIMESTAMP(3) | datetime | timestamp(3) | The date and time the first step of the job started (in GMT time zone). | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL ETL HISTORY | JOB_ID | VARCHAR2(64 CHAR) | varchar(64) | varchar(64) | yes | yes | ID that uniquely identifies the execution instance of the job. | ||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL ETL HISTORY | JOB_NAME | VARCHAR2(32 CHAR) | varchar(32) | varchar(32) | The name of the job, such as Job_ExtractICON. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL ETL HISTORY | JOB_VERSION | VARCHAR2(32 CHAR) | varchar(32) | varchar(32) | The version of the job, such as 8.1.000.10. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL ETL HISTORY | LOCAL_END_TIME | TIMESTAMP(3) | datetime | timestamp(3) | The date and time the last step of the job ended (in the time zone where Genesys Info Mart Server is running). Note: Because the Genesys Info Mart Server always runs in the GMT time zone, the value of this field is always the same as GMT_END_TIME. |
||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL ETL HISTORY | LOCAL_START_TIME | TIMESTAMP(3) | datetime | timestamp(3) | The date and time the first step of the job started (in the time zone where Genesys Info Mart Server is running). Note: Because the Genesys Info Mart Server always runs in the GMT time zone, the value of this field is always the same as GMT_START_TIME. |
||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL ETL HISTORY | STATUS | VARCHAR2(32 CHAR) | varchar(32) | varchar(32) | The status of the job, such as COMPLETE or FAILED. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL ETL HISTORY | WORKFLOW_TYPE | VARCHAR2(32 CHAR) | varchar(32) | varchar(32) | yes | yes | The name of the step of the job, such as Outbound. | ||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL EXTRACT HISTORY | CREATED_TS | NUMBER(10) | int | integer | yes | The UTC-equivalent value of the date and time at which the extraction job started. | |||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL EXTRACT HISTORY | CREATE_AUDIT_KEY | NUMBER(19) | numeric(19) | numeric(19) | yes | yes | 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. | ||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL EXTRACT HISTORY | DAP_NAME | VARCHAR2(255 CHAR) | varchar(255)/nvarchar(255) | varchar(255) | The name of the Database Access Point (DAP) through which data was extracted. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL EXTRACT HISTORY | DATA_SOURCE_KEY | NUMBER(10) | int | integer | yes | The surrogate key that is used to join this table to the CTL_DS table. | |||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL EXTRACT HISTORY | DATA_SOURCE_TYPE | NUMBER(10) | int | integer | The type of the data source server as reported by ICON. This field is set to one of the following values:
|
||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL EXTRACT HISTORY | DSS_ID | NUMBER(10) | int | integer | The data source session identifier that is used in a given extraction cycle. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL EXTRACT HISTORY | EXTRACT_END_TIME | TIMESTAMP(3) | datetime | timestamp(3) | The date and time when the extraction job finished. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL EXTRACT HISTORY | EXTRACT_START_TIME | TIMESTAMP(3) | datetime | timestamp(3) | The date and time when the extraction job started. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL EXTRACT HISTORY | ICON_DBID | NUMBER(10) | int | integer | yes | 0 | ID that uniquely identifies the ICON application instance. The value is the same as the one that ICON provided in the IDB. | ||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL EXTRACT HISTORY | JOB_ID | VARCHAR2(64 CHAR) | varchar(64) | varchar(64) | yes | ID that uniquely identifies the execution instance of the job. | |||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL EXTRACT HISTORY | JOB_NAME | VARCHAR2(32 CHAR) | varchar(32) | varchar(32) | The name of the job that extracted data--for example, Job_ExtractICON. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL EXTRACT HISTORY | JOB_VERSION | VARCHAR2(64 CHAR) | varchar(64) | varchar(64) | The version of the job that extracted data--for example, 8.1.000.10. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL EXTRACT HISTORY | MAX_TIME | TIMESTAMP(3) | datetime | timestamp(3) | The date and time, in the Genesys Info Mart server time zone, that represent the highest timestamp value for the records that are extracted in a given extraction cycle. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL EXTRACT HISTORY | MAX_TS | NUMBER(10) | int | integer | The UTC-equivalent value of the date and time that represents the highest timestamp value for the records that are extracted in a given extraction cycle. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL EXTRACT HISTORY | PROVIDERTAG | NUMBER(10) | int | integer | The ID of the ICON provider class, such as 5 for the configuration information provider (cfg). This field is reserved. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL EXTRACT HISTORY | ROW_COUNT | NUMBER(10) | int | integer | The number of records that are extracted in a given extraction cycle. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL EXTRACT HISTORY | TABLE_NAME | VARCHAR2(255 CHAR) | varchar(255) | varchar(255) | yes | The name of the IDB table from which data was extracted. | |||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL GDPR HISTORY | AUDIT_KEY | NUMBER(19) | numeric(19) | numeric(19) | yes | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key is used for data lineage purposes. | |||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL GDPR HISTORY | COLUMN_NAME | VARCHAR2(64 CHAR) | nvarchar(64) | varchar(64) | yes | The name of the column that was evaluated for PII. (See the table description above for possible values.) | |||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL GDPR HISTORY | CONSUMER_ID | VARCHAR2(255 CHAR) | varchar(255)/nvarchar(255) | varchar(255) | yes | The instance of PII that was searched for. The value is derived from one of the following consumer- or employee-identifying attributes in the customer-provided JSON input file:
|
|||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL GDPR HISTORY | CREATED_TS | NUMBER(10) | int | integer | yes | The UTC-equivalent value of the date and time of row creation. | |||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL GDPR HISTORY | FACT_ID | VARCHAR2(255 CHAR) | varchar(255)/nvarchar(255) | varchar(255) | The ID of the table record in which the PII was found. A value of NULL indicates that a particular table was evaluated for that PII and no instance was found. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL GDPR HISTORY | FORGET | NUMBER(1) | numeric(1) | numeric(1) | yes | 0 | Indicates whether the PII was processed for a "forget" request: 0 = No, 1 = Yes | ||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL GDPR HISTORY | KEY_NAME | VARCHAR2(255 CHAR) | nvarchar(255) | varchar(255) | The name of the custom user data KVP key or custom Outbound Contact Server (OCS) record field that the customer has identified might contain PII and, therefore, has specified in the "gim-attached-data" element in the JSON input file. For example, while consumers are identified in Genesys Info Mart only by phone number or email address, custom KVPs or record fields might contain PII such as a name, Social Security number, or mailing address. The custom key would already have been mapped to a custom user data table and column or a RECORD_FIELD_* column in the CONTACT_ATTEMPT_FACT table, when you configured your Genesys Info Mart deployment. In Genesys Engage cloud deployments, this column might also specify a non-custom KEY_NAME, such as “TRANSCRIPTION.” |
||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL GDPR HISTORY | KEY_VALUE | VARCHAR2(4000 CHAR) | nvarchar(4000) | varchar(4000) | The value of the custom user data KVP or custom OCS record field that contained the PII. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL GDPR HISTORY | TABLE_NAME | VARCHAR2(64 CHAR) | nvarchar(64) | varchar(64) | yes | The name of the table that was evaluated for PII. (See the table description above for possible values.) | |||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL GDPR HISTORY | TENANT_KEY | NUMBER(10) | int | integer | yes | yes | 0 | The surrogate key that is used to join the TENANT dimension to other tables in the Info Mart database. | |||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL PURGE HISTORY | CREATED_TS | NUMBER(10) | int | integer | yes | The UTC-equivalent value of the date and time at which the maintenance job started the purge cycle. | |||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL PURGE HISTORY | JOB_ID | VARCHAR2(64 CHAR) | varchar(64) | varchar(64) | yes | ID that uniquely identifies the execution instance of the maintenance job. | |||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL PURGE HISTORY | JOB_VERSION | VARCHAR2(64 CHAR) | varchar(64) | varchar(64) | The version of the job that purged data--for example, 8.1.000.10. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL PURGE HISTORY | PURGE_END_TIME | TIMESTAMP(3) | datetime | timestamp(3) | The date and time when the maintenance job finished the purge cycle. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL PURGE HISTORY | PURGE_MAX_TIME | TIMESTAMP(3) | datetime | timestamp(3) | The date and time, in the GMT time zone, that represent the highest timestamp value for the records that are deleted in a given purge cycle. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL PURGE HISTORY | PURGE_MAX_TS | NUMBER(10) | int | integer | yes | The UTC-equivalent value of the date and time that represents the highest timestamp value for the records that are deleted in a given purge cycle. | |||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL PURGE HISTORY | PURGE_START_TIME | TIMESTAMP(3) | datetime | timestamp(3) | The date and time when the maintenance job started the purge cycle. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL PURGE HISTORY | ROW_COUNT | NUMBER(10) | int | integer | The number of rows that was deleted in a given purge cycle. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL PURGE HISTORY | TABLE_NAME | VARCHAR2(255 CHAR) | varchar(255) | varchar(255) | yes | The name of the table from which data was purged. | |||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL TRANSFORM HISTORY | AUDIT_KEY | NUMBER(19) | numeric(19) | numeric(19) | yes | The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key is used for data lineage purposes, in particular to identify the HWM_VALUE or HWM_VALUE2 related to a particular audit key. | 8.5.009 | ||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL TRANSFORM HISTORY | CREATED_TS | NUMBER(10) | int | integer | yes | The UTC-equivalent value of the date and time at which the transformation job started. | |||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL TRANSFORM HISTORY | HWM_NAME | VARCHAR2(255 CHAR) | varchar(255) | varchar(255) | The name of the table from which data was taken for transformation. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL TRANSFORM HISTORY | HWM_VALUE | NUMBER(19) | numeric(19) | numeric(19) | yes | Provides the value of the numeric high-water mark (HWM) for the records that are processed in a given transformation cycle. | |||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL TRANSFORM HISTORY | HWM_VALUE2 | VARCHAR2(255 CHAR) | varchar(255)/nvarchar(255) | varchar(255) | Provides supplemental information about the value of HWM_VALUE, when applicable. The column was introduced to support future alternative data streams in which the HWMs might require nonnumeric values for context. |
8.5.010 | |||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL TRANSFORM HISTORY | JOB_ID | VARCHAR2(64 CHAR) | varchar(64) | varchar(64) | yes | ID that uniquely identifies the execution instance of the job. | |||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL TRANSFORM HISTORY | JOB_VERSION | VARCHAR2(64 CHAR) | varchar(64) | varchar(64) | The version of Job_TransformGIM--for example, 8.1.000.10. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL TRANSFORM HISTORY | ROW_COUNT | NUMBER(10) | int | integer | Provides the number of records that are processed in a given transformation cycle. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL TRANSFORM HISTORY | TRANSFORM_END_TIME | TIMESTAMP(3) | datetime | timestamp(3) | The date and time when the transformation job finished. | ||||||||||||
| Documentation:PEC-REP/Library/PDMLibraryGIM/Table-CTL TRANSFORM HISTORY | TRANSFORM_START_TIME | TIMESTAMP(3) | datetime | timestamp(3) | The date and time when the transformation job started. | ||||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-AGENT LOCATION | AGENT_LOCATION_KEY | NUMBER(10) | int | integer | yes | yes | The primary key of this table and the surrogate key that is used to join this dimension to the fact tables. | ||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-AGENT LOCATION | AGENT_LOCATION_STRING | VARCHAR2(255 CHAR) | nvarchar(255) | varchar(255) | yes | The value reported by SIP Server or Interaction Server for the voice or multimedia login session, respectively. | 8.5.014.34 (in Microsoft SQL Server, data type changed from varchar to nvarchar in single-language databases) | ||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-AGENT LOCATION | CREATE_AUDIT_KEY | NUMBER(19) | numeric(19) | numeric(19) | yes | yes | 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. | ||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-AGENT LOCATION | TENANT_KEY | NUMBER(10) | int | integer | yes | yes | The surrogate key that is used to join the TENANT dimension to the fact tables. | ||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-AGENT LOCATION NewTitle | AGENT_LOCATION_KEY | NUMBER(10) | int | integer | yes | yes | The primary key of this table and the surrogate key that is used to join this dimension to the fact tables. | ||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-AGENT LOCATION NewTitle | AGENT_LOCATION_STRING | VARCHAR2(255 CHAR) | nvarchar(255) | varchar(255) | yes | The value reported by SIP Server or Interaction Server for the voice or multimedia login session, respectively. | 8.5.014.34 (in Microsoft SQL Server, data type changed from varchar to nvarchar in single-language databases) | ||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-AGENT LOCATION NewTitle | CREATE_AUDIT_KEY | NUMBER(19) | numeric(19) | numeric(19) | yes | yes | 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. | ||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-AGENT LOCATION NewTitle | TENANT_KEY | NUMBER(10) | int | integer | yes | yes | The surrogate key that is used to join the TENANT dimension to the fact tables. | ||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-ANCHOR FLAGS | ANCHOR_FLAGS_KEY | NUMBER(10) | int | integer | yes | yes | The surrogate key that is used to join this dimension to the fact tables. | ||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-ANCHOR FLAGS | CREATE_AUDIT_KEY | NUMBER(19) | numeric(19) | numeric(19) | yes | yes | 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. | ||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-ANCHOR FLAGS | CUSTOMER_LEFT_FIRST | NUMBER(1) | numeric(1) | numeric(1) | yes | 0 | Indicates whether the customer left a chat first: 0 = No, 1 = Yes. This flag is set in the IRF for each agent engaged in the chat or chat consultation, if data about the party that ended a chat session is available from Interaction Concentrator. In IRFs in which this flag is set, IRF_ANCHOR_TS records the time the customer left the chat. |
8.5.004 | |||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-ANCHOR FLAGS | FIRST_ENGAGE_FOR_AGENT_IXN | NUMBER(1) | numeric(1) | numeric(1) | yes | In the IRF for an agent, indicates whether this is the first participation by that agent in the interaction: 0 = No, 1 = Yes. This flag is set in the IRF for an agent’s first connection into the interaction — for example, when the agent accepts a route, accepts a transfer or conference, or pulls an interaction from a queue or workbin (excluding workbin hold). Unlike the other flags, which can be set for multimedia interactions only, this flag can also apply to voice interactions. This flag applies to participation in either the inbound or outbound portions of an interaction; for example, it will be set when the agent’s first participation in an interaction is in an OutboundReply to an Inbound interaction. This flag does not apply if the IRF does not show the agent connecting to the interaction — for example, if the agent is offered an interaction but does not accept. This flag also does not apply to collaborations. |
|||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-ANCHOR FLAGS | FIRST_ENGAGE_FOR_AGENT_THRD | NUMBER(1) | numeric(1) | numeric(1) | yes | Writer's note: Delete this description. If the column is still in make_gim.sql, what to say here? Maybe just "Reserved" or perhaps something like: "The functionality represented by this column has been deprecated. This column is no longer populated." In the IRF for an agent, indicates whether this is the first participation by that agent in any of the interactions in a thread: 0 = No, 1 = Yes. This flag is set in the IRF for an agent’s first connection into any one of the interactions in the thread — for example, when the agent accepts a route, accepts a transfer or conference, or pulls an interaction from a queue or workbin (excluding workbin hold). This flag applies to participation in either the inbound or outbound portions of an interaction; for example, it will be set if the agent’s first participation in the interaction thread is in an OutboundReply to an Inbound interaction. This flag does not apply if the IRF does not show the agent connecting to the interaction — for example, if the agent is offered an interaction but does not accept. This flag also does not apply to collaborations. Starting with release 8.5.001, this flag is set only if the populate-thread-facts configuration option is set to true. Otherwise, the value of this field is always 0. |
|||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-ANCHOR FLAGS | FIRST_ENGAGE_THRD | NUMBER(1) | numeric(1) | numeric(1) | yes | Writer's note: Ditto. Indicates whether this is the first participation, by any handling resource, in the interaction thread: 0 = No, 1 = Yes. This flag is set in the IRF for the handling resource (agent or strategy) that first participates in the thread — for example, when an agent accepts an Inbound interaction, or when a strategy generates an AutoResponse. IRFs in which this flag is set also have IRF_ANCHOR = 1. Starting with release 8.5.001, this flag is set only if the populate-thread-facts configuration option is set to true. Otherwise, the value of this field is always 0. |
|||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-ANCHOR FLAGS | FIRST_REPLY_FOR_AGENT_IXN | NUMBER(1) | numeric(1) | numeric(1) | yes | In the IRF for an agent, indicates whether this is the first participation by that agent in a reply within the interaction: 0 = No, 1 = Yes. This flag is set in the IRF for an agent’s first connection into an OutboundReply for the interaction — for example, when the agent initiates an OutboundReply, accepts a route, accepts a transfer, or pulls an interaction from a queue or workbin (excluding workbin hold). If the interaction contains more than one OutboundReply, this flag applies to the agent’s first participation in any one of them. The OutboundReply does not need to be successful (in other words, sent). This flag does not apply if the IRF does not show the agent connecting to the interaction — for example, if the agent is offered an OutboundReply but does not accept. This flag also does not apply to collaborations. Note: An agent’s first participation in an OutboundReply for an interaction might also be the agent’s first participation in the interaction, which is indicated in FIRST_ENGAGE_FOR_AGENT_IXN. |
|||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-ANCHOR FLAGS | FIRST_REPLY_FOR_AGENT_THRD | NUMBER(1) | numeric(1) | numeric(1) | yes | Writer's note: Ditto. In the IRF for an agent, indicates whether this is the first participation by the agent in a reply for any of the interactions in the thread: 0 = No, 1 = Yes. This flag is set in the IRF for an agent’s first connection into an OutboundReply for any one of the interactions in the thread — for example, when the agent initiates an OutboundReply, accepts a route, accepts a transfer, or pulls an interaction from a queue or workbin (excluding workbin hold). The OutboundReply does not need to be successful (in other words, sent). This flag does not apply if the IRF does not show the agent connecting to the interaction — for example, if the agent is offered an OutboundReply but does not accept. This flag also does not apply to collaborations. Note: An agent’s first participation in an OutboundReply for a thread might also be the agent’s first participation in the thread, which is indicated in FIRST_ENGAGE_FOR_AGENT_THRD. Starting with release 8.5.001, this flag is set only if the populate-thread-facts configuration option is set to true. Otherwise, the value of this field is always 0. |
|||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-ANCHOR FLAGS | UPDATE_AUDIT_KEY | NUMBER(19) | numeric(19) | numeric(19) | yes | yes | 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. | ||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-ATTEMPT DISPOSITION | ATTEMPT_DISPOSITION_KEY | NUMBER(10) | int | integer | yes | yes | The key that uniquely identifies the disposition. The value combines the state and the descriptor that provides additional details. The key value enables you to calculate the state by using appropriate bit masks. The first eight bits specify the cause, which equals the integer value that is supplied by Outbound Contact Server. The next eight bits specify the descriptor that is generated by Genesys Info Mart. | ||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-ATTEMPT DISPOSITION | CAUSE | VARCHAR2(255 CHAR) | nvarchar(255) | varchar(255) | The cause as specified in the OCS model. This value can change with localization. | 8.5.014.34 (in Microsoft SQL Server, data type changed from varchar to nvarchar in single-language databases) | |||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-ATTEMPT DISPOSITION | CAUSE_CODE | VARCHAR2(255 CHAR) | nvarchar(255) | varchar(255) | The cause code that is equivalent to the OCS model cause. This value does not change with localization. | 8.5.014.34 (in Microsoft SQL Server, data type changed from varchar to nvarchar in single-language databases) | |||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-ATTEMPT DISPOSITION | CAUSE_ID | NUMBER(10) | int | integer | An integer that equals the value that is supplied by Outbound Contact Server to specify the cause. | ||||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-ATTEMPT DISPOSITION | CREATE_AUDIT_KEY | NUMBER(19) | numeric(19) | numeric(19) | yes | yes | 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. | ||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-ATTEMPT DISPOSITION | DESCRIPTOR | VARCHAR2(255 CHAR) | nvarchar(255) | varchar(255) | Specifies whether the final transition was caused by an agent or by the system, or whether this is unknown. Because not all outbound dispositions support descriptor, most dispositions have only an 'Unknown' value. This is a string value that can be localized or changed, based on reporting needs. | 8.5.014.34 (in Microsoft SQL Server, data type changed from varchar to nvarchar in single-language databases) | |||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-ATTEMPT DISPOSITION | DESCRIPTOR_CODE | VARCHAR2(255 CHAR) | nvarchar(255) | varchar(255) | The code of the descriptor. This field is set to one of the following values:
This value is not localizable and should not be changed. |
8.5.014.34 (in Microsoft SQL Server, data type changed from varchar to nvarchar in single-language databases) | |||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-ATTEMPT DISPOSITION | UPDATE_AUDIT_KEY | NUMBER(19) | numeric(19) | numeric(19) | yes | yes | 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. | ||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-BGS BOT DIM | BOT_CATEGORY | VARCHAR2(50 CHAR) | nvarchar(50) | varchar(50) | yes | NO_VALUE | The generic category describing the type of function performed by the bot, such as Monitoring, Dialog, Notification, or Service. For information about how you can define and set bot categories, see Note to self: Confirm if there's an updated link for Azure/PE. Integrating BGS with Genesys Historical Reporting in the Bot Gateway Server Quick Start Guide. | /chatBot_info/chatBot_category | |||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-BGS BOT DIM | BOT_FUNCTION | VARCHAR2(50 CHAR) | nvarchar(50) | varchar(50) | yes | NO_VALUE | The specific bot functionality, such as Translator, Advisor, Escalation, Recording, AI, or Questioner. For information about how you can define and set bot functions, see Integrating BGS with Genesys Historical Reporting in the Bot Gateway Server Quick Start Guide. | /chatBot_info/chatBot_function | |||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-BGS BOT DIM | CREATE_AUDIT_KEY | NUMBER(19) | numeric(19) | numeric(19) | yes | yes | 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. | ||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-BGS BOT DIM | ID | NUMBER(10) | int | integer | yes | yes | The primary key of this table. This ID is referenced from other tables as BGS_BOT_DIM_KEY. | ||||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-BGS BOT NAME DIM | BOT_NAME | VARCHAR2(50 CHAR) | nvarchar(50) | varchar(50) | yes | NO_VALUE | The ChatBotID-ChatBotName pair that identifies the bot, where:
|
/chatBot_info/chatBot_name | |||||||||
| Draft:PEC-REP/Library/PDMLibraryGIM/Table-BGS BOT NAME DIM | CREATE_AUDIT_KEY | NUMBER(19) | numeric(19) | numeric(19) | yes | yes | 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. |