fab23a5f-5f0b-41fd-a29a-2567279b123d.jpg

UiPath MVP/ RPA Solution Architect

This component will be very helpful to handle browser issues especially when network was slow.

Lahiru, I want to use this Browser Page Load Timeout Handler Template. But it didn't show under activities even after installation. Could you please hep? Thank you 777741745 (Sri Lanka)

3d291518-fe2c-4d76-97c5-2260bfa6f38c.zip

Snippet DescriptionWeb page UI automation solutions are built around the UI elements in the web application page. However, if web page is loading slower than usual, automation solution might run into run-time errors due to not being able to load the required UI elements on time. Such failures can result in the termination of the execution process. This component provides two set of xaml file snippets which can use used to handle such instances by trying to reload the page if a particular unique UI element is not available in the web page.Web application automation includes two main tasks.Open browser activity to open up a browser and to load a particular web pageNavigating to a different web page using an already open web application.Each of the scenarios mentioned will result in a web page load. However, if the web page is not loaded as expected, there should be a way to reload the web page as a fail safe mechanism. The two template snippets provided in this component address these two scenarios mentioned.WebApplicationInitiation.xaml - This xaml file will handle the first scenario mentionedWebApplicationPageChange.xaml - This xaml file will handle the page change of an already open applicationYou can simply apply these two xaml files for your automation solution to handle web automation.Web Application InitiationInput Arguments<ul><li>In_RetryAttmpts: Describes the number of times you wish to retry a page reload. The default would be three attempts</li><li>In_WebURL: The web URL you need to be accessed</li><li>In_PageLoadConfirmationSelector: A successful page load is identified using a unique UI element of the web page. If the UI element is available, in the web page and if the existence check returns true, it is identified that the page was loaded successfully. If it's not, it will be identified as a trigger to reload the page. Provide a selector for a unique UI element of the web page for this argument.</li></ul>Output Arguments<ul><li>Out_IsPageLoaded: Boolean value that describes whether the page load was successful or not</li><li>Out_UIBrowser: Since this xaml file opens up the web browser for the first time, it will also return the Browser variable so that it can be used for further processing within the solution.</li></ul>Web Application Page ChangeThis is very much similar to the web application initiation. The only difference of the arguments would be that this xaml file will expect one additional argument. The additional argument would be the Browser element which was returned from Web Application Initiation xaml file. It will be used to identify the browser object.

There can be many reasons for web applications to not properly respond to page loads. Such reasons most of the time causes runtime errors in automation solutions that cause it to fail

bfe07f15-7600-4a50-a892-cc74d30c8394.PNG

15511ad9-a97d-4ee8-9e03-22967f39a7ee.PNG

MIT License Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

3b1d749d-923f-4a4d-b91b-3faa0d3c84f7.zip

950735d1-adda-4c0c-b889-2e27efb8d8d1.zip

This template will ease out the handling of web page loading problems by introducing an automatic page reload option. This mechanism comes in really handy when you have web page loading issues like slowness of the system/ network or any other page loading issues.

Web page UI automation solutions are built around the UI elements in the web application page. However, if a web page is loading slower than usual, the automation solution might run into run-time errors due to not being able to load the required UI elements on time. Such failures can result in the termination of the execution process. This template provides two set of xaml files which can be used to handle such instances by trying to reload the page if a particular unique UI element is not available in the web page.

Web application automation includes two main tasks.

Open browser activity to open up a browser and to load a particular web page.

Navigating to a different web page using an already open web application.

Each of the scenarios mentioned will result in a web page load. However, if the web page is not loaded as expected, there should be a way to reload the web page as a fail safe mechanism. The two template provided address the two scenarios mentioned.

WebApplicationInitiation.xaml - This xaml file will handle the first scenario mentioned.

WebApplicationPageChange.xaml - This xaml file will handle the page change of an already open application.

You can simply apply these two xaml files for your automation solution to handle web automation.

In_RetryAttmpts: Describes the number of times you wish to retry a page reload. The default would be three attempts.

In_WebURL: The web URL you need to access.

In_PageLoadConfirmationSelector: A successful page load is identified using an unique UI element of the web page. If the UI element is available in the web page and if the existence check returns true, it is identified that the page was loaded successfully. If it's not, it will be identified as a trigger to reload the page. Provide a selector for an unique UI element of the web page for this argument.

Out_IsPageLoaded: Boolean value that describes whether the page load was successful or not.

Out_UIBrowser: Since this xaml file opens up the web browser for the first time, it will also return the Browser variable so that it can be used for further processing within the solution.


This is very much similar to the web application initiation. The only difference of the arguments would be that this xaml file will expect one additional argument. The additional argument would be the Browser element which was returned from Web Application Initiation xaml file. It will be used to identify the browser object.

Introduced Attached browser activity to follow best practices where it was not used earlier

31991619-f9b2-4549-b46d-ca735dcd3156.zip

5b2a8ec9-9822-4f07-9d29-63291c85c020.nupkg

Conversion to .nupkg file for availability in Studio Template Feed