Guys, I would like some help with a problem I came across here. I’m using the click to click print button activity on a website in the browser to generate a PDF file, but when I get to the print dialog I ask to click save, but it won’t work at all, does anyone have a solution for this ?
@Natan_Crespo Did you check by enabling
Click properties like simulate key:
Put some delay before in property.
Enable Disabled Element
Use Full selector (Strict+fuzzy)
After the Click activity that clicks the print button, you have to use a Use Application/Browser activity to attach to the print dialog window. Within it, add the activities to click/type etc what you need.
Simulate Click: Instead of using the regular “click” activity, you can use the “Simulate Click” or “Send Window Messages” options in the properties of the click activity.
Hotkeys: Instead of clicking on the “save” button, you can try sending hotkeys to the print dialog. For example, you can use the “Type Into” activity to send the “Ctrl+S” hotkey combination, which is commonly used for the “Save” action. Make sure the print dialog has focus before sending the hotkeys.
@Natan_Crespo
Are you using classic activities or Modern activities.
If you are using classic activity then use attach browser for this window and use click inside.
If you are using modern design then use browser/application and set property never open. It will behave like attach browser
Click ‘Save’: Unable to find GUI element for this action.
Possible solutions:
• Check that the application is open and that the GUI element is visible on the screen at runtime
• Edit the GUI Activity Target and use Validation to debug the issue.
• If necessary, indicate the element again if its properties have been changed
• Use the “Check state” activity to check the state of the application before executing the action
• Increase the value of “Delay before” for the application to render completely in time and become responsive
For click activity that you are using to click on save button make the input mode to hardware events, you can find the input mode option in click activity properties.
Why because when you click on print it will open a window which is the desktop application for the desktop applications we have to use the hardware events as input mode of any UI activity.