Scheduling parameters are automatically replaced with specific values based on the data timestamps of nodes and value formats of scheduling parameters. This enables dynamic parameter configuration for node scheduling. This topic describes how to configure and use scheduling parameters. This topic also describes how to perform smoke testing to check whether the scheduling parameters configured for an ODPS SQL node work as expected.
Process of configuring and using scheduling parameters
To configure and use scheduling parameters, perform the following steps:- Go to the Parameters section of the Properties tab on the configuration tab of a desired node. For more information, see Go to the Parameters section of the Properties tab.
- Configure scheduling parameters for the node. For more information, see Configure scheduling parameters.
- Test whether the scheduling parameters work as expected. For more information, see Test scheduling parameters.
- Check the configurations of the scheduling parameters in the production environment. For more information, see View the configurations of scheduling parameters in Operation Center in the production environment.
Go to the Parameters section of the Properties tab
Configure scheduling parameters
In the Parameters section, you can add parameters or load existing parameters in the code of the node
on a visual interface. Alternatively, you can use expressions to define scheduling
parameters.
Method to define scheduling parameters | Feature | Description | Screenshot |
---|---|---|---|
Visual interface | Add Parameter | You can click Add Parameter to configure multiple scheduling parameters for a node.
DataWorks provides the following scheduling parameters:
For more information about scheduling parameters, see Overview of scheduling parameters.
|
![]() |
Load Parameters in Code | After you click Load Parameters in Code, DataWorks identifies the variable names defined
in the code of the current node and adds the identified variable names to the Parameters
section.
Note
|
![]() |
|
Expressions | Define by expression | By default, the system provides a visual interface on which you can configure scheduling
parameters for a node. You can also click Define by expression to configure scheduling parameters by using an expression.
Note
|
![]() |
Note If you use the built-in variable
${bdp.system.bizdate}
or ${bdp.system.cyctime}
in the code of a node, you do not need to assign values to the variable in the Parameters section.
Test scheduling parameters
After you configure scheduling parameters, you must click the
icon to perform smoke testing in the development environment. You can configure a
data timestamp to simulate the scenario in which the node is scheduled to run. Then,
you can check whether the scheduling parameters work as expected.
After the smoke testing is complete, click the
icon to check whether the results in smoke testing logs meet your expectations.

Note When you perform smoke testing in the development environment, you are charged for
the generated test instances. For more information about instance pricing, see Shared resource group for scheduling and Billing of exclusive resource groups for scheduling (subscription).



Note
- Before you click the
or
icon in the toolbar to run a node, you must manually assign constants to the variables that you want to reference in the code of the node. In this case, you cannot check whether the configured scheduling parameters work as expected.
- After you modify the code of a node, you must click the
icon and then the
icon to save the modifications and commit the node to the development environment. Otherwise, you cannot perform smoke testing on the node in the development environment.
View the configurations of scheduling parameters in Operation Center in the production environment
To prevent unexpected configurations of scheduling parameters from affecting the running
of an auto triggered node, we recommend that you check the configurations of the scheduling
parameters for the auto triggered node on the Cycle Task page in Operation Center in the production environment after the auto triggered node
is deployed. For more information about auto triggered nodes, see View and manage auto triggered nodes.

Note If the scheduling parameters of an auto triggered node are not configured as expected
or you cannot find the auto triggered node in Operation Center, check whether the
node is successfully deployed. For more information about how to deploy nodes, see Deploy nodes.
Example on how to configure scheduling parameters
This section describes how to perform smoke testing in the development environment
to check whether the scheduling parameters of a node work as expected. In this section,
an ODPS SQL node is used. After the node is deployed, you can view the configurations
of the scheduling parameters in Operation Center in the production environment.
Note For more information about how to configure scheduling parameters for different types
of nodes, see Configure scheduling parameters for different types of nodes.