Community Tip - When posting, your subject should be specific and summarize your question. Here are some additional tips on asking a great question. X
If the user doesn't have at least Read permission, there is no other way for him to know that file already exists. That's what the Read permission does: allow users like him to at least know the file exists. While Read & Download are used together quite often (IME), the separation should allow permission to at least search if the file exists if the intent is to prohibit that user from downloading it to a workspace and seeing/using it.
If that user should be able to both see and download/use the file, then it's a policy problem.
You are in the same situation when a CADuser has uploaded a new CADdocument. Since it's not checked in yet, never, it's not accessible by other users. But the identity is already reserved for that CADdocument, so someone else can't use it anymore. Only the org administrator can help you out, here.
Regards and enjoy your weekend, Hugo.
<< ProE WF5 - PDMLink 10.1 M040>>
As Org Admin (probably Site Admin, too) I can see any objects created by any user even if it hasn't yet been checked in, with a basic search. This may require them to be uploaded (which we do automatically).
I'm not sure if it's possible to set it up for an account with less permissions, such as a product manager. Probably just a matter of finding the right policy settings.
In Reply to Ben Bailey:
So, just to add to this, for the programming gurus here: Is there an API
call or algorithm that can be used to identify when a given object exists
in a Private Access Product?
This is causing some major grief.
Benjamin A Bailey
Department Manager
Information Technology
Engineering Data Systems/PDM
Missile Systems
Raytheon Company
Right after posting I remembered we also have this set up (see attached).
I'm not sure if would even see objects in restricted/private contexts, but it's worth bringing up in case prmpts someone else's memory.
(Now, if only I could remember where that setting is at...)
In Reply to Antonio Villanueva:
Thanks for the replies. Yes, you have described my issue correctly. If we had users check a different method, then they could avoid wasting time. Another thing we could do is ask that they create a CAD Document first in workspace before just creating model in Creo and saving. That should indicate if item exists or not.
One of the simplest way is to define the Report for EPMDoocument (limited columns/data) with bypass acess control and exposed report to Users Home tab.
By running this report, user can easily find out if CAD of same number/file name already exists (location/container) in Windchill or not
Issue I see with such report is that User can generate report without giving any criteria or value. In such case windchill will retrive all data.
Regards,
Avinash