Community Tip - Visit the PTCooler (the community lounge) to get to know your fellow community members and check out some of Dale's Friday Humor posts! X
I thought I saw a thread on here about allowing a user to act as a Principal Administrator without making them an Org/Site Admin? If you've done this can you explain how?
Thanks,
Steve D.
Folks,
As Mike has already suggested you have to use a sub select to limit query returns to the latest version. Adding to the complexity this doesn’t necessarily work if you are using View versions on wtparts, if you are using views you will have to limit returns to just the view lineage you are interested in or perhaps add a Maximum sub-select on “last updated” if you just want the newest one. The query builder is also a little buggy when attempting to add criteria particularly in the sub-select, you have to add extra criteria then remove that before saving. Needless to say the sub select is expensive and I have had problems when using it with a large return.
The rest of this post is really just whining and in no way helps with your request…….
I feel the lack of a distinct “latestVersion” is one of the weakest areas in Windchill, it is a huge gap that continues to exist because it has always been there. I suspect that nearly every implementation wants customers of their data to only be able to access the latest Version and latest Iteration of an object when it is in certain states. Similarly they probably only want data authors to be able to modify the latest Version, same story when reporting on data, generally you are only interested in the latest version and iteration. It would be great to have some distinct criteria on the objects to allow reporting and access control rule creation.
Currently the only way I know of to achieve this is to put something in place to set the lifecycle state of earlier versions when a revision takes place and have access control rules on the state of the early versions as necessary. As far as I am aware there are no out of the box tools for doing even that, but that is something you typically only realise (with great disappointment) once you are well into your first deployment.
On a related pain point, to be able to modify name/descriptions held on an object master users have to be able to modify all versions. I don’t follow that “logic”, really if they can update the latest version it is desirable for them to be able to make edits to the name/description. Ideally I would prefer the name/description to be moved from the master to the version/iteration. Such a change could be used in conjunction with an extension to the Attribute master definition and some sort of “alternate language view version” to properly support alternate language views of parts which is another gap, particularly when using an ESI connection to an ERP system that supports a multi-language dataset.
-----
Lewis
In Reply to Mike Lockwood:
Below returns latest Iteration of each Revision.
Attached gives only latest Revision; needs latest Iteration also.
Greetings Steve,
Just wondering if you were able to get this to work?
I created a user, put them in as Org Admin, put them in a Profile that hid all the Org minor tabs, then gave a link to the Principle admin page. This all works, except the user is denied the ability to create a new user. Interestingly, the same user is able to create a new uservia the copy from another user(Similar User).
Any advice?
Cam