@alicloud/dms20250414 4.2.0 → 4.2.2

package/src/models/SendChatMessageRequest.ts

@@ -5,21 +5,21 @@ import * as $dara from '@darabonba/typescript';
 export class SendChatMessageRequestDataSourcePermissionTables extends $dara.Model {
   /**
    * @remarks
-   * The list of columns that are allowed for querying in the current table. If this field is left empty, all columns can be queried. If specified, SQL statements that exceed the allowed scope are blocked. For example, syntax such as SELECT * is blocked. To ensure DataAgent analysis effectiveness, avoid specifying columns beyond the allowed scope in the DataAgent prompts, knowledge, or instructions modules. Otherwise, unauthorized SQL statements may be generated and blocked, which reduces DataAgent analysis speed and effectiveness.
+   * The list of columns that are allowed to be queried in the current table. If you leave this field empty, all columns can be queried. If you specify this field, SQL statements that query columns beyond the allowed scope, such as `SELECT *`, will be blocked. To ensure the analysis performance of DataAgent, make sure that the prompts, knowledge, and instructions modules of DataAgent do not include columns beyond the allowed scope. Otherwise, unauthorized SQL statements may be generated and blocked, which degrades the analysis speed and performance of DataAgent.
    */
   allowedColumns?: string[];
   /**
    * @remarks
-   * The list of columns that are not allowed for querying in the current table. If this field is left empty, all columns **can be queried**. If specified, SQL statements that exceed the allowed scope are blocked. For example, syntax such as SELECT * is blocked.  
+   * The list of columns that are not allowed to be queried in the current table. If you leave this field empty, all columns **can be queried**. If you specify this field, SQL statements that query columns beyond the allowed scope, such as `SELECT *`, will be blocked.  
    * 
-   * If both the disallowed list and the allowed list are configured, the disallowed list takes higher priority. For example, if Table 1 has columns A, B, C, and D, and columns A and B are configured as not queryable while columns B and C are configured as queryable, the final result is that only column C is queryable.
+   * If both the disallowed list and the allowed list are configured, the disallowed list takes precedence. For example, if Table 1 has columns A, B, C, and D, and you configure columns A and B as not allowed, while configuring columns B and C as allowed, only column C is ultimately allowed to be queried.
    * 
-   * To ensure DataAgent analysis effectiveness, avoid specifying columns beyond the allowed scope in the DataAgent prompts, knowledge, or instructions modules. Otherwise, unauthorized SQL statements may be generated and blocked, which reduces DataAgent analysis speed and effectiveness.
+   * To ensure the analysis performance of DataAgent, make sure that the prompts, knowledge, and instructions modules of DataAgent do not include columns beyond the allowed scope. Otherwise, unauthorized SQL statements may be generated and blocked, which degrades the analysis speed and performance of DataAgent.
    */
   disallowedColumns?: string[];
   /**
    * @remarks
-   * The required row filter condition for the current table. If this field is left empty, it is ignored. If specified, all SQL statements involving this table are validated to check whether they carry the filter field and whether the WHERE condition meets the constraints. SQL statements that do not meet the constraints are rejected. Ensure the validation condition format is correct.
+   * The row filter condition that must be included for the current table. If you leave this field empty, it is ignored. If you specify this field, the system checks whether all SQL statements involving this table include the filter column and whether the WHERE clause meets the constraints. SQL statements that do not meet the constraints will be rejected. Pay attention to the format of the validation condition.
    * 
    * @example
    * region = \\"east\\"
@@ -27,7 +27,7 @@ export class SendChatMessageRequestDataSourcePermissionTables extends $dara.Mode
   requiredRowFilter?: string;
   /**
    * @remarks
-   * The table name to which the permission constraint rule applies.
+   * The name of the table to which the permission constraint rules apply.
    * 
    * @example
    * sample_table
@@ -69,7 +69,7 @@ export class SendChatMessageRequestDataSourcePermissionTables extends $dara.Mode
 export class SendChatMessageRequestDataSourcePermission extends $dara.Model {
   /**
    * @remarks
-   * The table-level permission constraints for querying the current data source. Each item in the list represents the permission constraints for a table.
+   * The table-level permission constraints for querying the current data source. Each item in the list represents the permission constraints for a specific table.
    */
   tables?: SendChatMessageRequestDataSourcePermissionTables[];
   static names(): { [key: string]: string } {
@@ -99,7 +99,7 @@ export class SendChatMessageRequestDataSourcePermission extends $dara.Model {
 export class SendChatMessageRequestDataSource extends $dara.Model {
   /**
    * @remarks
-   * Deprecated. You do not need to specify this field.
+   * **[Deprecated]** You do not need to specify this field.
    * 
    * @example
    * 123
@@ -107,7 +107,7 @@ export class SendChatMessageRequestDataSource extends $dara.Model {
   dataSourceId?: string;
   /**
    * @remarks
-   * The data source type. Valid values: `[remote_data_center, database]`, indicating that the analysis is performed on a file or a database.
+   * The data source type. Valid values: `remote_data_center` and `database`. `remote_data_center` indicates a file, and `database` indicates a database.
    * 
    * @example
    * remote_data_center
@@ -115,7 +115,7 @@ export class SendChatMessageRequestDataSource extends $dara.Model {
   dataSourceType?: string;
   /**
    * @remarks
-   * Deprecated. You do not need to specify this field.
+   * **[Deprecated]** You do not need to specify this field.
    * 
    * @example
    * test_db
@@ -123,7 +123,7 @@ export class SendChatMessageRequestDataSource extends $dara.Model {
   database?: string;
   /**
    * @remarks
-   * The database name.
+   * The name of the database.
    * 
    * @example
    * ******
@@ -131,7 +131,7 @@ export class SendChatMessageRequestDataSource extends $dara.Model {
   dbName?: string;
   /**
    * @remarks
-   * The ID of the database in Data Management.
+   * The ID of the database in Data Management (DMS).
    * 
    * @example
    * 23******
@@ -139,7 +139,7 @@ export class SendChatMessageRequestDataSource extends $dara.Model {
   dmsDatabaseId?: string;
   /**
    * @remarks
-   * The ID of the instance in Data Management.
+   * The ID of the instance in DMS.
    * 
    * @example
    * 12******
@@ -155,7 +155,7 @@ export class SendChatMessageRequestDataSource extends $dara.Model {
   engine?: string;
   /**
    * @remarks
-   * The file ID.
+   * The ID of the file.
    * 
    * @example
    * 35****
@@ -163,7 +163,7 @@ export class SendChatMessageRequestDataSource extends $dara.Model {
   fileId?: string;
   /**
    * @remarks
-   * Deprecated. You do not need to specify this field.
+   * **[Deprecated]** You do not need to specify this field.
    * 
    * @example
    * localhost
@@ -171,7 +171,7 @@ export class SendChatMessageRequestDataSource extends $dara.Model {
   location?: string;
   /**
    * @remarks
-   * The permission constraints for querying the current data source. The permission constraint feature is available through a canary release. This field does not take effect for users who are not included in the canary release.
+   * The permission constraints for querying the current data source. The permission constraint feature is in canary release. This field does not take effect for users outside the canary release scope.
    */
   permission?: SendChatMessageRequestDataSourcePermission;
   /**
@@ -184,9 +184,17 @@ export class SendChatMessageRequestDataSource extends $dara.Model {
   regionId?: string;
   /**
    * @remarks
-   * The list of table names to analyze.
+   * The list of names of the tables to be analyzed.
    */
   tables?: string[];
+  /**
+   * @remarks
+   * The data source resource identifier.
+   * 
+   * @example
+   * datalake://abc/def
+   */
+  uri?: string;
   static names(): { [key: string]: string } {
     return {
       dataSourceId: 'DataSourceId',
@@ -201,6 +209,7 @@ export class SendChatMessageRequestDataSource extends $dara.Model {
       permission: 'Permission',
       regionId: 'RegionId',
       tables: 'Tables',
+      uri: 'Uri',
     };
   }
 
@@ -218,6 +227,7 @@ export class SendChatMessageRequestDataSource extends $dara.Model {
       permission: SendChatMessageRequestDataSourcePermission,
       regionId: 'string',
       tables: { 'type': 'array', 'itemType': 'string' },
+      uri: 'string',
     };
   }
 
@@ -239,21 +249,21 @@ export class SendChatMessageRequestDataSource extends $dara.Model {
 export class SendChatMessageRequestDataSourcesPermissionTables extends $dara.Model {
   /**
    * @remarks
-   * The list of columns that are allowed for querying in the current table. If this field is left empty, all columns can be queried. If specified, SQL statements that exceed the allowed scope are blocked. For example, syntax such as SELECT * is blocked. To ensure DataAgent analysis effectiveness, avoid specifying columns beyond the allowed scope in the DataAgent prompts, knowledge, or instructions modules. Otherwise, unauthorized SQL statements may be generated and blocked, which reduces DataAgent analysis speed and effectiveness.
+   * The list of columns that are allowed to be queried in the current table. If this parameter is left empty, all columns can be queried. If this parameter is specified, SQL statements that query columns beyond the allowed scope, such as SELECT *, are prohibited. To ensure the analysis performance of DataAgent, make sure that the prompts, knowledge, and instructions of DataAgent do not include columns beyond the allowed scope. Otherwise, unauthorized SQL statements may be generated and blocked, which degrades the analysis speed and performance of DataAgent.
    */
   allowedColumns?: string[];
   /**
    * @remarks
-   * The list of columns that are not allowed for querying in the current table. If this field is left empty, all columns **can be queried**. If specified, SQL statements that exceed the allowed scope are blocked. For example, syntax such as SELECT * is blocked.  
+   * The list of columns that are not allowed to be queried in the current table. If you leave this field empty, all columns **can be queried**. If you specify this field, SQL statements that query columns beyond the allowed scope, such as `SELECT *`, will be blocked.  
    * 
-   * If both the disallowed list and the allowed list are configured, the disallowed list takes higher priority. For example, if Table 1 has columns A, B, C, and D, and columns A and B are configured as not queryable while columns B and C are configured as queryable, the final result is that only column C is queryable.
+   * If both the disallowed list and the allowed list are configured, the disallowed list takes precedence. For example, if Table 1 has columns A, B, C, and D, and you configure columns A and B as not allowed, while configuring columns B and C as allowed, only column C is ultimately allowed to be queried.
    * 
-   * To ensure DataAgent analysis effectiveness, avoid specifying columns beyond the allowed scope in the DataAgent prompts, knowledge, or instructions modules. Otherwise, unauthorized SQL statements may be generated and blocked, which reduces DataAgent analysis speed and effectiveness.
+   * To ensure the analysis performance of DataAgent, make sure that the prompts, knowledge, and instructions modules of DataAgent do not include columns beyond the allowed scope. Otherwise, unauthorized SQL statements may be generated and blocked, which degrades the analysis speed and performance of DataAgent.
    */
   disallowedColumns?: string[];
   /**
    * @remarks
-   * The required row filter condition for the current table. If this field is left empty, it is ignored. If specified, all SQL statements involving this table are validated to check whether they carry the filter field and whether the WHERE condition meets the constraints. SQL statements that do not meet the constraints are rejected. Ensure the validation condition format is correct.
+   * The row filter condition that must be included for the current table. If you leave this field empty, it is ignored. If you specify this field, the system checks whether all SQL statements involving this table include the filter column and whether the WHERE clause meets the constraints. SQL statements that do not meet the constraints will be rejected. Pay attention to the format of the validation condition.
    * 
    * @example
    * region = \\"east\\"
@@ -261,7 +271,7 @@ export class SendChatMessageRequestDataSourcesPermissionTables extends $dara.Mod
   requiredRowFilter?: string;
   /**
    * @remarks
-   * The table name to which the permission constraint rule applies.
+   * The name of the table to which the permission constraint rules apply.
    * 
    * @example
    * sample_table
@@ -303,7 +313,7 @@ export class SendChatMessageRequestDataSourcesPermissionTables extends $dara.Mod
 export class SendChatMessageRequestDataSourcesPermission extends $dara.Model {
   /**
    * @remarks
-   * The table-level permission constraints for querying the current data source. Each item in the list represents the permission constraints for a table.
+   * The table-level permission constraints for querying the current data source. Each item in the list represents the permission constraints for a specific table.
    */
   tables?: SendChatMessageRequestDataSourcesPermissionTables[];
   static names(): { [key: string]: string } {
@@ -333,7 +343,7 @@ export class SendChatMessageRequestDataSourcesPermission extends $dara.Model {
 export class SendChatMessageRequestDataSources extends $dara.Model {
   /**
    * @remarks
-   * Deprecated. You do not need to specify this field.
+   * **[Deprecated]** You do not need to specify this field.
    * 
    * @example
    * 123
@@ -341,7 +351,7 @@ export class SendChatMessageRequestDataSources extends $dara.Model {
   dataSourceId?: string;
   /**
    * @remarks
-   * The data source type. Valid values: remote_data_center, database. These values indicate that the analysis is performed on a file or a database.
+   * The data source type. Valid values: remote_data_center and database, which indicate that the analysis is based on a file or a database, respectively.
    * 
    * @example
    * remote_data_center
@@ -349,7 +359,7 @@ export class SendChatMessageRequestDataSources extends $dara.Model {
   dataSourceType?: string;
   /**
    * @remarks
-   * Deprecated. You do not need to specify this field.
+   * **[Deprecated]** You do not need to specify this field.
    * 
    * @example
    * test_db
@@ -357,7 +367,7 @@ export class SendChatMessageRequestDataSources extends $dara.Model {
   database?: string;
   /**
    * @remarks
-   * The database name.
+   * The name of the database.
    * 
    * @example
    * mydatabase
@@ -365,7 +375,7 @@ export class SendChatMessageRequestDataSources extends $dara.Model {
   dbName?: string;
   /**
    * @remarks
-   * The ID of the database in Data Management.
+   * The ID of the database in Data Management (DMS).
    * 
    * @example
    * 123****
@@ -373,7 +383,7 @@ export class SendChatMessageRequestDataSources extends $dara.Model {
   dmsDatabaseId?: string;
   /**
    * @remarks
-   * The ID of the instance in Data Management.
+   * The ID of the instance in DMS.
    * 
    * @example
    * 248*****
@@ -397,7 +407,7 @@ export class SendChatMessageRequestDataSources extends $dara.Model {
   fileId?: string;
   /**
    * @remarks
-   * Deprecated. You do not need to specify this field.
+   * **[Deprecated]** You do not need to specify this field.
    * 
    * @example
    * localhost
@@ -405,7 +415,7 @@ export class SendChatMessageRequestDataSources extends $dara.Model {
   location?: string;
   /**
    * @remarks
-   * The permission constraints for querying the current data source. The permission constraint feature is available through a canary release. This field does not take effect for users who are not included in the canary release.
+   * The permission constraints for querying the current data source. The permission constraint feature is in canary release. This field does not take effect for users outside the canary release scope.
    */
   permission?: SendChatMessageRequestDataSourcesPermission;
   /**
@@ -418,9 +428,17 @@ export class SendChatMessageRequestDataSources extends $dara.Model {
   regionId?: string;
   /**
    * @remarks
-   * The list of table names to analyze.
+   * The list of names of the tables to be analyzed.
    */
   tables?: string[];
+  /**
+   * @remarks
+   * The data source resource identifier.
+   * 
+   * @example
+   * datalake://abc/def
+   */
+  uri?: string;
   static names(): { [key: string]: string } {
     return {
       dataSourceId: 'DataSourceId',
@@ -435,6 +453,7 @@ export class SendChatMessageRequestDataSources extends $dara.Model {
       permission: 'Permission',
       regionId: 'RegionId',
       tables: 'Tables',
+      uri: 'Uri',
     };
   }
 
@@ -452,6 +471,7 @@ export class SendChatMessageRequestDataSources extends $dara.Model {
       permission: SendChatMessageRequestDataSourcesPermission,
       regionId: 'string',
       tables: { 'type': 'array', 'itemType': 'string' },
+      uri: 'string',
     };
   }
 
@@ -473,11 +493,11 @@ export class SendChatMessageRequestDataSources extends $dara.Model {
 export class SendChatMessageRequestSessionConfigPermissionConfig extends $dara.Model {
   /**
    * @remarks
-   * The default action for table-level permissions. This parameter controls whether tables that are not configured in DataSources.[item].Permission can be queried. Valid values: allow, deny.
+   * The default behavior for table-level permissions. This parameter controls whether tables that are not configured in DataSources.[item].Permission can be queried. Valid values: `allow` and `deny`.
    * 
-   * - allow (default): works in blacklist mode. By default, all tables can be queried, and the actual permissions are subject to the permissions configured on the Data Management side. Row-level and column-level permissions are enforced only when you configure **row-level and column-level** permissions in DataSources.[item].Permission.
+   * - `allow`: the default value. This value indicates that the blacklist mode is used. By default, all tables can be queried, and the actual permissions are subject to the permissions configured in DMS. Only when you configure **row-level and column-level** permissions in DataSources.[item].Permission, the row-level and column-level permissions are used for access control.
    * 
-   * - deny (must be manually specified): works in whitelist mode. By default, no tables can be queried. A table can be queried only when you configure permissions for it in DataSources.[item].Permission. You can grant full access to a table by not configuring any row-level or column-level restrictions.
+   * - `deny`: This value indicates that the whitelist mode is used. You must manually specify this value. By default, no tables can be queried. A table can be queried only when you configure permissions for the table in DataSources.[item].Permission. You can grant full access to a table by not configuring any row-level or column-level restrictions.
    * 
    * @example
    * allow
@@ -507,7 +527,7 @@ export class SendChatMessageRequestSessionConfigPermissionConfig extends $dara.M
 export class SendChatMessageRequestSessionConfig extends $dara.Model {
   /**
    * @remarks
-   * The custom agent ID. A custom agent is an entity used to customize the analysis process. You can create one in the DataAgent console or by calling the CreateCustomAgent operation. The custom agent ID is a string that starts with `ca-`.
+   * The ID of the custom agent. A custom agent is an entity used to customize the analysis process. You can create a custom agent in the DataAgent console or by calling the CreateCustomAgent operation. The ID of a custom agent must start with `ca-`.
    * 
    * @example
    * ca-asfkjhqwe***aesrfqa
@@ -539,7 +559,7 @@ export class SendChatMessageRequestSessionConfig extends $dara.Model {
   kbUuidList?: string[];
   /**
    * @remarks
-   * Currently only Chinese and English are supported. The default value is Chinese. Only uppercase values are supported.
+   * The language. Only Chinese and English are supported. The default value is Chinese. Only uppercase letters are supported.
    * 
    * @example
    * ENGLISH
@@ -556,9 +576,9 @@ export class SendChatMessageRequestSessionConfig extends $dara.Model {
   /**
    * @remarks
    * The mode. Valid values:
-   *  - **ASK_DATA**: data query mode.
-   *  - **ANALYSIS**: analysis mode.
-   *  - **INSIGHT**: insight mode.
+   *  - **ASK_DATA**: the data query mode.
+   *  - **ANALYSIS**: the analysis mode.
+   *  - **INSIGHT**: the insight mode.
    * 
    * @example
    * ANALYSIS
@@ -566,12 +586,12 @@ export class SendChatMessageRequestSessionConfig extends $dara.Model {
   mode?: string;
   /**
    * @remarks
-   * The session level data permission settings. If this parameter is set multiple times across multiple turns within the same session, the last setting takes effect.
+   * The data permission settings at the session level. If you configure this parameter multiple times in multi-turn conversations within the same session, the last configuration prevails.
    */
   permissionConfig?: SendChatMessageRequestSessionConfigPermissionConfig;
   /**
    * @remarks
-   * Specifies whether to enable the plan. Valid values: disable, enable, force. Default value: enable.
+   * Specifies whether to enable the plan feature. Valid values: `disable`, `enable`, and `force`. Default value: `enable`.
    * 
    * @example
    * disable
@@ -579,7 +599,7 @@ export class SendChatMessageRequestSessionConfig extends $dara.Model {
   planMode?: string;
   /**
    * @remarks
-   * The text of up to 64 characters that is used as a watermark in the generated PDF report.
+   * The watermark text. You can enter up to 64 characters. The text is used to add a watermark to the generated PDF report.
    * 
    * @example
    * sample-watermark
@@ -686,7 +706,7 @@ export class SendChatMessageRequestSessionConfig extends $dara.Model {
 export class SendChatMessageRequestTaskConfigReportConfig extends $dara.Model {
   /**
    * @remarks
-   * The prompt that the report must follow.
+   * The prompt that must be followed for the current report.
    * 
    * @example
    * generate a report
@@ -702,7 +722,7 @@ export class SendChatMessageRequestTaskConfigReportConfig extends $dara.Model {
   reportTheme?: string;
   /**
    * @remarks
-   * The service type. Valid values: TextReport and WebReport, which indicate that the task generates a text report or a web report. Currently, only WebReport is supported.
+   * The service type. Valid values: TextReport and WebReport, which indicate that the current task generates a text report or a web report, respectively. Only WebReport is supported.
    * 
    * @example
    * WebReport
@@ -736,7 +756,7 @@ export class SendChatMessageRequestTaskConfigReportConfig extends $dara.Model {
 export class SendChatMessageRequestTaskConfig extends $dara.Model {
   /**
    * @remarks
-   * The configuration of the report rule. Only when MesageType is set to REPORT, a report task is executed based on this configuration.
+   * The configuration of the report rules. A report task is executed based on this configuration only when MessageType is set to REPORT.
    */
   reportConfig?: SendChatMessageRequestTaskConfigReportConfig;
   static names(): { [key: string]: string } {
@@ -766,7 +786,7 @@ export class SendChatMessageRequestTaskConfig extends $dara.Model {
 export class SendChatMessageRequest extends $dara.Model {
   /**
    * @remarks
-   * **[Optimized]** This field is now automatically obtained by the backend. You do not need to specify this field.
+   * **[Optimized]** This field is now automatically retrieved in the background. You do not need to specify it.
    * 
    * @example
    * agent_***
@@ -774,7 +794,7 @@ export class SendChatMessageRequest extends $dara.Model {
   agentId?: string;
   /**
    * @remarks
-   * **[Optimized]** This field is now automatically obtained by the backend. You do not need to specify this field when calling the API.
+   * **[Optimized]** This field is now automatically retrieved in the background. You do not need to specify it when calling the API.
    * 
    * @example
    * cn-hangzhou
@@ -782,7 +802,7 @@ export class SendChatMessageRequest extends $dara.Model {
   DMSUnit?: string;
   /**
    * @remarks
-   * The data source information. This parameter can be left empty. This parameter supports only one data source. Use the DataSources parameter instead.
+   * The data source information. This parameter can be left empty. You can specify only one data source for this parameter. Use the DataSources parameter instead.
    * 
    * @example
    * null
@@ -795,7 +815,7 @@ export class SendChatMessageRequest extends $dara.Model {
   dataSources?: SendChatMessageRequestDataSources[];
   /**
    * @remarks
-   * The message content to send to the Agent.
+   * The content of the message sent to the agent.
    * 
    * This parameter is required.
    * 
@@ -805,15 +825,15 @@ export class SendChatMessageRequest extends $dara.Model {
   message?: string;
   /**
    * @remarks
-   * The message type. Default value: `[primary]`.  
+   * The message type. Default value: `primary`.  
    * 
-   * - For regular interactions with the Agent, set the message type to `[primary]`.
+   * - In normal interactions with the agent, the message type is `primary`.
    * 
-   * - When the message is a response to the Agent\\"s Human-in-Loop question, set the type to `[additional]`.
+   * - When the message is a response to a human-in-the-loop question from the agent, the type must be `additional`.
    * 
-   * - When the message is intended to trigger report generation, set the type to `[report]`.
+   * - When the message is intended to trigger report generation, the type must be `report`.
    * 
-   * - When the message is intended to cancel the current session, set the type to `[cancel]`.
+   * - When the message is intended to cancel the current session, the type must be `cancel`.
    * 
    * @example
    * primary
@@ -821,7 +841,7 @@ export class SendChatMessageRequest extends $dara.Model {
   messageType?: string;
   /**
    * @remarks
-   * The parent session ID.
+   * The ID of the parent session.
    * 
    * @example
    * 20qrliuoo7p2vlsfg*****
@@ -829,15 +849,15 @@ export class SendChatMessageRequest extends $dara.Model {
   parentSessionId?: string;
   /**
    * @remarks
-   * This field is required when the message type is `additional`. Specify the specific question that the Agent asks the user through Human-in-Loop.
+   * Required when the message type is `additional`. Specifies the specific question asked by the agent to the user through human-in-the-loop.
    * 
    * @example
-   * Provide the criteria for calculating GMV
+   * Provide the calculation criteria for GMV
    */
   question?: string;
   /**
    * @remarks
-   * The quoted content. This is typically used during interactions with the Agent.
+   * The quoted content. This is typically used when interacting with the agent.
    * 
    * @example
    * {"version":"v0"}
@@ -847,9 +867,9 @@ export class SendChatMessageRequest extends $dara.Model {
    * @remarks
    * **Important**
    * 
-   * When this message is a reply to an Agent message (for example, the Agent asks a clarifying question through ASK_HUMAN), set reply_to to the exact Checkpoint sequence number carried in that Agent message. If this message is not a targeted reply, such as requesting the Agent to perform further in-depth analysis after analysis is complete, you can leave reply_to empty or set it to "0".  
+   * When this message is a reply to an agent message, such as an agent asking for clarification through ASK_HUMAN, `reply_to` must exactly match the checkpoint sequence number carried by that agent message. If this message is not a targeted reply, such as requesting the agent to perform further in-depth analysis after the initial analysis is complete, you can leave `reply_to` empty or set it to "0".  
    * 
-   * This field affects how the Agent decides to process the message. Incorrect values may lead to analysis results that do not meet expectations.
+   * This field affects how the agent decides to process the message. Passing an incorrect value may lead to suboptimal analysis results.
    * 
    * @example
    * 0
@@ -857,7 +877,7 @@ export class SendChatMessageRequest extends $dara.Model {
   replyTo?: string;
   /**
    * @remarks
-   * The special configuration for the current session. For the same session, only the configuration included in the first SendMessage call takes effect.
+   * The special configurations for the current session. For the same session, only the configurations specified in the first SendMessage call take effect.
    * 
    * **if can be null:**
    * true
@@ -865,10 +885,10 @@ export class SendChatMessageRequest extends $dara.Model {
   sessionConfig?: SendChatMessageRequestSessionConfig;
   /**
    * @remarks
-   * The session ID. This is an optional field used for multi-turn sessions.
-   * - You can start a session without specifying this field. The response includes the SessionID of the current session.
+   * The session ID. This optional field is used for multi-turn sessions.
+   * - You can start a session without specifying this field. The response will include the session ID for the current session.
    * - You can also manually create a session ID by calling the CreateDataAgentSession operation and include the ID when initiating a session.
-   * - For multi-turn conversations (such as follow-up questions or confirming execution plans), specify the SessionID returned by the previous SendChatMessage call.
+   * - If you need multi-turn conversations, such as follow-up questions or confirming execution plans, specify the session ID returned by the previous SendChatMessage operation in this operation.
    * 
    * @example
    * sess_***
@@ -881,7 +901,7 @@ export class SendChatMessageRequest extends $dara.Model {
   taskConfig?: SendChatMessageRequestTaskConfig;
   /**
    * @remarks
-   * The OSS bucket of the user. If this parameter is not specified, the analysis data is securely stored in built-in storage.
+   * The Object Storage Service (OSS) bucket of the user. If this parameter is left empty, the analysis process is securely stored in the built-in storage.
    * 
    * @example
    * my-bucket