Configuring Incoming Parameters for Tasks
This procedure is only applicable to tasks where parameters have been assigned or in the underlying data flows of integration tasks.
Assigned parameters have default values that are used during pipeline design time and runtime.
If you want, you can override the default value of an incoming parameter at design time and runtime. You can also override the default value of a parameter that's used within an expression in an incoming parameter.
To override a value, you can directly set another value at design time, or add a pipeline user-defined parameter for the value to be set at runtime. If applicable, you can also assign to the input a system parameter value or a value of an output from a previous operator.
- On the canvas of a pipeline, select the task for which you want to view or configure values for incoming parameters.
- In the Properties panel for the selected task, click Configuration.
-
Next to Incoming parameters configured, review the
number of configured and available incoming parameters.
For example, 0/4 means that four incoming parameters are available in this task, and none have been reconfigured.
- Click Configure next to Incoming parameters configured.
-
On the Configure incoming parameters page, review the
inputs that can be reconfigured.
An input has a Default value. If the incoming parameter is reconfigured, the input has a Configured value. A configured value can be a user-defined parameter name with the configured value shown in parentheses.
- (Optional)
In the row of the parameter type and value that you want to reconfigure, click Configure.
If the incoming parameter is already reconfigured, click Edit to change the configured value, or click Clear to remove the value.
-
On the Configure incoming parameter for <type> page that displays for the selected parameter, perform one of the input configuration options, and then click Done to return to the previous page.
Note the following when configuring incoming parameters:
-
If the incremental extract strategy for a BICC source is configured to use a date that's managed by the Data Integration system parameter
SYS.LAST_LOAD_DATE
, you're not allowed to change the date value during design time. -
If the incremental extract strategy for a BICC source is configured to use a parameterized last extract date that you have added, you can change the date value during design time and runtime.
-
If a parameterized target data entity is configured to use the Merge strategy, you can change the Merge key selection.
- For a parameterized data asset that requires a staging location: If you select a data asset that doesn't have a default staging location specified in that data asset, Data Integration displays a warning notification. When you see the notification, choose one of the following options:
- Update that data asset by adding a default staging location.
- Choose a different data asset that has a default staging location.
-
For a parameterized OCI Data Flow task:
-
With a parameterized driver or executor shape, the OCPUs and memory values are ignored if a non-flexible shape is configured in the parameter. The OCPUs and memory values are used only when you configure a flexible shape as the parameter value.
-
With parameterized OCPUs and memory values for a flexible shape, ensure that you specify a value that's in the acceptable range of values for that property. The acceptable values for OCPUs depend on the flexible shape. The acceptable values for memory depend on the OCPUs value.
-
Input option Description Assign a value Override the default value for this parameter by specifying a value directly. How you specify a value depends on the incoming parameter type.
For example, enter a value in a field for a numeric, string, or date type, but use a menu to select a value for a parameter of type data asset, connection, schema, and data entity. For a condition or expression type, use the condition or expression editor.
Previous operator output To use an output value from a previous operator as input for this parameter, select a value from the list of available outputs.
Only outputs of the same type as the incoming parameter are available for selection.
For example, if an incoming parameter is STRING, then only SYS.STATUS and SYS.ERROR_MESSAGE are available.
Assign a parameter Specify a pipeline parameter to set a different value when the pipeline is run. You can assign a user-defined parameter or a system parameter as the input of the incoming parameter.
-
Use user defined parameters: Select an existing user-defined parameter from the list of available parameters, if any. Only parameters of the same type as the incoming parameter are available for selection.
If applicable, click Add parameter to create a parameter in the pipeline for selection. In the Add parameter panel that appears, enter a name and optional description for the parameter. The data type can't be changed, which is the same as the type of the incoming parameter. How you define the rest of the fields for a parameter depends on the incoming type. To create the parameter, click Add. By default, the newly added user-defined parameter is selected.
-
Use system parameters: Select a system parameter from the list of available parameters generated by the runtime system, if any. Only system parameters of the same type as the incoming parameter are available for selection. OCID system parameters are treated as STRING.
For example, if an incoming parameter is VARCHAR, then only TASK_RUN_NAME, TASK_RUN_KEY, PARENT_TASK_RUN_KEY, TASK_SCHEDULE_TIMEZONE, PIPELINE_NAME, and PIPELINE_IDENTIFIER are available.
-
-
On the Configure incoming parameters page, review the
Default value and Configured
value for the parameter you just reconfigured.
A configured value can be a user-defined parameter name with the configured value shown in parentheses.
- Repeat steps 6 and 7 to configure other input values, as needed. You can also click Edit or Clear to change a previously configured value.
- On the Configure incoming parameters page, click Configure when you have finished configuring values for incoming parameters in the task.