Datasource Properties Dialog - Settings Tab (Datasource Settings)

Contains controls for defining the overall behavior of the datasource. For some of the datasource settings, such as audit trail settings, once they are configured here they can be further configured by editing the related user settings for each individual user.

Global delete restrictions

This setting controls at the datasource level who can and cannot delete documents.

Setting	Description
Default	If on, all users are permitted to delete documents, if their users settings and document permissions are so configured. Specifically, once this setting is turned on, to be able to delete a document, the user's user setting Document > Can delete must be on, and selected document must have the Delete permission turned on for that user on the Security tab of the Document Properties dialog. Also, when this setting is on, users with the correct user settings and document permissions can delete folders containing documents, whether they are the owner of that folder (or the documents therein) or not.
Admin only	If on, only an administrative user (that is, a member of the Administrator group) can delete a document. Also, when this setting is on, only the administrative user can also delete folders containing documents.
Owner	Turning on Owner enables the two options, Folder owner and Document owner. When Owner is on but Folder owner and Document owner are both off, then no users, not even administrative users, are able to delete any documents. Folder owner — When Folder owner is on and Document owner is off (and your user setting Document > Can delete is on), then only the owner of a folder will be able to delete or move the documents within it. In this scenario, the owner of a folder will also be able to delete or move documents which have the Delete permission turned off for that user on the Security tab of the Document Properties dialog. Document owner — When Document owner is on and Folder owner is off (and your user setting Document > Can delete is on), then only the owner of a document will be able to delete or move the document. In this scenario, the owner of a document will also be able to delete or move it, even if it has the Delete permission turned off for that user on the Security tab of the Document Properties dialog.

Note: When Folder owner and Document owner are both on, then to be able to delete or move a document you must be either the owner of the selected document or the owner of the folder it resides in.

Note: Regardless of the settings above, any user is able to delete an empty folder, if they have the correct user settings and folder permissions configured.

Miscellaneous

Setting	Description
Grant implicit 'Change Permissions' rights to owners of work areas, folders, and documents	When on (the default), an owner of a work area, folder, or document always has the ability to change and assign access control for the item, regardless of what their current access control settings are for the item. When off, an owner of a work area, folder, or document does not have any extra control over the item, beyond what their current access control settings are for the item.
Move deleted document files to the Recycle Bin on storage	When this setting is on and a document is deleted from the datasource, the document's file is sent to the Recycle Bin on the storage area's computer. To use this setting, you must first create a Windows user, and then make sure that the ProjectWise Design Integration Server or ProjectWise Caching Server is running as that user. Recycle bins under Windows are user specific. You will need to grant that user the right to run/login as a service, and you may also want to change the maximum size of the recycle bin.
Enable 'Deleted Items' folder	When this setting is off (default), deleting a folder or document permanently deletes the item from the datasource. When this setting is on, deleting a folder or document moves the item to the Deleted Items folder where it is kept for a period of time before being automatically permanently deleted. The administrator, or any user whose user setting Can access Deleted Items folder is on, can restore items in the Deleted Items folder as needed.
Keep items in 'Deleted Items' folder for:	Sets how long an item will remain in the Deleted Items folder before it is automatically permanently deleted from the datasource. You can set the retention period to be days, months, or years. By default, each deleted item is kept for two months.
Force case-insensitive search	When this setting is on, and Oracle is your database, searches run from the Search by Form and Define Search dialogs will not be case-sensitive. Note: This setting is for use with Oracle databases only; it has no effect when SQL Server is your database (as user searches against a SQL Server database are already case-insensitive). Note: Quick searches run from the Search toolbar are never case-sensitive, regardless of this setting, and regardless of database.
Display Access Control tab in Preview Pane	This setting determines whether or not the Access Control tab can be displayed in ProjectWise Explorer for this datasource. If this datasource setting is on, then the Access Control tab is able to be displayed; actual display of the tab is then controlled at the user level, through the related user setting (User Properties dialog > Settings tab > Administrative > Show Access Control tab in preview pane). If this datasource setting is off, then the Access Control tab cannot be displayed in ProjectWise Explorer for this datasource, regardless of how any individual user's user settings are configured.

