Which type of activity allows for parameter passing in UiPath workflows?

The Invoke Workflow File activity is designed specifically to call another workflow within a UiPath project. One of its key features is the ability to pass parameters both to and from the invoked workflow. This means that you can send arguments from your main workflow to the called workflow, and you can also return values back to the main workflow after execution.

Parameter passing is essential for creating modular, reusable components within your automation projects. When you use the Invoke Workflow File activity, you can define input and output arguments, which allows for dynamic and flexible workflows by enabling data sharing between different workflow files.

For the other activities listed, they do not support direct parameter passing in the same manner. The Message Box activity is primarily used to display messages to the user and does not have the capability to pass parameters. The Assign activity is used to assign values to variables but does not invoke other workflows or facilitate parameter exchange. The Invoke Code activity allows for executing VB.Net code but is not intended for parameter passing across workflows in the same clear and structured way that the Invoke Workflow File activity is designed to handle.