The layout of a Windchill package (9.1) is confusing to users, especially those who don't use Windchill or Pro/E.
Right now there are 3 views (all, product structure and models). At a minimum there should be a document list option.
It would also be nice if the product structure showed the models and documents underneith in one view.
The package should be a single file, open and run file (much like CreoView PVZ, or Adobe portfolio).
Users have problems unzipping all the files to a location and then locating the index.html and then browsing through the files to find what they need.
CreoView viewables won't even open directly if you have java installed as they are defaulted to .jar files in 9.1 (I think this is fixed in 10?)
We currently use packages for Design Reviews. They help collect the information into one place and allow us to export it for users external to our network.
Overall packages should be easy to comprehend and use for the average office user.
We're on 10.2. They fixed the JAR file issue though they took away "collections" and created the managed collection object outside of projects.
So now you can't have the last column that says which collection the object belonged to. This was a nice feature that allowed you to separate data. For example our groups used to have "Review" and "Reference" data so people knew which items needed review for release. The format is still confusing to those that don't have a lot of exposure to it. They muddle through but so many still unzip the package and try to find the documents they're looking for in the folders. We've even had to go so far as extracting published PDF's out of the PVZ files for some people.
Sort of a side note but interesting functionality as it relates to packages:
There is a functionality that isn't talked about much, and I'm not sure if it's still there today but it was documented here for Windchill 7.0 to include described by and reference documents as part of your product structure when opened in ProductView. I'm assuming it either stores them in the PVZ or as a link.
Same need with windchil 11.1, it would be great to improve possibilities of this offline viewer.
In our case it's a good way to exchange CAD with clients but we can't share custom attributes or quantity etc...
At a customer, we had to write some customization to show the CAD documents and documents inside the part structure view and to show more OOTB attributes/custom attributes inside the HTML file. It would be great if the OOTB possibilities were better to be able to decustomize that!
Change Notice exported in Package viewed offline also do not show relationship with affected and resulting objects
Could you share some inside what to look at, to customize the offline viewer in a similar way you have done?
@aacciano3: I wasn't involved technically, you can try to contact the technical architect who took care of that back then, Marcin Trojanowski: email@example.com .
I will share a project I did some time back to help users with Packages. I don't have access to it anymore, so don't ask for code. I created a Visual Basic or Powershell script that would essentially strip out all the PDFs from within the PVZ viewables in the zipped package and stick them in a separate folder. So those who wanted to look at the 2D drawings could, in standard Windows(or Mac) fashion, without having to deal with Creo View. Was definitely a shortcut process, but helped a lot of people who were new to Windchill/Creo/Packages...
Wow, here's a 10 year old request that could use some votes or updates. Windchill Packages are a critical component of sharing data with external suppliers and it could definitely use some updates. I agree with all the suggestions for the offline viewer. Sharing the Product Structure with all its associated links is a critical component and should be accompanied by some way to allow the recipient to use the data such as CSV or XLS. It would also be nice if the offline viewer was created when no PTC source documents are in the package. If I Lock a package with specific file extensions such as STP, PDF, CSV, etc. the offline view folder is created as a 0 file instead of a folder with content the index.html can reference.
It seems that because Packages was originally developed for data from Windchill A >> Windchill B, ongoing, it's is quite a lot more complex than needed for simply outputting data from Windchill A to be used outside any Windchill system.
There seems to be a great desire for providing needed sets of data to external parties - maybe a standalone approach that is not burdened by the complexities of bringing into Windchill system B.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.