after successfull login automation when its redirects too dashboard page i am not able too perform any activity on dashboard page using UIPath Studio
i was trying too perform click activity on dashboard page elemnts
Ensure that your window selector is updated once you move on to the next page. I have seen in almost every single automation I have created, the Login page has a different window title than the actual web app screens after login.
With the Modern Design Experience in UiPath, the Window selector is a little hidden from the rest of the selector, so make sure you open the Window Selector dropdown in the Selector Window (or modify the Window Selector property in the properties pane) to modify that when advancing from the Login screen to the main app screen.
Related
I'm developing a Firefox addon. I have already created a login dialog box using panels in firefox addon-sdk. As the next step i need to open up another windows to display some information queried from the internet at the click on a button in the panel after login in.
I have already tried creating another panel and calling it (panel2.show()) from the first panel(panel1) but the 2nd panel is destroyed immediately or it's not resident on the screen may be since I'm calling it from within the first panel and it's closing itself off after calling the 2nd panel to show.
So i need to know a way to create the 2nd panel from within the first panel yet keep it out the life scope of the first panel. Or to find a better alternative to load the content page 2 in a separate window.
Thank you.
I am creating an app with Laravel that is supposed to use GoogleMaps API to show certain data in the map.
What I want to achieve is, that when you browse the root of the app, so when the user hits the main website, a new window is opened that will show a map to work with. So I want to have the ability to work with a second screen that only shows the map and all the information that should be displayed on the map.
How can I open a new window with certain content automatically when I browse to the main page.
Best
Sebastian
All modern browsers prevent this from happening, as it's commonly abused to serve popup advertisements. You'll need to make the new window happen via a user action, like a click on a button.
Im on development of window phone application,
Scenario:
Mini browser opening a page(for example google.com)
Google.com has a button called 'Search'
If User clicked button 'Search'
Redirect to an redirect.xaml
Else
Do nothing
Here is my scenario, how can I actually detect the User clicked the button and only they can proceed to the next page? Is that I have to use javascript in this situation? because if on web, this is technique which I will use.
Webbrowser control downloads we content and you have to parse the content or to handle the js actions. Thats the way to do it.
I have developed a windows phone user control which has only Browser control in it's grid.
I am navigating to this Browser control from my main page of app upon clicking a button. This browser control load Facebook authentication page.After posting the message to facebook , I want to go back to my main app .
For this I tried to hide the Browser control and i have set visibility to collapsed,and it shows a blank screen.
Any help on how can I go back to the main app which has called this browser control and maintain the same state as before ?
The following code works...
(Application.Current.RootVisual as PhoneApplicationFrame).GoBack()
Is it allowed by Windows Phone application certification rules, to only have users be able to return to a previous screen with the use of a hardware back button?
In my scenario, a user clicks on a setting button and lands at a settings page. He changes settings if he decides to, and all the changes get saved automatically, like in iOS.
But currently, the only way for the user to get out of the settings screen, is to press a hardware Back button on the phone.
Will such implementation of navigation functionality pass the Windows Phone certification?
Yes - leave the back button as the navigation method to get back to your main page after visiting the settings page. Not only is this allowed, but it is the desired method of back navigation, and it is what Windows Phone users expect. Here is a great article on the subject: http://blogs.msdn.com/b/ptorr/archive/2011/10/06/back-means-back-not-forwards-not-sideways-but-back.aspx
As far as I understand the terms of the navigation guideline is your usage the right way to go.
Back button
Pressing the back button from the first screen of an application must exit the application.
Pressing the back button must return the application to the previous page.
If the current page displays a context menu or a dialog, the pressing the Back button must close the menu or dialog and cancel the
backward navigation to the previous page.
You should only implement back button behaviors that navigate back or dismiss context menus or modal dialog boxes. All other
implementations are prohibited.
See this cheat sheet for more informations on the design guidelines.