Work Areas

Setting	Description
Folder for template work areas	Sets the default folder that the Work Area Creation Wizard in ProjectWise Explorer looks for existing work areas, to be used as templates for creating new work areas. On the first page users encounter (after the Welcome page) in the Work Area Creation Wizard, the Template Work Area list displays all work areas that exist in this default folder. If no default folder is set here, the Template Work Area list displays `<none>`.

Setting

Description

Folder for template work areas

Sets the default folder that the Work Area Creation Wizard in ProjectWise Explorer looks for existing work areas, to be used as templates for creating new work areas. On the first page users encounter (after the Welcome page) in the Work Area Creation Wizard, the Template Work Area list displays all work areas that exist in this default folder. If no default folder is set here, the Template Work Area list displays <none>.

Network

Setting	Description
Enable Delta File Transfer	Turning this setting on enables delta file transfer for all ProjectWise Explorer clients connected to this datasource. Once you turn this setting on, you also need to turn on the user setting of the same name, for each user you want to benefit from delta file transfer. Note: Delta file transfer is the ProjectWise technology that improves performance when sending large files over networks with high latency / low bandwidth connections, by only sending the changes needed to update the file, rather than the entire file. For optimal performance, use delta file transfer along with existing ProjectWise local file caching functionality. Delta file transfer is enabled by default on every ProjectWise Design Integration Server, ProjectWise Caching Server, and ProjectWise Gateway Service. If you want to disable it for a particular server, there is a delta file transfer setting in the respective server module's dmskrnl.cfg file.
Compress client/server request data	Turning on this setting enables data compression for all ProjectWise Explorer and ProjectWise Administrator clients connected to this datasource. Once you turn this setting on, you also need to turn on the user setting of the same name, for each user you want to benefit from this data compression. Note: Data compression is the ProjectWise technology that improves performance over networks with high latency / low bandwidth connections by compressing the data that is being sent to or retrieved from the ProjectWise database. The data is then decompressed when it reaches its destination. Performance improvements will be most noticeable with large amounts of data (for example, thousands of documents in a folder) across high latency / low bandwidth connections.

Setting

Description

Enable Delta File Transfer

Turning this setting on enables delta file transfer for all ProjectWise Explorer clients connected to this datasource. Once you turn this setting on, you also need to turn on the user setting of the same name, for each user you want to benefit from delta file transfer.

Note: Delta file transfer is the ProjectWise technology that improves performance when sending large files over networks with high latency / low bandwidth connections, by only sending the changes needed to update the file, rather than the entire file. For optimal performance, use delta file transfer along with existing ProjectWise local file caching functionality. Delta file transfer is enabled by default on every ProjectWise Design Integration Server, ProjectWise Caching Server, and ProjectWise Gateway Service. If you want to disable it for a particular server, there is a delta file transfer setting in the respective server module's dmskrnl.cfg file.

Compress client/server request data

Turning on this setting enables data compression for all ProjectWise Explorer and ProjectWise Administrator clients connected to this datasource. Once you turn this setting on, you also need to turn on the user setting of the same name, for each user you want to benefit from this data compression.

Note: Data compression is the ProjectWise technology that improves performance over networks with high latency / low bandwidth connections by compressing the data that is being sent to or retrieved from the ProjectWise database. The data is then decompressed when it reaches its destination. Performance improvements will be most noticeable with large amounts of data (for example, thousands of documents in a folder) across high latency / low bandwidth connections.

Documents

