As a Workspace Administrator, you can configure workspace-level defaults for code templates, scheduling, and security in Data Studio. These settings help standardize node creation, automate task scheduling, and control code access across your team.
Limitations
Only Workspace Administrators can configure system settings. To grant a user this access, assign them the Workspace Administrator role. For details, see Add a workspace member and manage member roles and permissions.
Code template changes and default scheduling configurations apply only to new auto triggered tasks created after the change.
Security settings apply only to the current workspace.
Access the settings page
Go to the Workspaces page. In the top navigation bar, select a region. Find the workspace and click Shortcuts > Data Studio in the Actions column.
At the bottom of the left navigation pane, click
> DataStudio Settings to open the Settings page.
Configure code templates
A code template defines the default content pre-filled when you create a node of a specific type. It can include the node type, creator, and creation time, making it easier to standardize node management at the business layer.
Set a code template
On the Scheduling Settings tab, find the target Code Type and click Edit.
Modify the Code Template as needed, then click Save and confirm.
To verify the change, create a new node of the corresponding type and check its default content.
Template variables
Use the following variables in a code template to auto-populate node metadata at creation time:
Variable | Description |
| The account that created the node. Populated automatically at node creation. |
| The time the node was created. Populated automatically at node creation. |
Supported node types
Code templates are supported for the following node types:
Engine | Node types |
MaxCompute | MaxCompute Script node, MaxCompute SQL node, MaxCompute MR node, PyODPS 2 node, PyODPS 3 node |
Hologres | |
EMR | EMR Hive node, EMR Impala node, EMR Presto node, EMR Shell node, EMR Spark SQL node, EMR Trino node |
CDH | CDH Hive node, CDH Spark SQL node, CDH Presto node, CDH Impala node |
ClickHouse | |
General |
Set default scheduling configurations
To run auto triggered tasks on a schedule, enable scheduling and configure the default resource groups and rerun behavior. These defaults apply to all new auto triggered tasks in the workspace. Existing tasks retain their individual configurations.
On the Scheduling Settings tab, click Modify, configure the following settings, and then click Save Configuration.
Scheduling basics
Setting | Description |
Enable Scheduling | When enabled, auto triggered tasks are automatically scheduled and run. When disabled, instances already generated for the current day continue to run normally, but no new recurring instances are generated starting the following night. |
Scheduling Time Zone | The time zone used for timed scheduling. Corresponds to the region where the workspace is located. DataWorks supports time zone modification in some regions. For details, see Regions that support scheduling time zone modification and How to switch time zones. |
Timed Scheduling Time | The time at which timed scheduling runs. Defaults to a randomly generated time between |
Scheduling Resource Group | The default resource group for scheduled tasks. |
Data Integration Resource Group | The default resource group for data integration tasks. |
Rerun behavior
Configure how the workspace handles failed auto triggered tasks by default. Individual tasks can override these settings with their own configurations.
Setting | Description | Range |
Rerun Property | The default rerun policy. When set to allow reruns, make sure tasks are idempotent to avoid data quality issues from multiple reruns. | — |
Number Of Automatic Reruns | The number of times a failed task is automatically rerun. A value of 1 means the task is rerun once after the first failure. | 1–10 |
Rerun Interval | The wait time between consecutive reruns. | 1–30 minutes |
Configure security and other settings
The Security and Other Settings tab provides controls for code isolation, publish-time checks, and dependency validation. All settings apply only to the current workspace.
Enable code and log isolation
When enabled, users who are not members of this workspace cannot view its task code or run logs. To grant access, an administrator must add the user as a workspace member. For details, see Add a workspace member and manage member roles and permissions.
Enable baseline display upon task submission
When enabled, the baseline associated with a job is shown when you publish the job. This helps you assess whether changes to the job affect the baseline job's scheduled execution.
Enable mandatory smoke testing
When enabled, a smoke test must pass before a job can be published. For details, see Smoke Testing.
Enable the code comparison feature
When enabled, you must complete the Compare Content review before you can publish a task.
Enable the dependency check feature
When enabled, DataWorks automatically checks whether the upstream dependencies configured for a node match the results of the code kinship analysis before the task is published. The task can only be published if they match. For details, see Scheduling Dependencies.