Updated in 8.7
NOTE: In order to allow for seamless integration, Alloy Navigator uses Alloy Integration Launcher. Web users get this small program installed when they run such a workflow action for the first time. Desktop users get the launcher installed automatically.
Depending on the task you want your
INFO: For more detailed description of External Command operations, see Administration Guide: External Command.
To configure an
Under Run command on, choose where to run the command: on the client or on the server.
Under Run, enter the commands or scripts for the PowerShell to run. This can be a PowerShell cmdlet, a combination of cmdlets, a script, or any external program.
To enter a dynamic parameter, click Insert Placeholder and use the Select Placeholder window to insert a placeholder. At runtime, all placeholders will be replaced by the actual data.
IMPORTANT: Add double quotation marks (") around placeholders, so all placeholders in your command are enclosed in quotes. For example:
"%[DBF Field1]%%[DBF Field2]%%[DBF Field3]%".
INFO: For additional information, see Microsoft PowerShell documentation at https://docs.microsoft.com/powershell/.
For client commands: If you want the user to review the output information in the PowerShell window, select the Display PowerShell window check box.
For server commands: Specify the timeout period (in minutes) after which the Automation Server will finish inactive background jobs.
TIP: If you want the job to run with no timeout, enter 0 (zero).
Keep the Enable operation check box selected. Otherwise, the operation will be disabled.
NOTE: To run an External Command operation, the PowerShell executable file (
powershell.exe) must exist in the folder specified in the PATH environment variable on the computer where the operation runs, i.e. on the client or on the server.
NOTE: All External Command operations are run asynchronously without suspending other workflow operations.