Setting	Description
Creation in workflow	Provides options for the creation of documents in folders with a workflow assigned, when the user creating the documents may or may not have create privileges for that workflow or the workflow state. When Creation in workflow is off, and a user attempts to create a document in a folder that has a workflow assigned to it, ProjectWise attempts to place the new document in the folder state (that is, the lowest state in the workflow to which any documents in the folder are currently assigned). If the user does not have the Create permission for that particular state, then the document will not be created at all and the user will receive an error message. When Creation in workflow and Put created document into first workflow state having create permission are on, and a user attempts to create a document in a folder that has a workflow assigned to it, ProjectWise places the new document in the first state in the workflow that the user has the Create permission. For example, if a workflow having four states is assigned to a folder, and the third state of the workflow happens to be the first state in which a particular user has the Create permission, then whenever that user attempts to create a document in that folder, that document will automatically be placed in third state of the workflow. When Creation in workflow and Folder state does not prevent document creation are on, and a user attempts to create a document in a folder that has a workflow assigned to it, ProjectWise first tries to place the new document in the folder state. If the user does not have Create permission for that state, ProjectWise then attempts to place the document in the first state of the workflow that is assigned to the folder. If the user does not have Create permission for that state, then the document will not be created at all and the user will receive an error message.
Allow several users to fetch documents to the same location	The intent of this setting is to let multiple users, who may be sharing a workstation, use what appears to ProjectWise to be the same working directory, when in fact each user is using their own distinct working directory that happens to be mapped to the same drive. CAUTION: This setting should never be used to allow multiple users to share the same physical working directory, as it can cause severe problems with check outs and exports. Consider the following example as a valid workflow and use of this setting: Bob and Mary both use the same computer, `SHAREDWORKSTATION`, to work in ProjectWise Explorer on different shifts. Bob and Mary both have accounts in the same datasource, `exton-tbb-0216`. The administrator configures a Windows logon script for both Bob and Mary so that whenever either one logs on to the network, the same drive letter on their computer is automatically mapped to a specific location on the network. For example, the administrator configures it so that whenever Bob or Mary user logs in, the `T:\` drive on their computer automatically gets mapped to `\\NETWORKSERVER\pwworkdirs\%USERNAME%\`. In ProjectWise Administrator, the administrator configures both Bob's and Mary's user settings so that their ProjectWise Explorer working directory is set to the same path, such as: `T:\exton-tbb-0216-workdir\` In ProjectWise Administrator, the administrator also turns on this datasource setting, Allow several users to fetch documents to the same location. Bob happens to be working the first shift. From ProjectWise Explorer, Bob checks out the document, example.dgn. ProjectWise notes the check out location as `\\SHAREDWORKSTATION\T$\exton-tbb-0216-workdir\dms00050\`, when in actuality a copy of the checked out document is downloaded to `\\NETWORKSERVER\pwwdirs\Bob\exton-tbb-0216-workdir\dms00050\`. Bob leaves work for the day, and leaves example.dgn checked out. Now Mary starts her shift. From ProjectWise Explorer, Mary attempts to copy out example.dgn. ProjectWise notes the copy out location as `\\SHAREDWORKSTATION\T$\exton-tbb-0216-workdir\dms00050\`, when in actuality a copy of the document is downloaded to `\\NETWORKSERVER\pwwdirs\Mary\exton-tbb-0216-workdir\dms00050\`. Mary's copy out is successful, because Allow several users to fetch documents to the same location was turned ON. If Allow several users to fetch documents to the same location had been turned OFF, then Mary would have received an error when she attempted to copy out example.dgn, because ProjectWise thinks that a copy of the file already exists in the working directory.
Update Access Control Cache on Document Delete	All of the access control security settings for a datasource are stored in the database. For optimal performance, ProjectWise Design Integration Server maintains a cache of this information. When this datasource setting is on, then any change that affects access control will trigger the access control cache to be updated. When this setting is off (default), the access control cache will not be updated when a document, having security settings, is deleted. Information about the deleted document will be updated the next time some other action occurs that normally triggers the access control cache to be updated.
Force file name to be the same as document name	This setting goes along with the document name locking feature available to users in ProjectWise Explorer. When this setting is on, then the document name locking feature is not optional, and the document name and file name properties are always locked together. Existing documents are not affected until a user renames a document, renames the attached file, or replaces the attached file. When this setting is off (the default), then document name locking is optional for each user.

Versions

Setting	Description
Generate version string for first document version	New and imported documents will be assigned a version string (default uses an alpha character - A, B, C, and so on).
Use numeric version strings	Select to use a numeric string rather than the default of an alpha character. If this option is checked, you may specify the numeric string to be used. Double-click the # icon to set the version string prefix.
Put created version into first workflow state having create permission	When this setting is on, and Use current state if create permission is granted is off, and a user creates a new version of a document, ProjectWise places the new version in the first state in the workflow that the user has the Create permission. The original, now read-only document, remains in the workflow state it was in before it was versioned. For example, a workflow having four states is assigned to a folder. A particular user does not have the Create permission for the first state of the workflow, but does have the Create permission for the second state. If that user attempts to create a version of a document that is currently in the first state of the workflow, then the new version that gets created will be placed in second state of the workflow.
Use current state if create permission is granted	This setting becomes available when you turn on Put created version into first workflow state having create permission. When this setting is on and a user creates a new version of a document, ProjectWise places the new version in the same state that the original document is in, assuming that the user also has the Create permission for that state. For example, a workflow having four states is assigned to a folder. A particular user has the Create permission for both the first and second states of the workflow. If that user attempts to create a version of a document that is currently in the second state of the workflow, then the new version that gets created will also be placed in second state of the workflow.
Document having versions can be moved	When this setting is on, users can move documents that have versions. Specifically, when you move a document with versions, the versions will always move with the document — it is not possible to move a document and not move its versions. When this setting is off, users cannot move documents that have versions.
Lock flat set documents to versions	Next to each document in the set contents window for flat sets in ProjectWise Explorer, there is a check box called Lock to Version. When off, the active version of the document will always be included in the set. When on, the set locks to the sequence number of the document's active version. This way, as new versions of the document are created and the active version's sequence number slides forward, the set will always use a fixed version of the document (specifically, the version which now has the sequence number that the active version had when the document was originally added to the set). The Lock flat set documents to versions datasource setting, then, controls whether or not the Lock to Version check box is on by default when a document is added to a flat set in the set contents window in ProjectWise Explorer. When this datasource setting is off (the default), the check box in ProjectWise Explorer is also off by default. When this datasource setting is on, the check box in ProjectWise Explorer is on by default. Tip: This setting was called "Use active version in flat sets" in previous versions, and was renamed to be consistent with the Lock reference documents to versions setting below.
Lock reference documents to versions	When off (the default), the master document will always use the active version of a reference. (Off is the previous behavior, before the datasource setting was introduced.) When on, and the user attaches a reference to a master, the reference is locked to the sequence number of the reference's active version. This way, as new versions of the reference are created and the active version's sequence number slides forward, the master document will always use a fixed version of the reference (specifically, the version which now has the sequence number that the active version had when the reference was originally attached).
Prompt user to update master document's reference versions on open	If on, and the user opens a master document that is using a version of a reference that is not the active version, the Reference Version Manager dialog opens in ProjectWise Explorer to prompt them to update the master document to use the active version of that reference document. Only the reference documents that are not the active version are displayed in the dialog. The user can choose to update some, all, or none of the reference documents, and then open the master document.

Most Recently Used Lists

At the bottom of most applications' File menu is a list of files that were recently opened in that application. This is referred to as the most recently used (MRU) list. When MicroStation is integrated with ProjectWise, the File menu MRU list is also integrated with ProjectWise, so that you can quickly access a DGN document recently opened from ProjectWise. Integration with the File menu MRU list in other integrated applications is not yet supported.

The Address bar in the Open Document dialog that opens in integrated applications also contains an MRU list. The Address bar's MRU list displays all documents recently opened from ProjectWise, not just those opened in the application you are working in.

Setting	Description
Maximum number of recent items to show	This setting determines how many recently opened documents will be listed in the integrated application's MRU list. So for all integrated application, this affects the Address bar of the Open Document dialog, and for MicroStation it also affects the File menu MRU list. The default maximum number is set to 5. (For applications other than MicroStation, the File menu MRU list uses the application's own default maximum number.)
Time period to keep records	This setting determines how long a listing will be kept on the MRU list. The default is 20 days.

Setting

Description

Maximum number of recent items to show

This setting determines how many recently opened documents will be listed in the integrated application's MRU list. So for all integrated application, this affects the Address bar of the Open Document dialog, and for MicroStation it also affects the File menu MRU list. The default maximum number is set to 5. (For applications other than MicroStation, the File menu MRU list uses the application's own default maximum number.)

Time period to keep records

This setting determines how long a listing will be kept on the MRU list. The default is 20 days.

Engineering Components

Setting	Description
Display Components in ProjectWise Clients	To be used your datasource is using ProjectWise components indexing. If on, a Components node displays when a user logs in to this datasource from ProjectWise Explorer or ProjectWise Web Parts.
Folder for saved component searches	Sets the folder that relational searches will be saved to when searches are run and saved from ProjectWise Explorer.
Folder for component images	Sets the ProjectWise folder that contains the icons and gifs used for component classes.

Web Components

Setting	Description
Default ProjectWise Publishing Server	Update: This setting is only needed if you are still using the old ProjectWise Web Server, it does not apply (and is not needed or used at all) if you are using the newer ProjectWise Web and ProjectWise Web View cloud services. This setting is for use when ProjectWise Publishing Server is being used with ProjectWise Web Server. To modify this setting, expand Default ProjectWise Publishing Server and double-click the icon below it. The Specify server address dialog that opens is used to enter the name of the computer on which ProjectWise Publishing Server is installed. For example, `http://publishingserver`. To configure integrated ProjectWise Publishing Server to run in secure mode, in the Specify server address dialog, turn on Server uses secure protocol, then enter the name of your ProjectWise Publishing Server computer exactly as it appears in your certificate. To find this name, open Internet Information Services Manager, go to Web Sites > Default Web Site > Properties > Directory Security tab > View Certificate > Issued to. (Turning on the Server uses secure protocol setting automatically changes `http` to `https`.) ProjectWise Publishing Server always runs on IIS's Default Web Site, whose default port is 80. If the Default Web Site port has been changed from the default port 80, then when specifying the location of your ProjectWise Publishing Server, you will also need to specify the port after the server name, For example, `https://publishingserver:8081`.
Design Compare Utility Address	Update: This setting is only needed if you are still using the old ProjectWise Web Server, it does not apply (and is not needed or used at all) if you are using the newer ProjectWise Web and ProjectWise Web View cloud services. This setting is for use when ProjectWise InterPlot Server's Design Compare utility is being used with ProjectWise Web Server. To modify this setting, expand Design Compare Utility Address and double-click the icon below it. The Specify server address dialog that opens is used to enter the name of the computer on which the Design Compare utility is installed, followed by a forward slash, followed by the name of the Virtual Directory Alias that was specified during installation of the Design Compare utility. For example, `http://interplotserver/PWDI`. To configure the Design Compare utility to run in secure mode, in the Specify server address dialog, you must turn on Server uses secure protocol, then enter the name of the computer on which the Design Compare utility is installed exactly as it appears in your certificate, followed by a forward slash, followed by the name of the Virtual Directory Alias. For example, `https://interplotserver/PWDI`. To find the computer name as it appears in the certificate, open Internet Information Services, go to Web Sites > Default Web Site > Properties > Directory Security tab > View Certificate > Issued to. (Turning on the Server uses secure protocol setting automatically changes `http` to `https`.) If the Default Web Site port has been changed from the default port 80, or if you install the Design Compare utility to a site other than the Default Web Site, then when specifying the Design Compare utility address, you will also need to specify the port after the server name, and before the Virtual Directory Alias. For example, `https://interplotserver:88/PWDI`
WSG Work Areas URL for Connect services	The administrator of a ProjectWise project can enter the ProjectWise Web portal of that project and create a connection to a specific work area, in order to expose that work area and its contents inside the ProjectWise Web portal. Another way to create a work area connection in ProjectWise Web is to configure the WSG Work Areas URL for Connect services datasource setting so that associating a work area to a ProjectWise project (which is done in ProjectWise Explorer) automatically creates the work area connection in the ProjectWise Web portal of the associated ProjectWise project. To configure the WSG Work Areas URL for Connect services datasource setting, you specify the URL of the Bentley Web Services Gateway, including the path to the ProjectWise Design Integration Server and datasource that contains the work area(s). These are the basic steps: Install and deploy Bentley Web Services Gateway and the ProjectWise Plug-in as described in the ProjectWise Implementation Guide. In ProjectWise Administrator, configure the datasource setting, WSG Work Areas URL for Connect services (details below). In ProjectWise Explorer, associate a work area to a ProjectWise project. Now go to the ProjectWise Web portal within the associated ProjectWise project and you will see the new work area connection. Configuring the WSG URL: The important part of this configuration is getting the syntax of the URL right. The server does not verify whether or not you have entered it correctly, so make sure you enter it correctly! To find the first part of the URL, open the WSG Explorer on the server where Bentley Web Services Gateway is installed. To open the WSG Explorer, in a web browser enter: `https://WSGservername/ws/Pages/WsgExplorer.aspx` (for example, `https://maestrovm.bentley.com/ws/Pages/WsgExplorer.aspx`) In the WSG Explorer window that opens, on the Navigation tree tab, expand Repositories, then select the datasource you are configuring. In the WSG Explorer address bar, select the full URL that includes the datasource, as shown here, then right-click and select Copy. Then in ProjectWise Administrator, paste this URL into the new datasource setting, WSG Work Areas URL for Connect services. At the end of the pasted URL, append this text: `/PW_WSG/Project`, so that the full URL is now something like this: `https://WSGservername/ws/v2.8/Repositories/Bentley.PW--PWservername~3Apwtest/PW_WSG/Project` Make sure you use the fully qualified domain name when entering the Bentley Web Services Gateway and ProjectWise server names. This example shows the full URL, when the Bentley Web Services Gateway and ProjectWise servers are installed on the same computer: `https://maestrovm.bentley.com/ws/v2.8/Repositories/Bentley.PW--maestrovm.bentley.com~3Apwtest/PW_WSG/Project`

