Controlling Titleblock Integration in ProjectWise

RE: Controlling Titleblock Integration in ProjectWise

blogs — Tue, 28 Apr 2009 02:11:48 GMT

I believe these variables if set in the mcm.cfg file, it will be set in Microstation's configuration variable as "Appl" level. What you see in Projectwise Administrator module, there is Global, Application, Site, Project and user category. If a variable is set in Application level (in this example, variable is set in the mcm.cfg file) as well as site level, I believe Site level will have higher priority. I did some preliminary testing and confirms that is the case.

so to answer your question, yes if you set these values at site level, it should overwrite what is set in mcm.cfg. Please note, initiallly these variables especially PW_TITLEBLOCKS_SKIP_TAGS_IN_REFERENCES=1 is not enabled in mcm.cfg

also, once variable is defined in Appl level, you can also undefine it as well in site level...just thought you might want to know...

RE: Controlling Titleblock Integration in ProjectWise

Mark King — Mon, 23 Mar 2009 09:05:19 GMT

Can the variables

PW_TITLEBLOCKS_SKIP_TAGS_IN_REFERENCES=1

and

PW_TITLEBLOCKS_ENABLE_PRESCANNING,

PW_TITLEBLOCKS_NO_UPDATE_ON_REFRELOAD

be added to a configuration block in the "Workspace Profiles" under Managed workspaces, say at site level.

Will the original variable in the mcm.cfg file be overwritten with the new value.

I want to try and avoid having to edit every mcm.cfg file on every machine.

I was experimenting with the following projectwise variable

#---The below lines were added to disable ProjectWise Integration

#---when Microstation V8 is launched from the desktop

%if !defined (_PWEXPLORER)

PW_DISABLE_INTEGRATION = 1

%endif

I added these lines to our standards.cfg file on our local server to prevent projectwise integration with a desktop launch of bentley structural and it worked fine.

Will the same rules apply?