1 BEST ANSWER
Helpful Answers
Hi,
Please try the following as troubleshooting steps:
Note - with the default TabProcGrowth setting there will be the main iexplore process plus a separate process for each tab in the IE window. You want to identify the process that the BPTravel application is running in and copy that PID. If TabProcGrowth has been changed then there should only be one IE process.
Note - this is only to check that you can successfully attach to the current window you have open. You will need to remove the Process ID once the problem has been narrowed down.
Note - with TabProcGrowth in the default setting (a separate process is created for each IE tab) you need the Child Index in order for BP to attach successfully.
All going well you have been able to attach following through this series of steps. I performed each of these steps on my own system as I documented it and it worked fine for me. If it didn't work at any stage then hopefully breaking it down like this has helped to identify where the issue lies within your environment.
------------------------------
Jared Rumball
Q4 Associates Ltd
https://www.q4associates.biz/
------------------------------
Please try the following as troubleshooting steps:
- Launch the BP Travel application
- Open Task Manager and get the PID from the Details tab:
Note - with the default TabProcGrowth setting there will be the main iexplore process plus a separate process for each tab in the IE window. You want to identify the process that the BPTravel application is running in and copy that PID. If TabProcGrowth has been changed then there should only be one IE process.
- Back in BP, clear all other Inputs from the Attach stage except the Process Name and then enter the copied PID directly into the Process ID input field like so:
Note - this is only to check that you can successfully attach to the current window you have open. You will need to remove the Process ID once the problem has been narrowed down.
- Check that you can successfully Attach to the currently open window with this configuration. There should be no window titles or child index parameters involved at this point, we are telling BP to attach to a specific process by it's ID.
- If that Attach action worked then it's time to introduce and test the Window Title parameter.
- Reset the object and Detach from the application.
- Enter "BP Travel*" as the default value for a Window Title text data item:
- Add the Window Title into the Attach inputs. Leave the Process ID in there for now as well (make sure you haven't closed the application and re-opened it or you will need to get the new PID!). Your Attach stage Inputs should now look like this:
- Check that this still attaches okay.
- If you're still good then Reset and Detach again. Now we're going to revert the solution to use the environment variable and the Window Titles collection instead of the basic Window Title text data item.
- Set the BP Travel Window Titles environment variable to the text "BP Travel*, Untitled*" (with a comma)
- Add the Create Collection of Titles stage back into your Attach flow
- After the Create Collection of Titles stage is run your Window Titles collection should have two rows like this:
- Change the Attach stage to use the Window Titles Collection instead of the Window Title text data item:
- Check that this configuration still attaches okay
- If that's still a success then Reset and Detach
- Now remove the Process ID from the Attach stage but add Child Index = 0 and retry:
Note - with TabProcGrowth in the default setting (a separate process is created for each IE tab) you need the Child Index in order for BP to attach successfully.
All going well you have been able to attach following through this series of steps. I performed each of these steps on my own system as I documented it and it worked fine for me. If it didn't work at any stage then hopefully breaking it down like this has helped to identify where the issue lies within your environment.
------------------------------
Jared Rumball
Q4 Associates Ltd
https://www.q4associates.biz/
------------------------------
Hi Keerthana,
When using the 'Window Title' or 'Window Titles' as inputs to the Attach Action, the value of the input must 100% match the actual Windows Titles, or use a wildcard option.
The best way to check what the full Windows Title is for the application is through the Processes Tab in Windows Task Manager:
Hope this helps.
------------------------------
Carl Carter
Developer Program Manager
Blue Prism
Europe/London
------------------------------
When using the 'Window Title' or 'Window Titles' as inputs to the Attach Action, the value of the input must 100% match the actual Windows Titles, or use a wildcard option.
The best way to check what the full Windows Title is for the application is through the Processes Tab in Windows Task Manager:
Hope this helps.
------------------------------
Carl Carter
Developer Program Manager
Blue Prism
Europe/London
------------------------------