Setting

Description

Default ProjectWise Publishing Server

Update: This setting is only needed if you are still using the old ProjectWise Web Server, it does not apply (and is not needed or used at all) if you are using the newer ProjectWise Web and ProjectWise Web View cloud services.

This setting is for use when ProjectWise Publishing Server is being used with ProjectWise Web Server. To modify this setting, expand Default ProjectWise Publishing Server and double-click the icon below it. The Specify server address dialog that opens is used to enter the name of the computer on which ProjectWise Publishing Server is installed. For example, http://publishingserver. To configure integrated ProjectWise Publishing Server to run in secure mode, in the Specify server address dialog, turn on Server uses secure protocol, then enter the name of your ProjectWise Publishing Server computer exactly as it appears in your certificate. To find this name, open Internet Information Services Manager, go to Web Sites > Default Web Site > Properties > Directory Security tab > View Certificate > Issued to. (Turning on the Server uses secure protocol setting automatically changes http to https.) ProjectWise Publishing Server always runs on IIS's Default Web Site, whose default port is 80. If the Default Web Site port has been changed from the default port 80, then when specifying the location of your ProjectWise Publishing Server, you will also need to specify the port after the server name, For example, https://publishingserver:8081.

Design Compare Utility Address

Update: This setting is only needed if you are still using the old ProjectWise Web Server, it does not apply (and is not needed or used at all) if you are using the newer ProjectWise Web and ProjectWise Web View cloud services.

