31 August 2020
- The creation of personal workspaces is now selected by default for all new users.
- Attended robot creation is now enabled by default in all new tenants.
- We improved performance for release version filtering and test set creation.
- You can now choose from all available versions when selecting packages for test set creation.
Killing a test execution job resulted in an incorrect job state in Orchestrator.
10 August 2020
If you were looking for better-debugging capabilities, rest assured, as of now, you can select the host machine on which a certain job is launched. Click here for details about jobs.
To ease unattended automation ordeals concerning local Windows users residing on multiple host machines we made sure that unattended robots impersonating local accounts only require the corresponding Windows username and password - the host machine is no longer a mandatory identifier.
Say you are using LocalUser1 on 5 host machines. Instead of having to set up 5 user entities in Orchestrator for each combination,
you define the unattended robot on one user entity only, using the
.\LocalUser1 syntax in the Domain\Username field. This way you can make use of that specific Windows account on each host machine through one Orchestrator user entity
Nothing changed for domain accounts, where the robot requires the
domain\username syntax just as before.