Robot

Robot

Aktiviteler

Communicate With Robot

Robot-to-robot messaging is used to send commands or assign variable values between different robots and their scenarios.

Usage Scenarios:

Starting a scenario on another robot using the runScenario command
Stopping another robot’s scenario using the stopScenario command
Assigning values to variables inside another robot’s scenario using SetVariable
Creating control mechanisms between robots (for example, sending completion status)

Parameters:

Robot Unique Id: The unique identifier of the robot that will receive the message
Message: The command or variable assignment to be sent (runScenario|robotId, stopScenario|robotId, runScenario|robotId|SetVariable|variable=value)
Delay Time: Waiting time after the activity runs (in milliseconds)
Communication Result: Output indicating whether the message was transmitted successfully

Notes:

Robot Unique Id must be correct; otherwise, communication cannot be established
Command formatting must be exact; the | separators and segments must be written correctly
The target robot must be active and authorized
Communication is only possible with robots assigned through the Orchestrator

Get Robot Informations

Get Robot Informations activity retrieves the Robot Unique Id, Robot Name, and Machine Name of the robot assigned to the published scenario. These values can be used within the workflow. The scenario must be published and assigned to a robot; otherwise, the outputs will appear as “Not Active Robot.” The activity runs only when executed by the robot, not from the Studio.

Usage Scenarios:

Identifying which device and which user the robot is active on at runtime
Including system-level information for logging or auditing
Using the robot name or ID as a process differentiator in multi-robot environments
Recording which robot was running in case of errors

Parameters:

Robot Unique Id: The robot’s unique system identifier (output)
Robot Name: The defined name of the robot (output)
Machine Name: The name of the machine on which the robot is running (output)

Notes:

The scenario must be published for the activity to work.
If no robot is assigned, the returned values will be “Not Active Robot.”
The activity does not run in Studio; it must be executed from the robot.
Outputs are produced only when the robot is running; otherwise, they may be empty.

In order to be able to use this activity, the designed scenario must be published and paired with the robot. If there is no matching robot, the values will be displayed as “Not Active Robot”. After you add the activity to your scenario, you can only run it on the robot. Otherwise it will not run on studio.

Set Robot Info

Set Robot Info activity writes a custom message to the History section of the robot’s profile page in the Orchestrator environment. The Title field defines the message title, and the Description field contains the message content. This activity can only be used when the scenario is executed through the robot application.

Usage Scenarios:

Leaving error, warning, or information messages during the scenario
Adding logs at specific steps to simplify process tracking
Indicating successful completion of the process on the robot screen
Adding audit-related messages or alerts

Parameters:

Title: The title of the message to be written in the History section
Description: The detailed message text to be written

Notes:

The activity is effective only when the scenario is executed through the robot application
The message cannot be delivered if the Orchestrator session is not active
Multiple Set Robot Info messages will appear as separate entries
The robot must be active for the messages to be visible in the interface

Update Robot Transaction Message

You can add a transaction-based message with the Update Robot Transaction Message activity. You can report this data from the message column in the report named Robot’s Log Graph in Orchestrator.

When this activity is run on Studio, it gives an error message as “Active transaction not found!” because there is no active transaction. For this reason, when using it in the scenario, you should definitely connect the purple arrow (Catch leg) to an activity to skip this message.