Migrate Parameters

Jump to Section

In 4.1 and older versions, namespace node parameters were passed as JSON. When upgrading to 4.2 or newer versions, the parameter syntax is now better defined and easier to use. In cases where you were passing parameters to a namespace node that referenced a Pipeline, the 4.1 syntax for will continue to work, but you’ll need to manually migrate the syntax to use the new format. Below is a step-by-step guide on how to perform this migration.

Identify Nodes that Need Migration

If a node is using the old syntax, you’ll see this warning in the UI when selecting the node.

migration warning

How to Migrate the Syntax

Follow these steps to migrate to the new parameters’ syntax.

  1. Go to the Pipeline and create a Callable Trigger.
  2. Enable the trigger and add the parameters in the trigger settings.
  3. Go back to the namespace node, you should now be able to “upgrade” the parameters (see image below)
  4. You should now see the parameters you defined on the trigger, and can fill them in accordingly
  5. Save, and perform a smart query test on the node to ensure it’s working as expected

upgrade parameters