"Titleblock Integration" is one of the many features that ProjectWise has to offer. In short, it allows ProjectWise standard and custom attributes to be in sync with design file's titleblock information (represented by Microstation tag elements or AutoCAD's attributes). Users update ProjectWise attributes using ProjectWise Explorer interface will automatically be updated in the design file titleblock and vice versa.
Please note: Discussion mentioned in this blog is only applicable to MicroStation design files.
It is not uncommon to have a MicroStation drawing to reference multiple reference files; there are times when a drawing could be referencing 30 or 40 other drawings. If the drawings including reference files have titleblock information resided in the file, it could take a while for the drawing to be opened since ProjectWise will need to scan through each file including all reference files to update all titleblock information.
To improve the performance for opening the main drawing and updating titleblock information in the reference files are not required at the time, you may find enabling the following variable will help.
The following variable can be found in a file called mcm.cfg. This file is resided on user's machine ProjectWise installation directory (Drive:\program files\bentley\projectwise\bin)
PW_TITLEBLOCKS_SKIP_TAGS_IN_REFERENCES=1
After this variable is enabled, titleblock information in the main drawing will be updated and the titleblock resided in reference files will be skipped.
Other variables also resided in mcm.cfg file (such as PW_TITLEBLOCKS_ENABLE_PRESCANNING, PW_TITLEBLOCKS_NO_UPDATE_ON_REFRELOAD) could be enabled to aid speed up file open operations. JP
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...