14-11-22 06:03 PM
15-11-22 11:31 AM
Hi Maneesh,
When you are spying the elements in the windows are you following strict practices to ensure that they can be spied as quickly and efficiently as possible?
The rules to normally follow for anything foreground would be:
- Remove any traces of elements that could change such as URl's or Xpaths
- Limit the number of ticked attributes to as few as possible (usually 3-5)
- Include match index or indices where spying is slow to aid in matching speed
It is possible to spy using other methods such as accessibility however that may not be best suited.
Other than spying, can you ensure that your process is set to pick up after the first item where it can neatly handover into the process flow again?
E.g. When your process first starts it performs steps 1-3, then after getting an item performs steps 4-7.
Does your process navigate back to step 3 ahead of the process or is there a step 8 that needs to be closed and re-opened?
16-11-22 02:13 PM