As suggested above, a thorough review of client integration and
overall operation is recommended before you bring an upgraded ProjectWise system into production.
Review both datasource settings and user settings, as new options
may have been added or renamed in both of these areas. It is also suggested to
review any new
DMSKRNL.CFG
options as well as the current logging system configuration. These settings are
described in the ProjectWise Administrator help.
In ProjectWise V8i (SELECTseries
1), the
"Redline" action was renamed to
"Markup". For applications such as MicroStation, the Markup action is set by default to use Bentley Navigator, which points to the application class
name
Bentley.Navigator.Application in the Windows
Registry. After upgrading to the current
version from a pre-V8i (SELECTseries 1) version, you may notice that some
of your applications now have two
"Markup" actions. One is the new Markup action, and
the other is the old Redline action which got renamed to Markup during the
upgrade. If you see two Markup actions after an upgrade, simply delete the
second Markup action (the old Redline action which got renamed to Markup) in ProjectWise Administrator.
You must run a scan for references and link sets (in ProjectWise Explorer) after converting a pre-v8.1 datasource
to the current version.. This is to
allow for the population of additional data into the ProjectWise database about reference file relationships for
both MicroStation
and AutoCAD, and ensures the correct operation of reference data.
Some upgrades, depending on the version you are upgrading from,
require that you check in all checked out documents before upgrading, to ensure
the integrity of master/reference document relationships. If you did this, then
your master/reference document relationships should be in tact after upgrading.
However, if you did not do this, and you find that some of your
master/reference document relationships are broken, then running a scan for
references and link sets (in ProjectWise Explorer) after upgrading will fix the broken
relationships. Note that before you run the scan, you must check in all checked
out documents.
Starting with CONNECT Edition Update 3.1, ProjectWise now uses UTC
(Coordinated Universal Time) to determine the date and time (timestamp) that an
action occurs (prior to CONNECT Edition Update 3.1, ProjectWise used the local
time on the database server to determine the timestamp). Running the
DMSCONV.EXE utility on any pre-CONNECT Edition Update 3.1 database
automatically updates the
Datetime database column to use UTC (Coordinated
Universal Time). If you ran the DMSCONV.EXE utility on a different computer
than the database server and you were prompted to change your current time zone
setting to match the current time zone setting on the database server, remember
to change your current time zone setting back to the normal time zone setting
after conversion.
If your datasource is set up for file properties extractions, you
might need to re-process your documents after the upgrade, to ensure correct
times are assigned in your file properties. This is only needed if the
extractions were done in a time zone during daylight savings time and the
upgrade was done during standard time, or if the extractions were done during
standard time and the upgrade was done during daylight savings time.
