The PowerShell connector enables you to execute script files or commands and perform your Windows task automation as part of your integrations on any remote machine, where you install a remote agent.
The PowerShell scripts are executed on the remote machine with the same permissions as the permissions set for the remote agent when installed.
You can find more information about PowerShell on Wiki or Microsoft.
Configuration
PowerShell (ver.1.0.0)
Execute
Select relevant type of execution. Available:
-
PowerShell script file (.PS1)
-
PowerShell command(s)
Path to PowerShell script file (.PS1)
If you chose the execution using a PowerShell script file, provide the path the .PS1 file.
PowerShell command(s)
If you chose the execution using the PowerShell commands, write them into the PowerShell editor.
Abort on failure
If not checked, the task step using the PowerShell will be completed successfully even in case the script itself fails. In case you want the script to fail the task step, make sure you check it.
Write output to debug log
The output will be written into the Task run log at the debug log level.
PowerShell variables
There are no variables defined from the input schema, but you can define the required variables using this section:
-
Variable name - Define the name of the PowerShell variable.
-
Variable value - Set the value of the PowerShell variable.
-
Variable data type - Set the variable data type from the list. Available types:
string,integer,double,datetime,boolean,base64,JSON.
Note
The variable value can be easily taken from input data by a placeholder ${input[rowIndex].ColumnName}, which selects a single value from the input data column named ColumnName and row with index rowIndex. If you are sure that the input data contains only a single row, you can omit the row selector and simplify the placeholder to ${input.ColumnName}.
Input & Output Schema
Input
Data schema is optional
The connector does not expect a specific schema. The required data structure can be achieved by correct configuration. Although the selected connector doesn't require a schema generally, the individual integration task step may need to match the output data structure of the preceding task step and use a data schema selected from the repository or create a new input schema.
Output
Data schema is optional
The connector does not expect a specific schema. The required data structure can be achieved by correct configuration. Although the selected connector doesn't require a schema generally, the individual integration task step may need to match the output data structure of the preceding task step and use a data schema selected from the repository or create a new input schema.
Release notes
3.2.1
- Renamed Write output to agent's log -> Write output to debug log.
3.2.0
- Implementation of debug script generating.
3.1.5
- Fixed processing input variable type double.