When a job is created that has no arguments (for example run a node, stop a node, upgrade a node, i.e. commands with fixed parameters) there is no way to pass no parameters to the params(...) blueprint macro variable. You have to use a dummy placeholder value to get the editor / compiler to not complain. No arguments in params should be support or entirely omitting parameters if none exist should be supported.
Overview
When a job is created that has no arguments (for example run a node, stop a node, upgrade a node, i.e. commands with fixed parameters) there is no way to pass no parameters to the
params(...)blueprint macro variable. You have to use a dummy placeholder value to get the editor / compiler to not complain. No arguments in params should be support or entirely omitting parameters if none exist should be supported.