<?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 If BP can't find an element… in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Application-Modeller/m-p/66217#M18822</link>
    <description>If BP can't find an element at run time it's because the element as modelled at design time is not there. This will either be because the selection of attributes chosen by the developer is not unique or flexible enough to match the element in all situations, or because the synchronisation between the page logic and the application state is not being controlled. In other words, the logic is running too fast and the element is not yet present at the time when the business object tries to use it.</description>
    <pubDate>Mon, 16 Jul 2018 14:54:00 GMT</pubDate>
    <dc:creator>John__Carter</dc:creator>
    <dc:date>2018-07-16T14:54:00Z</dc:date>
    <item>
      <title>Application Modeller</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Application-Modeller/m-p/66216#M18821</link>
      <description>I am spying a window based application. At the time of spying the application after indentifying and highlighting the elements of application everything is good. But at the time of process run the same element is not been identified. How to solve the issue. I am using Bp 5.</description>
      <pubDate>Mon, 16 Jul 2018 14:37:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Application-Modeller/m-p/66216#M18821</guid>
      <dc:creator>Shashi_RanjanKu</dc:creator>
      <dc:date>2018-07-16T14:37:00Z</dc:date>
    </item>
    <item>
      <title>If BP can't find an element…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Application-Modeller/m-p/66217#M18822</link>
      <description>If BP can't find an element at run time it's because the element as modelled at design time is not there. This will either be because the selection of attributes chosen by the developer is not unique or flexible enough to match the element in all situations, or because the synchronisation between the page logic and the application state is not being controlled. In other words, the logic is running too fast and the element is not yet present at the time when the business object tries to use it.</description>
      <pubDate>Mon, 16 Jul 2018 14:54:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Application-Modeller/m-p/66217#M18822</guid>
      <dc:creator>John__Carter</dc:creator>
      <dc:date>2018-07-16T14:54:00Z</dc:date>
    </item>
    <item>
      <title>But at the time of initial…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Application-Modeller/m-p/66218#M18823</link>
      <description>But at the time of initial identifying and highlighting BP is not showing any error. But if the same application&amp;nbsp;&amp;nbsp;is used for run process BP does not find the element. And about logic running fast wait has been provided by me.</description>
      <pubDate>Mon, 16 Jul 2018 15:58:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Application-Modeller/m-p/66218#M18823</guid>
      <dc:creator>Shashi_RanjanKu</dc:creator>
      <dc:date>2018-07-16T15:58:00Z</dc:date>
    </item>
    <item>
      <title>Match rules are not unique…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Application-Modeller/m-p/66219#M18824</link>
      <description>Match rules are not unique. I would suggest to interrogate again and choose only those elements that are not dynamic in nature.</description>
      <pubDate>Mon, 16 Jul 2018 16:08:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Application-Modeller/m-p/66219#M18824</guid>
      <dc:creator>NishantChoukse1</dc:creator>
      <dc:date>2018-07-16T16:08:00Z</dc:date>
    </item>
  </channel>
</rss>

