Local Process
"Attended-Node-locked License" and "Attended-Floating License" Automation Worker both support displaying the Local Process list and adding Local Processes.
Process List
By default, the Local Process list is empty and requires the current user to manually add processes.
Add
Click the "Add" button to open a file selection dialog box, as shown below. Select and open a ".bot" file to add a Local Process.
Source of local .bot files: .botprocess files published locally from Automation Creator Enterprise Edition.
Once successfully added (with a prompt), the Local Process can be viewed in the list. The process is labeled as "Local Process" with the process details displayed on the right.
Similarly, the Local Process list includes displayed information (icon, process name, type) and action buttons (Quick Run, Run, Continuous Run, Run Settings, Process Input Settings, Delete). It also supports fuzzy searching by entering the process name. The difference lies in the "Type," which is "Local Process," and the support for deletion.
Note: If the selected process does not contain "Process Input," the "Process Input Settings" menu will not be displayed.
Delete
Single Deletion
Batch Deletion
To delete a Local Process, click the "Delete" menu/button. The system will prompt you for confirmation.
When you click the "Delete" button, the system will perform a check. If the process is used by a Group or trigger, the process cannot be deleted. Similarly, if a Group is used by a trigger, the Group cannot be deleted.
Running a Process
You can click the "Run" button to directly run the selected process.
While running, Automation Worker will minimize by default. Upon forcing the window to activate, the top of the main window will display "Running: xxxxxxx," and the "Run" button will switch to a "Stop" button. Clicking it will stop the process, and the task's result is typically "Failed."
When a process is running, you can forcibly terminate it by holding down Ctrl+F12.
Notes:
If you run an older process file version with a new version of Automation Worker, you may receive a system prompt like the one shown below. If the process fails to run or does not meet expectations, you can adjust the Automation Worker version for better compatibility or update the process using the latest version of Automation Creator.
If the process includes "Message Dialog" configurations during development, corresponding messages and buttons will appear during runtime. You may need to click "OK" to proceed or finish running.
For other scenarios, follow the on-screen instructions.
If issues arise with the process, contact technical staff to debug and troubleshoot the process using Automation Creator.
Single Run
On the right of the selected process, click the "..." icon to open a menu panel with five options: Run, Continuous Run, Run Settings, Process Input Settings, and Delete.
Selecting "Run" will execute a single run.
For "Continuous Run," you must specify the number of times or the end time.
Choosing "Run" from the menu has the same effect as directly clicking the "Run" icon, i.e., a single run.
Continuous Run
When selecting "Continuous Run," a popup window offers two options: (1) Specify the number of runs; (2) Specify the end time.
Continuous Run also allows settings to terminate upon a failed run.
Examples are shown below.
Run Settings
Run settings include "Clone Run," "Run Version," "Max Runtime," "Run Hotkey," and "Department" information. Due to the differences between "Attended-Node-locked License" and "Attended-Floating License," the "Department" information displayed in the "Local Process - Run Settings" area varies based on the license type.
For the "Attended-Node-locked License"
For the "Attended-Floating License"
Clone Run
Each process and Group can independently enable Clone Run in the "Run Settings." A process with Clone Run enabled runs in a Clone of the current Windows desktop.
Preconditions:
- CloneExtension plugin must be installed via settings.
- Local account and password must be configured in "Settings - Local Account."
Key Features of Clone Run:
- Clone Run windows operate independently from the user's original desktop window, allowing normal operation of applications on the original desktop.
- During Clone Run, users can view the real-time execution screen of the process in the Clone window.
- Users can choose whether to control the Clone window and whether to keep it on top. Selecting control allows mouse operations within the Clone desktop.
When a process or Group enables Clone Run, clicking "Run" or "Continuous Run" will open a Clone desktop window. Before execution, you must log into the current Windows user account. Alternatively, you can preconfigure local Windows user accounts in the settings. This enables automatic login during Clone Run. If not configured, the system will prompt for local account settings, as shown below.
After entering the Windows user account password, the specified process runs in the Clone Windows desktop.
Run Version
You can choose a specific version to run the current process, typically a lower version installed locally. The dropdown options can be managed via "Settings - Version Management."
Max Runtime
You can control the maximum runtime for the process. If exceeded, the process will be forcibly stopped.
Hotkey Run
You can configure a hotkey for running a process or Group in the "Run Settings." Once set, pressing the hotkey triggers the process or Group to run.
Department
This option is only available under the "Attended-Floating License." It records the department to which the process run belongs. It is selectable only when multiple departments are associated and allows viewing process run information per department in Automation Commander.
Process Input Settings
Process input settings allow personalized value assignment to input variables before the process runs, enabling customized business needs.
Process input variables include three parts: variable type, variable name, and variable value.
Variable types include text, numeric, boolean, and credential, as designed in Automation Creator.
Select a process, click the " ..." icon, and in the popup menu, click "Process Input Settings," as shown below.
Note: If the selected process does not contain "Process Input," the "Process Input Settings" menu will not be displayed.
Process Details
Selecting any process from the Local Process list will display more detailed information about it in the process details area on the right (as shown below):
- Basic information such as process name, version, add time, last run time, and process type.
- Configuration details like run version, run hotkey, max runtime, and Clone Run toggle.
- Action buttons such as usage instructions and version notes.
- Logs.
Note: The structure of detailed information for each process is consistent between the Automation Commander process list and the Local Process list.
View Usage Instructions
Click the "Usage Instructions" button to view the instructions written during the process's publication through Automation Creator. If no text is visible in this area, the publisher has not written usage instructions. This feature is not available for Groups.
View Version Notes
Click the "Version Notes" button to view the notes written during the process's publication through Automation Creator. If no text is visible in this area, the publisher has not written version notes. This feature is not available for Groups.
View Log
For processes, logs include records and results of each run.
For Groups, logs include records and results of each subprocess run.
Query Log
Logs can be queried by run result or date range.
Run results include four statuses: Success, Failure, Stopped, and Canceled.
Date ranges, as shown below, include "Today," "Yesterday," "Past 7 Days," "Last Month," and custom start and end dates.
View Run Logs
Logs in the process details can be viewed in a popup window.
View Screen Recordings
Logs in the process details also support viewing screen recordings in a popup window.