Launch Process

The 'Application Path' property specifies the command, file, or URL to launch.
This can be any value accepted by the Windows shell, such as:

• The path to an executable or batch file (e.g., C:\Tools\MyApp.exe).
• The path to a document or file (e.g., C:\Docs\Report.xlsx).
• The path to a folder (e.g., C:\Users\Public).
• A URL (e.g., https://www.example.com).

> Example:
To run a PowerShell script, enter powershell.exe -File "C:\Scripts\MyScript.ps1".

The command is executed as if entered in the Windows 'Run' dialog.

Enable the 'Should Wait' property to have Grooper pause execution until the launched process exits or the timeout is reached. This is useful for command-line tools, scripts, or background processes that must finish before the workflow continues.

• Set to true for non-interactive processes (e.g., scripts, utilities).
• Set to false for interactive applications or files that require user input (e.g., opening a document for review).

> Tip:
If the process does not exit within the 'Wait Timeout', an error will be raised.

The 'Wait Timeout' property controls how long Grooper will wait for the launched process to exit when 'Should Wait' is enabled. Enter the timeout in milliseconds (e.g., 60000 for 60 seconds).

• If the process does not exit within this time, an error is thrown and processing stops.
• If set too low, long-running processes may be interrupted.
• If set too high, Grooper may wait unnecessarily for processes that hang or never exit.

> Tip:
Adjust this value based on the expected duration of the process being launched.

A combination of the following flags:

The Error Disposition property determines the system's response to errors that occur while executing the activity.

• Flag: The affected Batch Folder or Batch Page will be flagged for review.
• Log: The error will be written to the Grooper event log.
• Stop: Processing will halt, the Batch will be set to an error state, and all pending tasks will be deleted.

You can combine multiple options using the IssueDisposition flags.
Adjust this property to match your organization's error handling and escalation policies.

If the number of consecutive errors reaches this value, a critical stop will occur and the Activity Processing service will halt further processing.

• Use this property to prevent runaway failures and to ensure that persistent errors are escalated for review.
• Set to a higher value to allow more retries before stopping, or to a lower value for stricter error control.

Can be one of the following values:

The Concurrency Mode property determines whether the activity can be executed in parallel across multiple Batch Objects, or if it must run sequentially.

• This setting affects which Processing Queue the activity is submitted to and how tasks are distributed.
• Choose the appropriate mode based on the activity's thread safety and resource requirements.