This setting is for use when ProjectWise InterPlot Server's Design Compare utility is being used with ProjectWise Web Server. To modify this setting, expand Design Compare Utility Address and double-click the icon below it. The Specify server address dialog that opens is used to enter the name of the computer on which the Design Compare utility is installed, followed by a forward slash, followed by the name of the Virtual Directory Alias that was specified during installation of the Design Compare utility. For example, http://interplotserver/PWDI. To configure the Design Compare utility to run in secure mode, in the Specify server address dialog, you must turn on Server uses secure protocol, then enter the name of the computer on which the Design Compare utility is installed exactly as it appears in your certificate, followed by a forward slash, followed by the name of the Virtual Directory Alias. For example, https://interplotserver/PWDI. To find the computer name as it appears in the certificate, open Internet Information Services, go to Web Sites > Default Web Site > Properties > Directory Security tab > View Certificate > Issued to. (Turning on the Server uses secure protocol setting automatically changes http to https.) If the Default Web Site port has been changed from the default port 80, or if you install the Design Compare utility to a site other than the Default Web Site, then when specifying the Design Compare utility address, you will also need to specify the port after the server name, and before the Virtual Directory Alias. For example, https://interplotserver:88/PWDI

WSG Work Areas URL for Connect services

The administrator of a ProjectWise project can enter the ProjectWise Web portal of that project and create a connection to a specific work area, in order to expose that work area and its contents inside the ProjectWise Web portal.

