Are the object recognition results depending on object position?

[nomad]

Hi Allan

Are the “selector” and “recorder” results “positional” (depending on the position of the “scanned” object on the screen)?

If I change the position/dimensions of the OS “open file” window, workflow will fail. The solution is to “recreate” recognition process.

How to avoid this effect?

---

Kind regards,
Andy

[Allan_Zimmermann]

No. Except image recognition with process limits

[nomad]

Hi Allan,

Yesterday I did working flow related to the “Open File” window and today it said “# Failed locating 1 item(s)”.

When I opened “selector” window related to the first failed activity, I did not see any Firefox branch in the left pane. But still have previously recorded selector.

I have to “reselect” all failed activities and flow will be back at work.

What I am doing wrong?

---

Kind regards,
Andy

[nomad]

Sorry, I forgot the screen.

When I open selector once more, the FF branch will appear in the left pane. But the flow still does not work.
I have to point desired elements once again.

[Allan_Zimmermann]

save the old and new, and then compare them. Then modify the selector to “hit” both versions ( by removing properties or using wildcard’s * )

[nomad]

Hi Allan,

I made the clipboard copy of the working (for a while) and not working activity and saved it as xml file.
Inside I found and picked up two differences only in “selector” area.

a. additional sequences xD;&# in the Selector (!) .
b. different recognition of the browser window/tab. Once it has attribute FrameworkId with value “Win32”, once “Gecko”. To be sure, in some circumstances both are working (!) ;), but “Gecko” seems to have wider area of stability.

Selector for “Open file” window of the browser was created only by arbitrary choice of the activity (win.get_element) and select element (menu) or browse object tree (left pane) and “select element” on the chosen tree node. Sometimes there is no tree in the left pane (message “loading” and nothing), sometimes both activities returns different results on the different levels…

Recorder does not recognized (correctly) this window and objects at all.

“modify the selector to “hit””
It remind me the “process of the normalization” in the test automation tools (Loadrunner, Silk Suite), where recorded scenarios demanded such “normalization” to be used repetitively.

I still miss stability.

---

Kind regards,
Andy

[nomad]

Hi Allan,

The only difference in selector which I constantly watch is “arguments” element. Depending on way of “select”, it has value “” (select menu) or null (select element).

The scenario is constant:
I save working workflow.
Close Designer.
Open Designer (not even browser).
Run working workflow, which stop on the random (?) activity.
Highlight not work for this activity.
Selector has no change relating to state before save.
Refresh selector by menu select or “select element” and save.
Workflow start to work (to the next time).

Still in “Open file” browser window, field file name.

---

Kind regards,

“Select menu” selector for “file name” field:

[
{
“filename”: “%ProgramFiles%\Mozilla Firefox\firefox.exe”,
“processname”: “firefox”,
“arguments”: “”,
“Selector”: “Windows”,
“search_descendants”: “True”,
“mouse_over_search”: “False”
},
{
“ClassName”: “MozillaWindowClass”,
“Name”: “BMC Remedy (Search) — Mozilla Firefox”,
“ControlType”: “Window”,
“FrameworkId”: “Win32”
},
{
“ClassName”: “#32770”,
“Name”: “Wysyłanie pliku”,
“ControlType”: “Window”,
“FrameworkId”: “Win32”
},
{
“ClassName”: “ComboBox”,
“Name”: “Nazwa pliku:”,
“ControlType”: “ComboBox”,
“AutomationId”: “1148”,
“FrameworkId”: “Win32”
},
{
“ClassName”: “Edit”,
“Name”: “Nazwa pliku:”,
“ControlType”: “Edit”,
“AutomationId”: “1148”,
“FrameworkId”: “Win32”
}
]

“Select element” selector for “file name” filed:

[
{
“filename”: “%ProgramFiles%\Mozilla Firefox\firefox.exe”,
“processname”: “firefox”,
“arguments”: null,
“Selector”: “Windows”,
“search_descendants”: “True”,
“mouse_over_search”: “False”
},
{
“ClassName”: “MozillaWindowClass”,
“Name”: “BMC Remedy (Search) — Mozilla Firefox”,
“ControlType”: “Window”,
“FrameworkId”: “Win32”
},
{
“ClassName”: “#32770”,
“Name”: “Wysyłanie pliku”,
“ControlType”: “Window”,
“FrameworkId”: “Win32”
},
{
“ClassName”: “ComboBox”,
“Name”: “Nazwa pliku:”,
“ControlType”: “ComboBox”,
“AutomationId”: “1148”,
“FrameworkId”: “Win32”
},
{
“ClassName”: “Edit”,
“Name”: “Nazwa pliku:”,
“ControlType”: “Edit”,
“AutomationId”: “1148”,
“FrameworkId”: “Win32”
}
]