New in ProjectWise CONNECT Edition Update 3.1
Updated Application Support
Updated ODBC Driver Support
ProjectWise Design Integration Server now supports:
Network Configuration Changes
- The ProjectWise Network Configuration Settings dialog can now be opened in one of two modes: user mode, or administrator mode.
- A new tab - Insecure Login - has been added, where you can allow users to connect to any insecure server, or configure an exception list of servers that the user can connect to in insecure mode.
User and Administrator modes
Administrators can now also open the dialog in administrator mode (with elevated privileges) by opening the dialog normally (in user mode) and then clicking the Run as administrator button at the bottom of the dialog, or by right-clicking the underlying pwcfg811.cpl file and selecting Run as administrator. In administrator mode you can configure global auto-login settings, and you can configure whether or not users can change their own network settings.
The mode you open the dialog in also determines where the network settings (information added on the DNS Services and Datasource Listing tabs) get stored in the Windows Registry. When you open the dialog in administrator mode, the network settings you configure get stored under HKEY_LOCAL_MACHINE (this is where all network settings were stored in CONNECT Edition Update 3 and earlier; network settings configured in previous releases will also remain in this location). When you open the dialog in user mode, the network settings get stored under HKEY_CURRENT_USER (this is new).
Insecure Login tab
This tab lets you set whether or not the user can connect to servers that are not configured to use secure connections. When the Allow insecure connection to any server setting on this tab is on (default), then the user will be able to log in to any server they have access to that shows up in their datasource list (this is the same behavior as before the setting was added). When this setting is off, the user will get a warning if they attempt to log in to a server that is not configured to use a secure connection. The user can then decide whether or not they want to proceed with the log in. If they click Yes to proceed with the log in, the server gets added to the exception list (the Insecure Log in tab) and they are connected to the server.
You can also manually add insecure servers to this tab the same way you add servers to the Datasource Listing tab (specify name and hostname and click Add). If you manually add a server, make sure that same server (or a ProjectWise Gateway Service that is configured to point to that server) is also added on the Datasource Listing tab.
; ; Uncomment this value to control security degradation when running as gateway. ; The value of 0 allows for secure messages received from client to be routed ; over insecure connection. For allowing insecure routing *only* for insecure ; client communication use 1. The value of 2 will always require secure routing ; connection. The default behavior is to always allow insecure routing (0). ; ;SecureRouting=1
ProjectWise Now Uses UTC (Coordinated Universal Time) for Timestamps
In previous releases, ProjectWise used the local time on the database server to determine the date and time (timestamp) that an action occurred. Starting with this release, ProjectWise now uses UTC (coordinated universal time) to determine the timestamp.
For administrators: Upgrading a datasource to the current version requires that you run the DMSCONV.EXE utility in order to update the Datetime database column so that it now uses UTC. If you are running the DMSCONV.EXE utility on a different computer than the database server, make sure the current time zone setting on your computer matches the current time zone setting on the database server (you can change it back after running the conversion).
Whenever a ProjectWise client encounters an item with a timestamp, one of the following things will happen, depending on the version of the client or server:
- For new clients (CONNECT Edition Update 3.1 or later) connecting to a new server (CONNECT Edition Update 3.1 or later), the client will automatically convert the timestamp from UTC and display it in the client's local time.
- For new clients (CONNECT Edition Update 3.1 or later) connecting to an older server (pre-CONNECT Edition Update 3.1), the client will not do any conversion, and the timestamp will display the database server local time.
- For older clients (pre-CONNECT Edition Update 3.1) connecting to a new server (CONNECT Edition Update 3.1 or later), the client will not do any conversion, and the timestamp will display the universal time (UTC).
iCS for PDF Job History
Job history is now stored in the database instead of the working directory. With this change, the Job History window will now only show job history that is stored in the database. Unless you have manually deleted them, job history from older jobs (created in CONNECT Edition Update 3 or earlier) can still be found in .HST files in the working directory.
Changes to the Delivery Set
- ProjectWise Server Setups:
These items are no longer delivered:
If you are currently using a standalone ProjectWise Indexing Service from a previous CONNECT Edition release, you can continue to use it with this release. Otherwise, if you want to perform text extractions and host the full text index catalog on a computer other than the main ProjectWise Design Integration Server, install a copy of ProjectWise Design Integration Server on another computer and set up a head / tail server configuration. See the ProjectWise Implementation Guide for details.
For ProjectWise Sync Service, you can download it separately from the Software Fulfillment Center if needed.
- ProjectWise Admin Setups and
ProjectWise Client Setups:
The ProjectWise Analytics Data Upload Service installer has been moved from ProjectWise Client Setups (ProjectWise Explorer installer) to ProjectWise Admin Setups.