I have been playing with MicroStation CONNECT and studying ProjectWise CONNECT.
While Bentley has changed names and operability of its MicroStation configuration levels (organization, workspaces, worksets, roles), it appears that Bentley has not made any changes to the managed workspace levels (site, project, discipline, etc.) in ProjectWise .
Is Bentley formally defining any parallels between MicroStation CONNECT configuration levels and the ProjectWise CONNECT managed workspace levels? Will the managed workspace levels change names or operability in ProjectWise CONNECT in future releases? Does the MicroStation CONNECT WorkSpaceSetup.cfg file have any impact on ProjectWise managed workspace CSB's? Will MicroStation users experience anything in the interface that says "WorkSpace" or "WorkSet" when working in the ProjectWise CONNECT environment?
I've upgraded my PW Client to 10.00.03.140 and still having the same issue. Does this also require a server upgrade?
We have gotten managed workspaces to function properly with the loading of the dgnws all in ProjectWise. To do this, we have stood up a CONNECT ProjectWise server to support fully managed workspaces, PWDI 3.49 and MicroStation CE U10. The workset.cfg currently is stored at the root of our active projects/worksets folder and the dgnws is located in the project. We have not taken a second look at relocation if the workset.cfg but at the time we were unable to load it from a different location. The dgnws however has to be created locally and then imported into ProjectWise as it is not branding it to the project when it is created. Bentley has not resolved this issue that I am aware of.
Setting everything up on our end so far has been quite the challenge as well as a loss of flexibility compared to V8i. But we do have it up and running with the Client workspaces located on the server at the Organization level, and the workset/project loading from inside of ProjectWise. We have bypassed the Workspaces level since it required a much more stringent workspace environment and folder structure. Greg, Bentley sent us an unofficial document on setting up managed configurations with only worksets in ProjectWise. It allowed us to maintain most of our flexibility and folder structure.
Currently, we have V8i tools and MicroStation CE, AECOsim CE and OpenRoads Designer CE up and running in a managed structure in ProjectWise.
We are running into the same issue now at our organization. Is there any official or "unofficial" documentation on how to setup CE projects with worksets to work with ProjectWise?
Here is the O\official configuration setup guide: https://docs.bentley.com/LiveContent/web/ProjectWise%20Managed%20Configuration%20Setup%20Guide-v1/en/GUID-94B9DA14-6B62-44E0-8778-716B16838208.html
Be sure to read the Limitations section under Before you Begin. You MUST have your Workspace and Workset cfg files in ProjectWise. We create a Workset folder under each project to store the matching workset cfg file and the .wsdgn file. The workset cfg file name should match the Project name assigned in PW as outlined in that document. The workset file in PW doesn't have set any configs if you're using a CSB to set things. The file just has to exist for things to work. We keep our workspace cfg files outside of the project folder structure in a normal folder and that works fine. Just depends on how you're organizing things.