Change State Dialog Window - Separate From Main Window

[bmcwilliam]

In Vault 2020, the Copy Design dialog was upgraded to be separate from the main Vault client. This meant that while the Copy Design dialog was in use, the main client window could be independently used to search for data etc.

I would request that the same treatment be given to the Change State dialog box.

Almost every time I am using the Change State dialog box, I am opening up a second instance of Vault to search for information I need on the parts coming up in the dialog box.

If the main client window was accessible during this dialog box I would not need to open a second client for this purpose.

[RajSchmidt]

I think that there is a very good reason for this: Status change is a functionality of Vault proper. Copy Design is a separate application which is only invoked from within Vault. You could start it separately, check your Windows menu.

[ihayesjr]

@bmcwilliam 

What other information are you looking for when you need to go back to the full client?

[bmcwilliam]

Usually History or Where Used information.

When I am doing Change State on some of our medium to larger assemblies, some files not used anywhere within the assembly are brought in to the Change State dialog. I need to use a second client to look up information on all the files Vault is requesting I change the state for to see if they are actually used anywhere within that assembly or not.

Some of the time these erroneous files are parents, sometimes I think they are "brothers/sisters" - maybe sharing a parent somewhere with the files I am concerned with. Other times I think there is a copy design history relationship between them.