I’m trying to navigate to the invoice number page directly post login. However, sometimes it gets routed to the desired page and sometimes doesnt. should i add a delay here? is attach browser required in this case or can we use navigate to without attach browser?
have attached a simple 4 step (static username and password for now) sequence. what would be the best fullproof method in this case.
Main.xaml (8.4 KB)
any guidance would be highly appreciated
3 ways to go about it.
- remove the attach browser. It is already within the open browser scope, and therefore it doesn’t need to have a browser variable in the input pane.
- Outside of the open browser activity, you can put in an attach browser activity & supply the browser variable from the open browser activity. Then put the navigate activity within here and don’t supply a browser variable.
- Outside of the open browser activity, put a navigate activity and supply the browser variable from the open browser activity.
If it was me, I’d just keep navigate activity within the open browser scope and there is no need to supply a browser variable (option 1). I attached it showing all options here: Main (3).xaml (20.7 KB)
Thanks for the detailed explanation. While i understood the concept, i still didnt work for me…I tried option 1, it still didnt navigate to that url without giving any error. Is something wrong that i am doing?
PFA the file while trying to replicate option1
Main.xaml (7.2 KB)
Putting an Delay will not work here.
Put an Element Exist Activity and Point it to the DashBoard or Acme Home Page link.
If Element Exist :True
— Proceed with the Navigation Link
— Do Nothing or Re Fresh page or Relogin - Depends on your implementation.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.