Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space DEV and version r083

...

  1. Open the flow where you wish to apply the flow parameter. 
  2. From the Flow View context menu, select Manage parameters.....select Parameters.
  3. In the Manage Parameters dialog, click the Parameters tab. 
  4. Click Add parameter.
  5. Enter a Name for your parameter.

    Info

    NOTE: Name values are case-sensitive. After saving a flow parameter, its name cannot be changed.

  6. Enter a default value for this parameter.

    Info

    NOTE: Input Values are evaluated as String type.

  7. Click Save.

...

This override value is applied to all references to the parameter in the flow. 

Tip

Tip: Overrides can also be applied to the recipe parameters that are included when flow tasks are executed as part of a plan. For more information, see Manage Parameters Dialog.

Override Evaluation

Override values can be applied in multiple locations. Parameter values are evaluated in the following order of precedence (highest to lowest):

...

D trans
RawWrangletrue
p03Value'storeId'
Typestep
WrangleTextderive type: single value: merge([$paramTimeZone,Store_Nbr], '-') as: 'storeId'
p01NameFormula type
p01ValueSingle row formula
p02NameFormula
p02Valuemerge([$paramTimeZone,Store_Nbr], '-')
p03NameNew column name
SearchTermNew formula

Example - parameter with multiple values

Suppose you wish to create a flow parameter that contains multiple values. Typically, you must track these values through an array, such as the following containing a set of colors:

Code Block
["red","white","blue","black"]

Flow parameters that are literals are String values only. As a workaround, you can define the above as a 

D s lang
itempattern


SettingValueNotes
NamemyColors
Value
Code Block
`red|white|blue|black`

Note how the value is specified using backticks (`), which are used to indicate a

D s lang
itempattern
.

The vertical bars are delimiters to separate the values, when they are processed within the application.

Within your recipe, you can test for the presence of a parameter value. In the following transformation, a value of true is set in the new column isBlue if the value of $myColors is blue:

d-trans
RawWrangletrue
p03Value'isBlue'
Typestep
WrangleTextderive type:single value:MATCHES([blue], $myColors, true) as:'isBlue'
p01NameFormula type
p01ValueSingle row formula
p02NameFormula
p02ValueMATCHES([blue], $myColors, true)
p03NameNew column name
SearchTermNew formula

Example - Integer parameter

Instead of segmenting the data by named time zone values, suppose your data is segmented by regions, which are numeric in number. Your flow parameter definition could look like the following:

...