Hi @surajseetha ,
My brain tells me that there is something solvable going on here. I can't put my finger on it, but I feel like there has to be something. I am honestly shocked that it isn't working when you change the application modeller's application manager mode to Embedded. And you did check both the launching object and the second attach object? I swear that behavior sounds like it is that issue. I am asking again because you said "the object is set to Embedded", and there are two objects involved, and they both need to be set to Embedded.
I'm going to type a whole bunch of words here for literally anything I can think of. These are the things I would try based on your scenario. Keep in mind that between each time you test, you need to close Blue Prism completed and re-open. The runtime resource process must close as part of this. If you're using Blue Prism the default way, then this should automatically close and reopen as you close and reopen Blue Prism. I'll be talking to myself a lot below and will not be making any attempt to give you advice on what to do. These are just the steps I would go through if I had that same issue, which I did in the past and that was solved by the Embedded application manager mode setting.
Okay so thinking about your error message, "Browser extension was not detected", we can pretty much guarantee that it isn't a tab name issue because we'd get a different error message for that. Blue Prism error messages related to the Browser Extension has been greatly improved, including (I think) in 7.3.
Then I'd want to go check the object where we're launching the browser from. When it launches the browser, is it able to do browser mode spying. Open Application Modeller and make sure that it really is working to use browser mode. Spy something new and then click to highlight it and make sure both of those work.
If that works, then I would try again to attach to the browser from the second object while I have the first object open in edit mode. I would expect to get the same error message. Then I'd detach the first object by resetting the object and then clicking Detach. Then in the first object (same one as launches the browser), I'd try to attach to the browser. I would expect this to fail. If it succeeds, then that would be pretty weird because with the browser open and both objects detached, I would expect either object can attach successfully. If the first object succeeds in attaching, then I'd detach it. Then I'd try to attach in the second object. If it succeeds, then of course you can take the approach many others have done where you detach in one object and attach in the other. But genuinely the ONLY reason I know of that can cause this scenario is the application manager mode.
So, at this point, if attaching to the browser worked from both objects but only when they take turns, I would check the application manager mode of both objects again to make sure they are both set to Embedded.
At this point, assuming I did the right testing before all of this in the first place, then I would guess I'll have the same results and the application manager mode is not the problem. So, then I'd start to suspect it is a Blue Prism version issue. I'd go to support.blueprism.com and search for "7.3 known issues" and read over the issues listed and search by "extension" and "attach".
So, I just went ahead and looked there on the support site. Here is an item that I see:
"Inconsistent behavior observed when launching or attaching to the Microsoft Edge browser depending on machine specification and application configuration" -- I want to look into the details of this, but it looks like the link for this one is incorrect. I should tell someone about this but I'm too lazy right now. Also it says this was introduced in v6.9 and fixed in 7.4.2 and 7.5, so I would assume it is saying the issue is in all versions between. Note the wording "Inconsistent" which does not mean "fails 100% of the time" which I assume we're seeing in our situation here.
However, I would still suspect the Blue Prism version. Before I'd go to the effort of installing another version to test, I'd ask a coworker to test the same scenario that I'm seeing with the second object failing to attach. If they have the issue as well in exactly the same way, then I'd move on to trying another version of Blue Prism. I'm not suggesting an upgrade here. I am suggesting I'd install it locally on a machine at work such as by using the Learning Edition. It's on 7.5.1 so I imagine that you could at least see if 7.5.1 has the same issue or not. You could download 7.3.2 and install it locally and install a SQL server locally as well and connect directly to it.
Then I'd test the same objects in 7.3.2 with the updated browser extension if applicable. If it works, then you can assume a Blue Prism version issue. Frankly, you probably shouldn't stay on 7.3 anyway. I recall testing that version and it had several issues that made it not viable for us. Depending on the size of your environment, it may or may not be easy to upgrade. If it's easy, then I'd say upgrade and move on even if it doesn't fix the issue because it'll definitely solve other issues. Anyway, if it doesn't work in 7.3.2 either, then you've got some other kind of issue.
I imagine all these words aren't going to help you, but it is worth checking.
Dave Morris, 3Ci at Southern Company
