Interact with windows warning "app locked"
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
13-07-22 10:21 AM
Hi,
I need to close the Windows warning shown in below screenshot. It should appear consistently during runtime. It blocks all other content on the screen, so I cannot figure out a way to spy it traditionally. I have two ideas:
1. Simply click the coordinate on the screen where the close button is without interacting or checking if the popup exists (not ideal and I have not investigated how to build it)
2. Spy a screenshot and using region mode, and interact using normal surface during runtime. I managed to spy the below screenshot and map the button, but I cannot get it to work, likely because I do not know how to define a window. Screenshot of my app modeller below. Maybe it is possible to set up a "floating" surface element outside any windows, or just define the entire screen as a window?
Any suggestions how to move forward with this?
------------------------------
Stefan Roi
------------------------------
I need to close the Windows warning shown in below screenshot. It should appear consistently during runtime. It blocks all other content on the screen, so I cannot figure out a way to spy it traditionally. I have two ideas:
1. Simply click the coordinate on the screen where the close button is without interacting or checking if the popup exists (not ideal and I have not investigated how to build it)
2. Spy a screenshot and using region mode, and interact using normal surface during runtime. I managed to spy the below screenshot and map the button, but I cannot get it to work, likely because I do not know how to define a window. Screenshot of my app modeller below. Maybe it is possible to set up a "floating" surface element outside any windows, or just define the entire screen as a window?
Any suggestions how to move forward with this?
------------------------------
Stefan Roi
------------------------------
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
15-07-22 07:58 AM
Hello Stefan,
One possible option to handle this scenario could be to:
1. Create a separate VBO to handle this popup window alone so you can call it repeatedly throughout your automation.
2. In that VBO, spy the entire blue popup window and call it in a 'Check Exists' intelligent wait stage.
3. At the start of the VBO, Activate application, then the check exists condition in point 2.
4. If it returns True, then go ahead and include the click close button stage. It its false then End.
Now there are two ways you could call this VBO.
1. Every-time you invoke an object from your process that interacts with this application, call the above VBO first.
2. OR you could call this VBO in the Exception handling logic of your process. Where the original object returns an error and going into the Recovery block, then you could call this VBO as one of the actions in that logic.
Alternatively, you can also reach out to your admin to remove the block for your automation accounts altogether.
------------------------------
Harpreet Kaur Product Consultant
------------------------------
One possible option to handle this scenario could be to:
1. Create a separate VBO to handle this popup window alone so you can call it repeatedly throughout your automation.
2. In that VBO, spy the entire blue popup window and call it in a 'Check Exists' intelligent wait stage.
3. At the start of the VBO, Activate application, then the check exists condition in point 2.
4. If it returns True, then go ahead and include the click close button stage. It its false then End.
Now there are two ways you could call this VBO.
1. Every-time you invoke an object from your process that interacts with this application, call the above VBO first.
2. OR you could call this VBO in the Exception handling logic of your process. Where the original object returns an error and going into the Recovery block, then you could call this VBO as one of the actions in that logic.
Alternatively, you can also reach out to your admin to remove the block for your automation accounts altogether.
------------------------------
Harpreet Kaur Product Consultant
------------------------------
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
15-07-22 09:54 AM
Hi Stefan
I think you might not be able to spy this window since it looks to be a MS windows screen rather than a window produced from the application you're using. I would suggest letting the pop up window appear and if possible open the task manager to check if this window shows in the list of open applications. If it does you could then use Utility-Environment - Read Memory stats as a way of identifying if the window exists by providing the process name as shown in task manager. This way you will be able to build in the condition if the window exists do one action and if not then carry on.
The issue of clicking the close button if you cant identify this could be a challenge but you could try doing a Global send key event action using {TAB} to get to the button then followed by global send key event action using {ENTER}. Alternatively you might need to spy it as a region and click the center.
------------------------------
Michael ONeil
Technical Lead developer
NTTData
Europe/London
------------------------------
I think you might not be able to spy this window since it looks to be a MS windows screen rather than a window produced from the application you're using. I would suggest letting the pop up window appear and if possible open the task manager to check if this window shows in the list of open applications. If it does you could then use Utility-Environment - Read Memory stats as a way of identifying if the window exists by providing the process name as shown in task manager. This way you will be able to build in the condition if the window exists do one action and if not then carry on.
The issue of clicking the close button if you cant identify this could be a challenge but you could try doing a Global send key event action using {TAB} to get to the button then followed by global send key event action using {ENTER}. Alternatively you might need to spy it as a region and click the center.
------------------------------
Michael ONeil
Technical Lead developer
NTTData
Europe/London
------------------------------