Trigger Activity vs Orchestrator Trigger

[tilarapiyush]

Hi All,

Could someone le tme know the use case for trigger activities ? And why it is not suitable to be done via Orchestrator trigger.

[ashokkarale]

@tilarapiyush,

Trigger activities are used to monitor event’s or appearance of desired situation or elements.
For example suppose every time your laptop starts you want few applications should be opened like chrome and login into mailbox, music player app and go to playlist… these activities will be your bot logic and trigger would be anything like you open notepad and type “Lets start”. So bot will continually monitor for notepad with this keyword to start further actions.

@tilarapiyush

why it is not suitable to be done via Orchestrator

Because these triggers are used on local or bot machine only through Attended license and can’t be monitored from Orchestrator.

Thanks,
Ashok

[mukesh.singh]

@tilarapiyush

Could someone le tme know the use case for trigger activities ? And why it is not suitable to be done via Orchestrator trigger.

I have never experience but got some information from Internet

Trigger Activities:

• Used to monitor events or specific conditions on the local machine where the robot is running (typically with an Attended Robot license).
• Examples include monitoring keyboard input, application state changes, or element appearances on the UI.
• The robot continuously checks for the trigger event and executes the defined actions when it occurs.

Why Not Suitable for Orchestrator Triggers:

• Orchestrator triggers are designed for scheduling and managing robot execution centrally.
• They cannot directly monitor events on the robot’s local machine.

Use Cases for Trigger Activities:

• Launching specific applications upon certain events (e.g., typing a keyword in Notepad).
• Responding to user interactions (e.g., hotkeys or button clicks within the attended robot interface).
• Automating tasks based on dynamic UI changes (e.g., starting a process when a new button becomes visible).

Advantages of Orchestrator Triggers:

• Centralized control and scheduling: Schedule robot execution based on time, events, or queue items.
• Monitoring and logging: Track robot execution status and logs from a central location.
• Reusability: Define triggers once and reuse them across multiple robots.
• Scalability: Manage robot execution across multiple machines.