Another way to create a work area connection in ProjectWise Web is to configure the WSG Work Areas URL for Connect services datasource setting so that associating a work area to a ProjectWise project (which is done in ProjectWise Explorer) automatically creates the work area connection in the ProjectWise Web portal of the associated ProjectWise project.

To configure the WSG Work Areas URL for Connect services datasource setting, you specify the URL of the Bentley Web Services Gateway, including the path to the ProjectWise Design Integration Server and datasource that contains the work area(s).

These are the basic steps:

Install and deploy Bentley Web Services Gateway and the ProjectWise Plug-in as described in the ProjectWise Implementation Guide.
In ProjectWise Administrator, configure the datasource setting, WSG Work Areas URL for Connect services (details below).
In ProjectWise Explorer, associate a work area to a ProjectWise project.
Now go to the ProjectWise Web portal within the associated ProjectWise project and you will see the new work area connection.

Configuring the WSG URL:

The important part of this configuration is getting the syntax of the URL right. The server does not verify whether or not you have entered it correctly, so make sure you enter it correctly!

To find the first part of the URL, open the WSG Explorer on the server where Bentley Web Services Gateway is installed.

To open the WSG Explorer, in a web browser enter: https://WSGservername/ws/Pages/WsgExplorer.aspx (for example, https://maestrovm.bentley.com/ws/Pages/WsgExplorer.aspx)

