topic Re: The Blue Prism Tool Box rows suddenly move around in Product Forum

The Blue Prism Tool Box rows suddenly move around

andber — Mon, 31 Oct 2022 13:31:25 GMT

I am having an issue today where the tool box rows are not where they are supposed to be, and it's messing with my workflow and efficiency.
As we can see here, they are all over the place.

I have tried the following:

Under View -> Tool Boxes I have unlocked them, placed them where they should be, locked them and restarted the process. Position has moved to some random looking position.
Under View -> Tool Boxes I have tested step 1 both with "Remember tool positions" on and off.
I have tried saving The process after performing step 1 and 2.
I have tried step 1 through 3 and then closed down Blue Prism, making sure instances are closed.

After restarting application, I still see the tool box rows in the incorrect placement.
Does anyone have any clue why this is happening?
It happened to me once before, over a year ago, but I don't remember what fixed it then.

Re: The Blue Prism Tool Box rows suddenly move around

ewilson — Mon, 31 Oct 2022 21:46:24 GMT

Hi @Leon André Bergman,

What version of Blue Prism and what O/S are you using?

Cheers,
Eric

Re: The Blue Prism Tool Box rows suddenly move around

andber — Tue, 01 Nov 2022 08:19:37 GMT

We are using Blue Prism version 6.10.4 and on my pc the OS version is Win 10 Enterprise 22H2 build 19045.2130 with Windows Feature experience pack 120.2212.4180.0
I see the same issue on our virtual resource pc's running windows 10 Enterprise 1709, Build 16299.64

Re: The Blue Prism Tool Box rows suddenly move around

ewilson — Tue, 01 Nov 2022 16:02:48 GMT

Hi @Leon André Bergman,

I've checked through our ticketing system. There was a bug back in pre-6.7 releases related to use of the Remember tool positions, but it was addressed in v6.7. I've also looked through the registry and various config files, but I don't see anything that looks like it's related to the configuration/positioning of the toolbars.

I'd suggest opening a ticket with support, so they can troubleshoot further to determine what's going on.

Cheers,
Eric