Switch to a new window in a browser session - Page index

Mitch Dale

Hey @Product,

Can someone clarify how the 'Page Index' match method is supposed to work? According to the WA config, the page index of the initial window is 0 and the first pop up will be 1, and so on.

However I'm observing something different. In a browser session of mine, there are 2 tabs open. When I attempt to Switch the focus to page 0, the job returns successful but nothing changes. When I switch the focus to page 1, the focus changes to the first tab, and when I switch the focus to page 2, the focus changes to the second tab.

Below is a screen recording where this behaviour occurred:

Has something changed with the 'Switch to a new window in a browser session' WA?

Nick

Hey Mitch,

Nothing has changed. Upon closer examination of the page index feature that we are using for this Wrk Action, it looks like the pages should be assigned in order of creation ascending (oldest tab is 0) rather than order from left to right on your chrome tab. In most cases new tabs appear on the right and everything works as expected. However, in this case the right tab might have been opened before the left tab? Or something that you've done in the Wrkflow may have reset the page indexes so your right tab is now 0.

If you share the Wrkflow I'd love to take a look to better understand what is causing this issue.

Mitch Dale

Thanks @Nick,

The Wrkflow I'm referencing here is https://account.wrk.com/designer/?wrkflow_id=54954&client_id=5833

For context, the Wrkflow works by logging into Sage online (we start with one tab with the title 'Clients and Prospects*'), and then it loops through a list of client names. When the very first loop iteration executes, a new tab is created, the Wrkflow switches focus to the new tab via it's title, performs some actions within the second tab, and then goes back to the first tab to go to the next client. As the Wrkflow loops through each client, the Wrkflow switches focus between the 2 tabs without closing anything.

Whenever a client name is clicked on in the first tab, the second tab should have the title 'Summary'. However sometimes it does not have this title, and instead either the tab is requiring the system to re-log in, or perform a CAPTCHA. In either case, what the WF attempts to do is switch focus to the second tab (on the right), and check whether there's a login prompt/captcha.