Skip to Content
Information
This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Running external processes introduction

One of the simplest ways to integrate two applications is to execute one application from within another. AR System enables you to include execution of external applications as part of workflow to enhance or supplement the features of AR System.

The reverse case, where another application executes a AR System client, is also valid.

Beyond simply starting the external application, AR System provides process-control functionality for these types of integration:

  • Data passing and retrieving—When AR System executes external applications (manually or automatically), information from any form in the AR System database can be extracted and passed as run-time arguments. You can also retrieve data by using a Run Process command and placing it in a field.
  • Client and server execution—External applications can be executed locally on the AR System client, or remotely on the AR System server.
  • Synchronously and Asynchronously—Run Process on a filter and escalation is asynchronous. All other Run Process commands (including $PROCESS$ in a Set Fields action) run synchronously.

Executing an external process is done by using the Run Process workflow action (which is available for filters, active links, and escalations) or a Set Fields action with the $PROCESS$ keyword. For additional information, see Defining-Run-Process-actions-to-run-processes-programs-or-commands.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

AR System 21.05