Automation techniques may be sensible to resolution differences between the development and production environments.
There are cases when your automation may break or misbehave, depending on host and Virtual Machine resolution variations:
For a smaller Virtual Machine resolution, elements might be rearranged in an application with responsive layout or elements may be left out of viewport if scrollbars appear
For a smaller host resolution than the VM resolution, elements may be either left out if scrollbars appear in the VM window or they may suffer severe visual distortion if autoscaling is applied instead
By default, when a robot starts an interactive Windows session via Orchestrator, it uses the system resolution that the user configured for the machine.
If a custom resolution needs to be designated for the robot, You can make changes in UiPath.settings file on the system.
Uipath.settins file path_ - %ProgramData%\UiPath\UiPath.settings
Set the fields:
- ResolutionWidth //E.g.- 1080
- ResolutionHeight //E.g.- 1920
- ResolutionDepth //E.g.- 32
- if you connect via RDP you should have loginToConsole: false
- if you connect directly you should have loginToConsole: true