Use a project parameter as a value in a pipeline task
Some value boxes in a task accept a project parameter instead of a typed value. When the parameter's value changes, the step uses the new value on its next run. You create and manage parameters in Parameters and snippets.
Which task values can use a parameter
| Function | Value you can bind | Parameter type |
|---|---|---|
| Find & Replace | The text to find and the replacement | Text |
| Label & Insert Values | The value to insert | Same type as the target column |
| Show Top/Bottom Rows | The number of rows | Number |
| Obtain Large or Small Values | The custom value | Number |
Conditions (Add Condition and Conditional Filter), Data Check thresholds and the SQL mode of Math Function (Insert Parameter) can use parameters too.
Bind a value to a parameter
- Click the small chip at the left of the value box. It reads Val for a typed value.
- Choose Parameter ("Bind to a project parameter"). The chip changes to #.
- Click Select a parameter and pick one. Only parameters of a matching type are listed.
- The box now shows the parameter's name. Click its X to remove the binding.
You can't apply the step while the box is set to Parameter with nothing picked ("Select a parameter to continue"). To go back to a typed value, click the chip and choose Value ("A fixed value").
What happens when a parameter changes
Every pipeline that uses the parameter is flagged as stale. Mammoth doesn't rerun them on its own: rerun from the parameter library or the stale banner. The rerun starts from the first task that uses the parameter.
Related
- How a Mammoth pipeline works: add a task from the Transform menu.
- Find and replace values: a common place to bind a text parameter.
- Filter rows: conditions that can use a parameter.
Something wrong? support@mammoth.io