<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Did you checked if you are… in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Surface-Automation-issue-in-BP-v4-2/m-p/62275#M15418</link>
    <description>Did you checked if you are capturing the window's titled or text on your application modeler? If you do, make sure that the name or text doesn't change from one machine to another. That was the issue on one of our automations that uses SA.</description>
    <pubDate>Fri, 04 May 2018 21:37:00 GMT</pubDate>
    <dc:creator>MelissaSuarez_G</dc:creator>
    <dc:date>2018-05-04T21:37:00Z</dc:date>
    <item>
      <title>Surface Automation issue in BP v4.2</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Surface-Automation-issue-in-BP-v4-2/m-p/62273#M15416</link>
      <description>Hi,

I am trying to replicate the work on other systems so I can run my process on different machines. I used&amp;nbsp;surface automation in object. I am facing issue while working on other machines. I checked all system properties like resolution, screen colour, font smoothening etc. but no luck.

Any comment is appreciated.

Thanks

&amp;nbsp;</description>
      <pubDate>Tue, 01 May 2018 15:16:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Surface-Automation-issue-in-BP-v4-2/m-p/62273#M15416</guid>
      <dc:creator>AkshikaSaxena</dc:creator>
      <dc:date>2018-05-01T15:16:00Z</dc:date>
    </item>
    <item>
      <title>There must be some…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Surface-Automation-issue-in-BP-v4-2/m-p/62274#M15417</link>
      <description>There must be some difference between environments/screens for Surface Automation to work in one but not the other - it is a rabbit hole of investigation you need to look into.
Font smoothing, resolution, color differences (different graphics cards can display different colors), different magnification settings in windows, different zoom settings in an application, different application performance with bad wait stage logic.&amp;nbsp; etc ,etc.
The most robust Surface Automation interfaces will use image searching to find screen element locations and then base clicks/keystrokes upon an offset from that image location.&amp;nbsp; You should also build logic to wait for these images as part of your intelligent waiting logic.&amp;nbsp; You should also use the color tolerance option in the image search object to allow for difference in colors.&amp;nbsp; The Surface Automation training for 4.2/5 details all these techniques.</description>
      <pubDate>Tue, 01 May 2018 17:00:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Surface-Automation-issue-in-BP-v4-2/m-p/62274#M15417</guid>
      <dc:creator>Denis__Dennehy</dc:creator>
      <dc:date>2018-05-01T17:00:00Z</dc:date>
    </item>
    <item>
      <title>Did you checked if you are…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Surface-Automation-issue-in-BP-v4-2/m-p/62275#M15418</link>
      <description>Did you checked if you are capturing the window's titled or text on your application modeler? If you do, make sure that the name or text doesn't change from one machine to another. That was the issue on one of our automations that uses SA.</description>
      <pubDate>Fri, 04 May 2018 21:37:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Surface-Automation-issue-in-BP-v4-2/m-p/62275#M15418</guid>
      <dc:creator>MelissaSuarez_G</dc:creator>
      <dc:date>2018-05-04T21:37:00Z</dc:date>
    </item>
  </channel>
</rss>

