564 attributed reviews in the last 3 years
Refreshingly small course sizes
Outstandingly good courseware
Whizzy online classrooms
Wise Owls only (no freelancers)
Almost no cancellations
We have genuine integrity
We invoice after training
Review 30+ years of Wise Owl
View our top 100 clients
This exercise is provided to allow potential course delegates to choose the correct Wise Owl Microsoft training course, and may not be reproduced in whole or in part in any format without the prior written consent of Wise Owl.
The aim of this exercise is to run a search for a specific string of text in Google. Start by creating a flow called Run a Google search, then use an input box to find what you're going to search for:
Capture your search text in a variable.
Add an action to start your favourite browser, going to the Google home page within it:
The familiar Google search box.
Add UI elements for the search box and the search button:
Initially you'll see something like this.
Give these elements better (more meaningful) names:
You can include spaces in UI element names.
Add commands to go to the search box and type in your search string:
If you leave the Emulate typing option chosen for the second action you can watch Power Automate Desktop typing in text!
You now realise that the easiest way to proceed is to just press Enter (or at least, use a Send keys action to mimic this). Add this action, then delete any UI elements you're not using:
The quickest way to remove UI elements that you're not using.
Run your flow to check that it works!
You may get an astonishingly high number of results, depending on your search string.
Edit your search text box UI element to see if you can make its definition a bit more forgiving:
Edit the search text box.
Choose to look at the selector path:
Click on the three dots to show the Selector builder dialog box for this UI element.
See if you can whittle the selector path down a bit. From this:
The original path will look something like this.
To more like this:
The final, (too?) simple selector path.
Test to see if your revised flow still works (it should).
A final thought: have you made your flow more or less robust?
Save this flow and close it down.
You can find other training resources for the subject of this exercise here:
25 Aytoun Street