- Getting Started
- Before You Begin
- How To
- Notifications
- Using VB Expressions
- Designing your App
- Events and Rules
- Rule: If-Then-Else
- Rule: Open a Page
- Rule: Open URL
- Rule: Close Pop-Over/Bottom Sheet
- Rule: Show Message
- Rule: Show/Hide Spinner
- Rule: Set Value
- Rule: Start Process
- Rule: Reset Values
- Rule: Upload File to Storage Bucket
- Rule: Download File From Storage Bucket
- Rule: Create Entity Record
- Rule: Update Entity Record
- Rule: Delete Entity Record
- Rule: Add to Queue
- Rule: Trigger workflow
- Leveraging RPA in your App
- Leveraging Entities in Your App
- Leveraging Queues in Your App
- Leveraging Media in your app
- Leveraging Actions in your app
- Application Lifecycle Management (ALM)
- Basic Troubleshooting Guide
Rule: Start Process
Use the Start process rule to start the execution of a process.
Clicking the What process to run field opens the Resources panel, which displays the available processes.
Select the process you want to start by double-clicking on it. Once selected, the following properties become available:
-
Run Asynchronous
-
Type: Attended or Unattended
-
Input Override
-
When started
-
When state changes
-
When completed
-
Errors
By default, processes run synchronously, meaning the rules that follow the current Start process rule do not execute until the selected process completes.
To run the remaining rules in parallel, select the Run Asynchronous box.
To run the process in unattended mode, select the Unattended radio button. By default, the process is set to run in Attended mode.
In this section you can set values for the input arguments of the process.
Clicking the Input Override filed opens the Resources panel, which displays the available input/output arguments of the selected process.
Select the input arguments, and set their values as the values of the input controls in your app.
The input argument of the workflow has the following syntax:
Processes.<process_name>.<input_argument_name>
The value expression of the Apps control has the following syntax:
<Apps_MainPage_name>.<input_control_name>.value
MainPage.text1.Value.
When the process inputs are linked to control values, these values are automatically passed into the process when it starts.
In this section you can define rules to be executed right after the execution of the process starts.
For example: You can show a spinner icon in this section, and then hide the spinner in the When completed section for workflow that take longer to execute.
In this section you can define rules to be executed when the state of the process changes.
The Report Status activity allows a message to be sent to the Assistant or an app during a process execution.
In this section you can define rules to be executed after the execution of the process completes.
For example: For workflows that take longer to execute, you can show a spinner icon in the When started section, and hide it in this section.
In this section you can define rules to be executed when the process encounters an error.
For example: To track the failure, you can add a Show Message rule. You can then specify the title, message, and type of the error.
