[CONNECT] Selectively disable ProjectWise Explorer client

Question

When ProjectWise (PW) Explorer client is installed it puts configuration file pw.cfg in MicroStation's config/appl folder. That configuration file instructs MicroStation to pop the PW login dialog when it starts. 
 
 But how do I prevent MicroStation from showing that PW dialog? I have only one project (workset) where I want to use PW. Most of my work does not require PW. 
 MicroStation CONNECT Update 14.2.

David Trejo-Rodriguez · Accepted Answer

the pw.cfg needs to be loaded at the appl level so its best to leave it there. no real elegant solution but what i would do is set the PW_DISABLE_INTEGRATION_FROM_DESKTOP variable. so when opening my local files i dont get the prompt. 
 When you need to work on the project that requires PW open the files from PW Exploer and in projectwise setup a profile so the correct workspace/workset is used.

Marc Thomas · Answer

Hi Jon, 
 To successfully use the PW_DISABLE_INTEGRATION_FROM_DESKTOP variable a complete block of configuration has to be used. 
 If you read through...\appl\pw.cfg you will find that PW_DISABLE_INTEGRATION_FROM_DESKTOP is defined only in that file and works only in the context of the code block that follows it, and is undefined once the logic is complete. 
 I realised this having finally got bored of uncommenting the PW_DISABLE_INTEGRATION_FROM_DESKTOP line in pw.cfg every time I installed a new version.... 
 So I now put the whole code section into WorkSpaceSetup.cfg in my Custom Configuration: 
 
 The pw.cfg syntax was originally designed to make it easy for a user to effect a change using the comment status of line 14: 
 # Uncomment to disable ProjectWise integration when this product is launched from the desktop. # PW_DISABLE_INTEGRATION_FROM_DESKTOP=1 
 However, that was a quick and dirty approach; unpicking this block reveals the obvious fact that the active variable is PW_DISABLE_INTEGRATION. 
 Thus the central IF statement: 
 %if !defined (_PWEXPLORER) PW_DISABLE_INTEGRATION = 1 %endif 
 works on it's own, and a s far as I can see the statement PW_DISABLE_INTEGRATION = 1 will also work alone. 
 I'd add a proviso here that this is something to treat with great caution in environments where ProjectWise integration is central to operations. 
 While I'm not confident it will consistently operate at the granularity of a WorkSet, the variable was almost certainly designed as an all or nothing switch; you may find that having turned integration off at the organisation level, adding %undef PW_DISABLE_INTEGRATION to the WorkSet.cfg of the WorkSet where you do want ProjectWise to kick in will enable integration, provided that you start a new session in that WorkSet. You could use the -WK and -WW command line switches in a custom shortcut to start in the desired WorkSet

[CONNECT] Selectively disable ProjectWise Explorer client

Top Replies