We will be moving to Pro/Intralink 9.1 mid-year. One of the intriguing features is the portable workspace (PWS) functionality.
Has anyone tried PWS in 9.0/9.1? I'm interested in hearing about both positive and negative experiences.
We've got a project involving approx. 250 files and 250 MB of data that we would like to be able to send off-site as a portable workspace. * Any experience with this number of files or file size? * How does PWS handle Pro/E file versions when you save models / drawings (e.g. x.prt.1, x.prt.2, x.prt.3, etc.). * Are all incremental file versions stored in the PWS? * Any limitations to the PWS file size? * How well does the PWS integrate back into Commonspace? * Are all objects marked as modified, or only the ones that were intentionally changed?
We use it primarily as branching in Intralink 3.x allowed. We're looking forward to true branching in PDMLInk eventually.
Offline Workspaces work perfectly (as a workaround) to address this fundamental use case.
USE CASE - Rev B Released exists - There is a need to make an enhancement, but there is some conceptual development required, maybe involving multiple concepts. You don't want a Rev C to exist in commonspace during development, but the work will eventually result in Rev C. Due to use of top down design, family tables and other Pro/E tools, you pretty much need to do the conceptual work in a PDMLink workspace, not stand-alone. - While doing the development, you need to make an unrelated small change to Rev C, then move on with the development work becoming Rev D eventually.
There are some major constraints and best practices needed to avoid problems. Leo/Frank - you may want to add to this...