- Before You Begin
- Getting Started
- How To
- Designing your App
- Events and Rules
- Function: And, Or, Not
- Function: Concat
- Function: Contains
- Function: Count
- Function: EndsWith
- Function: If
- Function: IsBlank
- Function: Length
- Function: List
- Function: StartsWith
- Function: Sum
- Function: Sort
- Function: Now
- Function: Today
- Function: Time
- Function: Year
- Function: Month
- Function: Day
- Function: Hour
- Function: Minute
- Leveraging RPA in your App
- Application Lifecycle Management (ALM)
- Basic Troubleshooting Guide
Rule: Start Process
Starts an RPA automation
When you add the Start Process rule to the rules builder, the first thing you need to specify is the process you wish to run. Once the process is chosen, the default settings will run the process in attended mode on the machine where the app is executing.
Clicking the Unattended radio button will change the process to be run in unattended mode.
By default, processes run synchronously, meaning the defined rule(s) after this won't execute until the process completes. If you wish to run those rules in parallel, we suggest checking "Run Asynchronous".
When the process inputs are bound to controls, the values are automatically passed into the process when it starts.
You can manually set input values by expanding the Input Override section of the rule and specifying the process input and value you want to pass in.
The Start Process rule provides the ability to define rules to be executed whenever the process starts or completes.
The example below shows how to overlay a spinner on the app, with a message stating that the transaction is executed, when the process starts and then hiding the spinner when the process completes.
The Report Status activity allows a message to be sent to the assistant or an app during a process's execution.
The example below shows how to set the value of a status label to the message that is passed from the automation.
