# OperatorByWebsiteIdAndUserId: Crisp Operator ## Documentation One operator of a website, retrieved by user identifier. Unlike the operator list, the columns are delivered without the details level. - Catalog: `Crisp` - Schema: `Crisp` - Primary Keys: `user_id` - Label: Operator This is a read-only table function. The Crisp API may not support changing the data or the Invantive UniversalSQL driver for Crisp does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Crisp API. ## Parameters of Table Function The following parameters can be used to control the behaviour of the table function `OperatorByWebsiteIdAndUserId`. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be evaluated using their default values. Value specification by position is done by listing all values from the first to the last needed value. For example: a `select * from table(value1, value2, value3)` on a table with four parameters will use the default value for the fourth parameter and the specified values for the first three. Value specification by name is done by listing all values that require a value. For example with `select * from table(name1 => value1, name3 => value3)` on the same table will use the default values for the second and fourth parameters and the specified values for the first and third. | Name | Data Type | Required | Default Value | Documentation | |---|:---:|:---:|:---:|---| | `user_id` | `varchar2` | ☑ | | The operator user identifier. | | `user_id` | `varchar2` | ☑ | | The operator user identifier. | | `website_id` | `varchar2` | ☐ | | The website identifier. Defaults to the website ID of the connection when left out. | | `website_id` | `varchar2` | ☐ | | The website identifier. Defaults to the website ID of the connection when left out. | ## Columns of Table Function The columns of the table function `OperatorByWebsiteIdAndUserId` are shown below. Each column has an SQL data type. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `availability` | `varchar2` | | ☐ | User availability; one of online, away and offline. | | `availability` | `varchar2` | | ☐ | User availability; one of online, away and offline. | | `avatar` | `varchar2` | | ☐ | User avatar. | | `avatar` | `varchar2` | | ☐ | User avatar. | | `email` | `varchar2` | | ☑ | User email. | | `email` | `varchar2` | | ☑ | User email. | | `first_name` | `varchar2` | | ☐ | User first name. | | `first_name` | `varchar2` | | ☐ | User first name. | | `has_token` | `char` | | ☐ | Whether the operator has Two Factor Authentication enabled or not. | | `has_token` | `char` | | ☐ | Whether the operator has Two Factor Authentication enabled or not. | | `last_name` | `varchar2` | | ☐ | User last name. | | `last_name` | `varchar2` | | ☐ | User last name. | | `role` | `varchar2` | | ☐ | User role; one of owner and member. | | `role` | `varchar2` | | ☐ | User role; one of owner and member. | | `title` | `varchar2` | | ☐ | User title (if any). | | `title` | `varchar2` | | ☐ | User title (if any). | | `user_id` | `varchar2` | | ☑ | User identifier. | | `user_id` | `varchar2` | | ☑ | User identifier. |# OperatorByWebsiteIdAndUserId: Crisp Operator ## Documentation One operator of a website, retrieved by user identifier. Unlike the operator list, the columns are delivered without the details level. - Catalog: `Crisp` - Schema: `Crisp` - Primary Keys: `user_id` - Label: Operator This is a read-only table function. The Crisp API may not support changing the data or the Invantive UniversalSQL driver for Crisp does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Crisp API. ## Parameters of Table Function The following parameters can be used to control the behaviour of the table function `OperatorByWebsiteIdAndUserId`. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be evaluated using their default values. Value specification by position is done by listing all values from the first to the last needed value. For example: a `select * from table(value1, value2, value3)` on a table with four parameters will use the default value for the fourth parameter and the specified values for the first three. Value specification by name is done by listing all values that require a value. For example with `select * from table(name1 => value1, name3 => value3)` on the same table will use the default values for the second and fourth parameters and the specified values for the first and third. | Name | Data Type | Required | Default Value | Documentation | |---|:---:|:---:|:---:|---| | `user_id` | `varchar2` | ☑ | | The operator user identifier. | | `user_id` | `varchar2` | ☑ | | The operator user identifier. | | `website_id` | `varchar2` | ☐ | | The website identifier. Defaults to the website ID of the connection when left out. | | `website_id` | `varchar2` | ☐ | | The website identifier. Defaults to the website ID of the connection when left out. | ## Columns of Table Function The columns of the table function `OperatorByWebsiteIdAndUserId` are shown below. Each column has an SQL data type. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `availability` | `varchar2` | | ☐ | User availability; one of online, away and offline. | | `availability` | `varchar2` | | ☐ | User availability; one of online, away and offline. | | `avatar` | `varchar2` | | ☐ | User avatar. | | `avatar` | `varchar2` | | ☐ | User avatar. | | `email` | `varchar2` | | ☑ | User email. | | `email` | `varchar2` | | ☑ | User email. | | `first_name` | `varchar2` | | ☐ | User first name. | | `first_name` | `varchar2` | | ☐ | User first name. | | `has_token` | `char` | | ☐ | Whether the operator has Two Factor Authentication enabled or not. | | `has_token` | `char` | | ☐ | Whether the operator has Two Factor Authentication enabled or not. | | `last_name` | `varchar2` | | ☐ | User last name. | | `last_name` | `varchar2` | | ☐ | User last name. | | `role` | `varchar2` | | ☐ | User role; one of owner and member. | | `role` | `varchar2` | | ☐ | User role; one of owner and member. | | `title` | `varchar2` | | ☐ | User title (if any). | | `title` | `varchar2` | | ☐ | User title (if any). | | `user_id` | `varchar2` | | ☑ | User identifier. | | `user_id` | `varchar2` | | ☑ | User identifier. |