@alicloud/dms20250414 4.3.0 → 4.3.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 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.
+   * The list of fields that are allowed to be queried in the current table. If you do not specify this parameter, all fields can be queried. If you specify this parameter, SQL statements that query fields outside the allowed range, such as the `SELECT *` syntax, will be blocked. To ensure the analysis performance of DataAgent, make sure that the prompts, knowledge, and instructions modules of DataAgent do not include fields outside the allowed range. 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 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.  
+   * The list of fields that are prohibited from being queried in the current table. If you do not specify this parameter, all fields **can be queried**. If you specify this parameter, SQL statements that query fields outside the allowed range, such as the `SELECT *` syntax, will be blocked.  
    * 
-   * 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.
+   * If both the prohibited list and the allowed list are configured, the prohibited list takes precedence. For example, if Table 1 has columns A, B, C, and D, and you configure columns A and B as non-queryable while configuring columns B and C as queryable, only column C is ultimately queryable.
    * 
-   * 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.
+   * To ensure the analysis performance of DataAgent, make sure that the prompts, knowledge, and instructions modules of DataAgent do not include fields outside the allowed range. Otherwise, unauthorized SQL statements may be generated and blocked, which degrades the analysis speed and performance of DataAgent.
    */
   disallowedColumns?: string[];
   /**
    * @remarks
-   * 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.
+   * The row filter condition that must be included for the current table. If you do not specify this parameter, it is ignored. If you specify this parameter, the system checks whether all SQL statements involving this table include the filter field and whether the WHERE condition 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\\"
@@ -107,7 +107,7 @@ export class SendChatMessageRequestDataSource extends $dara.Model {
   dataSourceId?: string;
   /**
    * @remarks
-   * The data source type. Valid values: `remote_data_center` and `database`. `remote_data_center` indicates a file, and `database` indicates a database.
+   * The data source type. Valid values: remote_data_center and database, which indicate that the analysis target is a file or a database, respectively.
    * 
    * @example
    * remote_data_center
@@ -147,7 +147,7 @@ export class SendChatMessageRequestDataSource extends $dara.Model {
   dmsInstanceId?: string;
   /**
    * @remarks
-   * The database engine type.
+   * The type of the database.
    * 
    * @example
    * mysql
@@ -155,7 +155,7 @@ export class SendChatMessageRequestDataSource extends $dara.Model {
   engine?: string;
   /**
    * @remarks
-   * The ID of the file.
+   * The file ID.
    * 
    * @example
    * 35****
@@ -184,7 +184,7 @@ export class SendChatMessageRequestDataSource extends $dara.Model {
   regionId?: string;
   /**
    * @remarks
-   * The list of names of the tables to be analyzed.
+   * The list of table names to be analyzed.
    */
   tables?: string[];
   /**
@@ -249,21 +249,21 @@ export class SendChatMessageRequestDataSource extends $dara.Model {
 export class SendChatMessageRequestDataSourcesPermissionTables extends $dara.Model {
   /**
    * @remarks
-   * 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.
+   * The list of columns that are allowed to be queried in the current table. If you do not specify this parameter, all columns can be queried. If you specify this parameter, SQL statements that query columns beyond the allowed scope are blocked. For example, syntax such as SELECT * is blocked. 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 are generated and blocked, which reduces the analysis speed and performance of DataAgent.
    */
   allowedColumns?: string[];
   /**
    * @remarks
-   * 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.  
+   * The list of fields that are prohibited from being queried in the current table. If you do not specify this parameter, all fields **can be queried**. If you specify this parameter, SQL statements that query fields outside the allowed range, such as the `SELECT *` syntax, will be blocked.  
    * 
-   * 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.
+   * If both the prohibited list and the allowed list are configured, the prohibited list takes precedence. For example, if Table 1 has columns A, B, C, and D, and you configure columns A and B as non-queryable while configuring columns B and C as queryable, only column C is ultimately queryable.
    * 
-   * 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.
+   * To ensure the analysis performance of DataAgent, make sure that the prompts, knowledge, and instructions modules of DataAgent do not include fields outside the allowed range. Otherwise, unauthorized SQL statements may be generated and blocked, which degrades the analysis speed and performance of DataAgent.
    */
   disallowedColumns?: string[];
   /**
    * @remarks
-   * 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.
+   * The row filter condition that must be included for the current table. If you do not specify this parameter, it is ignored. If you specify this parameter, the system checks whether all SQL statements involving this table include the filter field and whether the WHERE condition 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\\"
@@ -351,7 +351,9 @@ export class SendChatMessageRequestDataSources extends $dara.Model {
   dataSourceId?: string;
   /**
    * @remarks
-   * 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.
+   * The data source type. Valid values:
+   * - remote_data_center: The analysis is performed on a file.
+   * - database: The analysis is performed on a database.
    * 
    * @example
    * remote_data_center
@@ -391,7 +393,7 @@ export class SendChatMessageRequestDataSources extends $dara.Model {
   dmsInstanceId?: string;
   /**
    * @remarks
-   * The database engine type.
+   * The type of the database.
    * 
    * @example
    * mysql
@@ -428,7 +430,7 @@ export class SendChatMessageRequestDataSources extends $dara.Model {
   regionId?: string;
   /**
    * @remarks
-   * The list of names of the tables to be analyzed.
+   * The list of table names to be analyzed.
    */
   tables?: string[];
   /**
@@ -493,11 +495,9 @@ export class SendChatMessageRequestDataSources extends $dara.Model {
 export class SendChatMessageRequestSessionConfigPermissionConfig extends $dara.Model {
   /**
    * @remarks
-   * 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`: 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`: 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.
+   * The default behavior for table-level permissions. This parameter controls whether tables not configured in DataSources.[item].Permission can be queried. Valid values:
+   * - allow: Works in blacklist mode. This is the default value. By default, all tables can be queried, and the actual permissions are subject to the permissions configured in DMS. Only when you configure **row- and column-level** permissions in DataSources.[item].Permission will row- and column-level permissions be enforced.
+   * - deny: Works in whitelist mode. You must manually specify this value. 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- or column-level restrictions.
    * 
    * @example
    * allow
@@ -527,7 +527,7 @@ export class SendChatMessageRequestSessionConfigPermissionConfig extends $dara.M
 export class SendChatMessageRequestSessionConfig extends $dara.Model {
   /**
    * @remarks
-   * 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-`.
+   * The custom agent ID. A custom agent is an entity used to customize the analysis process. You can create it in the DataAgent console or by calling the CreateCustomAgent operation. A custom agent ID must be a string starting with ca-.
    * 
    * @example
    * ca-asfkjhqwe***aesrfqa
@@ -576,9 +576,9 @@ export class SendChatMessageRequestSessionConfig extends $dara.Model {
   /**
    * @remarks
    * The mode. Valid values:
-   *  - **ASK_DATA**: the data query mode.
-   *  - **ANALYSIS**: the analysis mode.
-   *  - **INSIGHT**: the insight mode.
+   * - **ASK_DATA**: Data query mode.
+   * - **ANALYSIS**: Analysis mode.
+   * - **INSIGHT**: Insight mode.
    * 
    * @example
    * ANALYSIS
@@ -586,12 +586,12 @@ export class SendChatMessageRequestSessionConfig extends $dara.Model {
   mode?: string;
   /**
    * @remarks
-   * 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.
+   * The data permission settings at the session level. If configured multiple times in multi-turn conversations within the same session, the last configuration prevails.
    */
   permissionConfig?: SendChatMessageRequestSessionConfigPermissionConfig;
   /**
    * @remarks
-   * Specifies whether to enable the plan feature. Valid values: `disable`, `enable`, and `force`. Default value: `enable`.
+   * Specifies whether to enable the plan feature. Valid values: disable, enable, and force. Default value: enable.
    * 
    * @example
    * disable
@@ -599,7 +599,7 @@ export class SendChatMessageRequestSessionConfig extends $dara.Model {
   planMode?: string;
   /**
    * @remarks
-   * The watermark text. You can enter up to 64 characters. The text is used to add a watermark to the generated PDF report.
+   * The text to be added as a watermark to the generated PDF report. The text can be up to 64 characters in length.
    * 
    * @example
    * sample-watermark
@@ -642,6 +642,14 @@ export class SendChatMessageRequestSessionConfig extends $dara.Model {
    * The list of user-specified skills.
    */
   userSpecifiedSkillList?: string[];
