Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
Information
This site will undergo maintenance on Friday, 26 September at 2:00 AM CDT / 12:30 PM IST and may experience a short period of instability during that time.
Running external processes introduction
One of the simplest ways to integrate two applications is to execute one application from within another. You can run external applications as part of the workflow to enhance or supplement the features of AR System.
Another application can also run an AR System client.
Beyond simply starting the external application, AR System provides process-control functionality for these types of integration:
Data passing and retrieving—When AR System runs 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 run 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.
You can run an external process 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.
