Configuring Integrations

Updated in 8.7

External Command operations run external PowerShell commands directly from Alloy Navigator. You configure this operation in the External Command window.

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.

TIP: Creating External Command operations requires a working knowledge of PowerShell. See Microsoft PowerShell documentation at https://docs.microsoft.com/powershell/.

Depending on the task you want your external command to perform, it can run it on a client computer, i.e. on the computer from which the workflow action is initiated, or on the server computer, i.e. the computer hosting the Automation Server. Client commands can be launched only from the Web App, Desktop App, and the Self Service Portal. Server commands can be launched from anywhere.

INFO: For more detailed description of External Command operations, see Administration Guide: External Command.

To configure an External Command operation:

  1. Under Run command on, choose where to run the command: on the client or on the server.

  2. 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]%" or "%[DBF Field1]%%[DBF Field2]%%[DBF Field3]%".

    INFO: For additional information, see Microsoft PowerShell documentation at https://docs.microsoft.com/powershell/.

  3. For client commands: If you want the user to review the output information in the PowerShell window, select the Display PowerShell window check box.

  4. 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).

  5. Keep the Enable operation check box selected. Otherwise, the operation will be disabled.

  6. Click OK.

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.