Why is Window Selector required when Check App State is inside a Use Application/Browser, using an Input Element?

These modern activities (UiAutomation.Activities 21.4.4) still don’t handle variables well.

I have a Use Application/Browser that doesn’t use selectors, it uses Input Element:

image

Therefore the embedded Check App State shouldn’t need a Window Selector, it should inherit from Use Application/Browser. But when I try to edit target:

image

And when running the automation:

image

Hey @postwick

This should work as we are the using the same in all the processes.

Btw, our version of activities is around 21.x

Thanks
#nK

I’m not saying it doesn’t work, I’m saying it shouldn’t require a Window Selector because the window is passed as a variable. But it still requires Window Selector. No idea what would happen if the window selector were incorrect, if it’s just ignore.

1 Like

Hey @postwick

Could you maybe clarify how do you extract the input element that you pass as a variable?

The design time selector editing experience makes sense, because the variable is not set at the time, but I am wondering what this GetWindowSelectorTags not implemented for tag 'webctrl' is all about. Where does it show this error?

From a previous Use Application/Browser.

When running the automation.

I can see that the internal issue that was tracking this topic was marked as completed in 22.10. Therefore, upgrading UIAutomation package to 22.10 should solve the issue.

1 Like

This update is going to be released with the 22.12 preview, within the next few days.

1 Like

Solves it how? What has been changed?

if activities are configured to use a UIElement variable as input, they will not longer require a card.

2 Likes

Hi Paul,
Did you ever find a fix for this? I just ran into this same issue with my project. We pass the browser through io argument throughout process but I can’t get this checkappstate to work with that.
Thanks,
Joshua

No. The only way I’ve been able to modify an activity that’s showing this error is to add a Use Application/Browser, indicate the window, then copy the activity into it, make the selector changes, then copy it back to the Use Application/Browser that has the input element.

What’s weird is it doesn’t always do this, maybe it depends on which app you’re working in - but I haven’t found any pattern.

1 Like