|
@@ -6,14 +6,23 @@ Parameters configured on the task definition page, the scope of this parameter i
|
|
|
|
|
|
## Usage
|
|
|
|
|
|
-Usage of local parameters is: at the task define page, click the '+' beside the 'Custom Parameters' and fill in the key and value to save:
|
|
|
+Usage of local parameters is: at the task define page, click the '+' beside the 'Custom Parameters' and fill in the key and value to save.
|
|
|
|
|
|
-<p align="center">
|
|
|
- <img src="/img/supplement_local_parameter_en.png" width="80%" />
|
|
|
-</p>
|
|
|
+## Examples
|
|
|
|
|
|
-<p align="center">
|
|
|
- <img src="/img/global_parameter_en.png" width="80%" />
|
|
|
-</p>
|
|
|
+This example shows how to use local parameters to print the current date. Create a Shell task and write a script with the content `echo ${dt}`. Click **custom parameter** in the configuration bar, and the configuration is as follows:
|
|
|
|
|
|
-If you want to call the [built-in parameter](built-in.md) in the local parameters, fill in thevalue of built-in parameters in `value`. As in the above figure, `${biz_date}` and `${curdate}`.
|
|
|
+
|
|
|
+
|
|
|
+Parameters:
|
|
|
+
|
|
|
+- dt: indicates the parameter name
|
|
|
+- in: IN indicates that local parameters can only be used on the current node, and OUT indicates that local parameters can be transmitted to the downstream
|
|
|
+- DATE: indicates the DATE of the data type
|
|
|
+- $[YYYY-MM-DD] : indicates a built-in parameter derived from a user-defined format
|
|
|
+
|
|
|
+Save the workflow and run it. View Shell task's log.
|
|
|
+
|
|
|
+
|
|
|
+
|
|
|
+> Note: The local parameter can be used in the workflow of the current task node. If it is set to OUT, it can be passed to the downstream workflow. Please refer to: [Parameter Context](context.md)
|