Application Modeller - Region Mode

[Anonymous]

Hi all, We are currently using the Region Mode to spy a particular application. We would like to use a wait stage to check a certain element is available before we click it (much like check exist in HTML mode). However, the nearest action we seem to be able to use is something called 'Check Window Attribute' which has an input of 'Attribute Name'. Can I ask what this input refers to and what value should we be inputting here? Thanks very much!

[TomBlackburn1]

What version of Blue Prism are you running? One of the later releases include a condition 'Contains Image' within the Wait stage. You can then use an image data item with an stored initial value of the image you want to wait for (this will need to be captured using a read image action on the specified region). I find this is the 1st port of call when trying to validate when to it is okay to continue processing on a Citrix based application. If this fails and the wait stage times out, then you could then revert to screen scraping images. Tom.

[Denis__Dennehy]

Hello, have you completed the Surface Automation training that is required for use of features such as regions? If not it is strongly recommended. The Surface Automation tells us how to wait for images - by using actions in either the image search or image recognition utility objects. You can then have a loop in your flow that keeps trying to find the image for a configured amount of time and then throw an exception if the image is not found. I recommended you wait for images with a tolerance (option in the image search utility - try setting it to 20) as colours in regions may be slightly different on different PCs.

[DeoCabral]

you must input the Attribute name to it e.g. html attribute ""Value"" and on the wait stage choose from equal, not equal, Reg(ex) or Wildcard there you must add the data contained inside the attribute ""Value"".

[Denis__Dennehy]

You should be using Image Recognition to search an image of your screen for an image. There is a lot about how to do this in the Surface Automation training (it uses the Image Search utility object). To wait for the element you would just build in some additional logic so that your flow loops around attempting to search for an image of your element in the full screen until the time has elapsed.