call_variables
Table name: call_variables
Contains/Role: Depending on the service, a call/written request might deliver variable values. Such variables can be picked up values from external look-ups, it can be calculation made “on the fly”, and so on. NOTE! The same variable might occur more than once within the same call_id. If so, the timestamp in column dte_time will be unique.
Please see more information here.
| Column Name | Datatype | Description |
|---|---|---|
| rec_id | Int Primary key. | Internal, auto-numbered. A unique id for each record. |
| internal_session_id | uniqueidentifier | The internal_iq_session_id for the request that “owns” the variable. |
| call_id | Numeric(19,0) | The call_id for the request that “owns” the variable. |
| dte_time | datetime | When the variable value was “stored”/dumped. |
| name | nvarchar(MAX) | The name of the variable. |
| value | nvarchar(MAX) | The value assigned to the variable. |
If new/updated info about a call_id becomes available after the call_id's call_events and call_variables are inserted into the Raw data db initially (e.g. wrap-up changed or a new session in the same call_id has ended), we will delete the existing records in call_events and call_variables for this call_id and insert them again with new values for rec_id.
Please note that for bot/Bose variables, it's the bot/Bose session that is the internal_session_id and call_id here in call_variables, and that the link between the Chat/Task session and the BoSE session can be found in table call_relations.