Synchronously invokes a specified workflow, optionally passing it a list of input arguments. Arguments can be imported from a specified workflow with this activity by using the Import Arguments button in the body of the activity.
- Importing arguments from a workflow auto-matches them to existing variables if they share the same name and data type.
- Unserializable data types cannot be passed between isolated workflows (e.g. UIBrowser, UIElement, etc).
- Antivirus policies that restrict PowerShell access may prevent the use of PowerShell-related activities. For example, you cannot use Invoke Workflow File and Invoke Power Shell when rule ID 6151 is enabled in McAfee Endpoint Security.
Passing IN arguments to an Invoke Workflow File activity that is not isolated acts as if a reference is passed, which means any changes to the object inside the invoked workflow change the object in the main workflow.
The workflow that is referenced in the WorkflowFileName property can be opened in the current project by using the Open Workflow button in the body of the activity.
.xamlfile whose title contains a dot (
.) has all the text that is before the dot (including the dot) replaced with an underscore (
- WorkflowFileName - The file path of the .xaml file to be invoked. This field accepts only string variables. The file path is relative to the current project folder. All string variables must be placed between quotes.
- Arguments - The parameters that can be passed to the application at startup.
- Isolated - If this check box is selected, the invoked workflow runs in a separate Windows process. This helps with isolating a faulty workflow from the main workflow.
Business Exceptions are not supported in an isolated workflow, all exceptions return as System Exceptions.
- DisplayName - The display name of the activity.
- ContinueOnError - Specifies if the automation should continue even when the activity throws an error. This field only supports Boolean values (
false). The default value is
false. As a result, if the field is blank and an error is thrown, the execution of the project stops. If the value is set to True, the execution of the project continues regardless of any error.
If this activity is included in Try Catch and the value of the ContinueOnError property is True, no error is caught when the project is executed.
- Timeout - Specifies the amount of time to wait for the activity to run before an error is thrown. This field supports only
TimeSpanvariables. By default, this field is empty.
- Current - The child process opens in the same session as the parent one.
- Process Default - The child process uses the Process Settings.
- Main - The child process starts in the main session regardless to where the parent process runs.
- Picture in Picture - The child process starts in the Picture in Picture session regardless to where the parent process runs.
When configuring the
Target Sessionfor the Invoke Workflow Activity, the
Isolatedparameter has to be enabled.
- Private - If selected, the values of variables and arguments are no longer logged at Verbose level.
Clicking the Import Arguments button in the body of the activity opens an Arguments panel which features all of the arguments of the workflow referenced in the WorkflowFilePath property.
This panel enables you to choose which arguments you want to import from the invoked workflow by using the directional controls or the Delete button to reorganize the arguments. Clicking OK saves the changes.
- Creating arguments in the panel causes them to be discarded, as they do not match the data in the invoked workflow.
- Argument names are case sensitive in the panel.
Once the panel is closed, a counter next to the button shows how many arguments have been selected for importing. The counter is color coded, as follows:
- orange - If there is a mismatch between the selected arguments and the ones that exist in the invoked workflow.
- grey - If the selected arguments are found in the invoked workflow.
The Open Workflow button In the body of the activity enables you to open the invoked workflow in a different tab of the same project.
Updated about a month ago