+  /**
+   * @remarks
+   * The default report theme ID for the current session.
+   * 
+   * @example
+   * default
+   */
+  webReportTheme?: string;
   static names(): { [key: string]: string } {
     return {
       customAgentId: 'CustomAgentId',
@@ -659,6 +667,7 @@ export class SendChatMessageRequestSessionConfig extends $dara.Model {
       skipSqlConfirm: 'SkipSqlConfirm',
       skipWebReportConfirm: 'SkipWebReportConfirm',
       userSpecifiedSkillList: 'UserSpecifiedSkillList',
+      webReportTheme: 'WebReportTheme',
     };
   }
 
@@ -679,6 +688,7 @@ export class SendChatMessageRequestSessionConfig extends $dara.Model {
       skipSqlConfirm: 'boolean',
       skipWebReportConfirm: 'boolean',
       userSpecifiedSkillList: { 'type': 'array', 'itemType': 'string' },
+      webReportTheme: 'string',
     };
   }
 
@@ -706,7 +716,7 @@ export class SendChatMessageRequestSessionConfig extends $dara.Model {
 export class SendChatMessageRequestTaskConfigReportConfig extends $dara.Model {
   /**
    * @remarks
-   * The prompt that must be followed for the current report.
+   * The prompt that the current report must follow.
    * 
    * @example
    * generate a report
@@ -714,7 +724,7 @@ export class SendChatMessageRequestTaskConfigReportConfig extends $dara.Model {
   reportPrompt?: string;
   /**
    * @remarks
-   * The report theme. Valid values: default, journal, legacy, and neobrutalism.
+   * The report theme. System themes include default, journal, legacy, and neobrutalism, which are globally available theme IDs. You can call the ListDataAgentTheme operation to obtain other available theme IDs.
    * 
    * @example
    * default
@@ -722,7 +732,10 @@ export class SendChatMessageRequestTaskConfigReportConfig extends $dara.Model {
   reportTheme?: string;
   /**
    * @remarks
-   * 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.
+   * The service type. Valid values:
+   * - TextReport: The task generates a text report.
+   * - WebReport: The task generates a web report.
+   * Currently, only WebReport is supported.
    * 
    * @example
    * WebReport
@@ -802,7 +815,7 @@ export class SendChatMessageRequest extends $dara.Model {
   DMSUnit?: string;
   /**
    * @remarks
-   * 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.
+   * The data source information. This parameter can be left empty. You can specify only one data source for this parameter. We recommend that you use the DataSources parameter instead.
    * 
    * @example
    * null
@@ -825,15 +838,12 @@ export class SendChatMessageRequest extends $dara.Model {
   message?: string;
   /**
    * @remarks
-   * The message type. Default value: `primary`.  
-   * 
-   * - In normal interactions with the agent, the message type is `primary`.
-   * 
-   * - 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, the type must be `report`.
+   * The message type. Default value: primary.
    * 
-   * - When the message is intended to cancel the current session, the type must be `cancel`.
+   * - In normal interactions with the agent, the message type is primary.
+   * - 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, the type must be report.
+   * - When the message is intended to cancel the current session, the type must be cancel.
    * 
    * @example
    * primary
@@ -841,7 +851,7 @@ export class SendChatMessageRequest extends $dara.Model {
   messageType?: string;
   /**
    * @remarks
-   * The ID of the parent session.
+   * The parent session ID.
    * 
    * @example
    * 20qrliuoo7p2vlsfg*****
@@ -849,7 +859,7 @@ export class SendChatMessageRequest extends $dara.Model {
   parentSessionId?: string;
   /**
    * @remarks
-   * Required when the message type is `additional`. Specifies the specific question asked by the agent to the user through human-in-the-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 calculation criteria for GMV
@@ -857,7 +867,7 @@ export class SendChatMessageRequest extends $dara.Model {
   question?: string;
   /**
    * @remarks
-   * The quoted content. This is typically used when interacting with the agent.
+   * The current quoted content. This is typically used during interactions with the agent.
    * 
    * @example
    * {"version":"v0"}
@@ -867,7 +877,7 @@ export class SendChatMessageRequest extends $dara.Model {
    * @remarks
    * **Important**
    * 
-   * 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".  
+   * When this message is a reply to an agent message (such as the 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. Passing an incorrect value may lead to suboptimal analysis results.
    * 
@@ -877,7 +887,7 @@ export class SendChatMessageRequest extends $dara.Model {
   replyTo?: string;
   /**
    * @remarks
-   * The special configurations for the current session. For the same session, only the configurations specified in the first SendMessage call take effect.
+   * The special configurations for the current session. For the same session, only the configurations passed during the first SendMessage call take effect.
    * 
    * **if can be null:**
    * true
@@ -885,10 +895,10 @@ export class SendChatMessageRequest extends $dara.Model {
   sessionConfig?: SendChatMessageRequestSessionConfig;
   /**
    * @remarks
-   * 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.
-   * - 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.
+   * The session ID. This is an optional field used for multi-turn sessions.
+   * - You can start a session without specifying this field, and the response will include the SessionID for the current session.
+   * - You can also manually create a session ID by calling the CreateDataAgentSession operation and include the ID when initiating the session.
+   * - If you need multi-turn conversations (such as follow-up questions or confirming execution plans), include the SessionID returned by the previous SendChatMessage operation in this API call.
    * 
    * @example
    * sess_***
@@ -901,7 +911,7 @@ export class SendChatMessageRequest extends $dara.Model {
   taskConfig?: SendChatMessageRequestTaskConfig;
   /**
    * @remarks
-   * 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.
+   * The Object Storage Service (OSS) bucket of the user. If you do not specify this parameter, the analysis process is securely stored in the built-in storage.
    * 
    * @example
    * my-bucket

package/src/models/SendChatMessageShrinkRequest.ts

@@ -21,7 +21,7 @@ export class SendChatMessageShrinkRequest extends $dara.Model {
   DMSUnit?: string;
   /**
    * @remarks
-   * 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.
+   * The data source information. This parameter can be left empty. You can specify only one data source for this parameter. We recommend that you use the DataSources parameter instead.
    * 
    * @example
    * null
@@ -44,15 +44,12 @@ export class SendChatMessageShrinkRequest extends $dara.Model {
   message?: string;
   /**
    * @remarks
-   * The message type. Default value: `primary`.  
+   * The message type. Default value: primary.
    * 
-   * - In normal interactions with the agent, the message type is `primary`.
-   * 
-   * - 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, the type must be `report`.
-   * 
-   * - When the message is intended to cancel the current session, the type must be `cancel`.
+   * - In normal interactions with the agent, the message type is primary.
+   * - 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, the type must be report.
+   * - When the message is intended to cancel the current session, the type must be cancel.
    * 
    * @example
    * primary
@@ -60,7 +57,7 @@ export class SendChatMessageShrinkRequest extends $dara.Model {
   messageType?: string;
   /**
    * @remarks
-   * The ID of the parent session.
+   * The parent session ID.
    * 
    * @example
    * 20qrliuoo7p2vlsfg*****
@@ -68,7 +65,7 @@ export class SendChatMessageShrinkRequest extends $dara.Model {
   parentSessionId?: string;
   /**
    * @remarks
-   * Required when the message type is `additional`. Specifies the specific question asked by the agent to the user through human-in-the-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 calculation criteria for GMV
@@ -76,7 +73,7 @@ export class SendChatMessageShrinkRequest extends $dara.Model {
   question?: string;
   /**
    * @remarks
-   * The quoted content. This is typically used when interacting with the agent.
+   * The current quoted content. This is typically used during interactions with the agent.
    * 
    * @example
    * {"version":"v0"}
@@ -86,7 +83,7 @@ export class SendChatMessageShrinkRequest extends $dara.Model {
    * @remarks
    * **Important**
    * 
-   * 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".  
+   * When this message is a reply to an agent message (such as the 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. Passing an incorrect value may lead to suboptimal analysis results.
    * 
@@ -96,7 +93,7 @@ export class SendChatMessageShrinkRequest extends $dara.Model {
   replyTo?: string;
   /**
    * @remarks
-   * The special configurations for the current session. For the same session, only the configurations specified in the first SendMessage call take effect.
+   * The special configurations for the current session. For the same session, only the configurations passed during the first SendMessage call take effect.
    * 
    * **if can be null:**
    * true
@@ -104,10 +101,10 @@ export class SendChatMessageShrinkRequest extends $dara.Model {
   sessionConfigShrink?: string;
   /**
    * @remarks
-   * 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.
-   * - 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.
+   * The session ID. This is an optional field used for multi-turn sessions.
+   * - You can start a session without specifying this field, and the response will include the SessionID for the current session.
+   * - You can also manually create a session ID by calling the CreateDataAgentSession operation and include the ID when initiating the session.
+   * - If you need multi-turn conversations (such as follow-up questions or confirming execution plans), include the SessionID returned by the previous SendChatMessage operation in this API call.
    * 
    * @example
    * sess_***
@@ -120,7 +117,7 @@ export class SendChatMessageShrinkRequest extends $dara.Model {
   taskConfigShrink?: string;
   /**
    * @remarks
-   * 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.
+   * The Object Storage Service (OSS) bucket of the user. If you do not specify this parameter, the analysis process is securely stored in the built-in storage.
    * 
    * @example
    * my-bucket