<?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 Using Wildcards for HTML Element in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Using-Wildcards-for-HTML-Element/m-p/73669#M26274</link>
    <description>Hi,

I am attempting to use Wildcards on some of my HTML elements because the web application uses tabs and values can change dynamically.
For example..

ID: ext-comp-###
Path: /HTML/BODY(1)/DIV(##)/UL(1)/LI(1)/A(1) 

Even thought I am able to highlight these elements using wildcards, the search is incredibly slow and does not work when I try actually to run a Click action on it. 
Do you have any possible workarounds for this? I've tried many different Match combinations and find it impossible to highlight/search the element I want effectively. 

Thanks in advance</description>
    <pubDate>Thu, 09 Mar 2017 20:42:00 GMT</pubDate>
    <dc:creator>jonathan_mak</dc:creator>
    <dc:date>2017-03-09T20:42:00Z</dc:date>
    <item>
      <title>Using Wildcards for HTML Element</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Using-Wildcards-for-HTML-Element/m-p/73669#M26274</link>
      <description>Hi,

I am attempting to use Wildcards on some of my HTML elements because the web application uses tabs and values can change dynamically.
For example..

ID: ext-comp-###
Path: /HTML/BODY(1)/DIV(##)/UL(1)/LI(1)/A(1) 

Even thought I am able to highlight these elements using wildcards, the search is incredibly slow and does not work when I try actually to run a Click action on it. 
Do you have any possible workarounds for this? I've tried many different Match combinations and find it impossible to highlight/search the element I want effectively. 

Thanks in advance</description>
      <pubDate>Thu, 09 Mar 2017 20:42:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Using-Wildcards-for-HTML-Element/m-p/73669#M26274</guid>
      <dc:creator>jonathan_mak</dc:creator>
      <dc:date>2017-03-09T20:42:00Z</dc:date>
    </item>
    <item>
      <title>Wildcards don't really work</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Using-Wildcards-for-HTML-Element/m-p/73670#M26275</link>
      <description>Wildcards don't really work on HTML. Workaround for this might be making the element have dynamic path and then, wherever you would want to use this element in process, you would have a numeric counter and a wait stage, basically, if element is not found, you add +1 to your number and try to find the element again, repeat till you find it. The dynamic path, in whatever stage you use the element in, would look something like - ""/HTML/BODY(1)/DIV("" &amp;amp; [Counter] &amp;amp; "")/UL(1)/LI(1)/A(1)</description>
      <pubDate>Thu, 09 Mar 2017 20:57:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Using-Wildcards-for-HTML-Element/m-p/73670#M26275</guid>
      <dc:creator>AgneseGurecka</dc:creator>
      <dc:date>2017-03-09T20:57:00Z</dc:date>
    </item>
    <item>
      <title>Thanks a lot agnese, I</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Using-Wildcards-for-HTML-Element/m-p/73671#M26276</link>
      <description>Thanks a lot agnese, I managed to effectively retrieve specific highlighted elements by enabling Match Index and Match Reverse. I'm not sure how robust this is but if it fails in the future I will try your method which sounds like a good idea. Thanks again.</description>
      <pubDate>Fri, 10 Mar 2017 01:07:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Using-Wildcards-for-HTML-Element/m-p/73671#M26276</guid>
      <dc:creator>jonathan_mak</dc:creator>
      <dc:date>2017-03-10T01:07:00Z</dc:date>
    </item>
  </channel>
</rss>

