Skip to main content
K
kpritchard1-Visitor
1-Visitor
March 9, 2011
Question

ProjectLink - Revision capability?

  • March 9, 2011
  • 14 replies
  • 3898 views

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?

14 replies

Show previous replies
S
SteveVinyard1-Visitor
1-Visitor
July 30, 2014
The release process isn't really functional as well. Sure you can route something in ProjectLink in order to collaborate effectively with them and other outside/internal parties but when you do a PDM Checkin...it just resets the LC state...no options there. I certainly don't want to do the general promotion process again (simplistic stuff) just to get it to released. I can't include the external entity in my Product Promotion either as I don't want to give them any access to my Product. I'm hoping I'm missing something simple here though.





[cid:image001.gif@01CF7046.C96AB930]

Stephen Vinyard
Business Development Manager/Solution Architect
M
22-Sapphire I
MikeLockwood22-Sapphire I
22-Sapphire I
July 30, 2014
Using statebased versioning and a two phase lifecycle (numbered Revs, then Letter Rev's) solves a lot of the fundamental problem of allowing free development and then more formal production.

With a two phase lifecycle, while the object (always in PDM) is at a Numbered Rev, Engineers / Designers can have all the needed flexibility that Project provides, but with the advantage of normal Revision processes. A cardboard box of Rev 3 Parts is traceable to Rev 3. This requires setting up different transitions in the lifecycle for Numbered vs. Letter Rev's.

At some point each object is "A Released" and then much more formal change management can be used to go to Rev B, etc. This also aligns well with prototype vs. production tooling, production worker training, normal receiving inspection, etc.

S
SteveVinyard1-Visitor
1-Visitor
July 30, 2014
I'm good with that Mike, its more related to the external entities. They never get access into PDMLink...only ProjectLink. Still need an easy way to get stuff generally released with the external entities input/work etc AND then maintain that released nature (maybe not fully released) when pushing into PDMLink. People get frustrated with having to do a "double released" for some basic stuff that was done and vetted in ProjectLink.



[cid:image001.gif@01CF7046.C96AB930]

Stephen Vinyard
Business Development Manager/Solution Architect
C
cc-21-Visitor
1-Visitor
August 6, 2014

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

    M
    MGleason_198310-Marble
    10-Marble
    October 15, 2023

    Vote here...

    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. 

      HelesicPetr
      22-Sapphire II
      HelesicPetr22-Sapphire II
      22-Sapphire II
      October 16, 2023

      Hi @MGleason_1983 

      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.)

      Terms & ConditionsAccessibility statement