Bolletje
May 4, 2020, 2:39pm
21
@badita , was this a recent change? See Robot Not Visible To Start Job In Orchestrator - #17 by Bolletje
Two months ago I was able to start a job from Orchestrator and push it to a Studio robot.(see screenshot 1).
Today I tested again and was not able to start manually from Orchestrator, but indeed it was possbile from tray agent. Then changed to Unattended, and it’s working from Orchestrator now.(screenshot 2)
badita
May 4, 2020, 2:57pm
22
Yes, there where many discussions. Please do search.
In 20.4 we’ll introduce a feature called Unattended Decoupling or, otherwise said, “breaking the robot”.
What does it mean? Suppose you have 10 machines x 10 runtimes each and 20 users. You won’t need to define anymore 200 fixed robots (userXmachine pairs) and input the password 100 times for the same user (for each 1000 machines). Instead you’ll define one machine template with 10 runtimes, 20 users and attach them to a folder. That’s all.The convention is that within a folder (which replaces …
Cloud Platform: New version of Orchestrator Cloud
We have updated the version of Orchestrator Cloud running on our Cloud Platform - Community instances, bringing you the latest changes and bug fixes. The version update is targeted to reach our Cloud Platform - Enterprise instances next week.
For details on everything that was included in this update, please check our Cloud Platform release notes .
Orchestrator highlights
Hi i also faced the issue which is due to in the main workflow i have not done anything. But i have done in bimboautomation.xaml. So invoke the BimboAutomation.xaml in main workflow. please find attached the screenshot
