<?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 Hello Sandeep,
Which version… in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Working-with-Siebel-web-application-on-Google-Chrome/m-p/87567#M38267</link>
    <description>Hello Sandeep,
Which version of BP are you using when having this time issues?
We are using 6.0.1 and only region mode recommended.
As far i know until 6.3.x version better not use chrome with BP, once you have this version or upper, i tried, and i can say it's really fast when using Browser/UI Mode.
More than HTML and AA, ofc.
Regards,
Daniel
&amp;nbsp;</description>
    <pubDate>Tue, 16 Oct 2018 16:56:00 GMT</pubDate>
    <dc:creator>DanielB_Frutos</dc:creator>
    <dc:date>2018-10-16T16:56:00Z</dc:date>
    <item>
      <title>Working with Siebel web application on Google Chrome</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Working-with-Siebel-web-application-on-Google-Chrome/m-p/87565#M38265</link>
      <description>Has any one tried automating the latest Siebel web application which only works in Chrome?
I find it hard to identify elements and it takes a long time to find and read the element on the screen.
Are there any command line arguments which can be used in Chrome to make&amp;nbsp;the identifying elements faster?</description>
      <pubDate>Wed, 08 Aug 2018 23:16:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Working-with-Siebel-web-application-on-Google-Chrome/m-p/87565#M38265</guid>
      <dc:creator>SandeepNalla</dc:creator>
      <dc:date>2018-08-08T23:16:00Z</dc:date>
    </item>
    <item>
      <title>I worked with Siebel but in…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Working-with-Siebel-web-application-on-Google-Chrome/m-p/87566#M38266</link>
      <description>I worked with Siebel but in Internet Explorer, and I imagine that in Chrome is similar. The fastest way to identify elements is using Region Mode (image recognition). With any other method (HTML, AA...) are 3-4 times lower. If anyone has obtained fast responses with any other methods, let us know them &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;</description>
      <pubDate>Mon, 20 Aug 2018 16:36:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Working-with-Siebel-web-application-on-Google-Chrome/m-p/87566#M38266</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-08-20T16:36:00Z</dc:date>
    </item>
    <item>
      <title>Hello Sandeep,
Which version…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Working-with-Siebel-web-application-on-Google-Chrome/m-p/87567#M38267</link>
      <description>Hello Sandeep,
Which version of BP are you using when having this time issues?
We are using 6.0.1 and only region mode recommended.
As far i know until 6.3.x version better not use chrome with BP, once you have this version or upper, i tried, and i can say it's really fast when using Browser/UI Mode.
More than HTML and AA, ofc.
Regards,
Daniel
&amp;nbsp;</description>
      <pubDate>Tue, 16 Oct 2018 16:56:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Working-with-Siebel-web-application-on-Google-Chrome/m-p/87567#M38267</guid>
      <dc:creator>DanielB_Frutos</dc:creator>
      <dc:date>2018-10-16T16:56:00Z</dc:date>
    </item>
  </channel>
</rss>

