To run a workflow in Studio in 2018.2 which was designed at a non-standard DPI in a previous version of Studio, you need to use the ScaleCoordinates tool to migrate it. Since workflows that were designed at standard DPI should work out of the box, the need for this tool is scarce.
However, not all applications properly respond to scaling, even after the ScaleCoordinates tool is used. Elements usually scale linearly according to the DPI factor, but the UI element position can vary depending on the application layout. Below are a few recommendations:
- Set the ClippingRegion relative to the target button instead of the top-level containers. This only occurs when running a workflow created in a Studio version prior to 2018.2 at 125% DPI.
- Set ClippingRegion or OffsetX and OffsetY properties to a maximum of 10 pixels. This is usually caused by Click activities with a ClippingRegion set on the border of the target UI element. Please note that this can also happen after using the ScaleCoordinates tool.
- Update Windows 10 to at least Build 1703. This fixes rare cases in which workflows with non-standard DPI would not scale properly, causing inconsistent UI element recognition.
Detecting web page elements in a Chrome instance can appear imprecise in particular scenarios. This can occur when the Chrome window is opened on a monitor with 125% DPI, moved to a monitor with default DPI, and attempting to select elements inside the browser page. In this case, you can do the following:
- Minimize and restore the Chrome window;
- Maximize the Chrome window;
- Resize the Chrome window.
Updated about a year ago