Within a flow, you can create and manage flow parameters, including specifying override values. From the flow menu, select Parameters. |
You specify flow parameters at the flow level. They can be invoked in any recipe within the flow.
Tip: Override values apply to all parameters in the flow that share the same name, even if they are output object parameters. |
Tip: Flow parameters can be inherited from upstream flows. For example, if you create a reference dataset that references flow parameters from its flow, those parameters are passed to the downstream flow. While you cannot change the default value for the downstream instance of the parameter, you can apply override values for all recipes in the downstream flow. |
In the Parameters tab, you can manage the flow parameters in your flow.
NOTE: Non-flow parameters cannot be edited or deleted from the Parameters tab. These parameters must be modified in the interface for the object to which they apply. Overrides can be applied to these types of parameters through the Overrides tab. |
Parameters for plans: When reviewing parameters for your plan, you may notice that a parameter has multiple values:
NOTE: When a parameter has conflicting values from objects in a plan task, you must fix them by applying a single override value. If these values are not fixed, then the plan fails to execute. |
Parameters tab |
To delete a parameter, hover over its entry and click the Trash icon.
Deleting a parameter cannot be undone. When you delete a parameter, all recipe steps that reference it are broken. |
Tip: If you accidentally delete a flow parameter, you can recreate it with the same case-sensitive name. All references to it should work again. |
Variable type parameters are single values. Values can be specified as String values, , or regular expression patterns.
Specify a flow parameter of variable type |
Specify the Name value and optional Description value.
NOTE: Name values are case-sensitive. After saving a parameter, you cannot change its name. |
Specify the default Value for the parameter. Examples by parameter type:
String literal:
This is my string. |
NOTE: Flow parameter values that are literal values are String values. You can convert them to other data types after they have been referenced in your recipe. |
: Patterns can be used to find matches in your recipes. The following pattern matches for two consecutive digits:
`{digit}{digit}` |
For more information on , see Text Matching.
Regular expression: These patterns also can be used for finding matches. The following pattern matches for two consecutive digits:
/[0-9][0-9]/ |
Regular expressions are a standard method for identifying patterns in data. The syntax is based on RE2 and PCRE regular expressions.
After you create a parameter, you can insert it into your recipes using the following type of reference:
${myRecipeParameterName} |
For more information, see Create Flow Parameter.
Specify a flow parameter of Selector type |
Specify the Name value and optional Description value.
NOTE: Name values are case-sensitive. After saving a parameter, you cannot change its name. |
For Choices, type or paste the permitted values for your selector type parameter.
Tip: The first value that you add is the default value. |
After you create a parameter, you can insert it into your recipes using the following type of reference and then selecting a value from the list of permitted values:
${myRecipeParameterName} == <selected_value> |
For more information, see Create Flow Parameter.
In the Overrides tab, you can apply override values to any parameters referenced in your flow, including:
NOTE: The parameters listed in this tab have override values applied to them. Parameters that are using their default values in this flow are not listed. |
Overrides tab |
All of the available parameter overrides are listed.
To edit a parameter override, hover over its entry and click the Pencil icon. Enter a new value.
NOTE: The override value is applied to all subsequent operations in the platform. When a job is submitted to the job queue, any overrides are applied at that time. Changes to override values do not affect jobs that are already in flight. |
If you have upgraded from a version of the product before Release 7.1, any parameters that were defined in the previous version appear grayed out in the Parameters tab.
The Parameters tab is used for defining new flow parameters, which is a new type of parameter. These parameters can be referenced inside your recipe steps. See above.
NOTE: Parameters that are not of flow parameter type cannot be edited in the Parameters tab. You can apply override values to these parameters through the Overrides tab. |
You can also specify parameter overrides at the plan level. For the recipes in your plan, you can pass in parameter overrides values, which are used during plan runs.
Manage Parameters Dialog for plans |
In the Manage Parameters dialog, you can review the parameters that are defined for the flows that are part of your plan.
NOTE: You cannot create parameters through Plan View. You must create the parameters within the flows that are part of your plan. After they are created, they are available for overrides through Plan View. |
NOTE: In a plan, parameters and their overrides apply only to the flow task from where they are sourced. They do not apply to other flow tasks. They do not apply back to the source flows. |
Tip: To pass a flow parameter value from one recipe to another, you can insert the parameter value in a column in a recipe, export the results as a reference dataset, and then ingest that reference into another flow. |
Columns:
See Manage Parameters Dialog for Plans.