In the WSG Explorer window that opens, on the Navigation tree tab, expand Repositories, then select the datasource you are configuring. In the WSG Explorer address bar, select the full URL that includes the datasource, as shown here, then right-click and select Copy.

Then in ProjectWise Administrator, paste this URL into the new datasource setting, WSG Work Areas URL for Connect services. At the end of the pasted URL, append this text: /PW_WSG/Project, so that the full URL is now something like this:

https://WSGservername/ws/v2.8/Repositories/Bentley.PW--PWservername~3Apwtest/PW_WSG/Project

Make sure you use the fully qualified domain name when entering the Bentley Web Services Gateway and ProjectWise server names.

This example shows the full URL, when the Bentley Web Services Gateway and ProjectWise servers are installed on the same computer:

https://maestrovm.bentley.com/ws/v2.8/Repositories/Bentley.PW--maestrovm.bentley.com~3Apwtest/PW_WSG/Project

Event System

By default, when a folder or document with spatial data is copied, the spatial data is not copied along with the folder or document. These settings let the administrator enable the copying of spatial data along with the copied folder or document.

Setting	Description
Enable folder copy server event notifications	If on, then when a folder with spatial data is copied, the spatial data is copied along with the folder.
Enable document copy server event notifications	If on, then when a document with spatial data is copied, the spatial data is copied along with the document.

