Community Tip - Did you get an answer that solved your problem? Please mark it as an Accepted Solution so others with the same problem can find the answer easily. X
Hi All,
Has anyone been able to implement versioning (i.e. Revision capability) in ProjectLink through a customization? Any other frustrated community members want to get together to share cost on getting this done?
PTC - any chance you're willing to look at the enhancement requests submitted on this issue?
Mike - with all due respect we'll have to agree to disagree on this one...
What we're trying to use Project for is "early real" where the majority of design iteration would occur. PDM side Change Management is somewhat stickier than Project side review andapprove mechanisms, and rightfully so. We've adopted a State-centric approach to"real" or not regardless of Context.
I do agree that at some point most data needs tobe sent to PDM assuming you're a design it and make it (or get someone to make it) company. I also suspect that I'm a bit more maniacal than most when it comes to revisions (Iuse them to "freeze" concepts).
Maybe there is some middle ground by making this behaviour a Site or Org level preference which would allow users to use ProjectLink in the way that best suits their business needs.
Does anyone use ProjectLink Routings? if so, how? Maybe this is the source of my confusion/frustration...
It would seem that ifyou can "Approve" something through aRouting, you might need also to "Approve" the something slightly different and be able to have a visible difference marker between the two. I have issues with the result in ProjectLink where you can have multiple "real" iterations of an object as a result of routings
What about deliverables and Action Items? being able tofreeze and force Revision would begreat friction for scope creep! Having a frozen action that is accepted by a resource would generate greater ownership and accountability within a Project Team.
Any good references on how to use ProjectLink effectively as intended? I'm having a hard time selling the benefits of ProjectLink to internal users. Why buy Project if you could just add a "Sandbox" State PDM side?
Control it via a Preference.
Win/Win
Hi,
Just found this thread while doing a search on the topic of supporting Revise in ProjectLink. It has been proposed as a new Idea on the PTC Windchill Community, but does not have a lot of traction, similar to this thread.
Curious how critical the ability to Revise an item in a Project is for people? If it is, what are the use cases and requirements you have? What types of items should be supported; documents, CAD, parts, all?
Personally, I would like to support it for items that originate in the Project only and their revision history would be lost if the item were "Sent to PDM" since it woudl be assigned a new lifecycle and revision scheme when created in PDM. I also like Joe's idea of controlling it via preference, but might need to be a configuration of the project like sharing to other projects and identifying out-of-date shared objects. The open issue is whether or not this could be changed once the project is created. It might need to be an initialzation option like linked deliverables and execution control that cannot be changed later.
Happy to hear any thoughts or ideas on this one.
-Scott
Hi,
I agree with Steve. I first believed it was fine not to be able to revise for the reasons Mike explained a few years ago in this post.
However, when using ProjectLink with external users such as customers or suppliers, Some of the documents could get approved/released for them to be able to know it is ready for them to do whatever they need. But if during the project we realise the document must be amended, then it gets tricky. of course PJL does offer versionning, so any change is still captured but it is not the same (I can still checked out an approved/released document in PJL). I could also set the state back to In Work but if a Route has been trigger, this mess up the states at least with 9.1. There is a fault there.
Anyway, I believed that with 10.1 or 10.2, one can now revised in PJL. We have 10.1 in production but have not had a chance to look at this yet.
In other words. While using PJL to support PDMLink to create new data, I believe revising is not really required, However, if we use PJL with people who do not have access to PDMLink, revising can help a lot.
My thoughts.
Best regards
Just added the request back to PTC. The last one was archived.
Again, I am resonating with those on this channel who are seeing value in the ability to revise from ProjectLink to PDM. I love the idea of sharing something released to a project and playing with some potential ideas without disturbing the released content. If the development is showing promise and we want to move that development to PDM, I wish I could create a revision in PDM and then share the project items back to PDM in the new revision. Obviously, the new items would have to go through an ECN to be released, but you could fully experiment without disturbing the released content till something looked viable.
I guess the idea is archived because your idea post does not include required information.
I saw it many times. If you do not provide this information in will be archived.
PetrH
1. What product and version are you running
2. What is the problem?
3. Are you using a workaround? If yes, please describe it.
4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.
5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)