Wait stage in java automation

[VratHimbo]

Hi team,
i read the document about java automation, I noticed that it is a very slow automation, also following best practices, i have to do with a java web app via iexplore, so my question is:it must always be used the "wait stage" to check that the java element is present before a click, reader, etc.?
How can i improve resilience and speed, any tips? 
Thanks in advance

------------------------------
Vrat Himbo
------------------------------

[VratHimbo]

up please

------------------------------
Vrat Himbo
------------------------------

[AmiBarrett]

Try adding (without quotes) "descendtree,ignorenotshowing" to the additional options field in the application modeler.

Additionally, you may want to consider using some of the following filters:

• Match Index
• Ancestor Count
• aAncestor Count
• Ordinal
• Visible
• Hidden
• Parent Child Count

------------------------------
Ami Barrett
Automation Developer, Team Lead
Blue Prism
Plano, TX
------------------------------

[NileshJadhavBP]

Hi Vrat,

Below point will help you.

1. You can select only required attributes.
2. 1 object for 1 application screen along with attach page.
3.Use wait stage to validate you reach on correct screen or page is loaded successfully.
4.Try to avoid static wait.
5.Use wait stage after each attach action call.

------------------------------
Nilesh Jadhav
Senior RPA Specialist
ADP
India
------------------------------

[VratHimbo]

Thanks @AmiBarrett,
what will be the changes by inserting​ descendtree,ignorenotshowing, can you explain me, please?

For the second tip, and that is to use some filters, how it improves speed execution?

Thanks again.

------------------------------
Vrat Himbo
------------------------------

[VratHimbo]

Hi @Nilesh Jadhav,
That's more or less what I did​. multi-object design, avoid static wait stage, or in case only before the "wait dinamic" java element, like described in java automation guide.
But i've seen that loads the elements and performs the actions very slowly, even in "fast" mode.

Have a nice day

------------------------------
Vrat Himbo
------------------------------

[AmiBarrett]

descendtree, as far as I'm aware, is just a sort optimization for the DOM. ignorenotshowing tells the parser to ignore hidden elements (something known to plague anything using Java/Accessibility). 

As for the filters, regardless of spy type, you can think of them as parameters to narrow down a DOM search. The more reliably refined you make it, the fewer elements the software will need to search through in order to find what you're looking for.

------------------------------
Ami Barrett
Automation Developer, Team Lead
Blue Prism
Plano, TX
------------------------------

[VratHimbo]

Hi @AmiBarrett,
i didn't find this field on my application modeler, how can i find it?
I don't know if it has anything to do with it, but is a web-based application so in application modeler i've selected browser web autiomation (internet explorer ) and not java automation, is that correct?

Many thanks​

------------------------------
Vrat Himbo
------------------------------

[VratHimbo]

I confirm that i don't have this field, why?

Thx

------------------------------
Vrat Himbo
------------------------------

[AmiBarrett]

Ah. Yes, that's likely the reason. If it'll let you attach to it as a Java model, those should show.

------------------------------
Ami Barrett
Automation Developer, Team Lead
Blue Prism
Plano, TX
------------------------------