how to use the Navigate (to URL) stage properly? Why am I encountering the said issue?

[RonAng]

I€™m currently encountering an issue using Navigate stage to a specified URL. "Internal - Failed to perform step 1 in Navigate Stage 'Navigate2' on page 'Launch' - Object reference not set to an instance of an object. So I guess basically my question is how to use the Navigate (to URL) stage properly? Why am I encountering the said issue? Inside the attached zip file is the screenshot of the table and the BO I coded (just remove the _.jpeg in the filename). Scenario: 1. Launch IE and go to page http://www.7continentslist.com/ - Start > Navigate (launch) 2. There will be a table there with the continents €“ Read > Save to a collection 3. Loop through the data €“ Loop collection 4. For every continent (column 2), go to a URL depending on the continent: https://en.wikipedia.org/wiki/{name of continent} €“ Navigate (URL) a. Example: https://en.wikipedia.org/wiki/Asia, https://en.wikipedia.org/wiki/Africa With the example above, I am encountering the issue on step 4. Also, I have already tried setting TabProcGrowth to 0.

[Denis__Dennehy]

Firstly, the object design for your solution is incorrect. 7continentslist and wikipedia are different browser applications, you should not have a single object for both of these, you should have different objects for them. This will solve your issue, as you will not be using Navigate URL. You should have an experienced Blue Prism user or consultant available to you to evaluate your object designs. If you do need to use Navigate URL (to naviage to different pages within the same application rather than navigating to totally different applications) there is a known issue in version 5 of the product that stops Navigate URL from working. It is currently being worked on by the product team so a fix shoudl be expected in a release shortly. In the meantime your workaround is to navigate between screens in your single application as you would manually (clicking on buttons/menu options etc) rather than using navigate url,

[RonAng]

Thanks Dennis! Ok that makes sense - they are different browser applications. So my follow-up question with that one is: How and when to use Navigate URL properly? I tried navigating to the same exact URL and still encounters the same issue. Does that mean that Navigate URL should not be used at this time because of it having a known issue?

[Denis__Dennehy]

Like I said, there is a known issue in v5 that stops navigate url from working. It is going to be fixed in the next release (5.0.27) available soon. Navigate URL is handy for quickly navigating between screens in the same application, where the URL changes on different screens. So rather than navigating several screens to get to the one you want, you just use the URL. For many applications this is not suitable because the URL stays the same no matter what screen you are on - so it's usefulness depends upon how the browser app is built.