About MICHIRU Assistant
MICHIRU Assistant is a feature designed to make business automation more convenient.
The Trigger feature allows automation sets to run automatically when specified conditions are met.
For example, you can use schedules or changes to file or folders as triggers to automatically execute predefined automation processes.
Note: Additional features besides the Trigger feature are planned for future releases.
MICHIRU Assistant Settings
MICHIRU Assistant is accessible via the subtab with the same name within the “Tool” tab.
The following sections explain each tab in the MICHIRU Assistant tab.
Trigger list
This tab is used to configure the Trigger feature.
You can view and edit the list of created triggers here.
Date/Time Trigger Calendar
This tab is used to view the configuration status of the Trigger feature’s “Date/Time Trigger” in a calendar format. You can create new triggers, as well as view and edit existing ones.
File Trigger Access Settings
This tab is used when setting up folders that require authentication, such as network folders, for the File Trigger feature. You can configure the login credentials used to access the folders.
Assistant status check
You can check the operating status of MICHIRU Assistant and start or stop the service.
Note: In most cases, you do not need to operate these settings.
Trigger Features
Types of Trigger Features
The Trigger feature includes the following two types:
- Date/Time Trigger：Executes an automation set based on specified conditions such as date, time, or day of the week.
- File Trigger：Detects file additions, updates, and deletions, then executes an automation set.
Creating Trigger
Click the “Create new trigger” button at the top of either the “Trigger list” screen or the “Date/Time Trigger Calendar” screen to open the “Create new trigger” window.
Basic Trigger Settings (Common to Date/Time and File Triggers)
| No. | Setting | Explanation |
|---|---|---|
| 1 | Valid / Invalid | Use this option to enable or disable the trigger. When turned on, the trigger becomes active and runs automatically when the specified conditions are met. |
| 2 | Trigger name | Set a name for identifying the trigger. Note: Duplicate names are allowed |
| 3 | Automation set | Select the automation set to execute. |
| 4 | Startup param | Set the value to be passed to “Startup param” data save destination when the automation set is executed. |
| 5 | Trigger Type Selection | Select either a Date/Time Trigger or a File Trigger. |
| 6 | Run with administrator privileges. | When turned on, the automation set will be executed with administrator privileges. Note: Administrator privilege are required for the Windows logon user. |
| 7 | Save settings | Save the settings for trigger. |
| 8 | Cancel | Cancel the settings for trigger. |
Date/Time Trigger Settings
| No. | Setting | Explanation |
|---|---|---|
| 1 | Start date | Set the date on which the trigger becomes enabled. After the specified date, the trigger will execute automatically based on the configured conditions. |
| 2 | Execution time | Set the time at which the trigger starts running. |
| 3 | Execution pattern | Configure how the trigger should repeat automatically. Select from one of the following 4 patterns. Once: Execute only once at the date and time specified in “Start date” and “Execution time”.  Weekly: Execute every week at the set time on the specified day of the week, starting from the “Start date”.  Monthly (day): Execute every month at the set time on the specified day, starting from the “Start date”.  Monthly (weekday): Execute every month at the set time on the specified weekday, starting from the “Start date”.  |
File Trigger Settings
| No, | Setting | Explanation |
|---|---|---|
| 1 | Monitored directory | Specify the folder to monitor for file changes. The trigger will run when files are added, updated, or deleted within the specified folder. |
| 2 | Monitor subdirectories as well | When turned on, the subdirectories within the monitored directory will also be included in monitoring. |
| 3 | Add pattern | Add conditions for the file name targeted by trigger. |
| 4 | Delete pattern | Delete configured file name pattern. |
| 5 | Configure pattern | Configure the conditions for triggers based on the file name. The trigger runs only when a file that matches the conditions below is detected witihn the monitored folder. ・Perfect match: Detect only files with a file name that exactly matches the specified name. ・Including: Detect files with a file name that includes the specified text. ・Prefix match: Detect files with a file name that begins with the specified text. ・Suffix match: Detect files with a file name that ends with the specified text. ・Exclude (Office temp file): Exclude temporary working files created by Office applications ・Exclude (Perfect match): Exclude files with a file name that exactly matches the specified name. ・Exclude (Including): Exclude files with a file name that includes the specified text. ・Exclude (Prefix match): Exclude files with a file name that begins with the specified text. ・Exclude (Suffix match): Exclude files with a file name that ends with the specified text. |
| 6 | Trigger timing | Set when the trigger should run based on file changes. ・On file create/save: Triggered when the file is created or saved. ・On file deletion: Triggered when the file is deleted. |
| 7 | Detected file path save destination | Set the data save destination that stores the file path of the file that trigger the automation set execution. |
| 8 | Detection timing save destination (write/delete) | Set the data save destination that stores the timing that the execution was triggered in text format. The following 2 are the possible outcome. -“write“: If triggered “On file create/save” -“delete“: If triggered “On file deletion” |
Some office application, such as Excel, Word, and PowerPoint, automatically create and delete temporary working files separately from the file currently being used.
If you want to exclude these temporary files from being monitored for file trigger, use the “Exclude (Office temp file)” condition in the “File name patterm” setting.
The following 5 conditions under “File name pattern” are available starting from Ver. 1.4.5.0. Please upgrade MICHIRU RPA if you are using an earlier version.
- Exclude (Office temp file)
- Exclude (Perfect match)
- Exclude (Including)
- Exclude (Prefix match)
- Exclude (Suffix match)
When using a cloud service folder, such as OneDrive, for a file trigger, please note the following:
- MICHIRU Assistant monitors changes in cloud service folders at regular intervals. However, if file synchronization has not yet completed, changes cannot be detected. As a result, execution by the file trigger may be delayed.
- If the same file is created and then deleted on the cloud in quick succession, MICHIRU Assistant may not detect the changes depending on the timing, and the change may not trigger the file trigger.
- If the PC is shut down before file synchronization is complete and synchronization finishes after the next startup, that file will not be detected by the file trigger.
Configuring File Trigger Access Settings
When setting a folder that requires authentication to access, such as a network folder, as the monitored directory, please configure the credentials information in the “File Trigger Access Setting” tab.
- Click the “New Destination” button in the “File Trigger Access Settings” tab.
- In the “New Destination” window displayed, select the “Monitored directory” and input the credential information required to access the directory in the “Username” and “Password” field.
- Click the “Test Connection” button.
- If the connection is successful, click the “OK” button.
Note: If the connection fail, you will not be able to set the directory as the monitored directory for File Trigger. - Click “Save settings” button to complete the configuration.
Behavior Settings for Execution Requests from MICHIRU Assistant
When MICHIRU Assistant sends an execution request, the automation set is executed immediately if MICHIRU RPA is not running. However, if MICHIRU RPA is in one of the following states, its behavior depends on the “Confirmation message when receiving an automation set instruction from an external source” setting in the “Other” tab.
- When editing an automation set
- When executing an automation set
- When an automation set is stopped due to an error
Please refer to this page for more information regarding the setting.