Federated Identity

Settings related to associating ProjectWise user accounts with Bentley IMS accounts (also called Bentley Cloud Services profiles) when using Bentley IMS authentication in ProjectWise. These settings assume that Bentley IMS authentication is enabled in the datasource (see Enabling Bentley IMS Authentication and Bentley IMS Single Sign-On in the Datasource).

Setting	Description
Associate identity with user account by e-mail address	If on, a person's ProjectWise user account will be automatically associated to their Bentley IMS account the first time they log in to this datasource using Bentley IMS authentication, if the email address that is saved in their ProjectWise user account properties matches the identity (the primary email address) of their Bentley IMS account. Note: Use of this setting assumes and requires that a user identity filter is configured on the Users datasource node (Users node > Users Properties dialog > Dynamic Creation tab) that specifies which organization a user must belong to, in order for their account to be associated (see Adding Users with Bentley IMS Accounts to the Datasource).
Prompt user to associate identity	If on, and there is no user account in the datasource that is currently associated to the Bentley IMS account of the person logging in to this datasource using Bentley IMS authentication, then that person is prompted to either: select an existing ProjectWise user account to associate with their Bentley IMS account or allow a new ProjectWise user account to be created and associated to their Bentley IMS account Note: Use of this setting assumes and requires that a user identity filter is configured on the Users datasource node (Users node > Users Properties dialog > Dynamic Creation tab) that specifies which organization a user must belong to, in order for their account to be associated (see Adding Users with Bentley IMS Accounts to the Datasource).
Allow user group membership updates by identity claims	Turn this setting on if you want to allow ProjectWise groups to be synchronized with matching Bentley IMS groups. For synchronization to work, the following must be true: this setting must be on both the ProjectWise group and the Bentley IMS group must have the same name the ProjectWise group setting called Update user membership from federated identity claims (on the Group Properties dialog) must be turned on See Synchronizing a ProjectWise Group with a Bentley IMS Group.
Apply identity filter when synchronizing Bentley IMS users	DO NOT TURN ON; INTENDED FOR FUTURE USE Synchronization of a datasource with Bentley IMS is optional. If you choose to synchronize, you must first contact Bentley in order to obtain a special Bentley email account called a service identity, and then add the service identity information to your server's DMSKRNL.CFG file. Upon synchronization, ProjectWise uses the service identity to search Bentley IMS for just the IMS accounts that belong to your organization, and then creates matching user accounts for them in ProjectWise. A service identity can only be associated to one organization, and Bentley will associate each service identity to the organization requesting it, therefore your own service identity will only ever have access to the Bentley IMS accounts that are associated to your own organization. At some point in the future, it might be possible to configure synchronization so that it only creates matching ProjectWise accounts for those users in your organization who belong to a particular group in Bentley IMS. In this situation, you would turn on this datasource setting, and then also configure a user identity filter that specifies which IMS group a user in your organization must belong to, in order for a matching ProjectWise account to be created upon synchronization. However, since ProjectWise synchronization with Bentley IMS does not currently support filtering by IMS groups, for now you should always leave this datasource setting turned OFF (it is off by default).